[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <79ff44d2-c20d-2dc7-9a0a-d77fb00df46d@intel.com>
Date: Thu, 19 Jan 2017 12:43:01 +0200
From: Adrian Hunter <adrian.hunter@...el.com>
To: Ritesh Harjani <riteshh@...eaurora.org>,
Shawn Lin <shawn.lin@...k-chips.com>, ulf.hansson@...aro.org
Cc: linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, georgi.djakov@...aro.org,
asutoshd@...eaurora.org, stummala@...eaurora.org,
venkatg@...eaurora.org, pramod.gurav@...aro.org,
jeremymc@...hat.com
Subject: Re: [RESEND RFC 1/3] mmc: sdhci: Add platform_dumpregs callback
support to sdhci_ops.
On 18/01/17 09:57, Ritesh Harjani wrote:
> Hi Shawn,
>
> On 1/10/2017 2:45 PM, Shawn Lin wrote:
>> On 2017/1/10 14:41, Ritesh Harjani wrote:
>>> From: Sahitya Tummala <stummala@...eaurora.org>
>>>
>>> Add new host operation ->platform_dumpregs to provide a
>>> mechanism through which host drivers can dump platform
>>> specific registers in addition to SDHC registers
>>> during error conditions.
>>>
>>
>> Although we have been preventing from adding new callback
>> for sdhci core, this one makes sense as there are more and more
>> vendor registers outside the scope of SDHCI spec.
We are not prevented from adding new callbacks, but they have to represent
logical functions not quirks.
This patch seems fine to me except the name "platform_dumpregs" because
"platform" doesn't mean "platform" here. Just plain "dumpregs" is better.
Powered by blists - more mailing lists