From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] ARM: OMAP3: Modify omap_hsmmc_late_init to handle deleting mmc devices
Date: Thu, 1 Mar 2012 10:58:54 -0800 [thread overview]
Message-ID: <20120301185854.GA18901@atomide.com> (raw)
In-Reply-To: <4F48677E.30803@ti.com>
* Rajendra Nayak <rnayak@ti.com> [120224 20:14]:
> On Saturday 25 February 2012 06:03 AM, Tony Lindgren wrote:
> >Hi,
> >
> >* Rajendra Nayak<rnayak@ti.com> [120224 01:27]:
> >>omap_hsmmc_late_init() adds deferred (if any) mmc devices which are
> >>dependent on twl4030-gpio device to be available.
> >>If twl4030-gpio is built as a module and inserted and deleted multiple
> >>times, the mmc devices also should be added and deleted accordingly.
> >>Split omap_hsmmc_late_init() into omap_hsmmc_deferred_add() and
> >>omap_hsmmc_deferred_del() to handle this.
> >>The .setup board hook for twl4030-gpio handles the runtime adding
> >>on deferred mmc devices. Similarly a .teardown board hook for twl4030-gpio
> >>should handle the runtime deletion by calling omap_hsmmc_deferred_del().
> >>This is done for all existing omap3 boards in subsequent patches.
> >
> >This gets complex.. But I think I've found a simpler way where we
> >can use the twl gpio offsets and let the drivers take care of the rest.
> >I'll post some patches hopefully on Monday.
>
> I agree it gets complex. If you have a simpler way to handle this, that
> would be great.
Posted now, sorry it too a bit longer, I got distracted with other
stuff. The thread is "[PATCH 0/4] Start getting rid of pdata callbacks
with gpio_find_by_chip_name()". Some further testing would be
appreciated.
Regards,
Tony
next prev parent reply other threads:[~2012-03-01 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 9:58 [PATCH 0/6] Fix issues around twl4030-gpio used as a module Rajendra Nayak
2012-02-24 9:58 ` [PATCH 1/6] ARM: OMAP: omap_device: Add omap_device_unregister() Rajendra Nayak
2012-02-24 9:58 ` [PATCH 2/6] mmc: omap_hsmmc: Make the driver support hotpluggable devices Rajendra Nayak
2012-02-24 9:58 ` [PATCH 3/6] mmc: omap_hsmmc: If probe fails, give out error messages Rajendra Nayak
2012-02-24 9:58 ` [PATCH 4/6] ARM: OMAP3: Mark only those mmc devices which use gpio_cd, as deferred Rajendra Nayak
2012-02-24 22:21 ` Tony Lindgren
2012-02-25 4:30 ` Rajendra Nayak
2012-02-24 9:58 ` [PATCH 5/6] ARM: OMAP3: Modify omap_hsmmc_late_init to handle deleting mmc devices Rajendra Nayak
2012-02-25 0:33 ` Tony Lindgren
2012-02-25 4:45 ` Rajendra Nayak
2012-03-01 18:58 ` Tony Lindgren [this message]
2012-02-24 9:58 ` [PATCH 6/6] ARM: OMAP3: Use .teardown of twl4030-gpio to clean board requests 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=20120301185854.GA18901@atomide.com \
--to=tony@atomide.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).