From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/7] pinctrl: berlin: add the core pinctrl driver for Marvell Berlin SoCs
Date: Fri, 23 May 2014 01:02:32 +0200 [thread overview]
Message-ID: <537E8208.6080308@gmail.com> (raw)
In-Reply-To: <CACRpkdbbyfPqFP=-+gO8TmOXSgovjkR_e=N57Xmj-N8jptOzVQ@mail.gmail.com>
On 05/22/2014 11:59 PM, Linus Walleij wrote:
> On Sat, May 17, 2014 at 12:08 PM, Sebastian Hesselbarth
> <sebastian.hesselbarth@gmail.com> wrote:
>
>> thinking of your request to make "function"/"groups" standard
>> properties, I guess you also had some corresponding helpers in
>> mind.
>
> Yeah :-)
>
>> Looking at the map and free functions here, I can see no Berlin
>> specific code at all. One option would be to make those functions
>> a standard callback for .dt_node_to_map and .dt_free_map, i.e.
>> pinctrl_utils_function_group_dt_node_to_map.
>>
>> IMHO, the more flexible option would be to rather have
>>
>> of_pinctrl_utils_read_function(node, &function_name, &ngroups)
>> and
>> of_pinctrl_for_each_function_group(node, group_name)
>> swallowing the property names and reuse it like below.
>>
>> The simple option would be to just remove the marvell, prefix
>> now and have a closer look at other pinctrl drivers to see what
>> will be required, of course.
>>
>> Do you have any preference?
>
> I would prefer a two-stage rocket, one removing the Marvell prefix
> and another bringing the helpers into pinctrl-utils.
You already the first stage some mails further down in your inbox.
> Do I hear a patch coming? :-)
Yes, but given the late time in v3.15 now and lack of time, I postpone
it to somewhere in v3.16.
Sebastian
next prev parent reply other threads:[~2014-05-22 23:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 5:27 [PATCH v3 0/7] ARM: berlin: add pinctrl support Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 1/7] pinctrl: berlin: add the core pinctrl driver for Marvell Berlin SoCs Antoine Ténart
2014-05-17 10:08 ` Sebastian Hesselbarth
2014-05-22 21:59 ` Linus Walleij
2014-05-22 23:02 ` Sebastian Hesselbarth [this message]
2014-05-05 5:27 ` [PATCH v3 2/7] pinctrl: berlin: add the BG2Q pinctrl driver Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 3/7] pinctrl: berlin: add the BG2 " Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 4/7] pinctrl: berlin: add the BG2CD " Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 5/7] ARM: berlin: add the pinctrl dependency for the Marvell Berlin SoCs Antoine Ténart
2014-05-05 5:27 ` [PATCH v3 6/7] Documentation: add the Marvell Berlin pinctrl documentation Antoine Ténart
2014-05-16 13:35 ` Linus Walleij
2014-05-16 16:47 ` Antoine Ténart
2014-05-22 21:56 ` Linus Walleij
2014-05-05 5:27 ` [PATCH v3 7/7] ARM: dts: berlin: add the pinctrl node and muxing setup for uarts Antoine Ténart
2014-05-16 12:43 ` [PATCH v3 0/7] ARM: berlin: add pinctrl support Linus Walleij
2014-05-18 21:10 ` Sebastian Hesselbarth
2014-05-22 22:03 ` Linus Walleij
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=537E8208.6080308@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--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).