From: jhovold@gmail.com (Johan Hovold)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys
Date: Thu, 31 Oct 2013 15:01:40 +0100 [thread overview]
Message-ID: <20131031140140.GG29813@localhost> (raw)
In-Reply-To: <201310302146.18248.arnd@arndb.de>
On Wed, Oct 30, 2013 at 09:46:17PM +0100, Arnd Bergmann wrote:
> On Wednesday 30 October 2013, Johan Hovold wrote:
> > > I really hate this type of patch, as it's papering over the real
> > > problem. What happens when someone else moves their driver to this
> > > level? Then you are back to the original problem.
> >
> > Yes, it's crude, but it's currently the only way to express a preferred
> > probe order.
>
> Does the same problem occur with the generic PWM subsystem?
It does not suffer from the problem with failed probe as it supports
deferred probing, but there could be added delays depending on probe
order.
> The atmel_pwm driver apparently is the last PWM driver that has
> not been converted to the generic subsystem yet. Doing that would
> also let us drop the atmel-pwm-bl driver in favor of the generic
> backlight.
As Bo mentioned, it's work in progress that hasn't been merged yet.
Johan
prev parent reply other threads:[~2013-10-31 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 16:32 [PATCH 0/2] misc: atmel_pwm: fix probe dependencies Johan Hovold
2013-10-22 16:32 ` [PATCH 1/2] misc: atmel_pwm: add deferred-probing support Johan Hovold
2013-10-30 11:25 ` Johan Hovold
2013-10-30 13:24 ` Greg Kroah-Hartman
2013-10-22 16:32 ` [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys Johan Hovold
2013-10-29 23:22 ` Greg Kroah-Hartman
2013-10-30 11:07 ` Johan Hovold
2013-10-30 20:46 ` Arnd Bergmann
2013-10-31 1:19 ` Bo Shen
2013-10-31 5:30 ` Jean-Christophe PLAGNIOL-VILLARD
2013-10-31 14:07 ` Johan Hovold
2013-10-31 14:01 ` Johan Hovold [this message]
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=20131031140140.GG29813@localhost \
--to=jhovold@gmail.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).