public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/5] Broadcom devicetree changes for 4.18
Date: Mon, 14 May 2018 13:26:45 -0700	[thread overview]
Message-ID: <20180514202645.tuovyugwijhfd2au@localhost> (raw)
In-Reply-To: <20180511214339.24139-3-f.fainelli@gmail.com>

On Fri, May 11, 2018 at 02:43:36PM -0700, Florian Fainelli wrote:
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
> 
>   Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.18/devicetree
> 
> for you to fetch changes up to a05f1e36a57d02374a203719abc5bf2e8c51e125:
> 
>   ARM: dts: BCM5301X: Switch D-Link DIR-885L to the new partitions syntax (2018-05-11 09:46:38 -0700)
> 
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM-based SoC Device Tree changes
> for 4.18, please pull the following:
> 
> - Stefan provides updates to the BCM2835 RNG Device Tree binding and
>   Device Tree node by adding its missing interrupt line.
> 
> - Rafal switches the Luxul XWC-1000 and the D-Link DIR-885L to the new
>   partitions syntax which allows specifying a partition parser
> 
> - Rafal also updates a bunch of BCM5301X Device Tree source files to a
>   more standard SPDX tag and dual GPL 2.0 and MIT. This is a follow-up
>   to this discussion with Greg:
>   https://lkml.org/lkml/2018/4/28/179
> 
> - Dan adds support for two Luxul devices: XAP-1610 (based on BCM47094)
>   and XWR-3150 V1 (similar to XWR-3100)
> 
> - Stefan provides a set of updates to the BCM283x Device Tree sources to
>   support the Raspberry Pi 3 B+ for both the ARM and ARM64 kernels. He
>   adds the required nodes for the LAN7515 USB Ethernet, Cypress CYW43455
>   BT/WiFi combo chip. Stefan also provides a few fixes for the PWM pin
>   assignment for RPi 3B and Zero/Zero W. Finally, Stefan adds the
>   missing GPIOs for controlling additional peripherals now that support
>   for the RPi 3 GPIO expander has landed

Merged, thanks!


-Olof

  reply	other threads:[~2018-05-14 20:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 21:43 [GIT PULL 1/5] Broadcom defconfig changes for 4.18 Florian Fainelli
2018-05-11 21:43 ` [GIT PULL 2/5] Broadcom defconfig-arm64 " Florian Fainelli
2018-05-13 17:01   ` [GIT PULL 2/5 v2] " Florian Fainelli
2018-05-14 20:24     ` Olof Johansson
2018-05-13 17:05   ` [GIT PULL 2/5] " Florian Fainelli
2018-05-11 21:43 ` [GIT PULL 3/5] Broadcom devicetree " Florian Fainelli
2018-05-14 20:26   ` Olof Johansson [this message]
2018-05-11 21:43 ` [GIT PULL 4/5] Broadcom drivers " Florian Fainelli
2018-05-14 20:27   ` Olof Johansson
2018-05-11 21:43 ` [GIT PULL 5/5] Broadcom soc " Florian Fainelli
2018-05-14 20:29   ` Olof Johansson
2018-05-14 20:21 ` [GIT PULL 1/5] Broadcom defconfig " Olof Johansson

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=20180514202645.tuovyugwijhfd2au@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