From: briannorris@chromium.org (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ARM: dts: rockchip: add veyron-jaq board
Date: Mon, 24 Aug 2015 11:06:23 -0700 [thread overview]
Message-ID: <20150824180623.GA84867@google.com> (raw)
In-Reply-To: <CABxcv=nXwL6LV0vnjffA0JV4NB-_mCufe3-0c7fsRKW3DE+-_g@mail.gmail.com>
On Mon, Aug 24, 2015 at 08:01:29PM +0200, Javier Martinez Canillas wrote:
> On Mon, Aug 24, 2015 at 7:58 PM, Heiko Stuebner <heiko@sntech.de> wrote:
> > Am Montag, 24. August 2015, 10:53:15 schrieb Brian Norris:
> >> On Thu, Aug 20, 2015 at 01:29:40AM +0200, Javier Martinez Canillas wrote:
> >> > [...]
> >> >
> >> > > +
> >> > > +&rk808 {
> >> > > + pinctrl-names = "default";
> >> > > + pinctrl-0 = <&pmic_int_l &dvs_1 &dvs_2>;
> >> > > + dvs-gpios = <&gpio7 12 GPIO_ACTIVE_HIGH>,
> >> > > + <&gpio7 15 GPIO_ACTIVE_HIGH>;
> >> >
> >> > I see the dvs-gpios DT property is documented in the downstream
> >> > ChromiumOS 3.18 tree [0] but I don't see it neither mentioned in
> >> > Documentation/devicetree/bindings/mfd/rk808.txt in mainline nor code
> >> > that parses it in the drivers/regulator/rk808-regulator.c driver.
> >>
> >> Good catch.
> >>
> >> > So I think this should be removed and also the dvs_{1,2} pinctrl
> >> > lines.
> >>
> >> OK, will do. I see that jerry, minnie, and speedy also have the pinctrl
> >> lines. Should they be killed as well?
> >
> > Personally I think the pinctrl settings can stay. Their configuration is part
> > of the hardware and not subject to the binding of the device using them.
> >
> > And of course, the change to support them is already pending, with the binding
> > itself already in the mfd tree.
> >
>
> I missed that the change to add support for this is already in the mfd tree.
Me too. So I'll leave all the dvs-* stuff as-is, then. This makes the
v2->v3 delta very small...
> >
> > So it doesn't matter to much if they're in there already or not, as we'll
> > hopefully soon make use of them anyway.
> >
>
> Agreed.
Brian
prev parent reply other threads:[~2015-08-24 18:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 22:18 [PATCH v2 1/3] ARM: dts: rockchip: add veyron-jaq board Brian Norris
2015-08-19 22:18 ` [PATCH v2 2/3] ARM: dts: rockchip: correct regulator PM properties Brian Norris
2015-08-19 23:35 ` Javier Martinez Canillas
2015-08-24 17:04 ` Heiko Stuebner
2015-08-19 22:18 ` [PATCH v2 3/3] ARM: dts: rockchip: correct regulator power states for suspend Brian Norris
2015-08-19 23:36 ` Javier Martinez Canillas
2015-08-24 17:04 ` Heiko Stuebner
[not found] ` <CAHNYxRzWHvy=mv+G6wwO29=9smOCwKh6gBPLbT-TNq0PmP2Xiw@mail.gmail.com>
2015-08-19 22:59 ` [PATCH v2 1/3] ARM: dts: rockchip: add veyron-jaq board Brian Norris
2015-08-19 23:29 ` Javier Martinez Canillas
2015-08-24 17:53 ` Brian Norris
2015-08-24 17:58 ` Heiko Stuebner
2015-08-24 18:01 ` Javier Martinez Canillas
2015-08-24 18:06 ` Brian Norris [this message]
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=20150824180623.GA84867@google.com \
--to=briannorris@chromium.org \
--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).