Hi Wolfram, On Monday, October 16, 2017, Chris Brandt wrote: > Most systems with this i2c are going to have a clock of either 33.33MHz or > 32MHz. That 4% difference is not reason enough to warrant that the driver > to completely fail. > > Signed-off-by: Chris Brandt <chris.brandt@xxxxxxxxxxx> > --- > v3: > * now check a range of safe frequencies > v2: > * simplified error message. > --- Actually, if you want to hold off on this patch, I'm almost done with a real fix which is to calculate any frequency based on current parent clock and rise/fall timings specified in the DT as you suggested. Chris
