linux-kernel - Re: [PATCH v2 1/2] ARM: dts: Add MDM9615 dtsi

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] [day] [month] [year] [list]

Date:   Mon, 22 Aug 2016 17:51:19 -0700
From:   Stephen Boyd <sboyd@...eaurora.org>
To:     Neil Armstrong <narmstrong@...libre.com>
Cc:     andy.gross@...aro.org, david.brown@...aro.org,
        linux@...linux.org.uk, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        linux-soc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 1/2] ARM: dts: Add MDM9615 dtsi

On 08/20, Neil Armstrong wrote:
> On 08/18/2016 08:08 PM, Stephen Boyd wrote:
> > On 08/18, Neil Armstrong wrote:
> > 
> > 
> >> +
> >> +		gsbi2: gsbi@...00000 {
> >> +			compatible = "qcom,gsbi-v1.0.0";
> >> +			cell-index = <2>;
> >> +			reg = <0x16100000 0x100>;
> >> +			clocks = <&gcc GSBI2_H_CLK>;
> >> +			clock-names = "iface";
> >> +			status = "disabled";
> >> +			#address-cells = <1>;
> >> +			#size-cells = <1>;
> >> +			ranges;
> >> +
> >> +			gsbi2_i2c: i2c@...80000 {
> >> +				compatible = "qcom,i2c-qup-v1.1.1";
> >> +				#address-cells = <1>;
> >> +				#size-cells = <0>;
> >> +				reg = <0x16180000 0x1000>;
> >> +				interrupts = <GIC_SPI 149 IRQ_TYPE_NONE>;
> > 
> > There should be a trigger type... high perhaps?
> 
> Well, I do not know, and other qcom dtsi has 0x0 or NONE here...

We should fix those. The driver uses IRQF_TRIGGER_HIGH so it
seems like we should put that here as well.

> 
> > 
> >> +
> >> +				clocks = <&gcc GSBI2_QUP_CLK>, <&gcc GSBI2_H_CLK>;
> >> +				clock-names = "core", "iface";
> >> +				status = "disabled";
> >> +			};
> >> +		};
> >> +
> >> +
> >> +		qcom,ssbi@...000 {
> >> +			compatible = "qcom,ssbi";
> >> +			reg = <0x500000 0x1000>;
> >> +			qcom,controller-type = "pmic-arbiter";
> >> +
> >> +			pmicintc: pmic@0 {
> >> +				compatible = "qcom,pm8018", "qcom,pm8921";
> > 
> > I know that DT specifies most specific compatible first, but when
> > the generic compatible is part number specific as well it never
> > feels right to me. I guess I'll have to get over this.
> > 
> >> +				interrupts = <GIC_PPI 226 IRQ_TYPE_NONE>;
> >> +				#interrupt-cells = <2>;
> >> +				interrupt-controller;
> >> +				#address-cells = <1>;
> >> +				#size-cells = <0>;
> > 
> > Can we have interrupt-parent = <&pmicintc> here instead of in
> > every node?
> 
> No since the pmic node interrupt parent is the GIC.

Ah ok. Silly me.

> > 
> >> +			compatible = "qcom,bam-v1.3.0";
> >> +			reg = <0x12142000 0x8000>;
> >> +			interrupts = <GIC_SPI 97 IRQ_TYPE_NONE>;
> > 
> > There should really be some flags.
> 
> Same as for the qup and uartdm, other qcom dtsi left 0x0 or NONE here...

The driver uses IRQF_TRIGGER_HIGH here, so use that in dtsi?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project