On Fri, Sep 29, 2017 at 08:08:28PM +0200, Alexander Kurz wrote:
> Hi,
> during xchg_single 32 bits will be sent and received:
> 2x32 bits / 10 Microseconds = 6.4MHz Clock.
why 2x?
> Hence, a 10 Microseconds timeout will break SPI communication for
> boards with SPI frequencies less then 6.4MHz.
>
Hi,
during xchg_single 32 bits will be sent and received:
2x32 bits / 10 Microseconds = 6.4MHz Clock.
Hence, a 10 Microseconds timeout will break SPI communication for
boards with SPI frequencies less then 6.4MHz.
On some boards spi-max-frequency is limited due to improper communication
at higher
On Wed, Aug 02, 2017 at 10:32:40PM +0200, Sam Ravnborg wrote:
> Hi Uwe.
> > I havn't looked at it, but it is included in my barebox as I'm using
> > 2017.08.0 + some patches.
> And I did not expect it to solve your problem, only to give you
> inspiration what could be the issue.
>
> >
> > Reading
Hi Uwe.
> Which SoC are you using? Doesn't seem to match my problem. I don't know
> what Sascha did, I'd route ecspi_root to cko2 and check if there is a
> clk in the failing situation. (Assuming that pin is accessible on your
> machine of course.)
The CPU is:
NXP i.MX 6 Single Core Cortex-A9 Ind
On Wed, Aug 02, 2017 at 10:32:40PM +0200, Sam Ravnborg wrote:
> Hi Uwe.
> > I havn't looked at it, but it is included in my barebox as I'm using
> > 2017.08.0 + some patches.
> And I did not expect it to solve your problem, only to give you
> inspiration what could be the issue.
>
> >
> > Reading
On Wed, Aug 02, 2017 at 09:54:40PM +0200, Sam Ravnborg wrote:
> Hi Uwe.
>
> On Wed, Aug 02, 2017 at 09:39:05PM +0200, Uwe Kleine-König wrote:
> > Hello,
> >
> > during bringup of an i.MX7 board I am faced with cspi_2_3_xchg_single not
> > returning. I don't know yet why this happens, but with thi
Hi Uwe.
> I havn't looked at it, but it is included in my barebox as I'm using
> 2017.08.0 + some patches.
And I did not expect it to solve your problem, only to give you
inspiration what could be the issue.
>
> Reading through the patch description, it doesn't match my situation.
OK
> I'm doing
Hi Uwe.
On Wed, Aug 02, 2017 at 09:39:05PM +0200, Uwe Kleine-König wrote:
> Hello,
>
> during bringup of an i.MX7 board I am faced with cspi_2_3_xchg_single not
> returning. I don't know yet why this happens, but with this patch set it at
> least
> doesn't block barebox.
Your description remind
Hello,
during bringup of an i.MX7 board I am faced with cspi_2_3_xchg_single not
returning. I don't know yet why this happens, but with this patch set it at
least
doesn't block barebox.
I didn't test on a working board, maybe the timeout (10 µs) I chose is too
tight?
Best regards
Uwe
Uwe Klei
