All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Amol Maheshwari <amahesh@qti.qualcomm.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Tengfei Fan <quic_tengfan@quicinc.com>,
	Ling Xu <quic_lxu5@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	Ekansh Gupta <quic_ekangupt@quicinc.com>
Subject: Re: [PATCH 2/2] arm64: dts: qcom: sa8775p: fix the fastrpc label
Date: Fri, 16 Aug 2024 16:05:47 +0200	[thread overview]
Message-ID: <b34c0826-44fc-46cf-93ca-e07afb5df4e5@kernel.org> (raw)
In-Reply-To: <20240816102345.16481-2-brgl@bgdev.pl>

On 16/08/2024 12:23, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> 
> The fastrpc driver uses the label to determine the domain ID and create
> the device nodes. It should be "cdsp1" as this is the engine we use here.
> 
> Fixes: df54dcb34ff2 ("arm64: dts: qcom: sa8775p: add ADSP, CDSP and GPDSP nodes")
> Reported-by: Ekansh Gupta <quic_ekangupt@quicinc.com>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof


  reply	other threads:[~2024-08-16 14:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 10:23 [PATCH 1/2] dt-bindings: misc: qcom,fastrpc: document new domain ID Bartosz Golaszewski
2024-08-16 10:23 ` [PATCH 2/2] arm64: dts: qcom: sa8775p: fix the fastrpc label Bartosz Golaszewski
2024-08-16 14:05   ` Krzysztof Kozlowski [this message]
2024-08-16 11:21 ` [PATCH 1/2] dt-bindings: misc: qcom,fastrpc: document new domain ID Krzysztof Kozlowski
2024-08-16 11:21   ` [PATCH 1/2] dt-bindings: misc: qcom, fastrpc: " Krzysztof Kozlowski
2024-08-16 12:29   ` [PATCH 1/2] dt-bindings: misc: qcom,fastrpc: " Bartosz Golaszewski
2024-08-16 12:29     ` [PATCH 1/2] dt-bindings: misc: qcom, fastrpc: " Bartosz Golaszewski
2024-08-16 14:05     ` [PATCH 1/2] dt-bindings: misc: qcom,fastrpc: " Krzysztof Kozlowski
2024-08-16 14:05       ` [PATCH 1/2] dt-bindings: misc: qcom, fastrpc: " Krzysztof Kozlowski
2024-08-16 14:05 ` [PATCH 1/2] dt-bindings: misc: qcom,fastrpc: " Krzysztof Kozlowski
2024-08-16 14:05   ` [PATCH 1/2] dt-bindings: misc: qcom, fastrpc: " Krzysztof Kozlowski
2024-08-20 22:12 ` (subset) [PATCH 1/2] dt-bindings: misc: qcom,fastrpc: " Bjorn Andersson
2024-08-20 22:12   ` (subset) [PATCH 1/2] dt-bindings: misc: qcom, fastrpc: " Bjorn Andersson

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=b34c0826-44fc-46cf-93ca-e07afb5df4e5@kernel.org \
    --to=krzk@kernel.org \
    --cc=amahesh@qti.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_ekangupt@quicinc.com \
    --cc=quic_lxu5@quicinc.com \
    --cc=quic_tengfan@quicinc.com \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.