From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: devicetree@vger.kernel.org, "Lee Jones" <lee.jones@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] dt-bindings: mfd: add Broadcom's MISC block
Date: Tue, 24 Aug 2021 09:30:26 -0500 [thread overview]
Message-ID: <YSUCgmC3pr7NbSDG@robh.at.kernel.org> (raw)
In-Reply-To: <20210819152552.23784-1-zajec5@gmail.com>
On Thu, 19 Aug 2021 17:25:52 +0200, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Broadcom's MISC is an MFD hardware block used on some of their SoCs like
> bcm63xx and bcm4908. At this point only PCIe reset is fully understood
> and documented. More functions may be added later.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> Broadcom's BCM4908 struct with MISC block registers:
>
> typedef struct Misc {
> uint32 miscStrapBus; /* 0x00 */
> uint32 miscStrapOverride; /* 0x04 */
> uint32 miscSoftwareDebug[6]; /* 0x08 */
> uint32 miscWDResetCtrl; /* 0x20 */
> uint32 miscSoftwareDebugNW[2];/* 0x24 */
> uint32 miscSoftResetB; /* 0x2c */
> uint32 miscQAMPllStatus; /* 0x30 */
> uint32 miscRsvd1; /* 0x34 */
> uint32 miscSpiMasterCtrl; /* 0x38 */
> uint32 miscAltBootVector; /* 0x3c */
> uint32 miscPeriphCtrl; /* 0x40 */
> uint32 miscPCIECtrl; /* 0x44 */
> uint32 miscAdsl_clock_sample; /* 0x48 */
> uint32 miscRngCtrl; /* 0x4c */
> uint32 miscMbox_data[4]; /* 0x50 */
> uint32 miscMbox_ctrl; /* 0x60 */
> uint32 miscxMIIPadCtrl[4]; /* 0x64 */
> uint32 miscxMIIPullCtrl[4]; /* 0x74 */
> uint32 miscWDResetEn; /* 0x84 */
> uint32 miscBootOverlayEn; /* 0x88 */
> uint32 miscSGMIIFiberDetect; /* 0x8c */
> uint32 miscUniMacCtrl; /* 0x90 */
> uint32 miscMaskUBUSErr; /* 0x94 */
> uint32 miscTOSsync; /* 0x98 */
> uint32 miscPM0_1_status; /* 0x9c */
> uint32 miscPM2_3_status; /* 0xa0 */
> uint32 miscSGB_status; /* 0xa4 */
> uint32 miscPM0_1_config; /* 0xa8 */
> uint32 miscPM2_3_config; /* 0xac */
> uint32 miscSGB_config; /* 0xb0 */
> uint32 miscPM0_1_tmon_config; /* 0xb4 */
> uint32 miscPM2_3_tmon_config; /* 0xb8 */
> uint32 miscSGB_tmon_config; /* 0xbc */
> uint32 miscMDIOmasterSelect; /* 0xc0 */
> uint32 miscUSIMCtrl; /* 0xc4 */
> uint32 miscUSIMPadCtrl; /* 0xc8 */
> uint32 miscPerSpareReg[3]; /* 0xcc - 0xd4 */
> uint32 miscDgSensePadCtrl; /* 0xd8 */
> uint32 miscPeriphMiscCtrl; /* 0xdc */
> uint32 miscPeriphMiscStat; /* 0xe0 */
> } Misc;
> ---
> .../devicetree/bindings/mfd/brcm,misc.yaml | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mfd/brcm,misc.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-08-24 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 15:25 [PATCH] dt-bindings: mfd: add Broadcom's MISC block Rafał Miłecki
2021-08-22 10:34 ` Florian Fainelli
2021-08-24 14:30 ` Rob Herring [this message]
2021-09-21 16:19 ` Lee Jones
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=YSUCgmC3pr7NbSDG@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=zajec5@gmail.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;
as well as URLs for NNTP newsgroup(s).