[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkda515hO6daP_4FZEXiGJTPHUaT1-ZLUW7sjVtR7-XjuZQ@mail.gmail.com>
Date: Tue, 3 Dec 2013 10:01:03 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Andersson, Björn
<Bjorn.Andersson@...ymobile.com>
Cc: Stephen Warren <swarren@...dotorg.org>,
Rob Herring <rob.herring@...xeda.com>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Rob Landley <rob@...dley.net>,
Grant Likely <grant.likely@...aro.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3] pinctrl: Add documentation for pinctrl-msm8x74
On Tue, Nov 26, 2013 at 1:52 AM, "Andersson, Björn"
<Bjorn.Andersson@...ymobile.com> wrote:
> On 11/25/13 4:14 PM, "Stephen Warren" <swarren@...dotorg.org> wrote:
>>> +Optional subnode-properties:
>>> +- qcom,function: A name of the function to be muxed to the specified
>>> + pins. Possible values are listed below.
>>
>>Are "pins" and "functions" generic enough now that they don't need a
>>vendor prefix? Both those property names are certainly mentioned in
>>pinctrl-bindings.txt.
>
> I've missed that these where in pinconf-generic. I based
> msm_dt_subnode_to_map
> on the tegra implementation and made changes to support pinconf-generic,
> which
> now seems identical with pinconf_generic_dt_subnode_to_map.
> I'll use that directly instead.
OK that's essentially one of my comments on patch 1/3 addressed,
so looking forward to see v2.
Yours,
Linus Walleij
--
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