From: pku.leo@gmail.com (Leo Li)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 04/10] doc/bindings: Update PCIe devicetree binding documentation for LS2080A
Date: Fri, 4 Sep 2015 12:56:39 -0500 [thread overview]
Message-ID: <CADRPPNRGpzWawsqLHCiv530HbtPf+9RaPzOtvy88ftwv2ffqLQ@mail.gmail.com> (raw)
In-Reply-To: <1441349872-4560-5-git-send-email-bhupesh.sharma@freescale.com>
On Fri, Sep 4, 2015 at 1:57 AM, Bhupesh Sharma
<bhupesh.sharma@freescale.com> wrote:
> Add the documentation for compatible string "fsl,ls2080a-pcie"
> for Freescale's LS2080A platform.
>
> Signed-off-by: Minghuan Lian <Minghuan.Lian@freescale.com>
> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@freescale.com>
> ---
> .../devicetree/bindings/pci/layerscape-pci.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/layerscape-pci.txt b/Documentation/devicetree/bindings/pci/layerscape-pci.txt
> index 6286f04..e72e68f 100644
> --- a/Documentation/devicetree/bindings/pci/layerscape-pci.txt
> +++ b/Documentation/devicetree/bindings/pci/layerscape-pci.txt
> @@ -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".
Make it generic like "fsl,<chip>-pcie"
- Leo
next prev parent reply other threads:[~2015-09-04 17:56 UTC|newest]
Thread overview: 32+ 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 ` [PATCH v2 01/10] arm64: Use generic Layerscape SoC family naming & rename LS2085A to LS2080A Bhupesh Sharma
2015-09-04 16:31 ` Li Yang
2015-09-04 20:10 ` Sharma Bhupesh
2015-09-08 20:24 ` Stuart Yoder
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 ` [PATCH v2 03/10] Documentation/dts: Add bindings for QIXIS FPGA controller found on FSL boards Bhupesh Sharma
2015-09-04 16:56 ` Li Yang
2015-09-04 20:16 ` Sharma Bhupesh
2015-09-04 21:12 ` Li Yang
2015-09-05 8:11 ` Sharma Bhupesh
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 17:56 ` Leo Li [this message]
2015-09-04 20:20 ` Sharma Bhupesh
2015-09-06 2:25 ` Lian M.H.
2015-09-06 20:00 ` Sharma Bhupesh
2015-09-07 11:32 ` Arnd Bergmann
2015-09-08 20:06 ` Li Yang
2015-09-09 3:45 ` Sharma Bhupesh
2015-09-09 9:07 ` Arnd Bergmann
2015-09-09 23:50 ` Li Yang
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-09 16:46 ` Scott Wood
2015-09-04 6:57 ` [PATCH v2 06/10] clk: qoriq: Add ls2080a support Bhupesh Sharma
2015-09-04 20:01 ` Li Yang
2015-09-04 20:09 ` Sharma Bhupesh
2015-09-04 21:06 ` Li Yang
2015-09-09 16:41 ` 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=CADRPPNRGpzWawsqLHCiv530HbtPf+9RaPzOtvy88ftwv2ffqLQ@mail.gmail.com \
--to=pku.leo@gmail.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;
as well as URLs for NNTP newsgroup(s).