From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chaitanya Sabnis <chaitanya.msabnis@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: dt-bindings: hisilicon: Convert hi6210 I2S to dt-schema
Date: Thu, 19 Mar 2026 10:13:26 +0100 [thread overview]
Message-ID: <20260319-didactic-placid-toucan-afea91@quoll> (raw)
In-Reply-To: <20260319032112.5251-1-chaitanya.msabnis@gmail.com>
On Thu, Mar 19, 2026 at 08:51:12AM +0530, Chaitanya Sabnis wrote:
> Convert the Hisilicon hi6210 I2S controller hardware binding from
> legacy plain text to modern YAML dt-schema format.
You need to document here the differences done during conversion with
explanation. You changed the order of DMA entries.
>
> Signed-off-by: Chaitanya Sabnis <chaitanya.msabnis@gmail.com>
> ---
> .../bindings/sound/hisilicon,hi6210-i2s.txt | 42 ----------
> .../bindings/sound/hisilicon,hi6210-i2s.yaml | 80 +++++++++++++++++++
> 2 files changed, 80 insertions(+), 42 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/sound/hisilicon,hi6210-i2s.txt
> create mode 100644 Documentation/devicetree/bindings/sound/hisilicon,hi6210-i2s.yaml
>
> diff --git a/Documentation/devicetree/bindings/sound/hisilicon,hi6210-i2s.txt b/Documentation/devicetree/bindings/sound/hisilicon,hi6210-i2s.txt
> deleted file mode 100644
> index 7a296784eb37..000000000000
> --- a/Documentation/devicetree/bindings/sound/hisilicon,hi6210-i2s.txt
> +++ /dev/null
> @@ -1,42 +0,0 @@
> -* Hisilicon 6210 i2s controller
> -
> -Required properties:
> -
> -- compatible: should be one of the following:
> - - "hisilicon,hi6210-i2s"
> -- reg: physical base address of the i2s controller unit and length of
> - memory mapped region.
> -- interrupts: should contain the i2s interrupt.
> -- clocks: a list of phandle + clock-specifier pairs, one for each entry
> - in clock-names.
> -- clock-names: should contain following:
> - - "dacodec"
> - - "i2s-base"
> -- dmas: DMA specifiers for tx dma. See the DMA client binding,
> - Documentation/devicetree/bindings/dma/dma.txt
> -- dma-names: should be "tx" and "rx"
...
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: HiSilicon hi6210 I2S controller
> +
> +maintainers:
> + - Chaitanya Sabnis <chaitanya.msabnis@gmail.com>
This should be someone with datasheet or hardware, e.g.: device driver
maintainer or platform maintainer. Unless you have datasheet or
hardware?
> +
> +allOf:
> + - $ref: dai-common.yaml#
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-19 9:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 3:21 [PATCH v2] ASoC: dt-bindings: hisilicon: Convert hi6210 I2S to dt-schema Chaitanya Sabnis
2026-03-19 9:13 ` Krzysztof Kozlowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-19 3:08 Chaitanya Sabnis
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=20260319-didactic-placid-toucan-afea91@quoll \
--to=krzk@kernel.org \
--cc=broonie@kernel.org \
--cc=chaitanya.msabnis@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@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