From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Dmitry <dbaryshkov@gmail.com>
Cc: linux-kernel@vger.kernel.org, cbou@mail.ru,
Andrew Morton <akpm@linux-foundation.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [PATCH] power_supply: only register tosa_battery driver on tosa
Date: Mon, 3 Nov 2008 20:32:37 +0300 [thread overview]
Message-ID: <20081103173237.GA13733@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <bc64b4640811030909s5bbb05dao9f83523aac9dd8ef@mail.gmail.com>
On Mon, Nov 03, 2008 at 08:09:14PM +0300, Dmitry wrote:
[...]
> >> Yup.
> >> I see few ways to resolve this:
> >> * write better wm97xx interface. Dunno if that is feasible or possible.
> >> One of the possible solutions is to pass battery and ts device names
> >> and data from within board data via ac97 layer to wm97xx-core. This
> >> will provide several benefits (e.g. then we can drop lots of parameters
> >> from wm97xx-core, which are really board parameters).
> >
> > That would be great indeed. But for now, just don't compile the two
> > drivers on the tosa platform. No need for machine_is_*() hacks...
>
> That is a bit strange requirement. During several past months there was
> a lot of efforts put into supporting multi-machine PXA kernel images.
Yes, I know this.
But you're implementing hacks instead of fixing the problem.
Btw, you inserted the machine_is() into the tosa driver, but
wm97xx driver registers unconditionally. That could be a problem
when wm97xx loads first, and then you try to load the tosa_battery
module on tosa machine.
Let's insert machine_is() hack into the wm97xx driver as well?
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2008-11-03 17:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 9:04 [PATCH] power_supply: only register tosa_battery driver on tosa Dmitry Baryshkov
2008-10-29 9:04 ` [PATCH] power_supply: change the way how wm97xx-bat driver is registered Dmitry Baryshkov
2008-11-02 20:36 ` Dmitry
2008-11-02 23:41 ` Marek Vasut
2008-11-03 15:11 ` Anton Vorontsov
2008-11-03 16:54 ` Jonathan Cameron
2008-11-03 17:21 ` Anton Vorontsov
2008-11-03 18:29 ` Dmitry Baryshkov
2008-11-03 19:34 ` Anton Vorontsov
2008-11-02 20:36 ` [PATCH] power_supply: only register tosa_battery driver on tosa Dmitry
2008-11-03 14:55 ` Anton Vorontsov
2008-11-03 16:20 ` Dmitry
2008-11-03 16:25 ` Anton Vorontsov
2008-11-03 16:41 ` Dmitry
2008-11-03 16:58 ` Anton Vorontsov
2008-11-03 17:09 ` Dmitry
2008-11-03 17:32 ` Anton Vorontsov [this message]
2008-11-03 18:14 ` Dmitry
2008-11-03 17:41 ` Mark Brown
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=20081103173237.GA13733@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cbou@mail.ru \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.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 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.