From: Florian Fainelli <f.fainelli@gmail.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"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: Re: [PATCH 1/2] dt-bindings: reset: document Broadcom's PMB binding
Date: Wed, 18 Nov 2020 13:47:01 -0800 [thread overview]
Message-ID: <3d66b723-3817-3fff-a464-8c04d9203f18@gmail.com> (raw)
In-Reply-To: <d09b2767-66df-fee6-cfc8-3eba116e10af@gmail.com>
On 11/18/20 1:45 PM, Florian Fainelli wrote:
> On 11/18/20 5:24 AM, Rafał Miłecki wrote:
>> From: Rafał Miłecki <rafal@milecki.pl>
>>
>> Broadcom's PMB is reset controller used for disabling and enabling SoC
>> devices.
>>
>> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>> ---
>> .../devicetree/bindings/reset/brcm,pmb.yaml | 51 +++++++++++++++++++
>> include/dt-bindings/reset/brcm,pmb.h | 9 ++++
>> 2 files changed, 60 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/reset/brcm,pmb.yaml
>> create mode 100644 include/dt-bindings/reset/brcm,pmb.h
>>
>> diff --git a/Documentation/devicetree/bindings/reset/brcm,pmb.yaml b/Documentation/devicetree/bindings/reset/brcm,pmb.yaml
>> new file mode 100644
>> index 000000000000..ea78ab629c45
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/reset/brcm,pmb.yaml
>> @@ -0,0 +1,51 @@
>> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/reset/brcm,pmb.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Broadcom PMB Master reset controller
>> +
>> +description: This document describes Broadcom's PMB controller. It supports
>> + resetting various types of connected devices (e.g. PCIe, USB, SATA). It
>> + requires specifying device address.
>> +
>> +maintainers:
>> + - Rafał Miłecki <rafal@milecki.pl>
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - brcm,bcm4908-pmb # PMB on BCM4908 and compatible SoCs
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + big-endian:
>> + $ref: /schemas/types.yaml#/definitions/flag
>> + description:
>> + Flag to use for block working in big endian mode.
>> +
>> + "#reset-cells":
>> + const: 2
>
> I believe we would need a description of the #reset-cells property that
> indicates what they do.
>
> Other than that and the build failure below:
I don't know how to express constraints on each of the cells, but since
they are represented by 8 bits you may want to add mininimum: 0 /
maximum: 255 constraints in the YAML binding.
--
Florian
next prev parent reply other threads:[~2020-11-18 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 13:24 [PATCH 0/2] reset: support Broadcom's PMB Rafał Miłecki
2020-11-18 13:24 ` [PATCH 1/2] dt-bindings: reset: document Broadcom's PMB binding Rafał Miłecki
2020-11-18 21:25 ` Rob Herring
2020-11-18 21:45 ` Florian Fainelli
2020-11-18 21:47 ` Florian Fainelli [this message]
2020-11-19 9:54 ` Rafał Miłecki
2020-11-18 21:53 ` Rafał Miłecki
2020-11-18 13:24 ` [PATCH 2/2] reset: brcm-pmc: add driver for Broadcom's PMB Rafał Miłecki
2020-11-18 21:50 ` 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=3d66b723-3817-3fff-a464-8c04d9203f18@gmail.com \
--to=f.fainelli@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 \
--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).