linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Huang Changming-R66093 <r66093@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] DTS: fix the bug and add the chip compatible for eSDHC
Date: Wed, 4 Jan 2012 11:37:35 -0600	[thread overview]
Message-ID: <4F048E5F.1050509@freescale.com> (raw)
In-Reply-To: <8A2FC72B45BB5A4C9F801431E06AE48F1165E56C@039-SN1MPN1-005.039d.mgd.msft.net>

On 01/03/2012 09:11 PM, Huang Changming-R66093 wrote:
> 
> 
>> -----Original Message-----
>> From: Wood Scott-B07421
>> Sent: Tuesday, January 03, 2012 2:28 AM
>> To: Huang Changming-R66093
>> Cc: linuxppc-dev@lists.ozlabs.org; Huang Changming-R66093
>> Subject: Re: [PATCH] DTS: fix the bug and add the chip compatible for
>> eSDHC
>>
>> On 12/23/2011 12:10 AM, r66093@freescale.com wrote:
>>> From: Jerry Huang <Chang-Ming.Huang@freescale.com>
>>>
>>> Accordint to latest kernel, the auto-cmd12 property should be
>>> "sdhci,auto-cmd12", and according to the SDHC binding and the
>>> workaround for the special chip, add the chip compatible for eSDHC:
>>> "fsl,p1022-esdhc", "fsl,mpc8536-esdhc", "fsl,p2020-esdhc" and
>> "fsl,p1010-esdhc".
>>>
>>> Signed-off-by: Jerry Huang <Chang-Ming.Huang@freescale.com>
>>> ---
>>>  arch/powerpc/boot/dts/fsl/mpc8536si-post.dtsi |    4 ++++
>>>  arch/powerpc/boot/dts/fsl/p1010si-post.dtsi   |    3 ++-
>>>  arch/powerpc/boot/dts/fsl/p1022si-post.dtsi   |    3 ++-
>>>  arch/powerpc/boot/dts/fsl/p2020si-post.dtsi   |    4 ++++
>>>  4 files changed, 12 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/arch/powerpc/boot/dts/fsl/mpc8536si-post.dtsi
>>> b/arch/powerpc/boot/dts/fsl/mpc8536si-post.dtsi
>>> index 89af626..44e0ed9 100644
>>> --- a/arch/powerpc/boot/dts/fsl/mpc8536si-post.dtsi
>>> +++ b/arch/powerpc/boot/dts/fsl/mpc8536si-post.dtsi
>>> @@ -236,6 +236,10 @@
>>>  	};
>>>
>>>  /include/ "pq3-esdhc-0.dtsi"
>>> +	sdhc@2e000 {
>>> +		compatible = "fsl,esdhc", "fsl,mpc8536-esdhc";
>>> +	};
>>
>> More-specific compatible entries should come first.
> 
> I don't understand you, why more-specific compatible entries should come?

Because the binding says so, as do ePAPR and the IEEE1275 generic names
recommendation.  It is relied on by some OS driver binding mechanisms to
resolve ambiguity in the event that drivers are present for both strings.

> The Documentation/devicetree/bindings/mmc/fsl-esdhc.txt has introduced it:
>   - compatible : should be
>     "fsl,<chip>-esdhc", "fsl,esdhc"
> I don't think I should introduce new entries.
> 

I'm not asking you to introduce a new entry.  I'm asking you to reverse
them as the above text specifies:

	compatible = "fsl,mpc8536-esdhc", "fsl,esdhc";

not:

	compatible = "fsl,esdhc", "fsl,mpc8536-esdhc";

-Scott

  reply	other threads:[~2012-01-04 17:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23  6:10 [PATCH] DTS: fix the bug and add the chip compatible for eSDHC r66093
2012-01-02 18:27 ` Scott Wood
2012-01-04  3:11   ` Huang Changming-R66093
2012-01-04 17:37     ` Scott Wood [this message]
2012-01-02 20:30 ` Tabi Timur-B04825
2012-01-04  3:14   ` Huang Changming-R66093
2012-01-04 19:19     ` Scott Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F048E5F.1050509@freescale.com \
    --to=scottwood@freescale.com \
    --cc=B07421@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=r66093@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).