All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/2] spi: imx: don't loop endlessly
Date: Thu, 3 Aug 2017 12:43:00 +0200	[thread overview]
Message-ID: <20170803104300.GA30477@ravnborg.org> (raw)
In-Reply-To: <20170803090725.knqzwxxroyvgcvwn@pengutronix.de>

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 Industrial processor
MCIMX6S5EVM10AC
We also ahev a quadcore variant.
Both are a proprietary design, which have roots from a freescale reference design.

I can send you the schematics (in private mail) if you think it is usefull for you.
But as you already wrote, this is likely a different problem you are fighting with.

	Sam

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2017-08-03 10:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 19:39 [PATCH 0/2] spi: imx: don't loop endlessly Uwe Kleine-König
2017-08-02 19:39 ` [PATCH 1/2] spi: imx: add error checking Uwe Kleine-König
2017-08-02 19:39 ` [PATCH 2/2] spi: imx: add timeout to xchg_single Uwe Kleine-König
2017-08-02 19:54 ` [PATCH 0/2] spi: imx: don't loop endlessly Sam Ravnborg
2017-08-02 20:19   ` Uwe Kleine-König
2017-08-02 20:32     ` Sam Ravnborg
2017-08-03  9:07       ` Uwe Kleine-König
2017-08-03 10:43         ` Sam Ravnborg [this message]
2017-08-03 18:41       ` Uwe Kleine-König
2017-09-29 18:08 ` Alexander Kurz
2017-10-02  5:31   ` Uwe Kleine-König

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170803104300.GA30477@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=barebox@lists.infradead.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.