public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: msm8996: Fix venus iommu nodename error
Date: Mon, 6 Jan 2020 11:13:21 -0800	[thread overview]
Message-ID: <20200106191321.GU3755841@builder> (raw)
In-Reply-To: <20200106102305.27059-1-stanimir.varbanov@linaro.org>

On Mon 06 Jan 02:23 PST 2020, Stanimir Varbanov wrote:

> Fix the following error/warn seen with make dtbs_check
> 
> arm,smmu-venus@d40000: $nodename:0: 'arm,smmu-venus@d40000' does not match '^iommu@[0-9a-f]*'
> arm,smmu-venus@d40000: clock-names:0: 'bus' was expected
> arm,smmu-venus@d40000: clock-names:1: 'iface' was expected
> 
> by rename nodename to "iommu".
> 
> Signed-off-by: Stanimir Varbanov <stanimir.varbanov@linaro.org>

Thanks Stan, applied.

> ---
>  arch/arm64/boot/dts/qcom/msm8996.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi
> index 4ca2e7b44559..9bbcee31f28b 100644
> --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8996.dtsi
> @@ -2267,7 +2267,7 @@
>  			};
>  		};
>  
> -		venus_smmu: arm,smmu-venus@d40000 {
> +		venus_smmu: iommu@d40000 {
>  			compatible = "qcom,msm8996-smmu-v2", "qcom,smmu-v2";
>  			reg = <0xd40000 0x20000>;
>  			#global-interrupts = <1>;
> -- 
> 2.17.1
> 

      reply	other threads:[~2020-01-06 19:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06 10:23 [PATCH] arm64: dts: qcom: msm8996: Fix venus iommu nodename error Stanimir Varbanov
2020-01-06 19:13 ` Bjorn Andersson [this message]

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=20200106191321.GU3755841@builder \
    --to=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stanimir.varbanov@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox