Re: [PATCH] Net: add mdio_i2c driver.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Nov 17, 2017 at 09:52:14AM +0100, Clément Leger wrote:
> Hi Sascha,
> 
> Indeed, I though about that and I was facing another problem.
> The mdio to i2c driver does not have a specific address.
> ie, it is not a device but rather a bus.
> If I put the mdio_i2c  node under the i2c bus, then I should assign
> it an i2c address. This address should represent the phy address.
> However, this would means I would have one mdio-i2c driver per phy.

Some AT24 EEPROMs have the same problem, they also use multiple
addresses. AFAIK for them only the first address is provided in the
"reg" property. See drivers/eeprom/at24c.c how the driver handles this
situation.
Normally I think multi address devices should simply provide their
reg space as reg = <start size>; like other devices do aswell. I don't
know what the I2C core maked from this though.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox




[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux