ARM: dts: qcom: IPQ4019 DK04.1 abd DK07.1 DTSI
Hi,
I am currently working on two IPQ401x boards. One is based on the DK04.1 and the other one is DK07.1 based. I've used the qcom-ipq4019-ap.dk04.1.dtsi from LEDE for the first board [1]. This seemed to work relatively well for me. But I was confused that it is still not upstreamed by QCA to Linux. This is rather odd because QCA promised some years ago to have full upstream support for the Dakota family in some months (which is still not on the horizon). Is it planned by QCA to get the patches from Matthew McClintock (and others) upstream?
The next board was an DK07.1. I couldn't find any official DTSI for upstream Linux. And the ones from the QCA SDK [1] are not compatible and quite confusing. For example, it doesn't provide spi_0* (but spi_1) - beside all boards only using spi_0*. I have therefore started (for my own project) to write an own one with the infos I got from "my" board. But it is not actually an DK07.1 and I have no documentation for the new board or the DK07.1-C* - so I might be wrong about a couple of things. Is QCA planning to upstream official support (DTSI + DTS) for the DK07.1-C1 and DK07.2-C2 board?
Kind regards,
Sven
[1] https://git.lede-project.org/?p=source.git;a=blob;f=target/linux/ipq806x/patches-4.9/0026-dts-ipq4019-Add-support-for-IPQ4019-DK04-board.patch;h=de0ea8e89a8776812de0d1e6547d05b3f10f6dee;hb=b8220883fd8fa209dae71def9b6d2a7656bca8bb
[2] https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/tree/arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1.dtsi?h=NHSS.QSDK.6.1.r1&id=0b51d4277668f64173a87c9f39f8099e873f8780
/* Copyright (c) 2015, The Linux Foundation. All rights reserved.
*
* Permission to use, copy, modify, and/or distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies. *
* THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
* WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
* MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
* ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
* ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
* OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. *
*/
#include "qcom-ipq4019.dtsi"
/ {
model = "Qualcomm Technologies, Inc. IPQ4019/AP-DK07.1";
compatible = "qcom,ipq4019";
clocks {
xo: xo {
compatible = "fixed-clock";
clock-frequency = <48000000>;
#clock-cells = <0>;
};
};
soc {
timer {
compatible = "arm,armv7-timer";
interrupts = <1 2 0xf08>,
<1 3 0xf08>,
<1 4 0xf08>,
<1 1 0xf08>;
clock-frequency = <48000000>;
};
pinctrl@0x01000000 {
serial_0_pins: serial_pinmux {
mux {
pins = "gpio16", "gpio17";
function = "blsp_uart0";
bias-disable;
};
};
spi_0_pins: spi_0_pinmux {
pinmux {
function = "blsp_spi0";
pins = "gpio13", "gpio14", "gpio15";
};
pinmux_cs {
function = "gpio";
pins = "gpio12";
};
pinconf {
pins = "gpio13", "gpio14", "gpio15";
drive-strength = <12>;
bias-disable;
};
pinconf_cs {
pins = "gpio12";
drive-strength = <2>;
bias-disable;
output-high;
};
};
i2c_0_pins: i2c_0_pinmux {
pinmux {
function = "blsp_i2c0";
pins = "gpio20", "gpio21";
};
pinconf {
pins = "gpio20", "gpio21";
drive-strength = <16>;
bias-disable;
};
};
mdio_pins: mdio_pinmux {
mux_1 {
pins = "gpio6";
function = "mdio0";
bias-bus-hold;
};
mux_2 {
pins = "gpio7";
function = "mdc";
bias-bus-hold;
};
};
};
blsp_dma: dma@7884000 {
status = "ok";
};
spi_0: spi@78b5000 {
pinctrl-0 = <&spi_0_pins>;
pinctrl-names = "default";
status = "ok";
cs-gpios = <&tlmm 12 0>;
mx25l25635e@0 {
#address-cells = <1>;
#size-cells = <1>;
reg = <0>;
compatible = "mx25l25635e";
spi-max-frequency = <24000000>;
};
};
i2c_0: i2c@78b7000 { /* BLSP1 QUP2 */
pinctrl-0 = <&i2c_0_pins>;
pinctrl-names = "default";
status = "ok";
};
serial@78af000 {
pinctrl-0 = <&serial_0_pins>;
pinctrl-names = "default";
status = "ok";
};
usb3_ss_phy: ssphy@9a000 {
status = "ok";
};
usb3_hs_phy: hsphy@a6000 {
status = "ok";
};
usb3: usb3@8af8800 {
status = "ok";
};
usb2_hs_phy: hsphy@a8000 {
status = "ok";
};
usb2: usb2@60f8800 {
status = "ok";
};
cryptobam: dma@8e04000 {
status = "ok";
};
crypto@8e3a000 {
status = "ok";
};
watchdog@b017000 {
status = "ok";
};
mdio@90000 {
status = "ok";
pinctrl-0 = <&mdio_pins>;
pinctrl-names = "default";
phy-reset-gpio = <&tlmm 41 0>;
bias-disable;
};
ess-switch@c000000 {
status = "ok";
switch_mac_mode = <0x0>; /* mac mode for RGMII RMII */
switch_initvlas = <
0x0007c 0x54 /* PORT0_STATUS */
>;
};
ess-psgmii@98000 {
status = "ok";
};
edma@c080000 {
status = "ok";
};
wifi@a000000 {
status = "ok";
};
wifi@a800000 {
status = "ok";
};
qpic_bam: dma@7984000 {
status = "ok";
};
nand: qpic-nand@79b0000 {
status = "ok";
};
};
};Hi Sven,
Quoted 11 lines · Sven Eckelmann
Hi,
I am currently working on two IPQ401x boards. One is based on the DK04.1 and the other one is DK07.1 based. I've used the
qcom-ipq4019-ap.dk04.1.dtsifrom LEDE for the first board [1]. This seemed to work relatively well for me. But I was confused that it is still not upstreamed by QCA to Linux. This is rather odd because QCA promised some years ago to have full upstream support for the Dakota family in some months (which is still not on the horizon). Is it planned by QCA to get the patches from Matthew McClintock (and others) upstream?
Quoted 9 lines
The next board was an DK07.1. I couldn't find any official DTSI for upstream Linux. And the ones from the QCA SDK [1] are not compatible and quite confusing. For example, it doesn't provide spi_0* (but
spi_1) - beside all boards only using spi_0*. I have therefore started (for my own project) to write an own one with the infos I got from "my" board. But it is not actually an DK07.1 and I have no documentation for the new board or the DK07.1-C* - so I might be wrong about a couple of things. Is QCA planning to upstream official support (DTSI + DTS) for the DK07.1-C1 and DK07.2-C2 board?
Right, currently there are pending updates to ipq4019/8074 dts for both soc and
board DT files. Will post out the updates in the coming week. Meanwhile, while
reading the DT for DK07.1-C* boards, looks like this,
qcom-ipq4019-ap.dk07.1-c2.dts
spi_0 spi@78b5000 -> spidev on both CS 0 and 1
qcom-ipq4019-ap.dk07.1-c1.dts
spi_0 spi@78b5000 -> spinor on CS 0
spi_1: spi@78b6000 -> spidev (probably used for zigbee)Regards,
Sricharan
Quoted 7 lines
Kind regards,
Sven[1] https://git.lede-project.org/?p=source.git;a=blob;f=target/linux/ipq806x/patches-4.9/0026-dts-ipq4019-Add-support-for-IPQ4019-DK04-board.patch;h=de0ea8e89a8776812de0d1e6547d05b3f10f6dee;hb=b8220883fd8fa209dae71def9b6d2a7656bca8bb
[2] https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/tree/arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1.dtsi?h=NHSS.QSDK.6.1.r1&id=0b51d4277668f64173a87c9f39f8099e873f8780
Signature · 5 lines
"QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus