From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3 00/29] SH pinctrl and pinmux implementation
Date: Thu, 07 Mar 2013 23:39:37 +0000 [thread overview]
Message-ID: <7368388.U4RWszQhVD@avalon> (raw)
In-Reply-To: <1362574370-17889-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Linus,
On Thursday 07 March 2013 09:41:27 Linus Walleij wrote:
> On Wed, Mar 6, 2013 at 1:52 PM, Laurent Pinchart,
> > Here's the third version of the SuperH and SH Mobile pin controllers (PFC)
> > pinctrl and pinmux support patches. The patches have been rebased on top
> > of v3.9-rc1
>
> The series:
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> For the stuff I've not already ACKed.
Thank you.
> Basically I see two annoying things in this driver set that would be
> nice to have fixed:
>
> - Alter the pinctrl.c file to register the GPIO range from the gpiochip
> side of things, essentially taking out pinctrl_add_gpio_range() and
> use gpiochip_add_pin_range() from the gpio.c code instead.
OK, I'll do that for v4. Is pinctrl_add_gpio_range() getting deprecated ?
> - Change gpio.c to get rid of the complex code in sh_gpio_to_irq()
> by using irqdomain. It'll need a custom mapping function but that makes
> it simpler overall. Change all mappings between Linux and hardware
> irq numbers to use the irqdomain.
I plan to split the GPIO handling functions to a separate driver, I'll try to
address that then.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-03-07 23:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 12:52 [PATCH v3 00/29] SH pinctrl and pinmux implementation Laurent Pinchart
2013-03-07 8:41 ` Linus Walleij
2013-03-07 23:39 ` Laurent Pinchart [this message]
2013-03-08 2:07 ` 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=7368388.U4RWszQhVD@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.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