linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: APQ8060 DragonBoard support
Date: Wed, 13 Aug 2014 07:15:05 -0700	[thread overview]
Message-ID: <20140813141505.GD32301@codeaurora.org> (raw)
In-Reply-To: <CACRpkdYpLk3KommD6SRqJehYB9fe-uPFjCefyJ4OV7voZpFn3w@mail.gmail.com>

On 08/13, Linus Walleij wrote:
> Can I ask a question about this ... in difference from everyone in the
> world who has APQ8070 DragonBoards I actually have the APQ8060
> DragonBoard.
> 
> I have been booting this using the qcom-msm8660-surf.dts device tree
> and it seems to work reasonably well, like the timer, intcon and stuff
> is obviously in the right place.
> 
> But how similar is it really? I am told the CPU type may not be the
> same even if the periphs seem to be in the same place.
> 
> Do I need a qcom-***8*60-dragonboard.dts at some point or is the
> "surf" electronics similar to the APQ8060 dragon?
> 
> The board layout and electronics are actually all the docs I have, I
> have no datasheet/trm for the APQ8060 per se, and no clue what the
> "surf" board really is, so I'm a bit in the dark here.
> 

For the basic stuff like timer, serial console, etc. the surf and
the dragonboard are the same. The Scorpion CPU is the same
between them. The main difference is that the 8060 doesn't have a
modem.

We probably only need a qcom-***8*60-dragonboard.dts file when
the two diverge. That might be soon given that ssbi and the pmic
core are in place. Enabling something like the keypad driver
should be possible.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

      reply	other threads:[~2014-08-13 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-13  9:07 APQ8060 DragonBoard support Linus Walleij
2014-08-13 14:15 ` Stephen Boyd [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=20140813141505.GD32301@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).