From: Christian Marangi <ansuelsmth@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] dt-bindings: mips: brcm: Document brcm,bmips-cbr-reg property
Date: Wed, 8 May 2024 19:17:49 +0200 [thread overview]
Message-ID: <663bb3bf.050a0220.38dcc.9b82@mx.google.com> (raw)
In-Reply-To: <20240508-prong-serving-660e6046621d@spud>
On Wed, May 08, 2024 at 06:14:34PM +0100, Conor Dooley wrote:
> On Wed, May 08, 2024 at 07:07:18PM +0200, Christian Marangi wrote:
> > Document brcm,bmips-cbr-reg property.
> >
> > Some SoC suffer from a BUG where read_c0_brcm_cbr() might return 0
> > if called from TP1. The CBR address is always the same on the SoC
> > hence it can be provided in DT to handle broken case where bootloader
> > doesn't init it or SMP where read_c0_brcm_cbr() returns 0 from TP1.
> >
> > Usage of this property is to give an address also in these broken
> > configuration/bootloader.
> >
> > Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
> > ---
> > .../devicetree/bindings/mips/brcm/soc.yaml | 23 +++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/mips/brcm/soc.yaml b/Documentation/devicetree/bindings/mips/brcm/soc.yaml
> > index 975945ca2888..77f73ab48c11 100644
> > --- a/Documentation/devicetree/bindings/mips/brcm/soc.yaml
> > +++ b/Documentation/devicetree/bindings/mips/brcm/soc.yaml
> > @@ -55,6 +55,15 @@ properties:
> > under the "cpus" node.
> > $ref: /schemas/types.yaml#/definitions/uint32
> >
> > + brcm,bmips-cbr-reg:
> > + description: Reference address of the CBR.
>
> Pretty sure that Rob commented last time that there's no definition
> anywhere here of CBR, but I don't see either a response to him or an
> explanation in v3 as to what CBR means.
>
Sorry I missed it.
> > + Some SoC suffer from a BUG where read_c0_brcm_cbr() might
> > + return 0 if called from TP1. The CBR address is always the
> > + same on the SoC hence it can be provided in DT to handle
> > + broken case where bootloader doesn't initialise it or SMP
> > + where read_c0_brcm_cbr() returns 0 from TP1.
>
> Why is a ?linux? function name in the binding? Surely this is just
> "or in SMP systems where reading CBR returns 0 from...", no? Ditto
> above.
>
It's really just a reference to reading c0 register at an offset, that
is why I was so specific. Ok I will be more verbose.
>
> > + $ref: /schemas/types.yaml#/definitions/uint32
> > +
> > patternProperties:
> > "^cpu@[0-9]$":
> > type: object
> > @@ -64,6 +73,20 @@ properties:
> > required:
> > - mips-hpt-frequency
> >
> > +if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - brcm,bcm6358
> > + - brcm,bcm6368
> > +
> > +then:
> > + properties:
> > + cpus:
> > + required:
> > + - brcm,bmips-cbr-reg
> > +
> > additionalProperties: true
> >
> > examples:
> > --
> > 2.43.0
> >
--
Ansuel
next prev parent reply other threads:[~2024-05-08 17:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 17:07 [PATCH v3 0/4] mips: bmips: improve handling of RAC and CBR addr Christian Marangi
2024-05-08 17:07 ` [PATCH v3 1/4] mips: bmips: rework and cache CBR addr handling Christian Marangi
2024-05-08 17:07 ` [PATCH v3 2/4] dt-bindings: mips: brcm: Document brcm,bmips-cbr-reg property Christian Marangi
2024-05-08 17:14 ` Conor Dooley
2024-05-08 17:17 ` Christian Marangi [this message]
2024-05-09 16:01 ` Florian Fainelli
2024-05-08 17:07 ` [PATCH v3 3/4] mips: bmips: setup: make CBR address configurable Christian Marangi
2024-05-08 17:07 ` [PATCH v3 4/4] mips: bmips: enable RAC on BMIPS4350 Christian Marangi
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=663bb3bf.050a0220.38dcc.9b82@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.de \
--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