devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Dunn <mikedunn@newsguy.com>
To: linux-arm-kernel@lists.infradead.org
Cc: devicetree-discuss@lists.ozlabs.org, haojian.zhuang@linaro.org,
	linus.walleij@linaro.org
Subject: pxa27x and pinctrl-single
Date: Wed, 05 Jun 2013 10:23:16 -0700	[thread overview]
Message-ID: <51AF7404.3090003@newsguy.com> (raw)

Hi,

I'd like to start converting to device tree usage some of the old pxa27x
platforms I'm fond of, starting with adding pinctrl support.  If I'm not
mistaken, this will clear the way for some ongoing updates to the pinctrl/gpio
code used by newer Marvell arches.

I noticed that Haojian pulled the pinctrl-pxa driver from the kernel, in favor
of using pinctrl-single, so I turned my attention to that.  From what I can
tell, pinctrl-single is currently inadequate for pxa27x because:

(1) On the pxa27x, setting the mux for a pin involves configuring both the alt
function register *and* the direction register, requiring the ability to specify
in the device tree multiple reg/value pairs for each pin.

(2) Some of the pinctrl-single code still assumes one register-per-pin; see for
example the functions pcs_allocate_pin_table() and pcs_get_pin_by_offset().
Curiously, the recently added pcs_request_gpio() function also suffers from
this, unless I'm mistaken.

So I'm wondering if it's appropriate to patch pinctrl-single to make it suitable
for pxa27x, or should there be a separate driver for pxa27x?

Normally I'd just submit a patch for consideration, but I think that work is
ongoing, so maybe I better ask first in case other plans are in progress.  Plus
I'm new to pinctrl and device tree.  Any comments, suggestions, hints, etc
appreciated.

Thanks,
Mike

             reply	other threads:[~2013-06-05 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 17:23 Mike Dunn [this message]
     [not found] ` <51AF7404.3090003-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-06  0:43   ` pxa27x and pinctrl-single Haojian Zhuang
2013-06-06 17:33     ` Mike Dunn
     [not found]       ` <51B0C7E8.5090308-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-06 23:58         ` Haojian Zhuang
2013-06-07  0:48           ` Mike Dunn
     [not found]             ` <51B12DE9.9040908-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-07  1:21               ` Haojian Zhuang
2013-06-07 14:50                 ` Mike Dunn
     [not found]                   ` <51B1F330.9080007-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-07 15:16                     ` Haojian Zhuang
2013-06-07 17:41                       ` Mike Dunn
     [not found]                         ` <51B21B3B.8050604-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org>
2013-06-08  1:20                           ` Haojian Zhuang
2013-06-09 18:05                             ` Mike Dunn

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=51AF7404.3090003@newsguy.com \
    --to=mikedunn@newsguy.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=haojian.zhuang@linaro.org \
    --cc=linus.walleij@linaro.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).