From: Krzysztof Kozlowski <krzk@kernel.org>
To: joakim.zhang@cixtech.com
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, perex@perex.cz,
tiwai@suse.com, linux-sound@vger.kernel.org,
devicetree@vger.kernel.org, cix-kernel-upstream@cixtech.com
Subject: Re: [PATCH V1 1/3] dt-bindings: sound: add binding for CIX IPBLOQ HDA controller
Date: Fri, 31 Oct 2025 09:58:48 +0100 [thread overview]
Message-ID: <20251031-pearl-pheasant-from-atlantis-bf4e7a@kuoka> (raw)
In-Reply-To: <20251030110928.1572703-2-joakim.zhang@cixtech.com>
On Thu, Oct 30, 2025 at 07:09:26PM +0800, joakim.zhang@cixtech.com wrote:
> From: Joakim Zhang <joakim.zhang@cixtech.com>
>
> This patch adds binding for CIX IPBLOQ HDA controller.
Please do not use "This commit/patch/change", but imperative mood. See
longer explanation here:
https://elixir.bootlin.com/linux/v6.16/source/Documentation/process/submitting-patches.rst#L94
Please use standard email subjects, so with the PATCH keyword in the
title. 'git format-patch -vX' helps here to create proper versioned patches.
Another useful tool is b4. Skipping the PATCH keyword makes filtering of
emails more difficult thus making the review process less convenient.
A nit, subject: drop second/last, redundant "binding for". The
"dt-bindings" prefix is already stating that these are bindings.
See also:
https://elixir.bootlin.com/linux/v6.17-rc3/source/Documentation/devicetree/bindings/submitting-patches.rst#L18
>
> Signed-off-by: Joakim Zhang <joakim.zhang@cixtech.com>
> ---
> .../bindings/sound/cix,ipbloq-hda.yaml | 69 +++++++++++++++++++
> 1 file changed, 69 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/sound/cix,ipbloq-hda.yaml
>
> diff --git a/Documentation/devicetree/bindings/sound/cix,ipbloq-hda.yaml b/Documentation/devicetree/bindings/sound/cix,ipbloq-hda.yaml
> new file mode 100644
> index 000000000000..a4285d1e0319
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/sound/cix,ipbloq-hda.yaml
Filename must match the compatible. See writing bindings doc.
> @@ -0,0 +1,69 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/sound/cix,ipbloq-hda.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: CIX IPBLOQ HDA controller
> +
> +description: |
Do not need '|' unless you need to preserve formatting.
> + CIX IPBLOQ High Definition Audio (HDA) Controller driver.
driver as in Linux driver? No, please describe here briefly hardware.
> +
> +maintainers:
> + - Joakim Zhang <joakim.zhang@cixtech.com>
> +
> +properties:
> + compatible:
> + const: cix,sky1-ipbloq-hda
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + description: The interrupt from the HDA controller
Drop description, obvious. Cannot be anything else.
> + maxItems: 1
> +
> + clocks:
> + maxItems: 2
You should list the items instead with description.
> +
> + clock-names:
> + maxItems: 2
No, you need to list the items. There is no syntax like that.
> +
> + resets:
> + maxItems: 1
> +
> + reset-names:
> + maxItems: 1
No, you need to list the items.
> +
> + cix,model:
> + $ref: /schemas/types.yaml#/definitions/string
Use standard properties, see other bindings. Maybe ones from
generic/simple audio card fit.
> + description: |
Do not need '|' unless you need to preserve formatting.
> + The user-visible name of this sound complex. If this property is
> + not specified then boards can use default name provided in hda driver.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - clocks
> + - clock-names
> + - resets
> + - reset-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include<dt-bindings/interrupt-controller/arm-gic.h>
> +
> + audss_ipb_hda: ipb-hda@70c0000 {
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
If you cannot find a name matching your device, please check in kernel
sources for similar cases or you can grow the spec (via pull request to
DT spec repo).
e.g. sound or sound-card. Maybe hda, if it is known enough.
Also drop unused label.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-31 8:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 11:09 [PATCH V1 0/3] ALSA: hda: add CIX IPBLOQ HDA controller support joakim.zhang
2025-10-30 11:09 ` [PATCH V1 1/3] dt-bindings: sound: add binding for CIX IPBLOQ HDA controller joakim.zhang
2025-10-31 8:58 ` Krzysztof Kozlowski [this message]
2025-10-31 9:28 ` Krzysztof Kozlowski
2025-10-31 14:57 ` Conor Dooley
2025-11-03 10:36 ` Joakim Zhang
2025-10-30 11:09 ` [PATCH V1 2/3] ALSA: hda: add bus callback for address translation joakim.zhang
2025-10-31 11:28 ` Takashi Iwai
2025-11-03 11:30 ` Joakim Zhang
2025-11-27 9:44 ` Joakim Zhang
2025-11-28 17:22 ` Takashi Iwai
2025-12-01 8:14 ` Joakim Zhang
2025-12-01 8:41 ` Takashi Iwai
2025-12-01 10:58 ` Joakim Zhang
2025-10-30 11:09 ` [PATCH V1 3/3] ALSA: hda: add CIX IPBLOQ HDA controller support joakim.zhang
2025-10-31 9:05 ` Krzysztof Kozlowski
2025-10-31 9:57 ` Takashi Iwai
2025-11-03 10:43 ` Joakim Zhang
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=20251031-pearl-pheasant-from-atlantis-bf4e7a@kuoka \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joakim.zhang@cixtech.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=tiwai@suse.com \
/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