public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	arnd@arndb.de, khilman@kernel.org,
	Linus Walleij <linus.walleij@linaro.org>,
	Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
	bcm-kernel-feedback-list@broadcom.com,
	Maxime Ripard <maxime@cerno.tech>,
	olof@lixom.net, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 7/7] Broadcom soc changes for 5.12
Date: Sun, 31 Jan 2021 14:17:21 -0800	[thread overview]
Message-ID: <20210131221721.685974-7-f.fainelli@gmail.com> (raw)
In-Reply-To: <20210131221721.685974-1-f.fainelli@gmail.com>

The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:

  Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)

are available in the Git repository at:

  https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.12/soc

for you to fetch changes up to e066cfd867aabe621be5c1855fc42ff699781ae4:

  Merge tag 'tags/bcm2835-soc-next-2021-01-25' into soc/next (2021-01-25 13:14:49 -0800)

----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs Kconfig/machine entry
changes for 5.12, please pull the following:

- Maxime adds a select of the Broadcom STB standard L2 interrupt
  controller driver which is used in the Raspberry Pi 4 HDMI controller to
  support I2C and CEC interrupts

- Florian adds a debug URT entry for the 72116 STB SoC

----------------------------------------------------------------
Florian Fainelli (2):
      ARM: brcmstb: Add debug UART entry for 72116
      Merge tag 'tags/bcm2835-soc-next-2021-01-25' into soc/next

Maxime Ripard (1):
      ARM: bcm: Select BRCMSTB_L2_IRQ for bcm2835

 arch/arm/include/debug/brcmstb.S | 30 ++++++++++++++++--------------
 arch/arm/mach-bcm/Kconfig        |  1 +
 arch/arm64/Kconfig.platforms     |  1 +
 3 files changed, 18 insertions(+), 14 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-01-31 22:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 22:17 [GIT PULL 1/6] Broadcom defconfig changes for 5.12 Florian Fainelli
2021-01-31 22:17 ` [GIT PULL 2/6] Broadcom defconfig-arm64 " Florian Fainelli
2021-02-02 21:38   ` Arnd Bergmann
2021-01-31 22:17 ` [GIT PULL 3/6] Broadcom devicetree " Florian Fainelli
2021-02-02 17:10   ` Arnd Bergmann
2021-01-31 22:17 ` [GIT PULL 4/6] Broadcom devicetree-arm64 " Florian Fainelli
2021-02-02 17:10   ` Arnd Bergmann
2021-01-31 22:17 ` [GIT PULL 5/6] Broadcom drivers " Florian Fainelli
2021-02-02 21:36   ` Arnd Bergmann
2021-01-31 22:17 ` [GIT PULL 6/6] Broadcom soc " Florian Fainelli
2021-02-02 21:47   ` Arnd Bergmann
2021-01-31 22:17 ` Florian Fainelli [this message]
2021-01-31 22:18   ` [GIT PULL 7/7] " Florian Fainelli
2021-02-02 21:38 ` [GIT PULL 1/6] Broadcom defconfig " Arnd Bergmann

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=20210131221721.685974-7-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=khilman@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=maxime@cerno.tech \
    --cc=nsaenzjulienne@suse.de \
    --cc=olof@lixom.net \
    --cc=soc@kernel.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