[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1501291543030.16475@utopia.booyaka.com>
Date: Thu, 29 Jan 2015 15:45:38 +0000 (UTC)
From: Paul Walmsley <paul@...an.com>
To: Rob Herring <robherring2@...il.com>
cc: Mark Rutland <mark.rutland@....com>,
Alexandre Courbot <gnurou@...il.com>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Stephen Warren <swarren@...dotorg.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Thierry Reding <thierry.reding@...il.com>,
Kumar Gala <galak@...eaurora.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH 02/24] Documentation: DT bindings: add more chip compatible
strings for Tegra PCIe
Hi Rob
On Thu, 29 Jan 2015, Rob Herring wrote:
> On Wed, Jan 28, 2015 at 5:49 PM, Paul Walmsley <paul@...an.com> wrote:
> >
> > Add compatible strings for the PCIe IP blocks present on several Tegra
> > chips. The primary objective here is to avoid checkpatch warnings,
> > per:
> >
> > http://marc.info/?l=linux-tegra&m=142201349727836&w=2
> >
> > Signed-off-by: Paul Walmsley <paul@...an.com>
> > Cc: Thierry Reding <thierry.reding@...il.com>
> > Cc: Rob Herring <robh+dt@...nel.org>
> > Cc: Pawel Moll <pawel.moll@....com>
> > Cc: Mark Rutland <mark.rutland@....com>
> > Cc: Ian Campbell <ijc+devicetree@...lion.org.uk>
> > Cc: Kumar Gala <galak@...eaurora.org>
> > Cc: Stephen Warren <swarren@...dotorg.org>
> > Cc: Alexandre Courbot <gnurou@...il.com>
> > Cc: linux-tegra@...r.kernel.org
> > Cc: linux-pci@...r.kernel.org
> > Cc: devicetree@...r.kernel.org
> > Cc: linux-kernel@...r.kernel.org
> > ---
> > .../bindings/pci/nvidia,tegra20-pcie.txt | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt b/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
> > index d763e047c6ae..e772884f1c33 100644
> > --- a/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
> > +++ b/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
> > @@ -5,6 +5,8 @@ Required properties:
> > - "nvidia,tegra20-pcie"
> > - "nvidia,tegra30-pcie"
> > - "nvidia,tegra124-pcie"
> > + - "nvidia,tegra132-pcie" (not yet matched in the driver)
> > + - "nvidia,tegra210-pcie" (not yet matched in the driver)
>
> Whether the driver matches or not is irrelevant to the binding and may
> change over time. Does this mean the driver matches on something else
> or Tegra132 is not yet supported in the driver?
It means that the driver currently matches on one of the first three
strings that don't carry that annotation.
> If the former, what is important is what are the valid combinations of
> compatible properties and that is not captured here. In other words,
> what is the fallback compatible string for each chip?
The intention was to try to be helpful: to document that anyone adding a
"nvidia,tegra132-pcie" compatible string would also need to add one of the
other strings as a fallback. Would you like that to be documented in a
different way, or removed?
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists