From: Florian Fainelli <f.fainelli@gmail.com>
To: arm@kernel.org
Cc: Florian Fainelli <f.fainelli@gmail.com>,
arnd@arndb.de, khilman@kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Markus Mayer <mmayer@broadcom.com>,
olof@lixom.net, linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/6] Broadcom drivers changes for 5.3
Date: Tue, 11 Jun 2019 19:50:25 -0700 [thread overview]
Message-ID: <20190612025028.13118-3-f.fainelli@gmail.com> (raw)
In-Reply-To: <20190612025028.13118-1-f.fainelli@gmail.com>
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.3/drivers
for you to fetch changes up to e3b7472362ba5ec84642e1c8d2cc8db6781afe4a:
memory: brcmstb: dpfe: introduce DPFE API v3 (2019-05-20 09:32:35 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM/ARM64/MIPS SoCs drivers changes
for 5.3, please pull the following:
- Markus provides a set of updates to the DPFE driver to support a new
revision of the API to the firmware (version 3) and provides minor fixes
about how the MR4-8 words are read for LPDDR4 devices
- Florian removes a print of a virtual address in brcmstb_gisb.c
----------------------------------------------------------------
Florian Fainelli (1):
bus: brcmstb_gisb: Remove print of base address
Markus Mayer (9):
memory: brcmstb: dpfe: use msleep() over udelay()
memory: brcmstb: dpfe: optimize generic_show()
memory: brcmstb: dpfe: use byte 3 of registers MR4-MR8
memory: brcmstb: dpfe: remove unused code and fix formatting
memory: brcmstb: dpfe: report firmware loading error
memory: brcmstb: dpfe: wait for DCPU to be ready
memory: brcmstb: dpfe: prepare support for multiple API versions
memory: brcmstb: dpfe: prepare for API-dependent sysfs attributes
memory: brcmstb: dpfe: introduce DPFE API v3
drivers/bus/brcmstb_gisb.c | 4 +-
drivers/memory/brcmstb_dpfe.c | 317 +++++++++++++++++++++++++++++++-----------
2 files changed, 240 insertions(+), 81 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-12 2:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 2:50 [GIT PULL 1/6] Broadcom devicetree changes for 5.3 Florian Fainelli
2019-06-12 2:50 ` [GIT PULL 2/6] Broadcom devicetree-arm64 " Florian Fainelli
2019-06-19 13:25 ` Olof Johansson
2019-06-12 2:50 ` Florian Fainelli [this message]
2019-06-17 11:53 ` [GIT PULL 3/6] Broadcom drivers " Olof Johansson
2019-06-12 2:50 ` [GIT PULL 4/6] Broadcom maintainers " Florian Fainelli
2019-06-19 16:10 ` Olof Johansson
2019-06-12 2:50 ` [GIT PULL 5/6] Broadcom soc " Florian Fainelli
2019-06-12 2:50 ` [GIT PULL 6/6] Broadcom soc-arm64 " Florian Fainelli
2019-06-17 12:16 ` Olof Johansson
2019-06-19 13:35 ` [GIT PULL 1/6] Broadcom devicetree " Olof Johansson
2019-06-23 2:22 ` Florian Fainelli
2019-06-25 11:17 ` Olof Johansson
2019-06-23 3:29 ` [GIT PULL 1/6 v2] Broadcom devicetree changes for 5.2 Florian Fainelli
2019-06-25 11:16 ` Olof Johansson
2019-06-25 12:56 ` 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=20190612025028.13118-3-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mmayer@broadcom.com \
--cc=olof@lixom.net \
/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).