linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Stefan Wahren <wahrenst@gmx.net>, Eric Anholt <eric@anholt.net>,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	linux-rpi-kernel@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 1/3] bcm2835-dt-next-2019-08-15
Date: Thu, 15 Aug 2019 20:34:01 +0200	[thread overview]
Message-ID: <1565894043-5249-1-git-send-email-wahrenst@gmx.net> (raw)

Hi Florian,

The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:

  Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)

are available in the git repository at:

  git://github.com/anholt/linux tags/bcm2835-dt-next-2019-08-15

for you to fetch changes up to 60c833d5664e1b3f71c4471233469790adf505ca:

  ARM: dts: bcm283x: Enable HDMI at board level (2019-08-15 19:35:15 +0200)

----------------------------------------------------------------
This pull request prepares the BCM2835 DTS files for the introduction
of the new SoC BCM2711.

----------------------------------------------------------------
Stefan Wahren (4):
      ARM: bcm283x: Reduce register ranges for UART, SPI and I2C
      ARM: dts: bcm283x: Define MMC interfaces at board level
      ARM: dts: bcm283x: Define memory at board level
      ARM: dts: bcm283x: Enable HDMI at board level

 arch/arm/boot/dts/bcm2835-rpi-a-plus.dts   | 14 ++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi-a.dts        | 14 ++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi-b-plus.dts   | 14 ++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi-b-rev2.dts   | 14 ++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi-b.dts        | 14 ++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi-cm1-io1.dts  |  9 +++++++++
 arch/arm/boot/dts/bcm2835-rpi-cm1.dtsi     |  5 +++++
 arch/arm/boot/dts/bcm2835-rpi-zero-w.dts   | 14 ++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi-zero.dts     | 14 ++++++++++++++
 arch/arm/boot/dts/bcm2835-rpi.dtsi         | 23 -----------------------
 arch/arm/boot/dts/bcm2836-rpi-2-b.dts      | 10 ++++++++++
 arch/arm/boot/dts/bcm2837-rpi-3-a-plus.dts |  3 +++
 arch/arm/boot/dts/bcm2837-rpi-3-b-plus.dts |  3 +++
 arch/arm/boot/dts/bcm2837-rpi-3-b.dts      |  3 +++
 arch/arm/boot/dts/bcm2837-rpi-cm3-io3.dts  |  9 +++++++++
 arch/arm/boot/dts/bcm2837-rpi-cm3.dtsi     |  1 +
 arch/arm/boot/dts/bcm283x.dtsi             |  6 +++---
 17 files changed, 144 insertions(+), 26 deletions(-)

             reply	other threads:[~2019-08-15 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 18:34 Stefan Wahren [this message]
2019-08-15 18:34 ` [GIT PULL 2/3] bcm2835-defconfig-next-2019-08-15 Stefan Wahren
2019-08-15 22:56   ` Florian Fainelli
2019-08-15 18:34 ` [GIT PULL 3/3] bcm2835-defconfig-64-next-2019-08-15 Stefan Wahren
2019-08-15 22:57   ` Florian Fainelli
2019-08-15 22:56 ` [GIT PULL 1/3] bcm2835-dt-next-2019-08-15 Florian Fainelli

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=1565894043-5249-1-git-send-email-wahrenst@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-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).