From: Conor Dooley <conor@kernel.org>
To: Alex Elder <elder@riscstar.com>
Cc: p.zabel@pengutronix.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, mohd.anwar@oss.qualcomm.com,
lorenzo.bianconi@oss.qualcomm.com, danielt@kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Thompson <daniel@riscstar.com>
Subject: Re: [PATCH 1/2] dt-bindings: reset: introduce toshiba,tc9564-reset.yaml
Date: Mon, 12 Oct 2026 19:51:18 +0100 [thread overview]
Message-ID: <20261012-shale-rosy-805c49f6c404@spud> (raw)
In-Reply-To: <20261012164354.3872326-2-elder@riscstar.com>
[-- Attachment #1: Type: text/plain, Size: 4761 bytes --]
On Mon, Oct 12, 2026 at 11:43:52AM -0500, Alex Elder wrote:
> Define the binding for the reset controller functionality present in
> the Toshiba TC9564 SoC.
>
> Co-developed-by: Daniel Thompson <daniel@riscstar.com>
> Signed-off-by: Daniel Thompson <daniel@riscstar.com>
> Signed-off-by: Alex Elder <elder@riscstar.com>
> ---
> .../bindings/reset/toshiba,tc9564-reset.yaml | 56 +++++++++++++++++++
> MAINTAINERS | 7 +++
> include/dt-bindings/reset/toshiba,tc9564.h | 26 +++++++++
> 3 files changed, 89 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reset/toshiba,tc9564-reset.yaml
> create mode 100644 include/dt-bindings/reset/toshiba,tc9564.h
>
> diff --git a/Documentation/devicetree/bindings/reset/toshiba,tc9564-reset.yaml b/Documentation/devicetree/bindings/reset/toshiba,tc9564-reset.yaml
> new file mode 100644
> index 0000000000000..1908e9539abac
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/reset/toshiba,tc9564-reset.yaml
> @@ -0,0 +1,56 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/reset/toshiba,tc9564-reset.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Toshiba TC9564 Reset Controller
> +
> +maintainers:
> + - Alex Elder <elder@riscstar.com>
> + - Daniel Thompson <daniel@riscstar.com>
> +
> +description:
> + The Toshiba TC9564 is an SoC accessed by a host system through the
> + upstream PCIe port on the PCIe switch it implements. The switch
> + includes an embedded PCIe endpoint that provides access to various
> + SoC peripherals (including a reset controller) via its BARs.
> +
> + A total of 13 resets are implemented, though two of these are not
> + controllable. Access to the reset controller relies on PCIe being
> + functional, so the PCIe reset is assumed to be deasserted. Similarly,
> + the PCIe controller relies on I2C, so the I2C reset is also assumed
> + to be deasserted.
> +
> + Reset ids are defined in <dt-bindings/reset/toshiba,tc9564.h>.
> +
> + The reset controller uses registers within the same page as a
> + clock controller, so both devices are defined as children of a
> + "config" syscon.
> +
> +properties:
> + compatible:
> + const: toshiba,tc9564-reset
Why does this need to exist as a standalone device, rather than be
rolled up into the parent syscon node? It doesn't have any resources, so
it should be doable.
This kind of thing for a syscon is always difficult to review when only
one element is present - where is the rest of the syscon's
functionality?
Thanks,
Conor.
> +
> + "#reset-cells":
> + const: 1
> +
> +required:
> + - compatible
> + - "#reset-cells"
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/reset/toshiba,tc9564.h>
> +
> + syscon@0 {
> + compatible = "syscon", "simple-mfd";
> + reg = <0x0 0x2000>;
> +
> + reset {
> + compatible = "toshiba,tc9564-reset";
> + #reset-cells = <1>;
> + };
> + };
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 252b6d7ee1638..d0eb44079fe17 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -28180,6 +28180,13 @@ S: Maintained
> F: Documentation/devicetree/bindings/misc/pci1179,0220.yaml
> F: drivers/misc/tc9564-pci.c
>
> +TOSHIBA TC9564 RESET DRIVER
> +M: Alex Elder <elder@kernel.org>
> +M: Daniel Thompson <danielt@kernel.org>
> +S: Maintained
> +F: Documentation/devicetree/bindings/reset/toshiba,tc9564-reset.yaml
> +F: include/dt-bindings/reset/toshiba,tc9564.h
> +
> TOSHIBA WMI HOTKEYS DRIVER
> M: Azael Avalos <coproscefalo@gmail.com>
> L: platform-driver-x86@vger.kernel.org
> diff --git a/include/dt-bindings/reset/toshiba,tc9564.h b/include/dt-bindings/reset/toshiba,tc9564.h
> new file mode 100644
> index 0000000000000..5fcc9a06d4ff6
> --- /dev/null
> +++ b/include/dt-bindings/reset/toshiba,tc9564.h
> @@ -0,0 +1,26 @@
> +/* SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) */
> +
> +/*
> + * Copyright (C) 2026 by RISCstar Solutions Corporation. All rights reserved.
> + */
> +
> +#ifndef __RESET_TOSHIBA_TC9564_H__
> +#define __RESET_TOSHIBA_TC9564_H__
> +
> +/* Reset IDs */
> +
> +#define RESET_MCU 0
> +#define RESET_MCU1 1
> +#define RESET_MSIGEN 2
> +#define RESET_INTC 3
> +#define RESET_UART 4
> +
> +#define RESET_MAC0_MAC 5
> +#define RESET_MAC0_PMA 6
> +#define RESET_MAC0_XPCS 7
> +
> +#define RESET_MAC1_MAC 8
> +#define RESET_MAC1_PMA 9
> +#define RESET_MAC1_XPCS 10
> +
> +#endif /* __RESET_TOSHIBA_TC9564_H__*/
> --
> 2.53.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-10-12 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 16:43 [PATCH 0/2] reset: introduce TC9564 reset support Alex Elder
2026-10-12 16:43 ` [PATCH 1/2] dt-bindings: reset: introduce toshiba,tc9564-reset.yaml Alex Elder
2026-10-12 16:48 ` sashiko-bot
2026-10-12 17:01 ` Alex Elder
2026-10-12 18:51 ` Conor Dooley [this message]
2026-10-12 19:10 ` Alex Elder
2026-10-12 21:22 ` Conor Dooley
2026-10-13 9:25 ` Krzysztof Kozlowski
2026-10-12 16:43 ` [PATCH 2/2] reset: toshiba: introduce a TC9564 SoC reset driver Alex Elder
2026-10-12 16:54 ` sashiko-bot
2026-10-12 17:01 ` Alex Elder
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=20261012-shale-rosy-805c49f6c404@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel@riscstar.com \
--cc=danielt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@riscstar.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.bianconi@oss.qualcomm.com \
--cc=mohd.anwar@oss.qualcomm.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@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