From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>,
bcm-kernel-feedback-list@broadcom.com,
Eric Anholt <eric@anholt.net>
Subject: [GIT PULL] bcm2835-drivers-next-2019-03-12
Date: Tue, 12 Mar 2019 13:06:56 -0700 [thread overview]
Message-ID: <20190312200656.30759-1-eric@anholt.net> (raw)
Hi Florian,
here's an updated PR on top of bcm2835-drivers-next-2019-02-01.
The following changes since commit e1dc2b2e1bef7237fd8fc055fe1ec2a6ff001f91:
ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware. (2019-02-01 10:34:32 +0100)
are available in the Git repository at:
git://github.com/anholt/linux tags/bcm2835-drivers-next-2019-03-12
for you to fetch changes up to 7a9b6be9fe58194d9a349159176e8cc0d8f10ef8:
arm64: bcm2835: Add missing dependency on MFD_CORE. (2019-03-12 13:01:05 -0700)
----------------------------------------------------------------
This pull request brings in a build fix for arm64 with bcm2835
enabled, and fixes the driver in the presence of -EPROBE_DEFER.
----------------------------------------------------------------
Eric Anholt (3):
soc: bcm: bcm2835-pm: Fix PM_IMAGE_PERI power domain support.
soc: bcm: bcm2835-pm: Fix error paths of initialization.
arm64: bcm2835: Add missing dependency on MFD_CORE.
arch/arm64/Kconfig.platforms | 1 +
drivers/soc/bcm/bcm2835-power.c | 49 +++++++++++++++++++++++++++++++++++------
2 files changed, 43 insertions(+), 7 deletions(-)
next reply other threads:[~2019-03-12 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 20:06 Eric Anholt [this message]
2019-03-18 17:31 ` 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=20190312200656.30759-1-eric@anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--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 \
--cc=stefan.wahren@i2se.com \
/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
all inboxes | Powered by JetHome®