From: Nishanth Menon <nm@ti.com>
To: MD Danish Anwar <danishanwar@ti.com>
Cc: Suman Anna <s-anna@ti.com>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <srk@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Roger Quadros <rogerq@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 2/2] dt-bindings: soc: ti: pruss: Add documentation for PA_STATS support
Date: Fri, 28 Jun 2024 01:34:23 -0500 [thread overview]
Message-ID: <20240628063423.cprgwhatogc2dapo@stuffing> (raw)
In-Reply-To: <cca91f88-d7cd-42e3-a4f3-065d536e623b@ti.com>
On 10:56-20240628, MD Danish Anwar wrote:
>
>
> On 27/06/24 8:15 pm, Nishanth Menon wrote:
> > On 21:03-20240625, MD Danish Anwar wrote:
> >> Add documentation for pa-stats node which is syscon regmap for
> >> PA_STATS registers. This will be used to dump statistics maintained by
> >> ICSSG firmware.
> >>
> >> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
> >> ---
> >> .../devicetree/bindings/soc/ti/ti,pruss.yaml | 20 +++++++++++++++++++
> >> 1 file changed, 20 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> >> index c402cb2928e8..3cb1471cc6b6 100644
> >> --- a/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> >> +++ b/Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> >> @@ -278,6 +278,26 @@ patternProperties:
> >>
> >> additionalProperties: false
> >>
> >> + ^pa-stats@[a-f0-9]+$:
> >> + description: |
> >> + PA-STATS sub-module represented as a SysCon. PA_STATS is a set of
> >> + registers where different statistics related to ICSSG, are dumped by
> >> + ICSSG firmware. This syscon sub-module will help the device to
> >> + access/read/write those statistics.
> >> +
> >> + type: object
> >> +
> >> + additionalProperties: false
> >> +
> >> + properties:
> >> + compatible:
> >> + items:
> >> + - const: ti,pruss-pa-st
> >> + - const: syscon
> >> +
> >> + reg:
> >> + maxItems: 1
> >> +
> >
> > Is this a patch in a driver series? I do not see the driver part..
>
> No Nishant, this is not a part of driver series. This binding patch is
> related to [1] which is merged to net-next. The regmap will not be used
> by drivers/soc/ti driver instead once both binding are in, the driver
> changes will be needed in drivers/net/ethernet/ti/icssg/icssg_prueth.c
> as there is no driver changes needed in drivers/soc/ti, I posted this
> patch as stand alone. Considering this binding and [1] they both go to
> different tree, I decided to get the bindings in first and in next
> kernel cycle when they both are part of mainline linux, I can post the
> driver changes.
This is indicating some strong coupling that is sounding a bit
suspicious. Please add in the full series so that folks can see the
inter dependencies.
>
> > if this is a memory map, why doesn't bus model work?
> >
>
> I am just trying to maintain consistency here. pa-stats sub-module is
> similar to mii-g-rt and mii-rt. I am adding pa-stats in the same way as
> mii-g-rt and mii-rt.
>
> All these three modules are eventually mapping a memory region so that
> the icssg driver can use them and read / configure registers.
Sounds like mapping a bus is more appropriate? I dont seem to see it
though.
>
> >
> >> interrupt-controller@[a-f0-9]+$:
> >> description: |
> >> PRUSS INTC Node. Each PRUSS has a single interrupt controller instance
> >> --
> >> 2.34.1
> >>
> >
>
> [1] https://lore.kernel.org/all/20240529115225.630535-1-danishanwar@ti.com/
>
> --
> Thanks and Regards,
> Danish
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2024-06-28 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 15:33 [PATCH v3 0/2] Add documentation for PA_STATS and MAINTAINERS entry for ti,pruss.yaml MD Danish Anwar
2024-06-25 15:33 ` [PATCH v3 1/2] MAINTAINERS: Add entry for ti,pruss.yaml to TI KEYSTONE MULTICORE NAVIGATOR DRIVERS MD Danish Anwar
2024-06-25 15:33 ` [PATCH v3 2/2] dt-bindings: soc: ti: pruss: Add documentation for PA_STATS support MD Danish Anwar
2024-06-27 14:45 ` Nishanth Menon
2024-06-28 5:26 ` MD Danish Anwar
2024-06-28 6:34 ` Nishanth Menon [this message]
2024-07-01 6:35 ` MD Danish Anwar
2024-07-29 11:36 ` MD Danish Anwar
2024-06-25 15:33 ` [PATCH v3 0/2] Add documentation for PA_STATS and MAINTAINERS entry for ti,pruss.yaml MD Danish Anwar
2024-06-26 8:59 ` Krzysztof Kozlowski
2024-06-26 9:03 ` MD Danish Anwar
2024-06-25 15:33 ` [PATCH v3 1/2] MAINTAINERS: Add entry for ti,pruss.yaml to TI KEYSTONE MULTICORE NAVIGATOR DRIVERS MD Danish Anwar
2024-06-25 15:33 ` [PATCH v3 2/2] dt-bindings: soc: ti: pruss: Add documentation for PA_STATS support MD Danish Anwar
2024-06-27 23:33 ` (subset) [PATCH v3 0/2] Add documentation for PA_STATS and MAINTAINERS entry for ti,pruss.yaml Nishanth Menon
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=20240628063423.cprgwhatogc2dapo@stuffing \
--to=nm@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-anna@ti.com \
--cc=srk@ti.com \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.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).