[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170104104508.4afbc9f7@endymion>
Date: Wed, 4 Jan 2017 10:45:08 +0100
From: Jean Delvare <jdelvare@...e.de>
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Pali Rohár <pali.rohar@...il.com>,
Steven Honeyman <stevenhoneyman@...il.com>,
<valdis.kletnieks@...edu>,
Jochen Eisinger <jochen@...guin-breeder.org>,
Gabriele Mazzotta <gabriele.mzt@...il.com>,
Andy Lutomirski <luto@...nel.org>,
<mario_limonciello@...l.com>, Alex Hung <alex.hung@...onical.com>,
kernel@...pniu.pl, Takashi Iwai <tiwai@...e.de>,
<linux-i2c@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<platform-driver-x86@...r.kernel.org>
Subject: Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on
Dell machines
On Wed, 28 Dec 2016 15:02:52 +0100, Wolfram Sang wrote:
> On Tue, Dec 27, 2016 at 02:51:01PM +0100, Pali Rohár wrote:
> > i2c_new_device() with lis3lv02d for i801 i2c bus needs to be called
> > after initializing i2c-i801 bus driver.
> >
> > I have no idea how to do it (properly) outside of i2c-i801.c file.
>
> I once used bus_notifiers to achieve something similar. You could check
> arch/arm/mach-shmobile/regulator-quirk-rcar-gen2.c to see an action
> triggered once a client device got added, but you could act on another
> action like BUS_NOTIFY_BOUND_DRIVER. I used exactly that, too, somewhen
> somewhere. Haven't checked if that helps here, too. And since we have
> a
> precedence (Fujitsu case), I'll leave it to Jean who is the maintainer
> of this driver.
I don't have a strong opinion on the matter, whatever works is fine
with me.
--
Jean Delvare
SUSE L3 Support
Powered by blists - more mailing lists