From: jg1.han@samsung.com (Jingoo Han)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/3] PCI: imx6: Add support for i.MX6 PCIe controller
Date: Tue, 17 Sep 2013 07:53:19 +0900 [thread overview]
Message-ID: <003901ceb32f$89941060$9cbc3120$%han@samsung.com> (raw)
In-Reply-To: <20130916090146.GL31147@S2101-09.ap.freescale.net>
On Monday, September 16, 2013 6:02 PM, Shawn Guo wrote:
> On Mon, Sep 16, 2013 at 02:54:32PM +0800, Sean Cross wrote:
> > >>@@ -116,6 +116,22 @@
> > >> arm,data-latency = <4 2 3>;
> > >> };
> > >>+ pcie: pcie at 0x01000000 {
> > >>+ compatible = "fsl,imx6-pcie", "snps,dw-pcie";
> > >We generally use particular SoC name to specify the compatible string.
> > >So "fsl,imx6q-pcie" will be more appropriate.
> > Any reason to specify imx6q in particular? It's also present on the
> > imx6d, imx6dl, and imx6s (basically, everything but the imx6sl).
>
> The compatible naming is not about coverage but versioning. We
> generally encode the name of the SoC that firstly integrates the block
> to specify the version.
>
Yes, you're right. :-)
The name of the first SoC would be used.
Best regards,
Jingoo Han
next prev parent reply other threads:[~2013-09-16 22:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 9:40 [PATCH v4 0/3] Add PCIe support for i.MX6q Sean Cross
2013-09-13 9:40 ` [PATCH v4 1/3] ARM: imx: Add LVDS general-purpose clocks to i.MX6Q Sean Cross
2013-09-13 12:42 ` Shawn Guo
2013-09-13 9:40 ` [PATCH v4 2/3] ARM: imx6q: Add PCIe bits to GPR syscon definition Sean Cross
2013-09-13 12:45 ` Shawn Guo
2013-09-13 9:40 ` [PATCH v4 3/3] PCI: imx6: Add support for i.MX6 PCIe controller Sean Cross
2013-09-14 23:54 ` Bjorn Helgaas
[not found] ` <CAJ+vNU2GGfW0SQV1NnROMBtN5V_ANrjLJw2_+tWCRDsYG8BEeQ@mail.gmail.com>
2013-09-16 5:57 ` Sean Cross
2013-09-16 6:06 ` Shawn Guo
2013-09-16 6:54 ` Sean Cross
2013-09-16 9:01 ` Shawn Guo
2013-09-16 22:53 ` Jingoo Han [this message]
2013-09-16 6:22 ` Jingoo Han
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='003901ceb32f$89941060$9cbc3120$%han@samsung.com' \
--to=jg1.han@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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