From: Stephen Boyd <sboyd@kernel.org>
To: Nuno Sa <nuno.sa@analog.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org
Cc: Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v2 2/2] clk: clk-axi-clkgen: make sure to enable the AXI bus clock
Date: Thu, 14 Nov 2024 14:45:58 -0800 [thread overview]
Message-ID: <c44cd4a76bd7100587e96d5e979ed8f8.sboyd@kernel.org> (raw)
In-Reply-To: <20241029-axi-clkgen-fix-axiclk-v2-2-bc5e0733ad76@analog.com>
Quoting Nuno Sa (2024-10-29 06:59:42)
> In order to access the registers of the HW, we need to make sure that
> the AXI bus clock is enabled. Hence let's increase the number of clocks
> by one.
>
> In order to keep backward compatibility and make sure old DTs still work
> we check if clock-names is available or not. If it is, then we can
> disambiguate between really having the AXI clock or a parent clock and
> so we can enable the bus clock. If not, we fallback to what was done
> before and don't explicitly enable the AXI bus clock.
>
> Note that if clock-names is given, the axi clock must be the last one in
> the phandle array (also enforced in the DT bindings) so that we can reuse
> as much code as possible.
>
> Fixes: 0e646c52cf0e ("clk: Add axi-clkgen driver")
> Signed-off-by: Nuno Sa <nuno.sa@analog.com>
> ---
Applied to clk-next
prev parent reply other threads:[~2024-11-14 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 13:59 [PATCH v2 0/2] clk: clk-axi-clkgen: make sure to enable the AXI bus clock Nuno Sa
2024-10-29 13:59 ` [PATCH v2 1/2] dt-bindings: clock: axi-clkgen: include AXI clk Nuno Sa
2024-10-31 13:09 ` Conor Dooley
2024-11-14 22:45 ` Stephen Boyd
2024-10-29 13:59 ` [PATCH v2 2/2] clk: clk-axi-clkgen: make sure to enable the AXI bus clock Nuno Sa
2024-11-14 22:45 ` Stephen Boyd [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=c44cd4a76bd7100587e96d5e979ed8f8.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
/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.