From: leo.yan@linaro.org (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: dts: add all hi6220 uart nodes
Date: Fri, 2 Oct 2015 22:28:09 +0800 [thread overview]
Message-ID: <20151002142809.GA13483@leoy-linaro> (raw)
In-Reply-To: <20151001102136.GC12635@sirena.org.uk>
On Thu, Oct 01, 2015 at 11:21:36AM +0100, Mark Brown wrote:
> On Thu, Oct 01, 2015 at 11:15:52AM +0800, Leo Yan wrote:
> > On Wed, Sep 30, 2015 at 04:54:51PM -0700, Tyler Baker wrote:
> > > On 30 September 2015 at 12:18, Mark Brown <broonie@kernel.org> wrote:
>
> > > > My understanding is that it applies to both with slightly different
> > > > driver sets, the slides aren't online yet (!) but if you look at 10:52
> > > > or so in the video we should have SD/eMMC on HiKey in v4.1 with thermal
> > > > and CPUfreq added in v4.2. It also looks like there's just some DT
> > > > additions needed to enable reset, cpuidle and CPU hotplug using generic
> > > > code (mainly the constants for PSCI I expect).
>
> > > I just skimmed the video and I see your point. I'll need to
> > > investigate a bit but I'm up for sending some follow up patches to get
> > > these drivers functioning. First lets get the UART working :)
>
> > If you think it's necessary, i could send out patches to enable cpuidle
> > firstly (actually now PSCI has been enabled yet); for cpufreq and
> > thermal features, need wait until mailbox driver has been merged.
>
> It seems sensible to get the DT bits for functionality that is already
> supported on the driver side upstream, that way we get the maximum
> functionality available as soon as possible and even if other bits get
> problems in review users can take advantage of things that are OK.
Okay, i will prepare patches for enabling CPUIdle ASAP.
Thanks,
Leo Yan
next prev parent reply other threads:[~2015-10-02 14:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 20:29 [PATCH] arm64: dts: add all hi6220 uart nodes Tyler Baker
2015-09-30 8:24 ` Arnd Bergmann
2015-09-30 17:31 ` Mark Brown
2015-09-30 18:12 ` Tyler Baker
2015-09-30 19:03 ` Rob Herring
2015-09-30 23:51 ` Tyler Baker
2015-10-01 1:43 ` Haojian Zhuang
2015-09-30 19:18 ` Mark Brown
2015-09-30 23:54 ` Tyler Baker
2015-10-01 3:15 ` Leo Yan
2015-10-01 10:21 ` Mark Brown
2015-10-02 14:28 ` Leo Yan [this message]
2015-10-02 16:48 ` Mark Brown
2015-10-02 18:00 ` Peter Griffin
2015-10-06 14:29 ` Tyler Baker
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=20151002142809.GA13483@leoy-linaro \
--to=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).