All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sharma Bhupesh <bhupesh.sharma@freescale.com>
To: Li Leo <LeoLi@freescale.com>, Arnd Bergmann <arnd@arndb.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	"Catalin.Marinas@arm.com" <Catalin.Marinas@arm.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"Lian M.H." <Minghuan.Lian@freescale.com>,
	"olof@lixom.net" <olof@lixom.net>,
	"bhupesh.linux@gmail.com" <bhupesh.linux@gmail.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v2 04/10] doc/bindings: Update PCIe devicetree binding documentation for LS2080A
Date: Wed, 9 Sep 2015 03:45:31 +0000	[thread overview]
Message-ID: <BY1PR0301MB130337BA5B78D1887FE1880C82520@BY1PR0301MB1303.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CADRPPNR-cSSQC5sLMmoqcxX46J6hdULa_V4v2BK7T8s8pcX0cg@mail.gmail.com>

> From: pku.leo@gmail.com [mailto:pku.leo@gmail.com]
> Sent: Wednesday, September 09, 2015 1:36 AM
> On Mon, Sep 7, 2015 at 6:32 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 04 September 2015 12:27:46 Bhupesh Sharma wrote:
> >> @@ -4,7 +4,8 @@ This PCIe host controller is based on the Synopsis
> >> Designware PCIe IP  and thus inherits all the common properties
> defined in designware-pcie.txt.
> >>
> >>  Required properties:
> >> -- compatible: should contain the platform identifier such as
> "fsl,ls1021a-pcie"
> >> +- compatible: should contain the platform identifier such as
> >> +"fsl,ls1021a-pcie",
> >> +  "fsl,ls2080a-pcie".
> >>  - reg: base addresses and lengths of the PCIe controller
> >>  - interrupts: A list of interrupt outputs of the controller. Must
> contain an
> >>    entry for each entry in the interrupt-names property.
> >>
> >
> > Are the two PCIe hosts mutually compatible? If they are, you should
> > mandate one of the strings as the base model for identification, with
> > the additional model being optional for identification of the specific
> SoC.
> 
> It seems that controllers on these chips are not exactly the same.
> They will get different driver data by matching the compatible strings.
> Probably we could define a more generic compatible string, such as
> "fsl,layerscape-pcie" or "fsl,ls-pcie".

Yes, Minghaun captured the differences in the two versions in the v1 review
discussion for the DTS here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-April/338343.html

Regards,
Bhupesh

WARNING: multiple messages have this Message-ID (diff)
From: Sharma Bhupesh <bhupesh.sharma@freescale.com>
To: Li Leo <LeoLi@freescale.com>, Arnd Bergmann <arnd@arndb.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	"Catalin.Marinas@arm.com" <Catalin.Marinas@arm.com>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"Lian M.H." <Minghuan.Lian@freescale.com>,
	"olof@lixom.net" <olof@lixom.net>,
	"bhupesh.linux@gmail.com" <bhupesh.linux@gmail.com>,
	"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v2 04/10] doc/bindings: Update PCIe devicetree binding documentation for LS2080A
Date: Wed, 9 Sep 2015 03:45:31 +0000	[thread overview]
Message-ID: <BY1PR0301MB130337BA5B78D1887FE1880C82520@BY1PR0301MB1303.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CADRPPNR-cSSQC5sLMmoqcxX46J6hdULa_V4v2BK7T8s8pcX0cg@mail.gmail.com>

> From: pku.leo@gmail.com [mailto:pku.leo@gmail.com]
> Sent: Wednesday, September 09, 2015 1:36 AM
> On Mon, Sep 7, 2015 at 6:32 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 04 September 2015 12:27:46 Bhupesh Sharma wrote:
> >> @@ -4,7 +4,8 @@ This PCIe host controller is based on the Synopsis
> >> Designware PCIe IP  and thus inherits all the common properties
> defined in designware-pcie.txt.
> >>
> >>  Required properties:
> >> -- compatible: should contain the platform identifier such as
> "fsl,ls1021a-pcie"
> >> +- compatible: should contain the platform identifier such as
> >> +"fsl,ls1021a-pcie",
> >> +  "fsl,ls2080a-pcie".
> >>  - reg: base addresses and lengths of the PCIe controller
> >>  - interrupts: A list of interrupt outputs of the controller. Must
> contain an
> >>    entry for each entry in the interrupt-names property.
> >>
> >
> > Are the two PCIe hosts mutually compatible? If they are, you should
> > mandate one of the strings as the base model for identification, with
> > the additional model being optional for identification of the specific
> SoC.
> 
> It seems that controllers on these chips are not exactly the same.
> They will get different driver data by matching the compatible strings.
> Probably we could define a more generic compatible string, such as
> "fsl,layerscape-pcie" or "fsl,ls-pcie".

Yes, Minghaun captured the differences in the two versions in the v1 review
discussion for the DTS here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-April/338343.html

Regards,
Bhupesh
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: bhupesh.sharma@freescale.com (Sharma Bhupesh)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 04/10] doc/bindings: Update PCIe devicetree binding documentation for LS2080A
Date: Wed, 9 Sep 2015 03:45:31 +0000	[thread overview]
Message-ID: <BY1PR0301MB130337BA5B78D1887FE1880C82520@BY1PR0301MB1303.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CADRPPNR-cSSQC5sLMmoqcxX46J6hdULa_V4v2BK7T8s8pcX0cg@mail.gmail.com>

> From: pku.leo at gmail.com [mailto:pku.leo at gmail.com]
> Sent: Wednesday, September 09, 2015 1:36 AM
> On Mon, Sep 7, 2015 at 6:32 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 04 September 2015 12:27:46 Bhupesh Sharma wrote:
> >> @@ -4,7 +4,8 @@ This PCIe host controller is based on the Synopsis
> >> Designware PCIe IP  and thus inherits all the common properties
> defined in designware-pcie.txt.
> >>
> >>  Required properties:
> >> -- compatible: should contain the platform identifier such as
> "fsl,ls1021a-pcie"
> >> +- compatible: should contain the platform identifier such as
> >> +"fsl,ls1021a-pcie",
> >> +  "fsl,ls2080a-pcie".
> >>  - reg: base addresses and lengths of the PCIe controller
> >>  - interrupts: A list of interrupt outputs of the controller. Must
> contain an
> >>    entry for each entry in the interrupt-names property.
> >>
> >
> > Are the two PCIe hosts mutually compatible? If they are, you should
> > mandate one of the strings as the base model for identification, with
> > the additional model being optional for identification of the specific
> SoC.
> 
> It seems that controllers on these chips are not exactly the same.
> They will get different driver data by matching the compatible strings.
> Probably we could define a more generic compatible string, such as
> "fsl,layerscape-pcie" or "fsl,ls-pcie".

Yes, Minghaun captured the differences in the two versions in the v1 review
discussion for the DTS here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-April/338343.html

Regards,
Bhupesh

  reply	other threads:[~2015-09-09  3:45 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04  6:57 [PATCH v2 00/10] ARM64: Update support for FSL's LS2085A SoC Bhupesh Sharma
2015-09-04  6:57 ` Bhupesh Sharma
2015-09-04  6:57 ` [PATCH v2 01/10] arm64: Use generic Layerscape SoC family naming & rename LS2085A to LS2080A Bhupesh Sharma
2015-09-04  6:57   ` Bhupesh Sharma
2015-09-04 16:31   ` Li Yang
2015-09-04 16:31     ` Li Yang
2015-09-04 20:10     ` Sharma Bhupesh
2015-09-04 20:10       ` Sharma Bhupesh
2015-09-08 20:24   ` Stuart Yoder
2015-09-08 20:24     ` Stuart Yoder
2015-09-09  3:54     ` Sharma Bhupesh
2015-09-09  3:54       ` Sharma Bhupesh
2015-09-04  6:57 ` [PATCH v2 02/10] Documentation: DT: Add entry for FSL LS2080A QDS and RDB boards Bhupesh Sharma
2015-09-04  6:57   ` Bhupesh Sharma
2015-09-04  6:57 ` [PATCH v2 03/10] Documentation/dts: Add bindings for QIXIS FPGA controller found on FSL boards Bhupesh Sharma
2015-09-04  6:57   ` Bhupesh Sharma
2015-09-04 16:56   ` Li Yang
2015-09-04 16:56     ` Li Yang
2015-09-04 20:16     ` Sharma Bhupesh
2015-09-04 20:16       ` Sharma Bhupesh
2015-09-04 20:16       ` Sharma Bhupesh
2015-09-04 21:12       ` Li Yang
2015-09-04 21:12         ` Li Yang
2015-09-04 21:12         ` Li Yang
2015-09-05  8:11         ` Sharma Bhupesh
2015-09-05  8:11           ` Sharma Bhupesh
2015-09-05  8:11           ` Sharma Bhupesh
     [not found]           ` <BY1PR0301MB130339BD3B988DC938AA524482560-M1kb196zaoqj58cWwZvmNZwN6zqB+hSMnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2015-09-09 23:38             ` Li Yang
2015-09-09 23:38               ` Li Yang
2015-09-09 23:38               ` Li Yang
2015-09-04  6:57 ` [PATCH v2 04/10] doc/bindings: Update PCIe devicetree binding documentation for LS2080A Bhupesh Sharma
2015-09-04  6:57   ` Bhupesh Sharma
2015-09-04 17:56   ` Leo Li
2015-09-04 17:56     ` Leo Li
2015-09-04 20:20     ` Sharma Bhupesh
2015-09-04 20:20       ` Sharma Bhupesh
2015-09-04 20:20       ` Sharma Bhupesh
2015-09-06  2:25       ` Lian M.H.
2015-09-06  2:25         ` Lian M.H.
2015-09-06  2:25         ` Lian M.H.
2015-09-06 20:00         ` Sharma Bhupesh
2015-09-06 20:00           ` Sharma Bhupesh
2015-09-06 20:00           ` Sharma Bhupesh
2015-09-07 11:32   ` Arnd Bergmann
2015-09-07 11:32     ` Arnd Bergmann
2015-09-08 20:06     ` Li Yang
2015-09-08 20:06       ` Li Yang
2015-09-08 20:06       ` Li Yang
2015-09-09  3:45       ` Sharma Bhupesh [this message]
2015-09-09  3:45         ` Sharma Bhupesh
2015-09-09  3:45         ` Sharma Bhupesh
2015-09-09  9:07       ` Arnd Bergmann
2015-09-09  9:07         ` Arnd Bergmann
2015-09-09  9:07         ` Arnd Bergmann
2015-09-09 23:50         ` Li Yang
2015-09-09 23:50           ` Li Yang
2015-09-09 23:50           ` Li Yang
2015-09-10  1:52           ` Lian M.H.
2015-09-10  1:52             ` Lian M.H.
2015-09-10  1:52             ` Lian M.H.
2015-09-04  6:57 ` [PATCH v2 05/10] doc/bindings: Update clk-qoriq bindings for FSL's chassis-3.0 SoCs Bhupesh Sharma
2015-09-04  6:57   ` Bhupesh Sharma
2015-09-09 16:46   ` Scott Wood
2015-09-09 16:46     ` Scott Wood
2015-09-04  6:57 ` [PATCH v2 06/10] clk: qoriq: Add ls2080a support Bhupesh Sharma
2015-09-04  6:57   ` Bhupesh Sharma
2015-09-04 20:01   ` Li Yang
2015-09-04 20:01     ` Li Yang
2015-09-04 20:09     ` Sharma Bhupesh
2015-09-04 20:09       ` Sharma Bhupesh
2015-09-04 21:06       ` Li Yang
2015-09-04 21:06         ` Li Yang
2015-09-09 16:41         ` Scott Wood
2015-09-09 16:41           ` Scott Wood
2015-09-09 16:39   ` Scott Wood
2015-09-09 16:39     ` 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=BY1PR0301MB130337BA5B78D1887FE1880C82520@BY1PR0301MB1303.namprd03.prod.outlook.com \
    --to=bhupesh.sharma@freescale.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=LeoLi@freescale.com \
    --cc=Minghuan.Lian@freescale.com \
    --cc=arnd@arndb.de \
    --cc=bhupesh.linux@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.