On 2017-08-03 15:44, Andrew Lunn wrote:
> On Thu, Aug 03, 2017 at 12:00:27PM +0200, Peter Rosin wrote:
>> Hi!
>>
>> Texas has apparently made copies for some of the NXP devices
>> handled by the drivers/i2c/muxes/i2c-mux-pca954x.c driver.
>
> This happens a lot in the i2c space. Look at all the at
On Thu, Aug 03, 2017 at 12:00:27PM +0200, Peter Rosin wrote:
> Hi!
>
> Texas has apparently made copies for some of the NXP devices
> handled by the drivers/i2c/muxes/i2c-mux-pca954x.c driver.
This happens a lot in the i2c space. Look at all the at24 EEPROM
clones. Yet they all use the same compa
Hi!
Texas has apparently made copies for some of the NXP devices
handled by the drivers/i2c/muxes/i2c-mux-pca954x.c driver.
How is that best handled?
I see e.g. that arch/arm/boot/dts/vf610-zii-dev-rev-{b,c}.dts has
this snippet:
&i2c2 {
tca9548@70 {
compatible = "nxp,pc
3 matches
Mail list logo
