linux-kernel - Re: [PATCH 1/1] arm64: dts: qcom: sc7280: add slimbus DT node

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <35ca2ef2-7613-4ddb-b863-2e429337fee3@linaro.org>
Date:   Wed, 22 Nov 2023 21:13:28 +0100
From:   Konrad Dybcio <konrad.dybcio@...aro.org>
To:     Viken Dadhaniya <quic_vdadhani@...cinc.com>, andersson@...nel.org,
        robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
        conor+dt@...nel.org, linux-arm-sm@...r.kernel.org,
        devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     vnivarth@...cinc.com, msavaliy@...cinc.com, vtanuku@...cinc.com,
        cchiluve@...cinc.com, dkammath@...cinc.com
Subject: Re: [PATCH 1/1] arm64: dts: qcom: sc7280: add slimbus DT node



On 11/16/23 19:39, Viken Dadhaniya wrote:
> Add slimbus DT node to enable slimbus usecase on Bluetooth
> for audio streaming and playback.
How can I test this?

> 
> Based on requirement, client team can enable slimbus node
> on target specific dt file.
You can even enable it if you're not part of the client team!
This paragraph is a bit obvious for what it describes

> 
> Signed-off-by: Viken Dadhaniya <quic_vdadhani@...cinc.com>
> ---
>   arch/arm64/boot/dts/qcom/sc7280.dtsi | 25 +++++++++++++++++++++++++
>   1 file changed, 25 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi b/arch/arm64/boot/dts/qcom/sc7280.dtsi
> index 04bf85b0399a..fba352504f3f 100644
> --- a/arch/arm64/boot/dts/qcom/sc7280.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi
> @@ -2528,6 +2528,31 @@
>   			status = "disabled";
>   		};
>   
> +		slimbam: dma-controller@...4000 {
> +			compatible = "qcom,bam-v1.7.0";
> +			reg = <0x0 0x03a84000 0x0 0x20000>;
0x0 -> 0 to be consistent with other nodes

> +			#dma-cells = <1>;
> +			interrupts = <GIC_SPI 164 IRQ_TYPE_LEVEL_HIGH>;
interrupts should come after reg

> +			qcom,controlled-remotely;
> +			num-channels  = <31>;
> +			qcom,ee = <1>;
> +			qcom,num-ees = <2>;
> +			iommus = <&apps_smmu 0x1826 0x0>;
> +			status = "disabled";
> +		};
> +
> +		slim_msm: slim-ngd@...0000 {
slim_msm -> slim

> +			compatible = "qcom,slim-ngd-v1.5.0";
> +			reg = <0x0 0x03ac0000 0x0 0x2c000>;
ditto

> +			#address-cells = <1>;
> +			#size-cells = <0>;
these two properties should go before the status property

> +			interrupts = <GIC_SPI 163 IRQ_TYPE_LEVEL_HIGH>;
> +			dmas = <&slimbam 3>, <&slimbam 4>;
> +			dma-names = "rx", "tx";
> +			iommus = <&apps_smmu 0x1826 0x0>;
> +			status = "disabled";
> +		};
Konrad