mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Russell King <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] ARM: sa1100: Initialize gpio after gpio subsystem has been initialized
Date: Thu, 31 Mar 2016 09:21:16 -0700	[thread overview]
Message-ID: <20160331162116.GB5605@roeck-us.net> (raw)
In-Reply-To: <1459275349-11356-1-git-send-email-linux@roeck-us.net>

On Tue, Mar 29, 2016 at 11:15:49AM -0700, Guenter Roeck wrote:
> The sa1100 gpio driver was initialized from interrupt initialization code,
> which is earlier than the gpio subsystem is initialized. Since commit
> ff2b13592299 ("gpio: make the gpiochip a real device"), this is fatal
> and causes the system to crash.
> 
> The sa1100 gpio driver must be initialized prior to arch_initcall, since
> its gpio pins are used in arch_initcall code, but after the gpio subsystem
> is initialized (core_initcall). Initialize it with postcore_initcall.
> 
> Fixes: ff2b13592299 ("gpio: make the gpiochip a real device")
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>

Please ignore/drop this patch - a better (cleaner) fix is in the works
for gpiolib.

Thanks,
Guenter

> ---
> 
> Tested by building collie_defconfig and:
> 
> qemu-system-arm -M collie -kernel arch/arm/boot/zImage \
> 	-no-reboot -initrd busybox-armv4.cpio \
> 	--append "rdinit=/sbin/init console=ttySA1" -monitor null -nographic
> 
>  arch/arm/mach-sa1100/generic.c | 11 +++++++++--
>  1 file changed, 9 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm/mach-sa1100/generic.c b/arch/arm/mach-sa1100/generic.c
> index 345e63f4eb71..850aa7f8f649 100644
> --- a/arch/arm/mach-sa1100/generic.c
> +++ b/arch/arm/mach-sa1100/generic.c
> @@ -321,6 +321,15 @@ static int __init sa1100_init(void)
>  
>  arch_initcall(sa1100_init);
>  
> +static int __init sa1100_gpio_init(void)
> +{
> +	sa1100_init_gpio();
> +
> +	return 0;
> +}
> +
> +postcore_initcall(sa1100_gpio_init);
> +
>  void __init sa11x0_init_late(void)
>  {
>  	sa11x0_pm_init();
> @@ -386,8 +395,6 @@ void __init sa1100_init_irq(void)
>  	request_resource(&iomem_resource, &irq_resource);
>  
>  	sa11x0_init_irq_nodt(IRQ_GPIO0_SC, irq_resource.start);
> -
> -	sa1100_init_gpio();
>  }
>  
>  /*
> -- 
> 2.5.0
> 

  reply	other threads:[~2016-03-31 16:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 18:15 Guenter Roeck
2016-03-31 16:21 ` Guenter Roeck [this message]
2016-04-01  8:04   ` Linus Walleij
2016-04-01 14:02     ` Guenter Roeck
2016-04-03 16:35       ` 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=20160331162116.GB5605@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®