Re: [PATCH] arm64: dts: sdm630 SoC and Sony Pioneer (Xperia XA2) support
flat view
From: Bjorn Andersson <hidden>
Date: 2018-09-24 21:16:57
Also in:
linux-arm-kernel, linux-arm-msm, lkml
On Mon 24 Sep 13:42 PDT 2018, Craig wrote:
On 24 September 2018 20:19:29 BST, Bjorn Andersson [off-list ref] wrote:quoted
On Sat 11 Aug 09:25 PDT 2018, Craig Tatlor wrote:quoted
Initial device tree support for Qualcomm SDM630 SoC and Sony Pioneer (Xperia XA2). SDM630 is based off of the SDM660 soc and all SDM660 specific driversarequoted
compatible with it. SDM660 is also based off of MSM8998 so it usessomequoted
of its drivers aswell.Consider adding both sdm630 and sdm660 compatibles to the bindings and drivers and use the right one in the dts, in case we find details that differs in the future.This includes pinctrl and GCC?
Yes
quoted
quoted
The device tree is based on the CAF 4.4 kernel tree. The device can be booted into the initrd with a shell over UART. Signed-off-by: Craig Tatlor <redacted>[..]quoted
diff --git a/arch/arm64/boot/dts/qcom/sdm630-pins.dtsib/arch/arm64/boot/dts/qcom/sdm630-pins.dtsiquoted
new file mode 100644 index 000000000000..78b79c1076f1--- /dev/null +++ b/arch/arm64/boot/dts/qcom/sdm630-pins.dtsi@@ -0,0 +1,17 @@ +// SPDX-License-Identifier: GPL-2.0 +/* Copyright (c) 2018, Craig Tatlor. */ + +&tlmm { + blsp1_uart1_default: blsp1_uart1_default { + pinmux { + pins = "gpio0", "gpio1", "gpio2", "gpio3"; + function = "gpio";Please put these in the sdm630.dtsi directly, rather than spreading the pins out in a separate file.Okay, just followed what 8996 did
I have started to rework that based on the last year's discussions, but haven't posted any patches yet.
quoted
quoted
+ }; + + pinconf { + pins = "gpio0", "gpio1", "gpio2", "gpio3"; + drive-strength = <2>; + bias-disable;Please extend &blsp1_uart1_default in the pioneer dtsi with these "electrical properties".Are you meaning to put this in the pioneer DTS or just drive strength and bias?
The drive-strength and bias are board-specific properties, so we want to keep those in the board file, so I mean push the pinconf part into the board dtsi. [..]
quoted
quoted
+ gcc: clock-controller@100000 { + compatible = "qcom,gcc-sdm660"; + #clock-cells = <1>; + #reset-cells = <1>; + #power-domain-cells = <1>; + reg = <0x100000 0x94000>;Please 0-pad addresses in "reg", makes it easier to sort them as well (but keep the @address after the node name unpadded)Sure, how much should I pad up to?
reg = <0x00100000 0xb0000>; Regards, Bjorn