From: Stephen Warren <swarren@wwwdotorg.org> To: Thierry Reding <thierry.reding@gmail.com>, Linus Walleij <linus.walleij@linaro.org> Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>, Mark Rutland <mark.rutland@arm.com>, Ian Campbell <ijc+devicetree@hellion.org.uk>, Kumar Gala <galak@codeaurora.org>, Andrew Bresticker <abrestic@chromium.org>, devicetree@vger.kernel.org, linux-tegra@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/4] of: Add NVIDIA Tegra XUSB pad controller binding Date: Thu, 05 Jun 2014 10:47:45 -0600 [thread overview] Message-ID: <53909F31.4050603@wwwdotorg.org> (raw) In-Reply-To: <1401894990-30092-2-git-send-email-thierry.reding@gmail.com> On 06/04/2014 09:16 AM, Thierry Reding wrote: > From: Thierry Reding <treding@nvidia.com> > > This patch adds the device tree binding documentation for the XUSB pad > controller found on NVIDIA Tegra SoCs. It exposes both pinmuxing and PHY > capabilities. > diff --git a/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt b/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt > +- #phy-cells: Should be 1. The specifier is the index of the PHY to reference. > + Possible values are: > + - 0: PCIe > + - 1: SATA Those values are defined in include/dt-bindings/pinctrl/pinctrl-tegra-xusb.h. I personally consider the <dt-bindings/> header files to be part of the binding itself, rather than being derived from the binding. As such, I'd suggest the following changes: * Make this patch 1 not patch 2 * Move pinctrl-tegra-xusb.h into this patch. * Remove the list of values above, and replace it with the text "See <dt-bindings/pinctrl/pinctrl-tegra-xusb.h> for the set of valid values". We'll need to make sure this patch is applied to a topic branch that can be merged into the pinctrl tree and the Tegra tree for 3.17, assuming that you'll be sending patches for 3.17 that use pinctrl-tegra-xusb.h. > +Example: > +======== > + > +SoC file extract: > +----------------- > + > + padctl@0,7009f000 { > + compatible = "nvidia,tegra124-xusb-padctl"; > + reg = <0x0 0x7009f000 0x0 0x1000>; > + resets = <&tegra_car 142>; > + reset-names = "padctl"; > + > + #address-cells = <0>; > + #size-cells = <0>; Why are those two properties required? Yes, this node has sub-nodes, but those sub-nodes don't have a reg property or unit address. The main Tegra pinctrl nodes don't have #address/size-cells. > +Board file extract: > +------------------- > + padctl: padctl@0,7009f000 { > + pinmux { > + pinctrl-0 = <&padctl_default>; > + pinctrl-names = "default"; Isn't there one extra level of nodes here. In the DT patches later in this series, pinctrl-0/pinctrl-names are directly inside the top-level padctl node.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 2/4] of: Add NVIDIA Tegra XUSB pad controller binding Date: Thu, 05 Jun 2014 10:47:45 -0600 [thread overview] Message-ID: <53909F31.4050603@wwwdotorg.org> (raw) In-Reply-To: <1401894990-30092-2-git-send-email-thierry.reding@gmail.com> On 06/04/2014 09:16 AM, Thierry Reding wrote: > From: Thierry Reding <treding@nvidia.com> > > This patch adds the device tree binding documentation for the XUSB pad > controller found on NVIDIA Tegra SoCs. It exposes both pinmuxing and PHY > capabilities. > diff --git a/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt b/Documentation/devicetree/bindings/pinctrl/nvidia,tegra124-xusb-padctl.txt > +- #phy-cells: Should be 1. The specifier is the index of the PHY to reference. > + Possible values are: > + - 0: PCIe > + - 1: SATA Those values are defined in include/dt-bindings/pinctrl/pinctrl-tegra-xusb.h. I personally consider the <dt-bindings/> header files to be part of the binding itself, rather than being derived from the binding. As such, I'd suggest the following changes: * Make this patch 1 not patch 2 * Move pinctrl-tegra-xusb.h into this patch. * Remove the list of values above, and replace it with the text "See <dt-bindings/pinctrl/pinctrl-tegra-xusb.h> for the set of valid values". We'll need to make sure this patch is applied to a topic branch that can be merged into the pinctrl tree and the Tegra tree for 3.17, assuming that you'll be sending patches for 3.17 that use pinctrl-tegra-xusb.h. > +Example: > +======== > + > +SoC file extract: > +----------------- > + > + padctl at 0,7009f000 { > + compatible = "nvidia,tegra124-xusb-padctl"; > + reg = <0x0 0x7009f000 0x0 0x1000>; > + resets = <&tegra_car 142>; > + reset-names = "padctl"; > + > + #address-cells = <0>; > + #size-cells = <0>; Why are those two properties required? Yes, this node has sub-nodes, but those sub-nodes don't have a reg property or unit address. The main Tegra pinctrl nodes don't have #address/size-cells. > +Board file extract: > +------------------- > + padctl: padctl at 0,7009f000 { > + pinmux { > + pinctrl-0 = <&padctl_default>; > + pinctrl-names = "default"; Isn't there one extra level of nodes here. In the DT patches later in this series, pinctrl-0/pinctrl-names are directly inside the top-level padctl node.
next prev parent reply other threads:[~2014-06-05 16:47 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-04 15:16 [PATCH 1/4] pinctrl: Add NVIDIA Tegra XUSB pad controller support Thierry Reding 2014-06-04 15:16 ` Thierry Reding 2014-06-04 15:16 ` [PATCH 2/4] of: Add NVIDIA Tegra XUSB pad controller binding Thierry Reding 2014-06-04 15:16 ` Thierry Reding 2014-06-04 15:16 ` Thierry Reding 2014-06-05 16:47 ` Stephen Warren [this message] 2014-06-05 16:47 ` Stephen Warren [not found] ` <53909F31.4050603-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> 2014-06-05 22:08 ` Thierry Reding 2014-06-05 22:08 ` Thierry Reding 2014-06-05 22:08 ` Thierry Reding 2014-06-05 22:57 ` Stephen Warren 2014-06-05 22:57 ` Stephen Warren 2014-06-05 22:57 ` Stephen Warren [not found] ` <5390F5C7.5070301-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> 2014-06-12 8:46 ` Linus Walleij 2014-06-12 8:46 ` Linus Walleij 2014-06-12 8:46 ` Linus Walleij 2014-06-04 15:16 ` [PATCH 3/4] ARM: tegra: tegra124: Add XUSB pad controller Thierry Reding 2014-06-04 15:16 ` Thierry Reding 2014-06-04 15:16 ` [PATCH 4/4] ARM: tegra: jetson-tk1: " Thierry Reding 2014-06-04 15:16 ` Thierry Reding 2014-06-05 17:08 ` [PATCH 1/4] pinctrl: Add NVIDIA Tegra XUSB pad controller support Stephen Warren 2014-06-05 17:08 ` Stephen Warren [not found] ` <5390A426.1050307-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org> 2014-06-05 22:09 ` Thierry Reding 2014-06-05 22:09 ` Thierry Reding 2014-06-05 22:09 ` Thierry Reding
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=53909F31.4050603@wwwdotorg.org \ --to=swarren@wwwdotorg.org \ --cc=abrestic@chromium.org \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=ijc+devicetree@hellion.org.uk \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-tegra@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=pawel.moll@arm.com \ --cc=robh+dt@kernel.org \ --cc=thierry.reding@gmail.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: linkBe 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.