From: Rob Herring <robh@kernel.org>
To: "Alvin Šipraga" <alvin@pqrs.dk>
Cc: "Michael Turquette" <mturquette@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
�ipraga <alsi@bang-olufsen.dk>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/3] clk: si5351: add option to adjust PLL without glitches
Date: Tue, 10 Oct 2023 09:51:20 -0500 [thread overview]
Message-ID: <20231010145120.GA847407-robh@kernel.org> (raw)
In-Reply-To: <20231008111324.582595-1-alvin@pqrs.dk>
On Sun, Oct 08, 2023 at 01:09:36PM +0200, Alvin Šipraga wrote:
> From: Alvin Šipraga <alsi@bang-olufsen.dk>
>
> This series intends to address a problem I had when using the Si5351A as
> a runtime adjustable audio bit clock. The basic issue is that the driver
> in its current form unconditionally resets the PLL whenever adjusting
> its rate. But this reset causes an unwanted ~1.4 ms LOW signal glitch in
> the clock output.
>
> As a remedy, a new property is added to control the reset behaviour of
> the PLLs more precisely. In the process I also converted the bindings to
> YAML.
>
> Changes:
>
> v2 -> v3:
>
> - address further comments from Rob:
> - drop unnecessary refs and minItems
> - simplify if conditions for chip variants
> - ignore his comment about dropping '|', as line would be >80 columns
I've commented on v2 again.
> - move additionalProperties: false close to type: object
> - define clocks/clock-names at top-level
> - drop patch to dove-cubox dts per Krzysztof's comment - will send
> separately
> - collect Sebastian's Acked-by
>
> v1 -> v2:
>
> - address Rob's comments on the two dt-bindings patches
> - new patch to correct the clock node names in the only upstream device
> tree using si5351
>
> Alvin Šipraga (3):
> dt-bindings: clock: si5351: convert to yaml
> dt-bindings: clock: si5351: add PLL reset mode property
> clk: si5351: allow PLLs to be adjusted without reset
>
> .../bindings/clock/silabs,si5351.txt | 126 --------
> .../bindings/clock/silabs,si5351.yaml | 268 ++++++++++++++++++
> drivers/clk/clk-si5351.c | 47 ++-
> include/linux/platform_data/si5351.h | 2 +
> 4 files changed, 314 insertions(+), 129 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/clock/silabs,si5351.txt
> create mode 100644 Documentation/devicetree/bindings/clock/silabs,si5351.yaml
>
> --
> 2.42.0
>
prev parent reply other threads:[~2023-10-10 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 11:09 [PATCH v3 0/3] clk: si5351: add option to adjust PLL without glitches Alvin Šipraga
2023-10-08 11:09 ` [PATCH v3 1/3] dt-bindings: clock: si5351: convert to yaml Alvin Šipraga
2023-10-08 11:09 ` [PATCH v3 2/3] dt-bindings: clock: si5351: add PLL reset mode property Alvin Šipraga
2023-10-08 11:09 ` [PATCH v3 3/3] clk: si5351: allow PLLs to be adjusted without reset Alvin Šipraga
2023-10-10 14:51 ` Rob Herring [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=20231010145120.GA847407-robh@kernel.org \
--to=robh@kernel.org \
--cc=alsi@bang-olufsen.dk \
--cc=alvin@pqrs.dk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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 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).