[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1697b03c-56ab-4e8b-a268-f9ceeed91c31@linaro.org>
Date: Tue, 5 Mar 2024 22:09:18 +0100
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Sriram Dash <quic_sriramd@...cinc.com>, andersson@...nel.org,
vkoul@...nel.org, kishon@...nel.org, robh@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
gregkh@...uxfoundation.org, quic_wcheng@...cinc.com,
Thinh.Nguyen@...opsys.com, p.zabel@...gutronix.de,
linux-arm-msm@...r.kernel.org, linux-phy@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-usb@...r.kernel.org, quic_psodagud@...cinc.com,
quic_nkela@...cinc.com, manivannan.sadhasivam@...aro.org,
ulf.hansson@...aro.org, sudeep.holla@....com, quic_shazhuss@...cinc.com
Subject: Re: [RFC 0/3] Enable firmware-managed USB resources on Qcom targets
On 3/5/24 17:57, Sriram Dash wrote:
> Some target systems allow multiple resources to be managed by firmware.
> On these targets, tasks related to clocks, regulators, resets, and
> interconnects can be delegated to the firmware, while the remaining
> responsibilities are handled by Linux.
Aside from the comments you already got from others, please change
[RFC m/n] to [PATCH RFC m/n] so that your series isn't filtered out
out maintainers' inboxes due to the missing PATCH keyword..
Konrad
Powered by blists - more mailing lists