mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.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>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Felix Fietkau <nbd@nbd.name>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 06/10] dt-bindings: clock: airoha: Document new property airoha,chip-scu
Date: Wed, 16 Jul 2025 16:29:12 +0200	[thread overview]
Message-ID: <8582dbad-c773-4f46-827a-83b00eed0882@kernel.org> (raw)
In-Reply-To: <685e5446.df0a0220.369e9e.8cb1@mx.google.com>

On 27/06/2025 10:20, Christian Marangi wrote:
> 
> Here the current DTS [1]. Nothing is stable for this and we can change
> it but I want to stress that the current HW block are VERY CONFUSING and
> SCRAMBELED. So it's really a matter of finding the least bad solution.
> 
> In SCU there are:
> - PART fot the clock register
> - 2 MDIO controller register
> 
> In chip SCU:
> - Other part of the clock register
> - Thermal driver register
> - PART of the pinctrl register
> 
> [1] https://github.com/Ansuel/openwrt/blob/openwrt-24.10-airoha-an7581-stable/target/linux/airoha/dts/an7583.dtsi#L361


Thanks and it proves: that's a no. You cannot have two devices with same
unit address. It means that chip-scu and scu ARE THE SAME devices.

> 


Best regards,
Krzysztof

  reply	other threads:[~2025-07-16 14:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 13:04 [PATCH v2 00/10] clk: add support for Airoha AN7583 clock Christian Marangi
2025-06-17 13:04 ` [PATCH v2 01/10] clk: en7523: convert driver to regmap API Christian Marangi
2025-06-17 13:04 ` [PATCH v2 02/10] clk: en7523: generalize register clocks function Christian Marangi
2025-06-17 13:04 ` [PATCH v2 03/10] clk: en7523: convert to full clk_hw implementation Christian Marangi
2025-06-17 13:04 ` [PATCH v2 04/10] clk: en7523: add support for .set_rate Christian Marangi
2025-06-17 13:04 ` [PATCH v2 05/10] clk: en7523: permit to reference Chip SCU from phandle Christian Marangi
2025-06-17 13:04 ` [PATCH v2 06/10] dt-bindings: clock: airoha: Document new property airoha,chip-scu Christian Marangi
2025-06-27  7:59   ` Krzysztof Kozlowski
2025-06-27  8:20     ` Christian Marangi
2025-07-16 14:29       ` Krzysztof Kozlowski [this message]
2025-07-21 19:06         ` Christian Marangi
2025-06-17 13:04 ` [PATCH v2 07/10] clk: en7523: reword and clean clk_probe variables Christian Marangi
2025-06-17 13:04 ` [PATCH v2 08/10] clk: en7523: add support for probing SCU child Christian Marangi
2025-06-17 13:04 ` [PATCH v2 09/10] dt-bindings: clock: airoha: Document support for AN7583 clock Christian Marangi
2025-06-27  8:00   ` Krzysztof Kozlowski
2025-06-17 13:04 ` [PATCH v2 10/10] clk: en7523: add support for Airoha " Christian Marangi

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=8582dbad-c773-4f46-827a-83b00eed0882@kernel.org \
    --to=krzk@kernel.org \
    --cc=ansuelsmth@gmail.com \
    --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=mturquette@baylibre.com \
    --cc=nbd@nbd.name \
    --cc=p.zabel@pengutronix.de \
    --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®