[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f529c5ef-f61c-4c8b-a589-652aca162f07@kernel.org>
Date: Mon, 19 Aug 2024 17:39:20 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Mathieu Poirier <mathieu.poirier@...aro.org>,
Vignesh Raghavendra <vigneshr@...com>
Cc: Andrew Davis <afd@...com>, Bjorn Andersson <andersson@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Nishanth Menon <nm@...com>,
Tero Kristo <kristo@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>,
Hari Nagalla <hnagalla@...com>, linux-remoteproc@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v11 3/9] remoteproc: k3-m4: Add a remoteproc driver for
M4F subsystem
On 19/08/2024 17:32, Mathieu Poirier wrote:
>>>> Please remove.
>>> Forget this comment since it would cause an error in __rproc_detach().
>>>
>>>> Other than the above I'm good with this driver. That said I can't move forward
>>>> without a nod from the DT crew. I also noticed a fair amount of code
>>>> duplication with the k3_r5 and k3_dsp drivers. Dealing with that should not be
>>>> part of the current work but will need to be done before another k3 driver can
>>>> be merged.
>>>>
>>
>>> The above still apply though.
>>
>> Me or Nishanth will pick up the SoC DT patches via TI SoC tree, once the
>> driver patches are merged. Feel free to ignore those but queue
>> dt-bindings (already has DT maintainers ack) and driver patches via
>> rproc tree.
>>
>
> Can you provide a link where the DT maintainers have acknowledged the bindings?
The reviewed-by tag serves as acknowledgment as well and the binding
patch has it. Conor gave it on some earlier version of the patchset. I
did not check if there were any significant changes in the meantime, though.
Best regards,
Krzysztof
Powered by blists - more mailing lists