linux-kernel - Re: i2c-eg20t: regression since i2c_add_numbered

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6208908.ZjG7eB9lJn@ws-stein>
Date:	Thu, 30 Aug 2012 13:08:09 +0200
From:	Alexander Stein <alexander.stein@...tec-electronic.com>
To:	Feng Tang <feng.tang@...el.com>
Cc:	Jean Delvare <khali@...ux-fr.org>, linux-i2c@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Ben Dooks (embedded platforms)" <ben-linux@...ff.org>,
	Tomoya MORINAGA <tomoya.rohm@...il.com>
Subject: Re: i2c-eg20t: regression since i2c_add_numbered_adapter change

On Thursday 30 August 2012 17:19:15, Feng Tang wrote:
> > IMO the i2c_register_board_info only works in quite static setups. Especially with I2C-Busses attached to hotplugable PCI devices this way doesn't work reliable any more.
> > The device come and go dynamically so you can't assume fixed mapping.
> 
> Can you specify the hotplugable?
> 1. A hotplugable i2c bus controller (say i2c_eg20t) with all fixed i2c
>  devices connecting to it
> 2. i2c bus controller is fixed, while the i2c devices will be dynamically
>  connected to it.
> 3. Both the bus controller and devices are dynamically hotplugged

I had scenario 1 in mind, but with more than 1 bus controller (say 2x i2c_eg20t). How can you set a fixed numbering if there are more controllers, each with maybe more than 1 bus?
Anyway, how can you provide a static bus numbering if there are more than one driver or more than one device per driver if the devices are hotplugable?

Best regards,
Alexander

--
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/