Hello Marek,
Am 30.04.2019 um 09:01 schrieb Marek Behun:
You mean tha patch series
"[U-Boot] [PATCH u-boot-marvell v2 00/15] Fixes for Turris Omnia"
So we can ignore this patch?
bye,
Heiko
Yes :)
Ok, fine. I set Patchwork state for this patch to superseded
> You mean tha patch series
>
> "[U-Boot] [PATCH u-boot-marvell v2 00/15] Fixes for Turris Omnia"
>
> So we can ignore this patch?
>
> bye,
> Heiko
Yes :)
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
Hello Marek,
Am 30.04.2019 um 03:49 schrieb Marek Behun:
I would really like not to see such board specific code added to this
driver.
Frankly, I fail to understand why used udelay(11) instead of udelay(10)
should result in such a difference on your board. Could you please
investigate a bit
> I would really like not to see such board specific code added to this
> driver.
>
> Frankly, I fail to understand why used udelay(11) instead of udelay(10)
> should result in such a difference on your board. Could you please
> investigate a bit more and hopefully come up with a "better"
Hi Marek,
(added Heiko to Cc)
On 25.04.19 15:22, Marek BehĂșn wrote:
Commit c68c6243 ("i2c: mvtwsi: Make delay times frequency-dependent")
broke the default configuration of the Turris Omnia target.
With i2c frequency at 100kHz the twsi_wait function call to ndelay(tick)
the tick variable is
Commit c68c6243 ("i2c: mvtwsi: Make delay times frequency-dependent")
broke the default configuration of the Turris Omnia target.
With i2c frequency at 100kHz the twsi_wait function call to ndelay(tick)
the tick variable is computed to 10340 (nanoseconds). Since ndelay
calls
6 matches
Mail list logo