Message ID | 1433614726-1737-1-git-send-email-linux_wi@tinag.ch |
---|---|
State | Changes Requested |
Headers | show |
On Sat, Jun 06, 2015 at 08:18:46PM +0200, Silvan Wicki wrote: > Adds: make sure bits 16-31 of DIV register are always 0 > Adds: assume minimal divider of 2 if divider resulted in 0 > (bcm2835 sets divider to 32768 if cdiv is set to 0) > > See page 33/34 of BCM2835-ARM-Peripherals.pdf for the DIV register. > https://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf > > Signed-off-by: Silvan Wicki <linux_wi@tinag.ch> > --- Please provide a small changelog below the --- line, like: Changes since V3: ... I get so many patches and can't figure that out on my own. Thanks!
On 06/06/2015 12:18 PM, Silvan Wicki wrote: > Adds: make sure bits 16-31 of DIV register are always 0 > Adds: assume minimal divider of 2 if divider resulted in 0 > (bcm2835 sets divider to 32768 if cdiv is set to 0) > > See page 33/34 of BCM2835-ARM-Peripherals.pdf for the DIV register. > https://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf > diff --git a/drivers/i2c/busses/i2c-bcm2835.c b/drivers/i2c/busses/i2c-bcm2835.c > @@ -252,12 +255,28 @@ static int bcm2835_i2c_probe(struct platform_device *pdev) > + if (divider > BCM2835_I2C_CDIV_MAX) { > + dev_warn(&pdev->dev, > + "Clock too slow, falling back to min clock speed\n"); > + divider = BCM2835_I2C_CDIV_MAX; > + } > bcm2835_i2c_writel(i2c_dev, BCM2835_I2C_DIV, divider); Shouldn't this be an error? i.e. dev_err() not dev_warn(), and return an error code. If the divider that's required to reach the requested clock is higher than the HW can implement, that means the actual clock will be faster than the requested clock. Presumably there's a reason the specific slow rate was requested, and if we exceed it, there will be problems. -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Jun 08, 2015 at 07:48:25PM -0600, Stephen Warren wrote: > On 06/06/2015 12:18 PM, Silvan Wicki wrote: > > Adds: make sure bits 16-31 of DIV register are always 0 > > Adds: assume minimal divider of 2 if divider resulted in 0 > > (bcm2835 sets divider to 32768 if cdiv is set to 0) > > > > See page 33/34 of BCM2835-ARM-Peripherals.pdf for the DIV register. > > https://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf > > > diff --git a/drivers/i2c/busses/i2c-bcm2835.c b/drivers/i2c/busses/i2c-bcm2835.c > > > @@ -252,12 +255,28 @@ static int bcm2835_i2c_probe(struct platform_device *pdev) > > > + if (divider > BCM2835_I2C_CDIV_MAX) { > > + dev_warn(&pdev->dev, > > + "Clock too slow, falling back to min clock speed\n"); > > + divider = BCM2835_I2C_CDIV_MAX; > > + } > > bcm2835_i2c_writel(i2c_dev, BCM2835_I2C_DIV, divider); > > Shouldn't this be an error? i.e. dev_err() not dev_warn(), and return an > error code. > > If the divider that's required to reach the requested clock is higher > than the HW can implement, that means the actual clock will be faster > than the requested clock. Presumably there's a reason the specific slow > rate was requested, and if we exceed it, there will be problems. i searched for similar things in other i2c drivers and found that i2c-bcm-iproc, i2c-digicolor do a dev_err. so it seems like dev_err is the way it should be implemented. i'll update that. -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/drivers/i2c/busses/i2c-bcm2835.c b/drivers/i2c/busses/i2c-bcm2835.c index c9336a3..7a5b96d 100644 --- a/drivers/i2c/busses/i2c-bcm2835.c +++ b/drivers/i2c/busses/i2c-bcm2835.c @@ -50,6 +50,9 @@ #define BCM2835_I2C_S_CLKT BIT(9) #define BCM2835_I2C_S_LEN BIT(10) /* Fake bit for SW error reporting */ +#define BCM2835_I2C_CDIV_MIN 0x0002 +#define BCM2835_I2C_CDIV_MAX 0xFFFE + #define BCM2835_I2C_TIMEOUT (msecs_to_jiffies(1000)) struct bcm2835_i2c_dev { @@ -252,12 +255,28 @@ static int bcm2835_i2c_probe(struct platform_device *pdev) divider = DIV_ROUND_UP(clk_get_rate(i2c_dev->clk), bus_clk_rate); /* + * A divider of 0 results in extremely high bus_clk_rate values + * such as bus_clk_rate >= 4044967297 with core_clock = 250MHz. + * In such a case assume the minimal possible divider, since + * bcm2835 chip sets divisor internally to 32768 if cdiv is 0. + */ + if (divider < BCM2835_I2C_CDIV_MIN) { + dev_warn(&pdev->dev, + "Clock too fast, falling back to max clock speed\n"); + divider = BCM2835_I2C_CDIV_MIN; + } + /* * Per the datasheet, the register is always interpreted as an even * number, by rounding down. In other words, the LSB is ignored. So, * if the LSB is set, increment the divider to avoid any issue. */ if (divider & 1) divider++; + if (divider > BCM2835_I2C_CDIV_MAX) { + dev_warn(&pdev->dev, + "Clock too slow, falling back to min clock speed\n"); + divider = BCM2835_I2C_CDIV_MAX; + } bcm2835_i2c_writel(i2c_dev, BCM2835_I2C_DIV, divider); irq = platform_get_resource(pdev, IORESOURCE_IRQ, 0);
Adds: make sure bits 16-31 of DIV register are always 0 Adds: assume minimal divider of 2 if divider resulted in 0 (bcm2835 sets divider to 32768 if cdiv is set to 0) See page 33/34 of BCM2835-ARM-Peripherals.pdf for the DIV register. https://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf Signed-off-by: Silvan Wicki <linux_wi@tinag.ch> --- drivers/i2c/busses/i2c-bcm2835.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)