| Message ID | 20180326111927.16040-1-tudor.ambarus@microchip.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
ping On 03/26/2018 02:19 PM, Tudor Ambarus wrote: > The clock-frequency property is not mandatory for the i2c buses. If it's > not present in device tree, the buses usually asume that it is 100kHZ. > There are i2c clients that need to know the i2c bus frequency in order to > compute their wake token. Spare the clients of making (wrong) assumptions > and save the bus frequency in the i2c_adapter structure. > > Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com> > --- > include/linux/i2c.h | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/include/linux/i2c.h b/include/linux/i2c.h > index 44ad14e..7a1f26e 100644 > --- a/include/linux/i2c.h > +++ b/include/linux/i2c.h > @@ -671,6 +671,7 @@ struct i2c_adapter { > struct rt_mutex bus_lock; > struct rt_mutex mux_lock; > > + u32 bus_freq_hz; > int timeout; /* in jiffies */ > int retries; > struct device dev; /* the adapter device */ >
diff --git a/include/linux/i2c.h b/include/linux/i2c.h index 44ad14e..7a1f26e 100644 --- a/include/linux/i2c.h +++ b/include/linux/i2c.h @@ -671,6 +671,7 @@ struct i2c_adapter { struct rt_mutex bus_lock; struct rt_mutex mux_lock; + u32 bus_freq_hz; int timeout; /* in jiffies */ int retries; struct device dev; /* the adapter device */
The clock-frequency property is not mandatory for the i2c buses. If it's not present in device tree, the buses usually asume that it is 100kHZ. There are i2c clients that need to know the i2c bus frequency in order to compute their wake token. Spare the clients of making (wrong) assumptions and save the bus frequency in the i2c_adapter structure. Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com> --- include/linux/i2c.h | 1 + 1 file changed, 1 insertion(+)