From: Li Yang <leoli-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Hu Vincent <Mingkai.Hu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
"Lian M.H."
<Minghuan.Lian-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: Re: [PATCH v2] dts/ls2080a: Update PCIe compatible
Date: Mon, 18 Jan 2016 16:09:22 +0800 [thread overview]
Message-ID: <CADRPPNSpf6--KFqaFD8AV8jyUCZ1eD=F2pipHz1_zaR16ec4_A@mail.gmail.com> (raw)
In-Reply-To: <BY2PR03MB3169DD34DF302BCF7A60FF284090-+7O3WWA3DPuCr+ldVt6je+O6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
On Mon, Dec 7, 2015 at 4:44 PM, Hu Vincent <Mingkai.Hu-KZfg59tc24xl57MIdRCFDg@public.gmane.org> wrote:
>
>
>> -----Original Message-----
>> From: Rob Herring [mailto:robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org]
>> Sent: Saturday, December 05, 2015 12:23 AM
>> To: Hu Mingkai-B21284
>> Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org; devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; Li Yang-Leo-R58472;
>> linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org; Lian Minghuan-B31939
>> Subject: Re: [PATCH v2] dts/ls2080a: Update PCIe compatible
>>
>> On Fri, Dec 04, 2015 at 06:20:17PM +0800, Mingkai Hu wrote:
>> > From: Minghuan Lian <Minghuan.Lian-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>> >
>> > The patch adds LS2085a to PCIe compatible to fix the compatibility
>> > issue when using firmware with LS2085a compatible property.
>> >
>> > Signed-off-by: Minghuan Lian <Minghuan.Lian-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>> > Signed-off-by: Mingkai Hu <Mingkai.Hu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>> > ---
>> > v2 change:
>> > - Rebased to latest kernel base
>>
>> How about implementing my comments on v1, too?
>>
>
> Hi Rob,
>
> Do you mean to change the combinations in layerscape-pci.txt as follows?
>
>> --- a/Documentation/devicetree/bindings/pci/layerscape-pci.txt
>> +++ b/Documentation/devicetree/bindings/pci/layerscape-pci.txt
>> @@ -15,6 +15,7 @@ Required properties:
>> - compatible: should contain the platform identifier such as:
>> "fsl,ls1021a-pcie", "snps,dw-pcie"
>> - "fsl,ls2080a-pcie", "snps,dw-pcie"
>> + "fsl,ls2080a-pcie", "fsl,ls2085a-pcie", "snps,dw-pcie"
>
>
> And the ls2085a was released first, but the dts file is for ls2080a (fsl-ls2080a.dtsi),
> So I prefer to put the ls2080a as the first compatible string. How about your suggestion?
I think this is what Rob suggested in v1 to make the combination in
document align with real dts. And it would be good to also have an
entry for ls2085: "fsl,ls2085a-pcie", "snps,dw-pcie". Can you send an
updated version?
Regards,
Leo
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-01-18 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 10:20 [PATCH v2] dts/ls2080a: Update PCIe compatible Mingkai Hu
[not found] ` <1449224417-20753-1-git-send-email-Mingkai.Hu-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-12-04 16:22 ` Rob Herring
2015-12-07 8:44 ` Hu Vincent
[not found] ` <BY2PR03MB3169DD34DF302BCF7A60FF284090-+7O3WWA3DPuCr+ldVt6je+O6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2016-01-18 8:09 ` Li Yang [this message]
2015-12-15 2:01 ` Hu Vincent
[not found] ` <BY2PR03MB3160E6BF80C63C5DF0AB91F84EE0-+7O3WWA3DPuCr+ldVt6je+O6mTEJWrR4XA4E9RH9d+qIuWR1G4zioA@public.gmane.org>
2015-12-15 2:02 ` Scott Wood
2015-12-15 2:05 ` Hu Vincent
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='CADRPPNSpf6--KFqaFD8AV8jyUCZ1eD=F2pipHz1_zaR16ec4_A@mail.gmail.com' \
--to=leoli-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=Minghuan.Lian-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=Mingkai.Hu-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/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).