From: "Michal Vokáč" <michal.vokac@ysoft.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Shawn Guo <shawnguo@kernel.org>,
Petr Benes <petr.benes@ysoft.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Herburger <gregor.herburger@ew.tq-group.com>,
Hiago De Franco <hiago.franco@toradex.com>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
Joao Paulo Goncalves <joao.goncalves@toradex.com>,
Michael Walle <mwalle@kernel.org>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Mathieu Othacehe <m.othacehe@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] Add support for new IMX8MP based board
Date: Tue, 24 Sep 2024 11:37:03 +0200 [thread overview]
Message-ID: <40d982aa-79b9-49f7-b5d8-d7cc2510fe35@ysoft.com> (raw)
In-Reply-To: <vghktkih6pdjrui7sjs2gn2elfcdlplh37ahzcm2xnqin3rh4g@cck4xniyourm>
On 24. 09. 24 10:22, Krzysztof Kozlowski wrote:
> On Mon, Sep 23, 2024 at 05:14:13PM +0200, Michal Vokáč wrote:
>> Hi,
>>
>> this series adds support for a new member in our IOTA platform.
>> The board is based on the i.MX8MP SoC. The first two patches
>> add support for most of the board functionality except USB Type-C
>> port and some other minor things.
>>
>> [PATCH 3] adds new device tree binding for a Diodes Incorporated
>> PI5USB30213A Type-C Controller and [PATCH 4] enables that port on
>> the IOTA2 Lumpy board.
>>
>> We also wrote a driver for that Type-C port controller. I would like
>> to get that driver upstream as well but I expect it will take much
>> more iterations and effort to get it into mainline-ready shape so
>> I intentionally excluded it from this series. AFAIK it should not
>> be a problem to accept a device tree binding for a HW that does not
>> have a driver in the kernel yet.
>
> It's unusual but okay. It will be however more difficult for you - any
> changes in the binding in the future (when writing driver) will be
> rejected on basis of breaking ABI, even if Linux does not use that ABI.
OK, your argument is valid and I would be better on the safer side.
I will remove the binding for the Type-C controller from this series
and post it a bit later including the driver.
I will reduce this series to just add basic support for the board.
Can I keep your R-b tag for the Type-C dt-binding for the future
submission or should I better remove it?
Best regards,
Michal
prev parent reply other threads:[~2024-09-24 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 15:14 [PATCH v3 0/4] Add support for new IMX8MP based board Michal Vokáč
2024-09-23 15:14 ` [PATCH v3 1/4] dt-bindings: arm: Add i.MX8MP IOTA2 Lumpy board Michal Vokáč
2024-09-23 15:14 ` [PATCH v3 2/4] arm64: dts: imx: Add imx8mp-iota2-lumpy board Michal Vokáč
2024-09-24 7:16 ` Marco Felsch
2024-09-24 9:06 ` Michal Vokáč
2024-09-23 15:14 ` [PATCH v3 3/4] dt-bindings: usb: Add Diodes Incorporated PI5USB30213A Type-C Controller Michal Vokáč
2024-09-24 7:24 ` Marco Felsch
2024-09-24 8:21 ` Krzysztof Kozlowski
2024-09-24 9:08 ` Krzysztof Kozlowski
2024-09-24 9:15 ` Marco Felsch
2024-09-23 15:14 ` [PATCH v3 4/4] arm64: dts: imx8mp-iota2: Enable the USB Type-C port Michal Vokáč
2024-09-24 7:23 ` Marco Felsch
2024-09-24 9:08 ` Michal Vokáč
2024-09-24 8:22 ` [PATCH v3 0/4] Add support for new IMX8MP based board Krzysztof Kozlowski
2024-09-24 9:37 ` Michal Vokáč [this message]
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=40d982aa-79b9-49f7-b5d8-d7cc2510fe35@ysoft.com \
--to=michal.vokac@ysoft.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=gregor.herburger@ew.tq-group.com \
--cc=hiago.franco@toradex.com \
--cc=hvilleneuve@dimonoff.com \
--cc=imx@lists.linux.dev \
--cc=joao.goncalves@toradex.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=mwalle@kernel.org \
--cc=petr.benes@ysoft.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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