From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sven Eckelmann Subject: IPQ8068 support Date: Wed, 26 Apr 2017 10:26:59 +0200 Message-ID: <2798304.oiRXTY8cqN@bentobox> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart10744470.4MKqDOj0AQ"; micalg="pgp-sha512"; protocol="application/pgp-signature" Return-path: Received: from mail-wm0-f48.google.com ([74.125.82.48]:36669 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751037AbdDZI1G (ORCPT ); Wed, 26 Apr 2017 04:27:06 -0400 Received: by mail-wm0-f48.google.com with SMTP id u65so42991976wmu.1 for ; Wed, 26 Apr 2017 01:27:05 -0700 (PDT) Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: linux-arm-msm@vger.kernel.org Cc: simon.wunderlich@openmesh.com --nextPart10744470.4MKqDOj0AQ Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Hi, (the next paragraph is just an explanation of the situation - can be skipped to get to the actual question) I've received a board (either called EWS370 or EWS870AP in their firmware) which was announced as AP148 based. But the initial booting up with LEDE wasn't working and even the serial port didn't start up. And some tests with the standard earlycon registers for the IPQ8064 also didn't work. But then I saw that the original firmware used some registers at 0x16640000 for ttyHSL0. A quick test showed that this is really the correct address for the serial console. I found in the Linux sources that apq8064 is the only one which actually uses this register offset. Unsure whether this is actually an APQ8064, I've removed the antennas, heatsinks and shielding to find a CPU with the name IPQ8068 on it. It looks like the support for this CPU was never upstreamed by QCA. A quick search in the linux-msm tree in codeaurora also showed only uninteresting mentions of this CPU [1]. I already know from Dakota that the upstreaming effort from some QCA developers were suddenly stopped. Some of the Dakota drivers were therefore waiting in some branch of some repository [2] or hanging around in an unfinished state on some mailing list. So maybe there are similar things somewhere for the IPQ8068. Can someone maybe point me in the right direction? Kind regards, Sven [1] https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=1fc998bf276c7407e03953d8c306cda25b29b6b5 https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=5ae236e30ff401f4600125ad452e93973ddc205b https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=613c5a41ed666383c778129c7b172987aa16f31c https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=4aa6962af93bf32dd5c5e6b2313c80f4732b3286 https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=8b2089087088e08f5e68b83ba04af44ecc3f9e9d [2] https://source.codeaurora.org/quic/qsdk/mmcclint-qca/log/?h=for-next --nextPart10744470.4MKqDOj0AQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEF10rh2Elc9zjMuACXYcKB8Eme0YFAlkAWdMACgkQXYcKB8Em e0Y0bhAA0JKEWflXSivaU7iyXi0n4OB7ZGvIjh3fHNW6Cnh7Op5lVFLnMTTXfoBe lpl27eASUIdRbp9cAauTkkLBdM7zIIr2Mf9EN5++o6i/ZvXvRCTGmLpvK+IKfwXO ZBALTd+1mj/nqMj+eHDwZMTYa437oOPQFcvkuiEn15+YG8CJbiKqwew2LzhXodvd Oy629khHnnAQOMVcMoDgApQkKAsSa4FTw3qxfVfk9xhNggB/HMgfkowNdOw5apwM 5/tt7HIbpkafO2Uvdk7XhgSEWxNGjr3UK9sOQDZ5JIKbKtzRdqkza64dZxb+djSN BxToc/b4wyGs3rSgS+LsrFRfw+D7RyYzrLjICcroExJrZzfz0CtLifXXin99bBff Ki29sdh4vqjJQMFlpcv6KYhw3EV8ppFX5+WigRgzbv1WJp/1vNJ1fbUg8mXOBQDj n2CanTBUZgRt8MU6DANnQCOWq45IcJ9MTInNYpQaneiP3Cj5ewb+vb4SSpFJO09a u5mwuo8dgvFCP58U48oqjUVC82HKdAnmG/oiBpjX3h7PmLOzTN/GUGbCF5qYzzDj AGYKehQyAXRzYJrBlqlEukyY45IixQ7UAPiocIpD3RDStSa7zzQLXgEZb3v7lWfJ m/s2Ns86MSyh6rCqbYBHylVWHJBqd4NsPGl/FpOFAAfyp7HwQzQ= =BiOh -----END PGP SIGNATURE----- --nextPart10744470.4MKqDOj0AQ--