From: Stephen Boyd <sboyd@codeaurora.org>
To: Will Newton <will.newton@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: msm8909 support in a recent kernel
Date: Tue, 5 Dec 2017 18:45:50 -0800 [thread overview]
Message-ID: <20171206024550.GG4283@codeaurora.org> (raw)
In-Reply-To: <CAFbHwiRx-BOEa8AGH0yntVW5asyn__ddRr4uedFBP7jmkHMG9Q@mail.gmail.com>
On 12/01, Will Newton wrote:
> On Wed, Nov 29, 2017 at 6:50 PM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>
> > It's not completely insane to support this SoC upstream though. You'd
> > have to bring in the pinctrl and clk drivers, which may be a bit of
> > effort. After that it should mostly be enabling various devices by
> > adding DT nodes and testing things out. It looks like this is 32-bit, so
> > getting SMP support may require some tweaks to the smp_ops code for qcom
> > platforms. You're right that it isn't too different from msm8916, so it
> > may be that most of the driver support for that SoC transfers over
> > nicely to this one.
>
> I've started from the 8916 drivers and started to port in the changes
> from the 3.18 tree that seem relevant. I have a kernel that boots and
> talks over the serial. I've done a bunch of pinctrl although it is not
> complete yet. I've had a look at the clocks and got the PLL working
> but I think I'm probably missing a document that describes the
> clocking architecture in more detail (I have the register reference
> but that's a bit of a worm's eye view).
>
> The current issue I am experiencing is the first write to an SPMI
> channel causes the board to reset. I suspect this means that I have
> not setup clocks correctly somewhere?
The SPMI controller typically always has clks enabled, so I would
be surprised if the clk was off. More likely, you're attempting
to read/write a channel that is locked down and triggering an
access control violation. Something configured incorrectly in DT
perhaps?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-06 2:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 16:47 msm8909 support in a recent kernel Will Newton
2017-11-29 18:50 ` Stephen Boyd
2017-12-01 17:23 ` Will Newton
2017-12-06 2:45 ` Stephen Boyd [this message]
2017-12-06 14:39 ` Will Newton
2017-12-06 18:43 ` Bjorn Andersson
2017-12-06 20:10 ` Will Newton
2017-12-06 21:58 ` Bjorn Andersson
2017-12-07 14:13 ` Will Newton
2017-12-08 15:17 ` Will Newton
2017-12-08 17:07 ` Stephen Boyd
2017-12-10 9:37 ` Will Newton
2017-12-11 6:11 ` Bjorn Andersson
2017-12-12 10:59 ` Will Newton
2017-12-12 17:24 ` Will Newton
2017-12-13 0:01 ` Bjorn Andersson
2017-12-13 9:46 ` Will Newton
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=20171206024550.GG4283@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=will.newton@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox