From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kamal Dasu <kamal.dasu@broadcom.com>,
andersson@kernel.org, baolin.wang@linux.alibaba.com,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
florian.fainelli@broadcom.com, ulf.hansson@linaro.org,
adrian.hunter@intel.com
Cc: bcm-kernel-feedback-list@broadcom.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
Kamal Dasu <kdasu@broadcom.com>
Subject: Re: [PATCH 3/4] dt-bindings: mmc: add brcmstb share register and hwlocks reference
Date: Sun, 13 Jul 2025 10:40:01 +0200 [thread overview]
Message-ID: <3bec28b9-5ac6-4d93-887d-481495d6cf95@kernel.org> (raw)
In-Reply-To: <20250711154221.928164-5-kamal.dasu@broadcom.com>
On 11/07/2025 17:42, Kamal Dasu wrote:
> From: Kamal Dasu <kdasu@broadcom.com>
>
> Adding optional controller share registers and hwspinlock reference fields
> to be used by sdhci-brcmstb driver.
>
> Signed-off-by: Kamal Dasu <kamal.dasu@broadcom.com>
> ---
> .../bindings/mmc/brcm,sdhci-brcmstb.yaml | 29 +++++++++++++++++--
> 1 file changed, 27 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml b/Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml
> index eee6be7a7867..fe9be7a7eca5 100644
> --- a/Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml
> +++ b/Documentation/devicetree/bindings/mmc/brcm,sdhci-brcmstb.yaml
> @@ -27,15 +27,20 @@ properties:
> - const: brcm,sdhci-brcmstb
>
> reg:
> - maxItems: 2
> + minItems: 2
> + maxItems: 4
>
> reg-names:
> + minItems: 2
> items:
> - const: host
> - const: cfg
> + - const: share # Optional reg
> + - const: flshr_ipis0 # Optional reg
Drop comments. Schema says these are optional, so no need to point obvious.
>
> interrupts:
> - maxItems: 1
> + minItems: 1
> + maxItems: 2
You need to list items with minItem: 1.
Why all devices now got new reg and interrupts? What changed in EXISTING
hardware? All this has to be explained in the commit msg. If not all
devices got it, then you miss constraints.
>
> clocks:
> minItems: 1
> @@ -60,6 +65,9 @@ properties:
> type: boolean
> description: Specifies that controller should use auto CMD12
>
> + hwlocks:
> + maxItems: 1
> +
> allOf:
> - $ref: mmc-controller.yaml#
> - if:
> @@ -115,3 +123,20 @@ examples:
> clocks = <&scmi_clk 245>;
> clock-names = "sw_sdio";
> };
> + - |
> + mmc@84b1000 {
> + mmc-ddr-1_8v;
> + mmc-hs200-1_8v;
> + mmc-hs400-1_8v;
> + no-sd;
> + no-sdio;
> + non-removable;
> + bus-width = <0x8>;
> + compatible = "brcm,bcm74165b0-sdhci", "brcm,sdhci-brcmstb";
> + reg = <0x84b1000 0x260>, <0x84b1300 0x200>, <0x84b1600 0x10>, <0x84a5404 0x4>;
> + reg-names = "host", "cfg", "share", "flshr_ipis0";
> + hwlocks = <&hw_lock 0x0>;
> + interrupts = <0x1 0x0 0x1f 0x4 0x1b 0x11>;
Undecipherable.
> + clocks = <&scmi_clk 245>;
> + clock-names = "sw_sdio";
Totally random order of properties. Please align it closely with DTS
coding style.
> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-13 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 15:42 [PATCH 0/4] mmc: sdhci-brcmstb: rpmb sharing by claiming host for TZOS Kamal Dasu
2025-07-11 15:42 ` Kamal Dasu
2025-07-11 15:42 ` [PATCH 1/4] dt-bindings: brcmstb-hwspinlock: support for hwspinlock Kamal Dasu
2025-07-13 8:37 ` Krzysztof Kozlowski
2025-07-11 15:42 ` [PATCH 2/4] hwspinlock: brcmstb hardware semaphore support Kamal Dasu
2025-07-13 6:33 ` kernel test robot
2025-07-11 15:42 ` [PATCH 3/4] dt-bindings: mmc: add brcmstb share register and hwlocks reference Kamal Dasu
2025-07-13 8:40 ` Krzysztof Kozlowski [this message]
2025-07-11 15:42 ` [PATCH 4/4] mmc: sdhci-brcmstb: rpmb sharing by claiming host for TZOS Kamal Dasu
2025-07-13 8:44 ` Krzysztof Kozlowski
2025-07-28 9:11 ` [PATCH 0/4] " Adrian Hunter
2025-07-31 16:43 ` 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=3bec28b9-5ac6-4d93-887d-481495d6cf95@kernel.org \
--to=krzk@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=andersson@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=kdasu@broadcom.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®