If it is ok for you I will add "id" parameter in mfd driver and forward it to the sub-devices drivers to be able to distinguish the hardware blocks 2016-11-22 18:18 GMT+01:00 Lee Jones <lee.jones@xxxxxxxxxx>: > On Tue, 22 Nov 2016, Benjamin Gaignard wrote: > >> [snip] >> >> + "st,stm32-iio-timer5" >> >> + "st,stm32-iio-timer6" >> >> + "st,stm32-iio-timer7" >> >> + "st,stm32-iio-timer8" >> >> + "st,stm32-iio-timer9" >> >> + "st,stm32-iio-timer10" >> >> + "st,stm32-iio-timer11" >> >> + "st,stm32-iio-timer12" >> >> + "st,stm32-iio-timer13" >> >> + "st,stm32-iio-timer14" >> > >> > We can't do this. This is a binding for a driver, not for the hardware. >> > >> >> Unfortunately each instance for the hardware IP have little >> differences like which triggers they could accept or size of the >> counter register, >> and I doesn't have value inside the hardware to distinguish them so >> the only way I found is to use compatible. > > Can't you represent these as properties? > > -- > Lee Jones > Linaro STMicroelectronics Landing Team Lead > Linaro.org │ Open source software for ARM SoCs > Follow Linaro: Facebook | Twitter | Blog -- Benjamin Gaignard Graphic Study Group Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
