From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@stericsson.com>,
Liam Girdwood <lrg@slimlogic.co.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.arm.linux.org.uk,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH] AB3100 regulator support v1
Date: Sun, 30 Aug 2009 14:51:57 +0200 [thread overview]
Message-ID: <63386a3d0908300551s9c7f69dt5b3861fa329da35a@mail.gmail.com> (raw)
In-Reply-To: <20090830103448.GD4334@sirena.org.uk>
2009/8/30 Mark Brown <broonie@opensource.wolfsonmicro.com>:
> [While setting up a child platform device from a platform driver
> probe...]
>
>> >> + /* This would seem logical but makes everything break... */
>> >> + /* pdev->dev.parent = parent; */
>
>> > Err... it does? In what way?
>
>> The sub-platform devices are added, but when I add a platform driver for
>> them, the probing does not commence, because they hang in
>> driver base/dd.c: __driver_attach() trying to take the parent semaphore,
>> i.e. this line:
>
>> if (dev->parent) /* Needed for USB */
>> down(&dev->parent->sem);
>
>> In this case the parent is ab3100-regulators, the platform device for
>> the set of regulators.
>
> On the face of it (and without having actually looked at a running
> system or anything yet) I'm rather surprised that platform based MFD
> drivers aren't running into this issue more often. CCing in Alan who
> made the change.
I think it hasn't happened a lot because most MFD:s spawn their
platform device children at subsystem_init and then register drivers
for them at driver_init. E.g. all the wm8350 children have their
drivers at higher init levels, except for the regulators which are by
chance saved by having the i2c device as parent.
> However, fixing this is not required to avoid the issue for this
> particular driver. The problem is being caused because in addition to
> the core MFD driver for the device you've chosen to create both a
> platform device covering all regulators and further per-regulator child
> platform devices.
Yeah I know, I thought it was elegant... :-/
> If you create only one level of child device for the
> MFD you'll avoid the issue because your core device is an I2C device.
> Either have a device per regulator or have a single device which
> registers multiple regulators.
Yep I elaborated registering multiple regulators to the ab3100-regulators
platform device, I'll try this.
Linus
next prev parent reply other threads:[~2009-08-30 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 22:11 Linus Walleij
2009-08-21 10:56 ` Mark Brown
2009-08-29 23:03 ` Linus Walleij
2009-08-30 0:37 ` Linus Walleij
2009-08-30 10:08 ` Mark Brown
2009-08-30 10:34 ` Mark Brown
2009-08-30 12:51 ` Linus Walleij [this message]
2009-08-30 13:03 ` Mark Brown
2009-08-30 16:27 ` Alan Stern
2009-08-30 19:01 ` Mark Brown
2009-08-31 20:27 ` Alan Stern
2009-09-01 12:12 ` Russell King - ARM Linux
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=63386a3d0908300551s9c7f69dt5b3861fa329da35a@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@slimlogic.co.uk \
--cc=sameo@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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®