[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160507114531.GI24250@axis.com>
Date: Sat, 7 May 2016 13:45:31 +0200
From: Jesper Nilsson <jesper.nilsson@...s.com>
To: Rob Herring <robh@...nel.org>
Cc: Niklas Cassel <niklass@...s.com>, jespern@...s.com,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
linux-arm-kernel@...s.com, linux-pci@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: pci: add DT binding for Axis ARTPEC-6
PCIe controller
On Thu, May 05, 2016 at 05:03:31PM -0500, Rob Herring wrote:
> On Wed, May 04, 2016 at 01:54:17PM +0200, Niklas Cassel wrote:
> > From: Niklas Cassel <niklas.cassel@...s.com>
> >
> > This commit adds the Device Tree binding documentation that allows to
> > describe the PCIe controller found in the Axis ARTPEC-6 SoC.
> >
> > Signed-off-by: Niklas Cassel <niklas.cassel@...s.com>
> > ---
> > .../devicetree/bindings/pci/axis,artpec6-pcie.txt | 45 ++++++++++++++++++++++
> > 1 file changed, 45 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/pci/axis,artpec6-pcie.txt
> >
> > diff --git a/Documentation/devicetree/bindings/pci/axis,artpec6-pcie.txt b/Documentation/devicetree/bindings/pci/axis,artpec6-pcie.txt
> > new file mode 100644
> > index 0000000..fdac2a2
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/pci/axis,artpec6-pcie.txt
> > @@ -0,0 +1,45 @@
> > +* Axis ARTPEC-6 PCIe interface
> > +
> > +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: "axis,artpec6-pcie", "snps,dw-pcie"
> > +- reg: base addresses and lengths of the pcie controller (DBI),
> > + the phy controller, and configuration address space.
> > +- reg-names: Must include the following entries:
> > + - "dbi"
> > + - "phy"
> > + - "config"
> > +- interrupts: A list of interrupt outputs of the controller. Must contain an
> > + entry for each entry in the interrupt-names property.
> > +- interrupt-names: Must include the following entries:
> > + - "msi": The interrupt that is asserted when an MSI is received
> > +- syscon: Should contain a link to the syscon device node.
>
> What is the syscon for? Perhaps a name that reflects the purpose.
It's the SoC System Controller, and holds some chip-specific registers
for the Synopsys IP control, clocks and some termination variables spring
to mind. It was named sysctrl earlier, although that's not very much more
descriptive.
> Rob
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@...s.com
Powered by blists - more mailing lists