From: Josua Mayer <josua@solid-run.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Yazan Shhady <yazan.shhady@solid-run.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v7 4/4] arm64: dts: ti: hummingboard-t: add overlays for m.2 pci-e and usb-3
Date: Wed, 30 Oct 2024 12:18:15 +0000 [thread overview]
Message-ID: <533c54e5-d024-4fd0-b92d-0f320f25999f@solid-run.com> (raw)
In-Reply-To: <cd02e760-54c6-4a92-af4e-e786d80cfbbd@ti.com>
Am 28.10.24 um 19:44 schrieb Vignesh Raghavendra:
>
> On 28/10/24 22:49, Josua Mayer wrote:
>> Hi Geert, Vignesh,
>>
>> Am 28.10.24 um 16:31 schrieb Vignesh Raghavendra:
>>> On 25/10/24 19:27, Geert Uytterhoeven wrote:
>>>> Hi Josua,
>>>>
>>>> On Mon, Feb 19, 2024 at 4:05 PM Josua Mayer <josua@solid-run.com> wrote:
>>>>> HummingBoard-T features two M.2 connectors labeled "M1" and "M2".
>>>>> The single SerDes lane of the SoC can be routed to either M1 pci-e
>>>>> signals, or M2 usb-3 signals by a gpio-controlled mux.
>>>>>
>>>>> Add overlays for each configuration.
>>>>>
>>>>> Signed-off-by: Josua Mayer <josua@solid-run.com>
>>>> Thanks for your patch, which is now commit bbef42084cc170cb ("arm64:
>>>> dts: ti: hummingboard-t: add overlays for m.2 pci-e and usb-3") in v6.9.
>>>>
>>>>> --- /dev/null
>>>>> +++ b/arch/arm64/boot/dts/ti/k3-am642-hummingboard-t-usb3.dtso
>>>>> @@ -0,0 +1,44 @@
>>>>> +// SPDX-License-Identifier: GPL-2.0+
>>>>> +/*
>>>>> + * Copyright (C) 2023 Josua Mayer <josua@solid-run.com>
>>>>> + *
>>>>> + * Overlay for SolidRun AM642 HummingBoard-T to enable USB-3.1.
>>>>> + */
>>>>> +
>>>>> +/dts-v1/;
>>>>> +/plugin/;
>>>>> +
>>>>> +#include <dt-bindings/phy/phy.h>
>>>>> +
>>>>> +#include "k3-serdes.h"
>>>>> +
>>>>> +&serdes0 {
>>>>> + #address-cells = <1>;
>>>>> + #size-cells = <0>;
>>>>> +
>>>>> + serdes0_link: phy@0 {
>>>>> + reg = <0>;
>>>>> + cdns,num-lanes = <1>;
>>>>> + cdns,phy-type = <PHY_TYPE_USB3>;
>>>>> + #phy-cells = <0>;
>>>>> + resets = <&serdes_wiz0 1>;
>>>>> + };
>>>>> +};
>>>>> +
>>>>> +&serdes_ln_ctrl {
>>>>> + idle-states = <AM64_SERDES0_LANE0_USB>;
>>>>> +};
>>>>> +
>>>>> +&serdes_mux {
>>>>> + idle-state = <0>;
>>>>> +};
>>>>> +
>>>>> +&usbss0 {
>>>>> + /delete-property/ ti,usb2-only;
>>>> /delete-property/ (and /delete-node/) to delete something in the base DTS
>>>> does not work.
>> My understanding is that flags are equivalent to boolean, i.e:
>>
>> ti,usb2-only = <true>;
>> ti,usb2-only;
>>
>> are equivalent.
>>
>> If so, can we assign <false> within the overlay?
>>
>>> Geert,
>>>
>>> Thanks for the catching
>> Excellent spotting indeed.
>> I noticed this in passing about a week ago when I requested
>> Debian enable the necessary drivers in their distro kernel
>> (without understanding the root cause).
>>> Joshua,
>>>
>>> This overlay is pretty useless in light of above issue. I intend to
>>> just drop this file unless you convince me otherwise?
>>>
>> I would really prefer to fix it, or somehow replace with equivalent functionality.
>>
>> My original proposal was having the board a dtsi, and the pci and usb3
>> variants as standalone dts.
>>
>
> Yeah, you would need a separate board dts for this profile. Please
> propose a patch
Is there any chance of reassigning <false> and making an argument
that this should be fixed?
I find it frustrating that overlays can't override boolean properties,
and for consistency reasons I would otherwise change both
pcie and usb3 overlays to standalone dts.
next prev parent reply other threads:[~2024-10-30 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 15:02 [PATCH v7 0/4] arm64: dts: add description for solidrun am642 som and hummingboard evb Josua Mayer
2024-02-19 15:03 ` [PATCH v7 1/4] dt-bindings: arm: ti: Add bindings for SolidRun AM642 HummingBoard-T Josua Mayer
2024-02-19 15:03 ` [PATCH v7 2/4] arm64: dts: ti: k3-am64-main: Add ICSSG IEP nodes Josua Mayer
2024-02-27 14:12 ` Vignesh Raghavendra
2024-02-19 15:03 ` [PATCH v7 3/4] arm64: dts: add description for solidrun am642 som and evaluation board Josua Mayer
2024-02-19 15:03 ` [PATCH v7 4/4] arm64: dts: ti: hummingboard-t: add overlays for m.2 pci-e and usb-3 Josua Mayer
2024-10-25 13:57 ` Geert Uytterhoeven
2024-10-28 15:31 ` Vignesh Raghavendra
2024-10-28 17:19 ` Josua Mayer
2024-10-28 17:57 ` Geert Uytterhoeven
2024-10-28 18:44 ` Vignesh Raghavendra
2024-10-30 12:18 ` Josua Mayer [this message]
2024-11-04 15:56 ` Geert Uytterhoeven
2024-11-12 5:03 ` Josua Mayer
2024-02-27 14:09 ` (subset) [PATCH v7 0/4] arm64: dts: add description for solidrun am642 som and hummingboard evb Vignesh Raghavendra
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=533c54e5-d024-4fd0-b92d-0f320f25999f@solid-run.com \
--to=josua@solid-run.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=yazan.shhady@solid-run.com \
/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