[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4260401.mvXUDI8C0e@nukework.gtech>
Date: Tue, 23 Dec 2025 13:45:49 -0600
From: "Alex G." <mr.nuke.me@...il.com>
To: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk@...nel.org>
Cc: andersson@...nel.org, mathieu.poirier@...aro.org, krzk+dt@...nel.org,
Conor Dooley <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org,
linux-remoteproc@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject:
Re: [PATCH 2/9] dt-bindings: remoteproc: qcom: add IPQ9574 image loader
On Saturday, December 20, 2025 2:54:02 AM CST Krzysztof Kozlowski wrote:
> On Fri, Dec 19, 2025 at 08:44:33AM -0600, Rob Herring wrote:
> > On Thu, Dec 18, 2025 at 10:34:10PM -0600, Alexandru Gagniuc wrote:
> > > Document the IPQ9574 native (non-PAS) WCSS image loader. It is similar
> > > to IPQ8074 WCSS, but requires several new clocks. These clocks must be
> > > enabled by the host in non-PAS mode, and are not optional. Add an
> > > example that uses the "qcom,ipq9574-wcss-pil" binding.
Hi Rob and Krzysztof,
> > Is the new example really much different and unique. If not, drop it
> > (especially since it wasn't even tested).
>
> There is simply no example for existing devices, so this is fine. It
> could be mentioned here WHY it is being added, which would solve two
> people's questions (yours and mine earlier). If only people knew and
> said WHY they are doing something.
TIL, I need to put the third patch ("dt-bindings: clock: gcc-ipq9574: add wcss
remoteproc clocks") before this one to resolve dtb check issues with the
example. I'll also add a blurb to the commit message to explain WHY.
Alex
Powered by blists - more mailing lists