From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vivek Yadav <vivek.2311@samsung.com>,
pankaj.dubey@samsung.com, ravi.patel@samsung.com,
shradha.t@samsung.com, mturquette@baylibre.com, sboyd@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
will@kernel.org, mark.rutland@arm.com, s.nawrocki@samsung.com,
cw00.choi@samsung.com, alim.akhtar@samsung.com,
linux-fsd@tesla.com
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 5/6] arm64: dts: fsd: Add PPMU support for MFC block of FSD SoC
Date: Wed, 9 Jul 2025 16:02:36 +0200 [thread overview]
Message-ID: <ae058bda-c51a-4df0-b93c-5926030918a4@kernel.org> (raw)
In-Reply-To: <20250708103208.79444-6-vivek.2311@samsung.com>
On 08/07/2025 12:32, Vivek Yadav wrote:
> Add device tree node for PPMU instances in MFC block and
> enable the same for Tesla FSD platform.
>
> Signed-off-by: Ravi Patel <ravi.patel@samsung.com>
> Signed-off-by: Vivek Yadav <vivek.2311@samsung.com>
> ---
> arch/arm64/boot/dts/tesla/fsd-evb.dts | 8 ++++++++
> arch/arm64/boot/dts/tesla/fsd.dtsi | 20 ++++++++++++++++++++
> 2 files changed, 28 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/tesla/fsd-evb.dts b/arch/arm64/boot/dts/tesla/fsd-evb.dts
> index 8d7794642900..f543c7dad7cc 100644
> --- a/arch/arm64/boot/dts/tesla/fsd-evb.dts
> +++ b/arch/arm64/boot/dts/tesla/fsd-evb.dts
> @@ -110,3 +110,11 @@ &serial_0 {
> &ufs {
> status = "okay";
> };
> +
> +&ppmu0_mfc {
Follow DTS coding style.
> + status = "okay";
> +};
> +
> +&ppmu1_mfc {
> + status = "okay";
> +};
> diff --git a/arch/arm64/boot/dts/tesla/fsd.dtsi b/arch/arm64/boot/dts/tesla/fsd.dtsi
> index 690b4ed9c29b..7b6e7d81be10 100644
> --- a/arch/arm64/boot/dts/tesla/fsd.dtsi
> +++ b/arch/arm64/boot/dts/tesla/fsd.dtsi
> @@ -970,6 +970,26 @@ timer@10040000 {
> clock-names = "fin_pll", "mct";
> };
>
> + ppmu0_mfc: ppmu@12840000 {
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> + compatible = "samsung,ppmu-v2";
See writing bindings, DTS coding style and all other documents there
explaining why this is wrong.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-09 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250708103228epcas5p27886821d1ff225f2e5cdd4d948d03a66@epcas5p2.samsung.com>
2025-07-08 10:32 ` [PATCH 0/6] Add PPMU support for Tesla FSD Vivek Yadav
[not found] ` <CGME20250708103231epcas5p1b9fe52dd6ea3cdd65a5df163ba05e139@epcas5p1.samsung.com>
2025-07-08 10:32 ` [PATCH 1/6] dt-bindings: clock: Add PPMU clock definitions for FSD platform Vivek Yadav
[not found] ` <CGME20250708103234epcas5p1a92b0b57315f6e81c906fedcc232c279@epcas5p1.samsung.com>
2025-07-08 10:32 ` [PATCH 2/6] clk: samsung: fsd: Use clock IDs for PPMU MFC block Vivek Yadav
[not found] ` <CGME20250708103237epcas5p1c4c5d7a5f43c0c88317e74d2f2458a1b@epcas5p1.samsung.com>
2025-07-08 10:32 ` [PATCH 3/6] dt-bindings: perf: Add devicetree binding for custom PPMU Vivek Yadav
2025-07-09 14:01 ` Krzysztof Kozlowski
[not found] ` <CGME20250708103240epcas5p336539d4c3a1fb489708c61f9aae6bfa8@epcas5p3.samsung.com>
2025-07-08 10:32 ` [PATCH 4/6] drivers: perf: samsung: Add PPMU driver support Vivek Yadav
2025-07-09 14:05 ` Krzysztof Kozlowski
2025-07-11 14:45 ` Jonathan Cameron
[not found] ` <CGME20250708103243epcas5p2d8fd5bf02e64e104eca3def802813230@epcas5p2.samsung.com>
2025-07-08 10:32 ` [PATCH 5/6] arm64: dts: fsd: Add PPMU support for MFC block of FSD SoC Vivek Yadav
2025-07-09 14:02 ` Krzysztof Kozlowski [this message]
[not found] ` <CGME20250708103246epcas5p47b446ec342f9d49361c0a9a3929bcdd2@epcas5p4.samsung.com>
2025-07-08 10:32 ` [PATCH 6/6] MAINTAINERS: Add maintainers for Samsung PPMU driver Vivek Yadav
2025-07-09 14:06 ` Krzysztof Kozlowski
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=ae058bda-c51a-4df0-b93c-5926030918a4@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-fsd@tesla.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=pankaj.dubey@samsung.com \
--cc=ravi.patel@samsung.com \
--cc=robh@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@kernel.org \
--cc=shradha.t@samsung.com \
--cc=vivek.2311@samsung.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).