Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752132AbbKXAMM (ORCPT ); Mon, 23 Nov 2015 19:12:12 -0500 Received: from mailout1.samsung.com ([203.254.224.24]:41427 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751812AbbKXALz (ORCPT ); Mon, 23 Nov 2015 19:11:55 -0500 X-AuditID: cbfee68f-f79666d0000076bb-77-5653ab4a825e Message-id: <5653AB49.3090901@samsung.com> Date: Tue, 24 Nov 2015 09:11:53 +0900 From: Jaehoon Chung User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-version: 1.0 To: Jorge Ramirez-Ortiz , Doug Anderson Cc: Ulf Hansson , Alim Akhtar , Sonny Rao , Andrew Bresticker , =?UTF-8?B?SGVpa28gU3TDvGJuZXI=?= , "linux-kernel@vger.kernel.org" , "linux-mmc@vger.kernel.org" Subject: Re: dw_mmc: HLE errors References: <56531E3B.6060601@linaro.org> <56534CFA.7070403@linaro.org> In-reply-to: <56534CFA.7070403@linaro.org> Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrLIsWRmVeSWpSXmKPExsWyRsSkWNdrdXCYwYIDrBYr3/9ltHgwbxub xdllB9ks/j96zWpx/uY5FovLu+awWRz5389o8eTMTEaL42vDHTg9ZjdcZPG4c20Pm0ffllWM HtuvzWP2+LxJLoA1issmJTUnsyy1SN8ugSvj+NzXrAVXRSoOdf9hamBcKdDFyMkhIWAi8ffd D1YIW0ziwr31bF2MXBxCAisYJd7NaWaGKdpzdA0jRGIpo8T8+5ugnAeMEnd/fWEDqeIV0JJ4 9ekTWAeLgKrEsUXz2UFsNgEdie3fjjOB2KICYRIP1u1lhagXlPgx+R4LiC0ikCixYu9tVpCh zAKXmSSaJ+0CaxYWkJfY3L+aGWLbBEaJ10tWg23jBNr2tn8dkM0B1KEuMWVKLkiYGaR+zVuw egmBR+wSeydOZYG4SEDi2+RDLCD1EgKyEpsOQL0mKXFwxQ2WCYxis5DcNAth6iwkUxcwMq9i FE0tSC4oTkovMtYrTswtLs1L10vOz93ECIzF0/+e9e9gvHvA+hCjAAejEg/vjKLgMCHWxLLi ytxDjKZAR0xklhJNzgdGfF5JvKGxmZGFqYmpsZG5pZmSOO9CqZ/BQgLpiSWp2ampBalF8UWl OanFhxiZODilGhh7FkkYPJc7uenCb3tru+OeHG3PWjTezl7oUbT9v+Ct/vCwHZ1bXxbvPG+Z +DmC79n7VGXHYrEshz+1m6V2KcqFz43SYjCVXtHfNN/twqO7Ukc27LNp1lv4Xq/X9FKjp1/v xnUa6t9fzPCbWrX3oe/htXt3fc9STd9X3DirTuao9eugsCXCL4uUWIozEg21mIuKEwEOcesp wAIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrFIsWRmVeSWpSXmKPExsVy+t9jAV3P1cFhBne/2lisfP+X0eLBvG1s FmeXHWSz+P/oNavF+ZvnWCwu75rDZnHkfz+jxZMzMxktjq8Nd+D0mN1wkcXjzrU9bB59W1Yx emy/No/Z4/MmuQDWqAZGm4zUxJTUIoXUvOT8lMy8dFsl7+B453hTMwNDXUNLC3MlhbzE3FRb JRefAF23zBygg5QUyhJzSoFCAYnFxUr6dpgmhIa46VrANEbo+oYEwfUYGaCBhDWMGcfnvmYt uCpScaj7D1MD40qBLkZODgkBE4k9R9cwQthiEhfurWfrYuTiEBJYyigx//4mRgjnAaPE3V9f 2ECqeAW0JF59+sQMYrMIqEocWzSfHcRmE9CR2P7tOBOILSoQJvFg3V5WiHpBiR+T77GA2CIC iRIr9t5mBRnKLHCZSaJ50i6wZmEBeYnN/auZIbZNYJR4vWQ12DZOoG1v+9cB2RxAHeoSU6bk goSZQerXvGWewCgwC8mOWQhVs5BULWBkXsUokVqQXFCclJ5rlJdarlecmFtcmpeul5yfu4kR HO/PpHcwHt7lfohRgINRiYd3RlFwmBBrYllxZe4hRgkOZiURXs0lQCHelMTKqtSi/Pii0pzU 4kOMpsBAmMgsJZqcD0xFeSXxhsYmZkaWRuaGFkbG5krivBf2+4UJCaQnlqRmp6YWpBbB9DFx cEo1MB7lU82RCd0nl941I/NkYJXM8rT+d5vaVpvcrjlzYOaZlRd9L85d+O7N6+2cFVY2DqcD bbZPMZ/qn1z78Wv209O7f0nbTzs8p1xFlS3FddvVebVmvD837E+61spz4dbM3R+EI4NulcYF 5i7hFr9+3eiaX0ORavKFi/G/PELndFpOfv36RLxZ6EElluKMREMt5qLiRAAmK/ESDQMAAA== DLP-Filter: Pass X-MTR: 20000000000000000@CPGS X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2813 Lines: 82 Dear, Jorge. On 11/24/2015 02:29 AM, Jorge Ramirez-Ortiz wrote: > On 11/23/2015 11:57 AM, Doug Anderson wrote: >> Jorge, >> >> On Mon, Nov 23, 2015 at 6:10 AM, Jorge Ramirez-Ortiz >> wrote: >>> Doug/Jaehoon, >>> >>> Were there any follow ups to this thread [1] from March 30, 2015? >>> We are seeing HLE errors on 3.18 and we are trying to determine if a solution >>> was ever delivered. >>> On inspection, I can't find anything specific in recent kernels that address >>> this particular issue (was the actual root cause identified?) >>> >>> I put together a possible work-around that avoids the HLE storm from occurring >>> for this specific SoC [2]. >>> However we'd rather not merge this -or any other similar fix- if there is a >>> generic solution already that we can pick up from mainline. >> Nothing landed that I'm aware of. Are you on SDIO, SD or eMMC? >> Trying to do UHS? > > SD even without UHS (yet, that is coming now) If you want to use the upper mode than UHS-DDR50 for SD-card, you need to apply the below patch. https://patchwork.kernel.org/patch/7456121/ Actually, this is not relevant to HLE error. When sd-card is inserted/removed quickly, then sometime dwmmc controller is occurred the HLE error. (Now, i can't see HLE error.) So i had applied the some reset processing at my official repository.(It's not generic solution.) > >> >> I know that this patch mattered for me for UHS: >> >> 7c5209c315ea mmc: core: Increase delay for voltage to stabilize from >> 3.3V to 1.8V >> >> >> Also important for UHS (for at least some folks) were patches like: >> >> 9c85f37a2984 mmc: core: Add mmc_regulator_set_vqmmc() >> >> ...that attempted to get voltages more proper... > > ack > >> >> >> In the ChromeOS tree we did just land treating HLE errors as data and >> cmd errors . It's not >> wonderful but it's better than letting an interrupt go off forever... > > Yes I did try this patch on 3.18 but it didn't seem to be enough for us. > Even though it would prevent the interrupt storm from flooding the kernel, once > the event triggered and the interrupt was handled no more card > insertions/ejections would be detected. If HLE error will be reproduce with the generic sequence, I think we can find the generic solution. So could you explain to me in more detail? If i can reproduce with v3.18, i will try to test it. Your case will be helpful to me for solving the HLE error. Best Regards, Jaehoon Chung > > ok, thanks for the info! > > > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/