From: Mark Brown <broonie@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Ben Whitten <ben.whitten@gmail.com>,
devicetree <devicetree@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Maxime Ripard <maxime.ripard@bootlin.com>,
netdev@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
"linux-lpwan@lists.infradead.org"
<linux-lpwan@lists.infradead.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Russell King <linux@armlinux.org.uk>,
starnight@g.ncu.edu.tw, linux-clk <linux-clk@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 lora-next 5/5] net: lora: sx125x sx1301: allow radio to register as a clk provider
Date: Thu, 3 Jan 2019 12:37:20 +0000 [thread overview]
Message-ID: <20190103123720.GR1846@sirena.org.uk> (raw)
In-Reply-To: <1904336c-3349-b22b-18ac-e82e4afebc51@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 795 bytes --]
On Wed, Jan 02, 2019 at 01:44:40AM +0100, Andreas Färber wrote:
> So, the third invocation of sun6i_transfer_one() calling clk_get_rate()
> hangs at the prepare_lock instead of reference-counting, because it runs
> from a separate kthread, unlike the two previous calls?
If there's any contestation for the bus we push all the I/O through a
separate thread to maintain ordering and improve performance.
> I did not find any *regmap_init_spi() based example in drivers/clk/, and
> all other "spi" mentions in drivers/clk/ appeared to be clock names.
> The closest was devm_regmap_init_i2c() based clk-cdce706.c, which uses
> the prepare/unprepare ops, as suggested by Mark, and does
> regmap_update_bits() from there.
You'll find a bunch of the MFDs have SPI options as well.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-01-03 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1539361567-3602-1-git-send-email-ben.whitten@lairdtech.com>
[not found] ` <1539361567-3602-2-git-send-email-ben.whitten@lairdtech.com>
2018-10-18 16:59 ` [PATCH v3 lora-next 1/5] regmap: Add regmap_noinc_write API Andreas Färber
2018-10-18 17:18 ` Mark Brown
[not found] ` <1539361567-3602-6-git-send-email-ben.whitten@lairdtech.com>
[not found] ` <a89c7974-672f-e5d0-8022-d2c2f9ffeac0@suse.de>
[not found] ` <d22f1f18-0c93-a537-a439-07363174a03b@suse.de>
2018-12-30 10:55 ` [PATCH v3 lora-next 5/5] net: lora: sx125x sx1301: allow radio to register as a clk provider Andreas Färber
2018-12-31 13:27 ` Andreas Färber
2018-12-31 17:50 ` Mark Brown
2018-12-31 22:56 ` Andreas Färber
2019-01-02 0:44 ` Andreas Färber
2019-01-03 12:37 ` Mark Brown [this message]
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=20190103123720.GR1846@sirena.org.uk \
--to=broonie@kernel.org \
--cc=afaerber@suse.de \
--cc=ben.whitten@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lpwan@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.ripard@bootlin.com \
--cc=mturquette@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=starnight@g.ncu.edu.tw \
/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;
as well as URLs for NNTP newsgroup(s).