From: Rajendra Nayak <rnayak@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] omap hsmmc init cleanup and section warning fixes for v3.4 merge window
Date: Thu, 16 Feb 2012 18:45:50 +0530 [thread overview]
Message-ID: <4F3D0186.2010500@ti.com> (raw)
In-Reply-To: <4F3CF7D1.8050807@ti.com>
On Thursday 16 February 2012 06:04 PM, Rajendra Nayak wrote:
>> Can you test something with these patches?
>>
>> 1. Build the gpio-twl4030.c as a module, but with HSMMC support built in
>> 2. Boot on the 4430SDP
>
> twl4030 gpio is used for card detect on OMAP3, so I tried this
> on my Beagle instead of 4430SDP.
> The kernel boots up but does not detect/enumerate the mmc card.
>
>> 3. Load the gpio-twl4030 module
>
> I was expecting this to now detect the card, but I instead got
> this error which seems to tell gpio-twl4030 has problems
> when built/used as a module, outside of the mmc issues.
Looks like I was mislead with the errors and though the twl4030
gpio probe was bailing out with errors, which its not.
It does seem to go ahead, does a mmc late init which registers
the mmc omap_device and hence does a platform_device_add, but the
device never seem to get probed. mmc driver is built in and
registered.
>
> # insmod gpio-twl4030.ko
> [ 16.217864] twl4030_gpio twl4030_gpio: can't dispatch IRQs from modules
> [ 16.242004] gpiochip_add: registered GPIOs 192 to 211 on device: twl4030
>
>
>> 4. Remove the gpio-twl4030 module
>> 5. Re-load the gpio-twl4030.ko module
>>
>> and report back what you get. Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: rnayak@ti.com (Rajendra Nayak)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] omap hsmmc init cleanup and section warning fixes for v3.4 merge window
Date: Thu, 16 Feb 2012 18:45:50 +0530 [thread overview]
Message-ID: <4F3D0186.2010500@ti.com> (raw)
In-Reply-To: <4F3CF7D1.8050807@ti.com>
On Thursday 16 February 2012 06:04 PM, Rajendra Nayak wrote:
>> Can you test something with these patches?
>>
>> 1. Build the gpio-twl4030.c as a module, but with HSMMC support built in
>> 2. Boot on the 4430SDP
>
> twl4030 gpio is used for card detect on OMAP3, so I tried this
> on my Beagle instead of 4430SDP.
> The kernel boots up but does not detect/enumerate the mmc card.
>
>> 3. Load the gpio-twl4030 module
>
> I was expecting this to now detect the card, but I instead got
> this error which seems to tell gpio-twl4030 has problems
> when built/used as a module, outside of the mmc issues.
Looks like I was mislead with the errors and though the twl4030
gpio probe was bailing out with errors, which its not.
It does seem to go ahead, does a mmc late init which registers
the mmc omap_device and hence does a platform_device_add, but the
device never seem to get probed. mmc driver is built in and
registered.
>
> # insmod gpio-twl4030.ko
> [ 16.217864] twl4030_gpio twl4030_gpio: can't dispatch IRQs from modules
> [ 16.242004] gpiochip_add: registered GPIOs 192 to 211 on device: twl4030
>
>
>> 4. Remove the gpio-twl4030 module
>> 5. Re-load the gpio-twl4030.ko module
>>
>> and report back what you get. Thanks.
next prev parent reply other threads:[~2012-02-16 13:15 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 18:28 [PATCH 0/3] omap hsmmc init cleanup and section warning fixes for v3.4 merge window Tony Lindgren
2012-02-15 18:28 ` Tony Lindgren
2012-02-15 18:28 ` [PATCH 1/3] ARM: OMAP: omap_device: Expose omap_device_{alloc, delete, register} Tony Lindgren
2012-02-15 18:28 ` Tony Lindgren
2012-02-15 18:28 ` [PATCH 2/3] ARM: OMAP2+: Split omap2_hsmmc_init() to properly support I2C GPIO pins Tony Lindgren
2012-02-15 18:28 ` Tony Lindgren
2012-02-16 10:03 ` Rajendra Nayak
2012-02-16 10:03 ` Rajendra Nayak
2012-02-16 10:13 ` Rajendra Nayak
2012-02-16 10:13 ` Rajendra Nayak
2012-02-16 16:35 ` Tony Lindgren
2012-02-16 16:35 ` Tony Lindgren
2012-02-16 16:46 ` Cousson, Benoit
2012-02-16 16:46 ` Cousson, Benoit
2012-02-16 16:51 ` Rajendra Nayak
2012-02-16 16:51 ` Rajendra Nayak
2012-02-16 17:06 ` Tony Lindgren
2012-02-16 17:06 ` Tony Lindgren
2012-02-17 18:10 ` Tony Lindgren
2012-02-17 18:10 ` Tony Lindgren
2012-02-16 16:45 ` Tony Lindgren
2012-02-16 16:45 ` Tony Lindgren
2012-02-17 19:05 ` Tony Lindgren
2012-02-17 19:05 ` Tony Lindgren
2012-02-15 18:28 ` [PATCH 3/3] ARM: OMAP2+: Mark omap_hsmmc_init and omap_mux related functions as __init Tony Lindgren
2012-02-15 18:28 ` Tony Lindgren
2012-02-16 10:11 ` Russell King - ARM Linux
2012-02-16 10:11 ` Russell King - ARM Linux
2012-02-16 16:41 ` Tony Lindgren
2012-02-16 16:41 ` Tony Lindgren
2012-02-17 19:17 ` Tony Lindgren
2012-02-17 19:17 ` Tony Lindgren
2012-02-16 12:00 ` [PATCH 0/3] omap hsmmc init cleanup and section warning fixes for v3.4 merge window Nayak, Rajendra
2012-02-16 12:00 ` Nayak, Rajendra
2012-02-16 12:12 ` Russell King - ARM Linux
2012-02-16 12:12 ` Russell King - ARM Linux
2012-02-16 12:34 ` Rajendra Nayak
2012-02-16 12:34 ` Rajendra Nayak
2012-02-16 13:15 ` Rajendra Nayak [this message]
2012-02-16 13:15 ` Rajendra Nayak
2012-02-16 13:51 ` Russell King - ARM Linux
2012-02-16 13:51 ` Russell King - ARM Linux
2012-02-17 9:14 ` Russell King - ARM Linux
2012-02-17 9:14 ` Russell King - ARM Linux
2012-02-17 9:33 ` Rajendra Nayak
2012-02-17 9:33 ` Rajendra Nayak
2012-02-17 9:37 ` Rajendra Nayak
2012-02-17 9:37 ` Rajendra Nayak
2012-02-17 9:59 ` Rajendra Nayak
2012-02-17 9:59 ` Rajendra Nayak
2012-02-17 10:06 ` Russell King - ARM Linux
2012-02-17 10:06 ` Russell King - ARM Linux
2012-02-17 10:18 ` Rajendra Nayak
2012-02-17 10:18 ` Rajendra Nayak
2012-02-17 10:26 ` Rajendra Nayak
2012-02-17 10:26 ` Rajendra Nayak
2012-02-17 21:23 ` Tony Lindgren
2012-02-17 21:23 ` Tony Lindgren
2012-02-17 14:24 ` Rajendra Nayak
2012-02-17 14:24 ` Rajendra Nayak
2012-02-17 20:21 ` Tony Lindgren
2012-02-17 20:21 ` Tony Lindgren
2012-02-17 22:37 ` Tony Lindgren
2012-02-17 22:37 ` Tony Lindgren
2012-02-21 5:19 ` Rajendra Nayak
2012-02-21 5:19 ` Rajendra Nayak
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=4F3D0186.2010500@ti.com \
--to=rnayak@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.