Linux clock framework development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alex Elder <elder@riscstar.com>,
	sboyd@kernel.org, bmasney+clk@redhat.com,
	jbrunet+clk@baylibre.com, p.zabel@pengutronix.de,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Cc: daniel@riscstar.com, mohd.anwar@oss.qualcomm.com,
	lorenzo.bianconi@oss.qualcomm.com, fabrice.gasnier@foss.st.com,
	alexandre.torgue@foss.st.com, marex@nabladev.com,
	changhuang.liang@starfivetech.com, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] soc: toshiba: tc9564: add a new syscon driver
Date: Thu, 12 Nov 2026 10:01:16 +0100	[thread overview]
Message-ID: <83e3e025-f877-4dfd-bc84-2cc90b601884@kernel.org> (raw)
In-Reply-To: <20261104004332.2141282-3-elder@riscstar.com>

On 04/11/2026 01:43, Alex Elder wrote:
> Introduce a new system controller driver for devices found within the
> Toshiba TC9564 SoC.  The system controller manages access to an 8 KB
> region, and implements controllers for a set of clocks as well as a
> set of resets.  The region also includes registers that indicate when
> initialization is done for the chip's two Ethernet interfaces.
> 
> The SoC has a single 25 MHz input clock, and from that derives clocks
> of various rates used by functional blocks within the chip.
> 
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
>  MAINTAINERS                         |  1 +
>  drivers/soc/Kconfig                 |  1 +
>  drivers/soc/Makefile                |  1 +
>  drivers/soc/toshiba/Kconfig         | 12 +++++++++
>  drivers/soc/toshiba/Makefile        |  3 +++
>  drivers/soc/toshiba/tc9564-syscon.c | 42 +++++++++++++++++++++++++++++
>  6 files changed, 60 insertions(+)
>  create mode 100644 drivers/soc/toshiba/Kconfig
>  create mode 100644 drivers/soc/toshiba/Makefile
>  create mode 100644 drivers/soc/toshiba/tc9564-syscon.c
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2b1b29169e0e9..c25ee6e0f1c68 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -28345,6 +28345,7 @@ M:	Alex Elder <elder@kernel.org>
>  M:	Daniel Thompson <danielt@kernel.org>
>  S:	Maintained
>  F:	Documentation/devicetree/bindings/soc/toshiba/toshiba,tc9564-config-syscon.yaml
> +F:	drivers/soc/toshiba/tc9564-syscon.c

No, this has to stop. There IS NO TOSHIBA SOC here, how we understand SoC.

drivers/soc/ are ONLY for SoCs running Linux, not for regular devices,
which you are describing here. You have standard PCI device, not
drivers/soc/

And if this was Toshiba SoC, you did not even Cc Toshiba maintainer.

Nacked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>


Best regards,
Krzysztof

  parent reply	other threads:[~2026-11-12  9:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  0:43 [PATCH 0/4] soc: toshiba: tc9564: config system controller Alex Elder
2026-11-04  0:43 ` [PATCH 1/4] dt-bindings: soc: introduce toshiba,tc9564-config-syscon.yaml Alex Elder
2026-11-05  0:25   ` Conor Dooley
2026-11-05  0:28   ` Conor Dooley
2026-11-05  2:09     ` Alex Elder
2026-11-05 20:23   ` Krzysztof Kozlowski
2026-11-09 17:41     ` Alex Elder
2026-11-12  9:04   ` Krzysztof Kozlowski
2026-11-04  0:43 ` [PATCH 2/4] soc: toshiba: tc9564: add a new syscon driver Alex Elder
2026-11-04  0:50   ` sashiko-bot
2026-11-04 21:22     ` Alex Elder
2026-11-12  9:01   ` Krzysztof Kozlowski [this message]
2026-11-04  0:43 ` [PATCH 3/4] clk: toshiba: introduce a TC9564 SoC clock driver Alex Elder
2026-11-04  0:54   ` sashiko-bot
2026-11-04 21:22     ` Alex Elder
2026-11-04  0:43 ` [PATCH 4/4] reset: toshiba: introduce a TC9564 SoC reset driver Alex Elder
2026-11-04  9:49   ` Philipp Zabel
2026-11-04 21:22     ` Alex Elder
2026-11-05 20:26 ` [PATCH 0/4] soc: toshiba: tc9564: config system controller Krzysztof Kozlowski
2026-11-06  1:50   ` Alex Elder
2026-11-09 17:42   ` Alex Elder
2026-11-12  9:01     ` Krzysztof Kozlowski

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=83e3e025-f877-4dfd-bc84-2cc90b601884@kernel.org \
    --to=krzk@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=bmasney+clk@redhat.com \
    --cc=changhuang.liang@starfivetech.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel@riscstar.com \
    --cc=devicetree@vger.kernel.org \
    --cc=elder@riscstar.com \
    --cc=fabrice.gasnier@foss.st.com \
    --cc=jbrunet+clk@baylibre.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.bianconi@oss.qualcomm.com \
    --cc=marex@nabladev.com \
    --cc=mohd.anwar@oss.qualcomm.com \
    --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