[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081103173237.GA13733@oksana.dev.rtsoft.ru>
Date: Mon, 3 Nov 2008 20:32:37 +0300
From: Anton Vorontsov <avorontsov@...mvista.com>
To: Dmitry <dbaryshkov@...il.com>
Cc: linux-kernel@...r.kernel.org, cbou@...l.ru,
Andrew Morton <akpm@...ux-foundation.org>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: Re: [PATCH] power_supply: only register tosa_battery driver on tosa
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@...il.com
irc://irc.freenode.net/bd2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists