From: Krzysztof Kozlowski <krzk@kernel.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>,
Conor Dooley <conor@kernel.org>
Cc: vkoul@kernel.org, kishon@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: phy: lan966x: Add optional microchip,sx-tx/rx-inverted
Date: Tue, 11 Nov 2025 11:06:02 +0100 [thread overview]
Message-ID: <58b0d712-48a4-4490-a63f-404716844557@kernel.org> (raw)
In-Reply-To: <20251111095831.lp4kvdfcahtwgrqc@DEN-DL-M31836.microchip.com>
On 11/11/2025 10:58, Horatiu Vultur wrote:
> The 11/10/2025 18:43, Conor Dooley wrote:
>
> Hi Conor,
>
>> On Mon, Nov 10, 2025 at 12:05:36PM +0100, Horatiu Vultur wrote:
>>> This allows to invert the N and P signals of the RX and TX Serdes
>>> signals. This option allows the board designer to trace their signals
>>> easier on the boards.
>>
>> Why can't this just be done in software, debugfs or something like that?
>> Maybe it's just your description is poor, but sounds like the intention
>> here is to just switch things around for debug purposes.
>
> I don't think it should be done through debugfs. As this describes the
> board layout and I don't think someone will want to change it at
> runtime to see how things behave. So maybe the description is poor.
You said it is purely for hardware designer to trace signals, so sorry,
but that's not DTs purpose.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-11 10:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 11:05 [PATCH 0/2] phy: microchip: lan966x: Allow to invert N and P signals Horatiu Vultur
2025-11-10 11:05 ` [PATCH 1/2] phy: microchip: lan966x: Add support for inverting the rx/tx lanes Horatiu Vultur
2025-11-10 11:05 ` [PATCH 2/2] dt-bindings: phy: lan966x: Add optional microchip,sx-tx/rx-inverted Horatiu Vultur
2025-11-10 18:43 ` Conor Dooley
2025-11-11 9:58 ` Horatiu Vultur
2025-11-11 10:06 ` Krzysztof Kozlowski [this message]
2025-11-11 17:39 ` Conor Dooley
2025-11-12 8:02 ` Horatiu Vultur
2025-11-12 18:32 ` Conor Dooley
2025-11-13 11:56 ` Horatiu Vultur
2025-11-13 19:13 ` Conor Dooley
2025-11-10 11:42 ` [PATCH 0/2] phy: microchip: lan966x: Allow to invert N and P signals Vladimir Oltean
2025-11-11 9:50 ` Horatiu Vultur
2025-11-13 16:30 ` Vladimir Oltean
2025-11-14 10:34 ` Horatiu Vultur
2025-11-19 19:23 ` Vladimir Oltean
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=58b0d712-48a4-4490-a63f-404716844557@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=horatiu.vultur@microchip.com \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=robh@kernel.org \
--cc=vkoul@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).