From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: sunxi Ensure the correct pinctrl drivers are enabled
Date: Thu, 08 May 2014 16:35:29 +0200 [thread overview]
Message-ID: <536B9631.2090401@redhat.com> (raw)
In-Reply-To: <20140508142101.GT7047@lukather>
Hi,
On 05/08/2014 04:21 PM, Maxime Ripard wrote:
> Hi Hans,
>
> On Thu, May 08, 2014 at 03:36:56PM +0200, Hans de Goede wrote:
>> The commit titled: "pinctrl: sunxi: Introduce per-driver Kconfig options"
>> adds a bunch of new Kconfig options, but nothing sets them resulting in a
>> non working kernel. Since they are per sunxi family, and we already have
>> sunxi family Kconfig options, make those options select the necessary
>> Kconfig options.
>>
>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>> ---
>> arch/arm/mach-sunxi/Kconfig | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/mach-sunxi/Kconfig b/arch/arm/mach-sunxi/Kconfig
>> index 3aff966..beab32e 100644
>> --- a/arch/arm/mach-sunxi/Kconfig
>> +++ b/arch/arm/mach-sunxi/Kconfig
>> @@ -4,7 +4,6 @@ menuconfig ARCH_SUNXI
>> select CLKSRC_MMIO
>> select GENERIC_IRQ_CHIP
>> select PINCTRL
>> - select PINCTRL_SUNXI
>> select SUN4I_TIMER
>>
>> if ARCH_SUNXI
>> @@ -12,11 +11,14 @@ if ARCH_SUNXI
>> config MACH_SUN4I
>> bool "Allwinner A10 (sun4i) SoCs support"
>> default ARCH_SUNXI
>> + select PINCTRL_SUN4I_A10
>>
>> config MACH_SUN5I
>> bool "Allwinner A10s / A13 (sun5i) SoCs support"
>> default ARCH_SUNXI
>> select SUN5I_HSTIMER
>> + select PINCTRL_SUN5I_A10S
>> + select PINCTRL_SUN5I_A13
>>
>> config MACH_SUN6I
>> bool "Allwinner A31 (sun6i) SoCs support"
>> @@ -25,6 +27,7 @@ config MACH_SUN6I
>> select ARM_GIC
>> select RESET_CONTROLLER
>> select SUN5I_HSTIMER
>> + select PINCTRL_SUN6I_A31
>>
>> config MACH_SUN7I
>> bool "Allwinner A20 (sun7i) SoCs support"
>> @@ -33,5 +36,6 @@ config MACH_SUN7I
>> select ARM_PSCI
>> select HAVE_ARM_ARCH_TIMER
>> select SUN5I_HSTIMER
>> + select PINCTRL_SUN7I_A20
>>
>> endif
>
> I already posted a similar patch that is still pending. I was only
> waiting for Linus to merge the branch I gave him to merge it in my
> tree.
>
> http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/251704.html
>
> I don't think he actually merged the branch yet. How did you
> encounter such breakage?
I've been sucking up various branches and posted patches for the next
sunxi-devel, including your sunxi/pinctrl-for-3.16 branch.
Regards,
Hans
next prev parent reply other threads:[~2014-05-08 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 13:36 [PATCH] pinctrl: sunxi Ensure the correct pinctrl drivers are enabled Hans de Goede
2014-05-08 14:21 ` Maxime Ripard
2014-05-08 14:35 ` Hans de Goede [this message]
2014-05-08 15:36 ` Maxime Ripard
2014-05-08 21:56 ` Linus Walleij
2014-05-09 0:41 ` [linux-sunxi] " Maxime Ripard
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=536B9631.2090401@redhat.com \
--to=hdegoede@redhat.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).