Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: "Łukasz Majewski" <lukma@nabladev.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: clock: vf610: Add definitions for MTIP L2 switch
Date: Fri, 23 Jan 2026 17:06:49 +0000	[thread overview]
Message-ID: <20260123-rework-stank-5a364bf88af6@spud> (raw)
In-Reply-To: <20260122202603.36ed7944@wsk>

[-- Attachment #1: Type: text/plain, Size: 1949 bytes --]

On Thu, Jan 22, 2026 at 08:26:03PM +0100, Łukasz Majewski wrote:
> Hi Conor,
> 
> > On Thu, Jan 22, 2026 at 01:58:38PM +0100, Lukasz Majewski wrote:
> > > This patch adds VF610_CLK_ESW and VF610_CLK_ESW_MAC_TAB{0123}
> > > macros definitions for L2 switch.
> > > 
> > > Those definitions describe clocks for MoreThanIP switch IP block;
> > > the switch itself and the MAC address lookup table clocks.
> > > 
> > > Signed-off-by: Lukasz Majewski <lukma@nabladev.com>
> > > ---
> > >  include/dt-bindings/clock/vf610-clock.h | 7 ++++++-
> > >  1 file changed, 6 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/include/dt-bindings/clock/vf610-clock.h
> > > b/include/dt-bindings/clock/vf610-clock.h index
> > > 373644e46747..b6f7b1745cc2 100644 ---
> > > a/include/dt-bindings/clock/vf610-clock.h +++
> > > b/include/dt-bindings/clock/vf610-clock.h @@ -197,6 +197,11 @@
> > >  #define VF610_CLK_TCON1			188
> > >  #define VF610_CLK_CAAM			189
> > >  #define VF610_CLK_CRC			190
> > > -#define VF610_CLK_END			191  
> > 
> > If end is modifiable, it is removable. If you need the define for the
> > driver, please move it there.
> 
> Could you be more specific regarding your comment?

Values in bindings are immutable, so changing a definition is an ABI
break. If you can break the ABI for this definition, then you should
just remove it instead, because it doesn't represent a clock and it is
liable to change when you information comes to light (e.g. this patch).

> The VF610_CLK_END has now value 191.
> 
> However, there are other clocks in this SoC - like CLK_ESW and
> CLK_MAC_TAB{x} - which were not taken into account earlier.
> 
> What shall be done?
> 
> Shall I remove the VF610_CLK_END entirely?
> 
> Or move to the new "end" (as done with this patch)?

If you need VF610_CLK_END for your driver, rather than just using
(VF610_CLK_ESW_MAC_TAB + 1), please move the definition there.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-01-23 17:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 12:58 [PATCH] dt-bindings: clock: vf610: Add definitions for MTIP L2 switch Lukasz Majewski
2026-01-22 18:21 ` Conor Dooley
2026-01-22 19:26   ` Łukasz Majewski
2026-01-23 17:06     ` Conor Dooley [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=20260123-rework-stank-5a364bf88af6@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukma@nabladev.com \
    --cc=mturquette@baylibre.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