>> The "status" here could be useful information about the status
>> register, which is not considered while printing errors by the "higher
>> levels". An option could be to print the error, but not when you
>> perform tuning.
>>
>> No big deal though, just a thought.
>
> Right, I could potentially
Seungwon / Ulf,
On Wed, Apr 23, 2014 at 1:17 AM, Ulf Hansson wrote:
> On 23 April 2014 01:51, Doug Anderson wrote:
>> Data errors are completely expected during tuning. Printing them out
>> is confusing people looking at the kernel logs. They see things like:
>>
>> [3.613296] dwmmc_exynos
On 23 April 2014 01:51, Doug Anderson wrote:
> Data errors are completely expected during tuning. Printing them out
> is confusing people looking at the kernel logs. They see things like:
>
> [3.613296] dwmmc_exynos 1220.dwmmc0: data error, status 0x0088
>
> ...and they think someth
On Wed, April 23, 2014, Doug Anderson wrote:
> Data errors are completely expected during tuning. Printing them out
> is confusing people looking at the kernel logs. They see things like:
>
> [3.613296] dwmmc_exynos 1220.dwmmc0: data error, status 0x0088
>
> ...and they think somet
Hi Doug,
On Wed, Apr 23, 2014 at 5:21 AM, Doug Anderson wrote:
> Data errors are completely expected during tuning. Printing them out
> is confusing people looking at the kernel logs. They see things like:
>
> [3.613296] dwmmc_exynos 1220.dwmmc0: data error, status 0x0088
>
> ...an
