From: Sricharan R <sricharan@codeaurora.org>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>,
linux-arm-msm@vger.kernel.org
Cc: simon.wunderlich@openmesh.com,
Varadarajan Narayanan <varada@codeaurora.org>,
Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Yifeng Tu <yifeng@qti.qualcomm.com>,
Ram Chandra Jangir <rjangir@codeaurora.org>
Subject: Re: ARM: dts: qcom: IPQ4019 DK04.1 abd DK07.1 DTSI
Date: Wed, 13 Dec 2017 16:37:58 +0530 [thread overview]
Message-ID: <ba36fc63-7f39-5145-2ca5-e8fc3516b798@codeaurora.org> (raw)
In-Reply-To: <2173291.qgT9lyRsIB@bentobox>
Hi Sven,
On 12/12/2017 2:38 PM, Sven Eckelmann wrote:
> 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?
>
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
> 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
>
--
"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
prev parent reply other threads:[~2017-12-13 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 9:08 ARM: dts: qcom: IPQ4019 DK04.1 abd DK07.1 DTSI Sven Eckelmann
2017-12-13 11:07 ` Sricharan R [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=ba36fc63-7f39-5145-2ca5-e8fc3516b798@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=david.brown@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=rjangir@codeaurora.org \
--cc=simon.wunderlich@openmesh.com \
--cc=sven.eckelmann@openmesh.com \
--cc=varada@codeaurora.org \
--cc=yifeng@qti.qualcomm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.