Oh, but to be clear, the iic instances themselves would not be in conflict, because they are direct-configured by THEIR parents, and alipm and tsc wont both exist on a given machine.
It’s the i2c devices themselves I was referring to in my previous message. The autoconfig system used to be able to handle “foo0” being specified at multiple parents (but it would only attach one of them). Has that changed? -- thorpej Sent from my iPhone. > On May 14, 2018, at 6:24 PM, Jason Thorpe <thor...@me.com> wrote: > > They would have conflicted already in the old stuff. This would be a great > application for using direct configuration of i2c on this platform. > > -- thorpej > Sent from my iPhone. > >> On May 14, 2018, at 6:11 PM, Jonathan A. Kollasch <jakll...@netbsd.org> >> wrote: >> >> Module Name: src >> Committed By: jakllsch >> Date: Mon May 14 22:11:30 UTC 2018 >> >> Modified Files: >> src/sys/arch/alpha/conf: GENERIC >> >> Log Message: >> Move iic0 at alipm? to iic1. Using iic0 will conflict with the >> iic0 at tsciic? on the API CS20. >> >> XXX: Enumerate the similar-to-DS20L I2C devices on the CS20, which >> IIRC are not all on the tsciic(4) I2C bus, and comment GENERIC >> accordingly. >> >> >> To generate a diff of this commit: >> cvs rdiff -u -r1.380 -r1.381 src/sys/arch/alpha/conf/GENERIC >> >> Please note that diffs are not public domain; they are subject to the >> copyright notices on the relevant files. >>
