From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alexey Charkov <alchark@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] dt-bindings: soc: Add VIA/WonderMedia SoC identification
Date: Fri, 25 Apr 2025 12:20:59 +0200 [thread overview]
Message-ID: <b32ac98d-6db7-493e-a780-5c4943111184@kernel.org> (raw)
In-Reply-To: <20250423-wmt-soc-driver-v1-1-bd8bf32521c2@gmail.com>
On 23/04/2025 21:18, Alexey Charkov wrote:
> VIA/WonderMedia SoC's have a chip ID register inside their system
> configuration controller space, which can be used to identify
> appropriate hardware quirks at runtime. Add binding for it.
>
> Signed-off-by: Alexey Charkov <alchark@gmail.com>
> ---
> .../devicetree/bindings/soc/vt8500/via,scc-id.yaml | 37 ++++++++++++++++++++++
chipid should probably go to hwinfo directory in bindings.
> 1 file changed, 37 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/vt8500/via,scc-id.yaml b/Documentation/devicetree/bindings/soc/vt8500/via,scc-id.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..eac72bd66fd6331c8d9316288bc1acc3e337efaa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/vt8500/via,scc-id.yaml
> @@ -0,0 +1,37 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/soc/vt8500/via,scc-id.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: VIA/WonderMedia SoC system configuration information
> +
> +maintainers:
> + - Alexey Charkov <alchark@gmail.com>
> +
> +description:
> + The system configuration controller on VIA/WonderMedia SoC's contains a chip
> + identifier and revision used to differentiate between different hardware
> + versions of on-chip IP blocks having their own peculiarities which may or
> + may not be captured by their respective DT compatible strings
> +
> +properties:
> + compatible:
> + items:
> + - const: via,scc-id
Compatible based on SoC (and then also keep filename matching it).
> +
> + reg:
> + maxItems: 1
> +
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-25 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 19:18 [PATCH 0/3] ARM: vt8500: Add runtime SoC version identification Alexey Charkov
2025-04-23 19:18 ` [PATCH 1/3] dt-bindings: soc: Add VIA/WonderMedia SoC identification Alexey Charkov
2025-04-25 10:20 ` Krzysztof Kozlowski [this message]
2025-04-23 19:18 ` [PATCH 2/3] soc: Add VIA/WonderMedia SoC identification driver Alexey Charkov
2025-04-25 10:24 ` Krzysztof Kozlowski
2025-04-25 12:15 ` Alexey Charkov
2025-04-23 19:18 ` [PATCH 3/3] ARM: dts: vt8500: add DT nodes for the system config ID register Alexey Charkov
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=b32ac98d-6db7-493e-a780-5c4943111184@kernel.org \
--to=krzk@kernel.org \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®