From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mark Brown <broonie@kernel.org>
Cc: Ron Economos <re@w6rz.net>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: cadence-qspi: Fix requesting of APB and AHB clocks on JH7110
Date: Tue, 31 Mar 2026 15:10:59 +0200 [thread overview]
Message-ID: <878qb89mak.fsf@bootlin.com> (raw)
In-Reply-To: <20260307-spi-cadence-qspi-fix-jh7110-v1-1-c9f37b8c58b1@kernel.org> (Mark Brown's message of "Sat, 07 Mar 2026 09:50:35 +0000")
Hello,
On 07/03/2026 at 09:50:35 GMT, Mark Brown <broonie@kernel.org> wrote:
> The move of the AHB and APB clocks from a JH7110 specific quirk to the
> main clock init dropped the specification of the clock names to request
> for the AHB and APB clocks, resulting in the clock framework requesting
> a clock with a NULL name three times. On most platforms where the
> clocks are physically the same or some are always on this makes no
> difference but the reason we had the specific quirk for JH7110 is that
> it does actually have separate, controllable clocks. Update the new
> code to request the AHB and APB clocks by name to restore the original
> behaviour on JH7110.
I know I'm late, but I wanted to understand what was wrong. Clearly I
misunderstood the clk bulk API. It only works with names, not indexes,
and I didn't got that right when I proposed the switch. The fix from
Mark is correct (thanks). The RZ/N1 platform was also only getting a
single clock instead of two, but the one it was getting is derived from
the other, so in turns both were enabled.
It eventually makes sense. Thanks Mark.
Miquèl
prev parent reply other threads:[~2026-03-31 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 9:50 [PATCH] spi: cadence-qspi: Fix requesting of APB and AHB clocks on JH7110 Mark Brown
2026-03-07 13:08 ` Ron Economos
2026-03-10 14:32 ` Mark Brown
2026-03-31 13:10 ` Miquel Raynal [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=878qb89mak.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=re@w6rz.net \
/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