Hi Andrew,
Andrew Lunn <and...@lunn.ch> writes:
>> - ret = mdiobus_read_nested(bus, addr, reg);
>> + ret = mdiobus_read_nested(bus, sw_addr + addr, reg);
>> if (ret < 0)
>> return ret;
>
> If we are doing direct access, doesn't it means sw_addr is 0?
>
> So isn't this pointless?
6060 has no indirect access and directly responds to 16 SMI addresses,
regardless its chip address which can be strapped to either 0 or 16.
If we want to add support for it in mv88e6xxx someday (which is likely),
the code is ready for that.
Question 1) given this, should I still consider your first comment on
this patch about the mv88e6xxx_smi_ops assignment?
Question 2) is MV88E6XXX_FLAG_MULTI_CHIP confusing? I took a short name
for style but maybe a longer MV88E6XXX_FLAG_MULTI_CHIP_ADDRESSING or
MV88E6XXX_FLAG_MULTI_CHIP_MODE would be clearer to make to distinction
between "Single-chip Addressing Mode" and "Multi-chip Addressing Mode".
Thanks,
Vivien
