From: Krzysztof Kozlowski <krzk@kernel.org>
To: Romain Naour <romain.naour@smile.fr>, devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
conor+dt@kernel.org, krzk+dt@kernel.org, robh@kernel.org,
kristo@kernel.org, vigneshr@ti.com, nm@ti.com,
Romain Naour <romain.naour@skf.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>
Subject: Re: [PATCHv2] arm64: dts: ti: k3-j721e-beagleboneai64: Enable ACSPCIE output for PCIe1
Date: Mon, 2 Dec 2024 11:14:46 +0100 [thread overview]
Message-ID: <dabbad2b-f8a6-4ed7-86da-ec696cf67461@kernel.org> (raw)
In-Reply-To: <20241202101140.48778-1-romain.naour@smile.fr>
On 02/12/2024 11:11, Romain Naour wrote:
> From: Romain Naour <romain.naour@skf.com>
>
> Unlike the SK-TDA4VM (k3-j721e-sk) board, there is no clock generator
> (CDCI6214RGET) on the BeagleBone AI-64 (k3-j721e-beagleboneai64) to
> provide PCIe refclk signal to PCIe Endponts. So the ACSPCIE module must
> provide refclk through PCIe_REFCLK pins.
>
> Use the new "ti,syscon-acspcie-proxy-ctrl" property to enable ACSPCIE
> module's PAD IO Buffers.
>
> Reuse the compatible "ti,j784s4-acspcie-proxy-ctrl" since the ACSPCIE
> buffer and its functionality is the same across all K3 SoCs.
>
> Cc: Siddharth Vadapalli <s-vadapalli@ti.com>
> Signed-off-by: Romain Naour <romain.naour@skf.com>
> ---
> With this patch, we can remove "HACK: Sierra: Drive clock out" patch
> applied on vendor kernel for BeagleBone AI-64:
> https://openbeagle.org/beagleboard/linux/-/commit/ad65d7ef675966cdbc5d75f2bd545fad1914ba9b
>
> v2:
> - use generic style comments
> - use "syscon" as generic node name for "acspcie0_proxy_ctrl" node
> - Keep the compatible "ti,j784s4-acspcie-proxy-ctrl" since the
> ACSPCIE buffer and its functionality is the same across all K3 SoCs.
> (Siddharth Vadapalli)
>
> "The compatible "ti,j784s4-acspcie-pcie-ctrl" should be reused for
> J721E and all other K3 SoCs.
No, it shouldn't and you got comment on this. You always need specific
compatible, see writing bindings doc.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-02 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 10:11 [PATCHv2] arm64: dts: ti: k3-j721e-beagleboneai64: Enable ACSPCIE output for PCIe1 Romain Naour
2024-12-02 10:14 ` Krzysztof Kozlowski [this message]
2024-12-02 10:58 ` Siddharth Vadapalli
2024-12-02 11:07 ` Krzysztof Kozlowski
2024-12-02 11:17 ` Siddharth Vadapalli
2024-12-02 14:53 ` Siddharth Vadapalli
2024-12-02 15:09 ` Krzysztof Kozlowski
2024-12-02 15:45 ` Siddharth Vadapalli
2024-12-02 15:54 ` 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=dabbad2b-f8a6-4ed7-86da-ec696cf67461@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=romain.naour@skf.com \
--cc=romain.naour@smile.fr \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.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