linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Primoz Fiser <primoz.fiser@norik.com>
To: Wadim Egorov <w.egorov@phytec.de>,
	Stefan Wahren <wahrenst@gmx.net>,
	Mathieu Othacehe <othacehe@gnu.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>, Li Yang <leoyang.li@nxp.com>,
	Christoph Stoidner <c.stoidner@phytec.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, upstream@lists.phytec.de
Subject: Re: [PATCH v4 3/3] arm64: dts: imx93: Add phyBOARD-Segin-i.MX93 support
Date: Thu, 25 Jan 2024 07:12:13 +0100	[thread overview]
Message-ID: <26efc165-7319-434a-82b3-b557949f671d@norik.com> (raw)
In-Reply-To: <13f6edd6-f3ae-4e32-88e9-03355d78153c@phytec.de>

Hi,

On 25. 01. 24 07:05, Wadim Egorov wrote:
> 
> Am 24.01.24 um 18:28 schrieb Stefan Wahren:
>> Hello Mathieu,
>>
>> Am 24.01.24 um 14:48 schrieb Mathieu Othacehe:
>>> Hello Stefan,
>>>
>>>>> Defining line names should be fine. But I would still prefer to have
>>>>> the muxing in an overlay bound to a specific use case.
>>>> I'm fine with this. Unfortunately Mathieu dropped the line names in V5
>>>> today :-(
>>>>
>>>> AFAIR reviewers should have 2 weeks time maximum. This was just 2 days.
>>> I am sorry but it is not easy for me to deal with contradictory input. I
>>> chose to remove the gpio-line-names even though it also seemed like a
>>> nice addition to me. The idea was to not interfere with Phytec plans in
>>> the future.
>> tbh sending v5 before the discussion between Wadim and me was finished
>> made it more complicated. Please keep in mind that some reviewers do
>> this in their spare time, so a response could take some time.
>>
>> In this particular case Wadim and me agreed on a solution, so no action
>> from your side was necessary except a little bit patience.
>>
>> The reason why i suggested the gpio-line-names in the first place is
>> that users doesn't need to care about different versions of the DT files
>> (except the downstream one). Changing the line names afterwards leads to
>> confusion.
>>
>> So before we discuss on a v6, just a question: are on the X16 connector
>> just 2 pins muxable as GPIO? This is hard to believe.
> 
> In theory you can use more of the Pins as GPIOs. But at this point I
> should mention that the Segin board became slightly more complicated
> since it started to support more SoMs with different SoCs. We have
> routings for various pins to help with the compatibility. So the naming
> in the schematics is not really trivial. And IMO the dt should follow
> the naming of the schematics.
> 
> I would prefer to go with v5 without having any namings for now.
> 
> Regards,
> Wadim

This would also be my preference.

Thanks,

BR,
Primoz


  reply	other threads:[~2024-01-25  6:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22  9:53 [PATCH v4 0/3] Add phyBOARD-Segin-i.MX93 support Mathieu Othacehe
2024-01-22  9:53 ` [PATCH v4 1/3] dt-bindings: arm: fsl: Add phyBOARD-Segin-i.MX93 Mathieu Othacehe
2024-01-22  9:53 ` [PATCH v4 2/3] dt-bindings: gpio: gpio-vf610: add gpio-line-names Mathieu Othacehe
2024-01-22 12:32   ` Stefan Wahren
2024-01-22 18:01   ` Conor Dooley
2024-01-22  9:53 ` [PATCH v4 3/3] arm64: dts: imx93: Add phyBOARD-Segin-i.MX93 support Mathieu Othacehe
2024-01-23  6:11   ` Wadim Egorov
2024-01-23  7:42     ` Stefan Wahren
2024-01-23  8:25       ` Wadim Egorov
2024-01-23 10:21         ` Stefan Wahren
2024-01-24  5:13           ` Wadim Egorov
2024-01-24 11:39             ` Stefan Wahren
2024-01-24 13:48               ` Mathieu Othacehe
2024-01-24 17:28                 ` Stefan Wahren
2024-01-25  6:05                   ` Wadim Egorov
2024-01-25  6:12                     ` Primoz Fiser [this message]
2024-01-25  7:41                     ` Stefan Wahren
2024-01-23  7:44     ` Mathieu Othacehe
2024-01-23  8:34   ` Primoz Fiser

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=26efc165-7319-434a-82b3-b557949f671d@norik.com \
    --to=primoz.fiser@norik.com \
    --cc=c.stoidner@phytec.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=othacehe@gnu.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=upstream@lists.phytec.de \
    --cc=w.egorov@phytec.de \
    --cc=wahrenst@gmx.net \
    /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).