From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org, linux-amarula@amarulasolutions.com,
michael@amarulasolutions.com,
Brian Masney <bmasney+clk@redhat.com>,
Conor Dooley <conor+dt@kernel.org>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: clock: ti: dpll: drop the ti,ssc-* properties
Date: Mon, 26 Oct 2026 11:00:50 +0100 [thread overview]
Message-ID: <20261026-laughing-chubby-lionfish-eaf8c6@quoll> (raw)
In-Reply-To: <20261023145555.3578469-2-dario.binacchi@amarulasolutions.com>
On Fri, Oct 23, 2026 at 04:55:30PM +0200, Dario Binacchi wrote:
> The common clock binding provides assigned-clock-sscs to configure
> spread spectrum clocking (SSC), supported by the clock core since commit
> a7f16660af39 ("clk: conf: Support assigned-clock-sscs"). Keeping the
> vendor specific ti,ssc-deltam, ti,ssc-modfreq-hz and ti,ssc-downspread
> properties would leave two ways to describe the same thing.
>
> The properties have no in-tree users, so they can be dropped.
I see the user:
git grep ti,ssc-deltam
Maybe you ordered patches incorrectly. Anyway, properties with in-tree
users must be documented, so make them deprecated instead.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-26 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 14:55 [PATCH 0/3] clk: ti: dpll: switch spread spectrum to the generic framework Dario Binacchi
2026-10-23 14:55 ` [PATCH 1/3] dt-bindings: clock: ti: dpll: drop the ti,ssc-* properties Dario Binacchi
2026-10-26 10:00 ` Krzysztof Kozlowski [this message]
2026-10-23 14:55 ` [PATCH 2/3] clk: ti: dpll: use the generic spread spectrum configuration Dario Binacchi
2026-10-23 14:55 ` [PATCH 3/3] clk: ti: dpll: apply the spread spectrum configuration right away Dario Binacchi
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=20261026-laughing-chubby-lionfish-eaf8c6@quoll \
--to=krzk@kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet+clk@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®