[PATCH] ARM: dts: aspeed: anacapa: Add eeprom device node
Andrew Jeffery
andrew at codeconstruct.com.au
Thu Mar 5 11:12:32 AEDT 2026
On Mon, 2026-03-02 at 12:20 +0800, Colin Huang wrote:
> eeprom address changed (0x50 to 0x51) in DCSCM rev D
> To support previous rev (B/C) and rev D,
> add eeprom device node for DCSCM rev D.
>
> Signed-off-by: Colin Huang <u8813345 at gmail.com>
> ---
> DCSCM rev D changed the eeprom address from 0x50 t0 0x51
> To support previous rev(B/C) and rev D.
> add new eeprom node for devscm rev d.
I feel different hardware revisions may deserved different devicetrees.
What are the trade-offs that lead you to avoiding that?
Why is it better to cause driver bind errors on both revisions?
Andrew
More information about the Linux-aspeed
mailing list