From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: linux-clk@vger.kernel.org, linux-i2c@vger.kernel.org,
linux-spi@vger.kernel.org, linux@arm.linux.org.uk,
mturquette@baylibre.com, sboyd@codeaurora.org, wsa@the-dreams.de
Subject: Re: Handling clocks on external busses
Date: Wed, 2 Dec 2015 13:30:10 +0000 [thread overview]
Message-ID: <20151202133010.GJ1929@sirena.org.uk> (raw)
In-Reply-To: <20151202125855.GB6058@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
On Wed, Dec 02, 2015 at 12:58:55PM +0000, Charles Keepax wrote:
> So after a bit more digging it seems this has been mitigated slightly
> as a lot of SPI driver have been updated to execute transfers in
> thread rather than from a worker thread and it seems the clock
> framework lets you re-enter the locked sections if called from the
> same thread.
No, this isn't something the drivers support (it's a framework feature)
and it isn't something that we're guaranteed to do, if the bus is busy
we defer to the thread and it's possible the drivers might do something
multi-threaded themselves. It might work a lot of the time but it's
never going to be guaranteed to work.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-12-02 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 17:37 Handling clocks on external busses Charles Keepax
2015-12-02 12:58 ` Charles Keepax
2015-12-02 13:30 ` Mark Brown [this message]
2016-04-04 9:57 ` Charles Keepax
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=20151202133010.GJ1929@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=wsa@the-dreams.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