On Tue, Jan 06, 2015 at 02:47:13PM +0100, Sascha Hauer wrote:
> On Mon, Jan 05, 2015 at 01:22:04PM +0100, Jan Weitzel wrote:
> > On Thu, Dec 11, 2014 at 10:47:59AM +0100, Jan Weitzel wrote:
> > > The compatible "ti,omap4-i2c" don't help to get fclk_rate. So set it
> > > acording to
> > > cpu compa
On Mon, Jan 05, 2015 at 01:22:04PM +0100, Jan Weitzel wrote:
> On Thu, Dec 11, 2014 at 10:47:59AM +0100, Jan Weitzel wrote:
> > The compatible "ti,omap4-i2c" don't help to get fclk_rate. So set it
> > acording to
> > cpu compatible: "ti,am33xx" and "ti,omap4"
> >
> > Signed-off-by: Jan Weitzel
>
On Thu, Dec 11, 2014 at 10:47:59AM +0100, Jan Weitzel wrote:
> The compatible "ti,omap4-i2c" don't help to get fclk_rate. So set it acording
> to
> cpu compatible: "ti,am33xx" and "ti,omap4"
>
> Signed-off-by: Jan Weitzel
> ---
> v2: set i2c_data directly
>-9.0.1.i586.deb
ping
Jan
> driver
The compatible "ti,omap4-i2c" don't help to get fclk_rate. So set it acording to
cpu compatible: "ti,am33xx" and "ti,omap4"
Signed-off-by: Jan Weitzel
---
v2: set i2c_data directly
drivers/i2c/busses/i2c-omap.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/driv
