From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 2/4] spi, spi_mxc: do not hang in spi_xchg_single
Date: Thu, 29 May 2014 07:22:23 +0200 [thread overview]
Message-ID: <5386C40F.1000202@denx.de> (raw)
In-Reply-To: <5386C1B9.7000009@gmail.com>
Hello Dirk,
Am 29.05.2014 07:12, schrieb Dirk Behme:
> Am 28.05.2014 12:16, schrieb Heiko Schocher:
>> if status register do never set MXC_CSPICTRL_TC, spi_xchg_single
>> endless loops. Add a timeout here to prevent endless hang.
>
> As I've never seen this, yet: Any idea what goes wrong if this happens?
I had a wrong pinmux (IIRC) and I saw this hang, so I thought
it would be good to not hang here ... but with correct pinmux
settings, I didn;t saw this anymore ... maybe unneeded patch?
bye,
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2014-05-29 5:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 10:16 [U-Boot] [PATCH v1 0/4] arm, imx6: add aristainetos board support Heiko Schocher
2014-05-28 10:16 ` [U-Boot] [PATCH v1 1/4] arm, imx6: add mxc_iomux_set_gpr_register function Heiko Schocher
2014-07-11 11:10 ` Stefano Babic
2014-07-11 13:00 ` Heiko Schocher
2014-05-28 10:16 ` [U-Boot] [PATCH v1 2/4] spi, spi_mxc: do not hang in spi_xchg_single Heiko Schocher
2014-05-28 11:09 ` Jagan Teki
2014-05-29 5:12 ` Dirk Behme
2014-05-29 5:22 ` Heiko Schocher [this message]
2014-05-28 10:16 ` [U-Boot] [PATCH v1 3/4] i.MX6: add enable_spi_clk() Heiko Schocher
2014-07-11 11:14 ` Stefano Babic
2014-07-11 13:22 ` Fabio Estevam
2014-07-15 8:15 ` Stefano Babic
2014-05-28 10:16 ` [U-Boot] [PATCH v1 4/4] arm, imx6: add aristainetos board Heiko Schocher
2014-07-11 12:26 ` Stefano Babic
2014-07-11 14:12 ` Heiko Schocher
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=5386C40F.1000202@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox