From: Andreas Kemnade <andreas@kemnade.info>
To: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
Cc: linux-kernel@vger.kernel.org, peter.ujfalusi@gmail.com,
dmitry.torokhov@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
lgirdwood@gmail.com, tiwai@suse.com, conor+dt@kernel.org,
lee@kernel.org, ukleinek@kernel.org, broonie@kernel.org,
gregkh@linuxfoundation.org, linux-input@vger.kernel.org,
devicetree@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-sound@vger.kernel.org, linux-usb@vger.kernel.org,
shuah@kernel.org
Subject: Re: [PATCH v2 2/9] mfd: dt-bindings: ti,twl6040: convert to DT schema
Date: Thu, 14 Aug 2025 16:27:20 +0200 [thread overview]
Message-ID: <20250814162720.342a27e7@akair> (raw)
In-Reply-To: <20250814132129.138943-3-jihed.chaibi.dev@gmail.com>
Am Thu, 14 Aug 2025 15:21:22 +0200
schrieb Jihed Chaibi <jihed.chaibi.dev@gmail.com>:
> Convert the legacy TXT binding for the TWL6040 MFD to the modern YAML
> DT schema format. This adds formal validation and improves documentation
> for the TWL6040/TWL6041 audio codec, which provides audio, vibra, and GPO
> functionality on OMAP4+ platforms.
>
> Changes in v2:
> - Renamed twl6040,audpwron-gpio to ti,audpwron-gpio for consistency
> with TI naming, this fixes the dt_binding_check vendor name error.
> - Minor description clarifications for improved readability.
>
> Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
This is unrelated to the PMIC stuff and can be handled separely, I would
propose to send it separately and not part of this series in further
submissions.
Regards,
Andreas
next prev parent reply other threads:[~2025-08-14 14:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:21 [PATCH v2 0/9] dt-bindings: Convert TWL4030/6040 family binding to DT schema Jihed Chaibi
2025-08-14 13:21 ` [PATCH v2 1/9] mfd: dt-bindings: ti,twl4030-audio: convert " Jihed Chaibi
2025-08-14 13:21 ` [PATCH v2 2/9] mfd: dt-bindings: ti,twl6040: " Jihed Chaibi
2025-08-14 14:27 ` Andreas Kemnade [this message]
2025-08-14 13:21 ` [PATCH v2 3/9] input: dt-bindings: ti,twl4030-keypad: " Jihed Chaibi
2025-08-14 18:35 ` Dmitry Torokhov
2025-08-14 13:21 ` [PATCH v2 4/9] mfd: dt-bindings: ti,twl4030-power: " Jihed Chaibi
2025-08-14 14:10 ` Andreas Kemnade
2025-08-14 13:21 ` [PATCH v2 5/9] pwm: dt-bindings: ti,twl-pwm: " Jihed Chaibi
2025-08-14 13:21 ` [PATCH v2 6/9] pwm: dt-bindings: ti,twl-pwmled: " Jihed Chaibi
2025-08-14 13:21 ` [PATCH v2 7/9] Documentation: omap-twl4030: " Jihed Chaibi
2025-08-14 13:33 ` Mark Brown
2025-08-14 14:27 ` Jihed Chaibi
2025-08-14 13:21 ` [PATCH v2 8/9] usb: dt-bindings: ti,twlxxxx-usb: " Jihed Chaibi
2025-08-14 13:21 ` [PATCH v2 9/9] dt-bindings: mfd: twl: Add missing sub-nodes for TWL4030 & TWL603x Jihed Chaibi
2025-08-14 14:22 ` Andreas Kemnade
2025-08-15 15:00 ` [PATCH v2 0/9] dt-bindings: Convert TWL4030/6040 family binding to DT schema Andreas Kemnade
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=20250814162720.342a27e7@akair \
--to=andreas@kemnade.info \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jihed.chaibi.dev@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=robh@kernel.org \
--cc=shuah@kernel.org \
--cc=tiwai@suse.com \
--cc=ukleinek@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;
as well as URLs for NNTP newsgroup(s).