From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Alexandre Courbot <gnurou@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Benoit Parrot <bparrot@ti.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/7] ARM: shmobile: Move gpio ranges from C code to DT
Date: Thu, 16 Jul 2015 11:06:06 +0200 [thread overview]
Message-ID: <CAMuHMdVvaFN_zQCcAog2akUJNxCZ2RzdENvmMqk2G33jb=0sWQ@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdYFE1xDV75_ecR36OTePPm8Ta_O1G1fSqOHO=s4TQw20A@mail.gmail.com>
Hi Linus,
On Thu, Jul 16, 2015 at 11:00 AM, Linus Walleij
<linus.walleij@linaro.org> wrote:
> On Tue, Jun 30, 2015 at 9:45 AM, Geert Uytterhoeven
> <geert+renesas@glider.be> wrote:
>> This patch series moves the setup of the GPIO-PFC pin mapping for
>> Renesas PFC/GPIO combos from C code to DT, and does some cleanups.
>> The move to DT is needed to make the GPIO hogging mechanism work, cfr.
>> the discussion following "[PATCH] [RFC] gpio: Retry deferred GPIO
>> hogging on pin range change" (https://lkml.org/lkml/2015/6/16/455).
>>
>> The series consists of 3 parts:
>> a. Patches 1-3 add the missing "gpio-ranges" properties to the dtsi
>> files for all affected SoCs,
>> b. Patch 4 disables the C code to set up the mapping on DT platforms
>> (it's still needed on SH or ARM-legacy),
>> c. Patches 5-7 do a few more cleanups in the sh-pfc gpio code.
>>
>> Dependencies:
>> - This series applies against next-next-20150630.
>> - Part a must go in first, to avoid regressions.
>> In addition, it's a prerequisite for "ARM: shmobile: armadillo800eva
>> dts: Add pinctrl and gpio-hog for lcdc0", which has been queued up
>> already in Simon's dt-for-v4.3 branch. Perhaps it can still be
>> reordered?
>> - While I didn't notice any bad behavior by having part a only, part b
>> should go in immediately after part a. Hence I think it's best if
>> Simon can take this one, too.
>> - Part c is independent (it doesn't touch the same code), so it can go
>> in before or after the other parts, or in parallel.
>>
>> Thanks for applying!
>>
>> Geert Uytterhoeven (7):
>> ARM: shmobile: r8a73a4 dtsi: Add missing "gpio-ranges" to gpio node
>> ARM: shmobile: r8a7740 dtsi: Add missing "gpio-ranges" to gpio node
>> ARM: shmobile: sh73a0 dtsi: Add missing "gpio-ranges" to gpio node
>> pinctrl: sh-pfc: Stop calling gpiochip_add_pin_range() on DT platforms
>> pinctrl: sh-pfc: Remove empty gpio_function_free()
>> pinctrl: sh-pfc: Move sh_pfc_add_gpiochip() up
>> pinctrl: sh-pfc: Confine legacy function GPIOs to SH
>
> I'm happy of shmobile people are happy.
Laurent was mostly worried about the phandle in the "gpio-ranges" property
pointing to the gpio/pfc combo node itself. Do you see any issues with that?
As there were comments on some of the patches, I have to resend this
series anyway...
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2015-07-16 9:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 7:45 [PATCH 0/7] ARM: shmobile: Move gpio ranges from C code to DT Geert Uytterhoeven
2015-06-30 7:45 ` [PATCH 1/7] ARM: shmobile: r8a73a4 dtsi: Add missing "gpio-ranges" to gpio node Geert Uytterhoeven
2015-06-30 9:49 ` Laurent Pinchart
2015-07-14 12:05 ` Geert Uytterhoeven
2015-07-16 9:42 ` Linus Walleij
2015-06-30 7:45 ` [PATCH 2/7] ARM: shmobile: r8a7740 " Geert Uytterhoeven
2015-06-30 9:41 ` Laurent Pinchart
2015-06-30 7:45 ` [PATCH 3/7] ARM: shmobile: sh73a0 " Geert Uytterhoeven
2015-06-30 9:48 ` Laurent Pinchart
2015-06-30 7:45 ` [PATCH 4/7] pinctrl: sh-pfc: Stop calling gpiochip_add_pin_range() on DT platforms Geert Uytterhoeven
2015-06-30 9:30 ` Laurent Pinchart
2015-06-30 9:44 ` Geert Uytterhoeven
2015-06-30 9:54 ` Laurent Pinchart
2015-06-30 7:45 ` [PATCH 5/7] pinctrl: sh-pfc: Remove empty gpio_function_free() Geert Uytterhoeven
2015-06-30 9:34 ` Laurent Pinchart
2015-06-30 7:45 ` [PATCH 6/7] pinctrl: sh-pfc: Move sh_pfc_add_gpiochip() up Geert Uytterhoeven
2015-06-30 9:35 ` Laurent Pinchart
2015-06-30 7:45 ` [PATCH 7/7] pinctrl: sh-pfc: Confine legacy function GPIOs to SH Geert Uytterhoeven
2015-06-30 9:38 ` Laurent Pinchart
2015-06-30 9:48 ` Geert Uytterhoeven
2015-07-16 9:00 ` [PATCH 0/7] ARM: shmobile: Move gpio ranges from C code to DT Linus Walleij
2015-07-16 9:06 ` Geert Uytterhoeven [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='CAMuHMdVvaFN_zQCcAog2akUJNxCZ2RzdENvmMqk2G33jb=0sWQ@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=boris.brezillon@free-electrons.com \
--cc=bparrot@ti.com \
--cc=geert+renesas@glider.be \
--cc=gnurou@gmail.com \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=maxime.ripard@free-electrons.com \
/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).