From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: aspeed: dts changes for 4.19
Date: Thu, 26 Jul 2018 12:51:27 -0700 [thread overview]
Message-ID: <20180726195127.jukxvbydddlwui4k@localhost> (raw)
In-Reply-To: <CACPK8Xeu2JAVBTyiUtyso1egbe3X+r5a--Cx30YDJV-JmK==DQ@mail.gmail.com>
Hi,
On Thu, Jul 26, 2018 at 02:00:49PM +0930, Joel Stanley wrote:
> Hello ARM Maintainers,
>
> Here are the ASPEED device tree updates for 4.19. No new machines this time
> around, but we now have some FSI (the bus between the BMC and the PowerPC host)
> descriptions, and USB support.
>
> The following changes since commit 7daf201d7fe8334e2d2364d4e8ed3394ec9af819:
>
> Linux 4.18-rc2 (2018-06-24 20:54:29 +0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/joel/aspeed.git
> tags/aspeed-4.19-devicetree
>
> for you to fetch changes up to 19617a35b08379b3e6da0a4ee0d2d62645bf1b9e:
>
> ARM: dts: aspeed: Add Power9 CFAM description (2018-07-25 17:43:36 +0930)
>
> ----------------------------------------------------------------
> ASPEED device tree updates for 4.19
>
> - New support for the ASPEED USB host controller and USB vhub (device)
> support
>
> - Descriptions for the FSI bus and hardware inside the Power8/Power9
> processors that are accessed over this bus. This includes the ColdFire
> processor that is part of the ASPEED SoC and is used to offload the FSI
> bit-banging
I had some feedback on one of these patches, it should be reworked before we
merge it. See separate email as reply to the actual patch.
If you prefer, you can send a branch without that contents for merging now, so
the rest of it isn't held up.
-Olof
next prev parent reply other threads:[~2018-07-26 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 4:30 [GIT PULL] ARM: aspeed: dts changes for 4.19 Joel Stanley
2018-07-26 19:51 ` Olof Johansson [this message]
2018-07-27 1:22 ` Joel Stanley
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=20180726195127.jukxvbydddlwui4k@localhost \
--to=olof@lixom.net \
--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