[2nd RESEND PATCH 2/2] i2c: at91: Save the bus clock frequency in adapter

2018-12-07 Thread Tudor.Ambarus
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 2/2] i2c: at91: Save the bus clock frequency in adapter

2018-12-07 Thread Tudor.Ambarus
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

[RESEND PATCH 2/2] i2c: at91: Save the bus clock frequency in adapter

2018-10-23 Thread Tudor.Ambarus
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 varies from bus to bus. There are i2c

[RESEND PATCH 2/2] i2c: at91: Save the bus clock frequency in adapter

2018-10-23 Thread Tudor.Ambarus
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 varies from bus to bus. There are i2c