From: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
To: robh@kernel.org
Cc: gregkh@linuxfoundation.org, krzk+dt@kernel.org,
conor+dt@kernel.org, peter.ujfalusi@gmail.com,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, shuah@kernel.org,
jihed.chaibi.dev@gmail.com
Subject: [PATCH v6 0/2] usb: dt-bindings: ti,twlxxxx-usb: convert to DT schema
Date: Fri, 22 Aug 2025 22:17:25 +0200 [thread overview]
Message-ID: <20250822201727.71593-1-jihed.chaibi.dev@gmail.com> (raw)
Hello,
This series converts the legacy TXT bindings for the TI TWL4030
and TWL6030 USB modules to the modern YAML DT schema format.
This version (v6) addresses maintainer feedback by defining the
'interrupts' property with a list of 'items' for better clarity and
validation.
With the conversion complete, the second patch in this series removes
the now-obsolete .txt binding file.
Thank you,
Jihed
---
Changes in v6:
- Reworked 'interrupts' property in both patches to use a list of
items with descriptions, per reviewer feedback.
Changes in v5:
- Split combined twlxxxx-usb binding into two dedicated files
for TWL4030 and TWL6030 per maintainer feedback.
- Used more accurate header file for interrupt macros.
- Improved formatting in the examples.
- Patch 2/2 removes the old .txt file.
Changes in v4:
- This patch is split from larger series per maintainer feedback.
- v3 link:
https://lore.kernel.org/all/20250816021523.167049-1-jihed.chaibi.dev@gmail.com/
- Removed i2c node as it wasn't required by the old binding file.
- Updated node names to 'usb' and 'usb-phy' in the examples to follow
generic naming conventions per the Device Tree specification.
- Replaced raw interrupt values with standard defines for clarity.
- Improved formatting in the examples for clarity and consistency.
Changes in v3:
- No changes.
Changes in v2:
- Added '#phy-cells' property to support PHY framework integration.
Jihed Chaibi (2):
usb: dt-bindings: ti,twl4030-usb: convert to DT schema
usb: dt-bindings: ti,twl6030-usb: convert to DT schema
.../bindings/usb/ti,twl4030-usb.yaml | 74 +++++++++++++++++++
.../bindings/usb/ti,twl6030-usb.yaml | 48 ++++++++++++
.../devicetree/bindings/usb/twlxxxx-usb.txt | 43 -----------
3 files changed, 122 insertions(+), 43 deletions(-)
create mode 100644 Documentation/devicetree/bindings/usb/ti,twl4030-usb.yaml
create mode 100644 Documentation/devicetree/bindings/usb/ti,twl6030-usb.yaml
delete mode 100644 Documentation/devicetree/bindings/usb/twlxxxx-usb.txt
--
2.39.5
next reply other threads:[~2025-08-22 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 20:17 Jihed Chaibi [this message]
2025-08-22 20:17 ` [PATCH v6 1/2] usb: dt-bindings: ti,twl4030-usb: convert to DT schema Jihed Chaibi
2025-08-24 9:17 ` Krzysztof Kozlowski
2025-08-22 20:17 ` [PATCH v6 2/2] usb: dt-bindings: ti,twl6030-usb: " Jihed Chaibi
2025-08-24 9:18 ` Krzysztof Kozlowski
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=20250822201727.71593-1-jihed.chaibi.dev@gmail.com \
--to=jihed.chaibi.dev@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=robh@kernel.org \
--cc=shuah@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).