From: Florian Fainelli <florian.fainelli@broadcom.com>
To: soc@kernel.org
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
olof@lixom.net, khilman@kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 2/3] Broadcom drivers changes for 6.9
Date: Thu, 7 Mar 2024 12:04:40 -0800 [thread overview]
Message-ID: <20240307200441.2151734-2-florian.fainelli@broadcom.com> (raw)
In-Reply-To: <20240307200441.2151734-1-florian.fainelli@broadcom.com>
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.9/drivers
for you to fetch changes up to 86964bb62a9334acfebd869ca8ffc184dc365b75:
bus: brcmstb_gisb: Added support for 74165 register layout (2024-01-29 10:43:22 -0800)
----------------------------------------------------------------
This pull request contains Broadcom SoC device drivers changes for 6.9,
please pull the following:
- Florian adds support for the 74165 GISB arbiter layout which shuffled
register offsets around
----------------------------------------------------------------
Florian Fainelli (2):
dt-bindings: bus: Document Broadcom GISB arbiter 74165 compatible
bus: brcmstb_gisb: Added support for 74165 register layout
Documentation/devicetree/bindings/bus/brcm,gisb-arb.yaml | 1 +
drivers/bus/brcmstb_gisb.c | 15 +++++++++++++++
2 files changed, 16 insertions(+)
next prev parent reply other threads:[~2024-03-07 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 20:04 [GIT PULL 1/3] Broadcom devicetree-arm64 changes for 6.9 Florian Fainelli
2024-03-07 20:04 ` Florian Fainelli [this message]
2024-03-07 20:04 ` [GIT PULL 3/3] Broadcom soc " Florian Fainelli
2024-03-11 8:14 ` [GIT PULL 1/3] Broadcom devicetree-arm64 " Arnd Bergmann
2024-03-11 19:50 ` patchwork-bot+linux-soc
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=20240307200441.2151734-2-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).