From: "Rafał Miłecki" <zajec5@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: [PATCH V2 0/2] reset: support Broadcom's PMB
Date: Thu, 19 Nov 2020 13:55:58 +0100 [thread overview]
Message-ID: <20201119125600.8559-1-zajec5@gmail.com> (raw)
From: Rafał Miłecki <rafal@milecki.pl>
PMB is Broadcom's old reset controller. Later it was replaced by PMC
which is a wrapper around PMB.
It's still important to support older PMB as:
1. It's the only reset option on older devices
2. Sometimes PMC may be unable to handle device reset and PMB should
be used as fallback
3. Some devices may be configured not to use PMC at all
I'll get back to working on PMC later.
Rafał Miłecki (2):
dt-bindings: reset: document Broadcom's PMB binding
reset: brcm-pmb: add driver for Broadcom's PMB
.../devicetree/bindings/reset/brcm,pmb.yaml | 54 +++
drivers/reset/Kconfig | 7 +
drivers/reset/Makefile | 1 +
drivers/reset/reset-brcm-pmb.c | 307 ++++++++++++++++++
include/dt-bindings/reset/brcm,pmb.h | 9 +
5 files changed, 378 insertions(+)
create mode 100644 Documentation/devicetree/bindings/reset/brcm,pmb.yaml
create mode 100644 drivers/reset/reset-brcm-pmb.c
create mode 100644 include/dt-bindings/reset/brcm,pmb.h
--
2.26.2
next reply other threads:[~2020-11-19 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 12:55 Rafał Miłecki [this message]
2020-11-19 12:55 ` [PATCH V2 1/2] dt-bindings: reset: document Broadcom's PMB binding Rafał Miłecki
2020-12-07 22:05 ` Rob Herring
2020-11-19 12:56 ` [PATCH V2 2/2] reset: brcm-pmb: add driver for Broadcom's PMB Rafał Miłecki
2020-12-08 11:02 ` Philipp Zabel
2020-12-08 20:20 ` Florian Fainelli
2020-12-09 11:24 ` Philipp Zabel
2020-12-11 11:34 ` Rafał Miłecki
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=20201119125600.8559-1-zajec5@gmail.com \
--to=zajec5@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rafal@milecki.pl \
--cc=robh+dt@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).