Re: [2nd RESEND PATCH 1/2] i2c: enable buses to save their clock frequency in adapter

On 2018-12-07 12:29, tudor.amba...@microchip.com wrote: > From: "tudor.amba...@microchip.com" > > The clock-frequency property is not mandatory for the i2c buses. If it's > not present in the device tree, the buses __usually__ assume it's 100kHZ > (see altera, at91, axxia, etc.). Broadcom uses a

Re: [2nd RESEND PATCH 1/2] i2c: enable buses to save their clock frequency in adapter

On 2018-12-07 12:29, tudor.amba...@microchip.com wrote: > From: "tudor.amba...@microchip.com" > > The clock-frequency property is not mandatory for the i2c buses. If it's > not present in the device tree, the buses __usually__ assume it's 100kHZ > (see altera, at91, axxia, etc.). Broadcom uses a

[2nd RESEND PATCH 1/2] i2c: enable buses to save their clock frequency in adapter

From: "tudor.amba...@microchip.com" The clock-frequency property is not mandatory for the i2c buses. If it's not present in the device tree, the buses __usually__ assume it's 100kHZ (see altera, at91, axxia, etc.). Broadcom uses a 375kHZ default clock-frequency, so the default clock frequency

[2nd RESEND PATCH 1/2] i2c: enable buses to save their clock frequency in adapter

From: "tudor.amba...@microchip.com" The clock-frequency property is not mandatory for the i2c buses. If it's not present in the device tree, the buses __usually__ assume it's 100kHZ (see altera, at91, axxia, etc.). Broadcom uses a 375kHZ default clock-frequency, so the default clock frequency