linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/6] Freescale arm64 device tree updates for 4.17
Date: Fri, 16 Mar 2018 09:56:09 +0800	[thread overview]
Message-ID: <20180316015608.GQ26859@dragon> (raw)
In-Reply-To: <CAK8P3a1RZjpSj=6eWAJ7Y=6=N9PPXkVcHN84LFBFJROyN0d0iw@mail.gmail.com>

On Thu, Mar 15, 2018 at 04:29:12PM +0100, Arnd Bergmann wrote:
> On Thu, Mar 15, 2018 at 12:36 PM, Shawn Guo <shawnguo@kernel.org> wrote:
> > The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
> >
> >   Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
> >
> > are available in the git repository at:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git tags/imx-dt64-4.17
> >
> > for you to fetch changes up to 4e017f1419397473cf3db6e9fa020013998b1aa4:
> >
> >   dt-bindings: ifc: Fix the unit address format in the examples (2018-03-12 15:38:49 +0800)
> >
> > ----------------------------------------------------------------
> > Freescale arm64 device tree updates for 4.17:
> >  - Move cpu_thermal device out of bus node to fix DTC simple_bus_reg
> >    warning seen with W=1 switch.
> >  - Fix IFC child nodes' unit-address to eliminate DTC simple_bus_reg
> >    warnings.
> >  - Add a dummy size memory 'reg' property for LS1046A device tree to
> >    avoid unit_address_vs_reg DTC warning, and the real size will be
> >    filled by bootloader.
> >  - Update ls208xa-qds board device tree to fix unit_address_vs_reg
> >    warnings with DSPI device.
> >  - Add idle-states for LS1012A and LS1043A, and correct
> >    arm,psci-suspend-param setting for already added idle-states.
> >  - DPAA QBMan portal and watchdog device addition.
> 
> Pulled into next/dt
> 
> What's the status of the imx8 support? Do you plan to send another
> pull request for that for 4.17, or are you still waiting for some
> dependencies?

The i.MX8 platform/DT support depends on clock driver which hasn't been
ready for merge.  And even for platform/DT series, I haven't seen the
new version from Lucas, since we put quite some comments on v2.

Shawn

  reply	other threads:[~2018-03-16  1:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 11:36 [GIT PULL 1/6] i.MX drivers updates for 4.17 Shawn Guo
2018-03-15 11:36 ` [GIT PULL 2/6] i.MX SoC changes " Shawn Guo
2018-03-15 15:12   ` Arnd Bergmann
2018-03-16  0:55     ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 3/6] i.MX device tree updates with new clock " Shawn Guo
2018-03-15 15:03   ` Arnd Bergmann
2018-03-15 11:36 ` [GIT PULL 4/6] i.MX device tree updates " Shawn Guo
2018-03-15 15:08   ` Arnd Bergmann
2018-03-15 16:58     ` Arnd Bergmann
2018-03-15 17:22       ` Fabio Estevam
2018-03-15 18:12         ` Fabio Estevam
2018-03-16  1:30           ` Shawn Guo
2018-03-15 11:36 ` [GIT PULL 5/6] Freescale arm64 " Shawn Guo
2018-03-15 15:29   ` Arnd Bergmann
2018-03-16  1:56     ` Shawn Guo [this message]
2018-03-15 11:36 ` [GIT PULL 6/6] i.MX defconfig " Shawn Guo
2018-03-15 15:21   ` Arnd Bergmann
2018-03-15 22:48     ` Fabio Estevam
2018-03-15 23:06       ` Fabio Estevam
2018-03-26 11:42   ` [GIT PULL v2 " Shawn Guo
2018-03-27 13:11     ` Arnd Bergmann
2018-03-15 15:25 ` [GIT PULL 1/6] i.MX drivers " Arnd Bergmann
2018-03-16  0:47   ` Shawn Guo
2018-03-16  1:22     ` Anson Huang

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=20180316015608.GQ26859@dragon \
    --to=shawnguo@kernel.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).