All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aakarsh Jain <aakarsh.jain@samsung.com>
To: linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: m.szyprowski@samsung.com, andrzej.hajda@intel.com,
	mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
	ezequiel@vanguardiasur.com.ar, jernej.skrabec@gmail.com,
	benjamin.gaignard@collabora.com,
	krzysztof.kozlowski+dt@linaro.org, stanimir.varbanov@linaro.org,
	dillon.minfei@gmail.com, david.plowman@raspberrypi.com,
	mark.rutland@arm.com, robh+dt@kernel.org, krzk+dt@kernel.org,
	andi@etezian.org, alim.akhtar@samsung.com,
	aswani.reddy@samsung.com, pankaj.dubey@samsung.com,
	smitha.t@samsung.com, aakarsh.jain@samsung.com
Subject: [PATCH 1/3] arm64: exynos: Add new compatible string for Exynos3250 SoC.
Date: Wed,  2 Nov 2022 18:36:00 +0530	[thread overview]
Message-ID: <20221102130602.48969-1-aakarsh.jain@samsung.com> (raw)
In-Reply-To: CGME20221102125810epcas5p36e6caf41f602debe17f25f13969fd6dc@epcas5p3.samsung.com

Exynos3250 uses the same compatible as Exynos5420, but both
the MFC IPs found in these SoC are different interms of clock
property. So using same compatible for both SoC is not correct.
Lets have a separate compatible for Exynos3250 and Exynos5420
to differentiate these SoCs.

Suggested-by: Alim Akhtar <alim.akhtar@samsung.com> 
Signed-off-by: Aakarsh Jain <aakarsh.jain@samsung.com>
---
 Documentation/devicetree/bindings/media/s5p-mfc.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

We are already in process of converting this txt file to yaml.
https://patchwork.kernel.org/project/linux-media/patch/
20221011122516.32135-2-aakarsh.jain@samsung.com/
modifying this txt binding for completeness.

diff --git a/Documentation/devicetree/bindings/media/s5p-mfc.txt b/Documentation/devicetree/bindings/media/s5p-mfc.txt
index aa54c8159d9f..4ff1898e5a51 100644
--- a/Documentation/devicetree/bindings/media/s5p-mfc.txt
+++ b/Documentation/devicetree/bindings/media/s5p-mfc.txt
@@ -11,9 +11,10 @@ Required properties:
 	(a) "samsung,mfc-v5" for MFC v5 present in Exynos4 SoCs
 	(b) "samsung,mfc-v6" for MFC v6 present in Exynos5 SoCs
 	(c) "samsung,mfc-v7" for MFC v7 present in Exynos5420 SoC
-	(d) "samsung,mfc-v8" for MFC v8 present in Exynos5800 SoC
-	(e) "samsung,exynos5433-mfc" for MFC v8 present in Exynos5433 SoC
-	(f) "samsung,mfc-v10" for MFC v10 present in Exynos7880 SoC
+	(d) "samsung,exynos3250-mfc" for MFC v7 present in Exynos3250 SoC
+	(e) "samsung,mfc-v8" for MFC v8 present in Exynos5800 SoC
+	(f) "samsung,exynos5433-mfc" for MFC v8 present in Exynos5433 SoC
+	(g) "samsung,mfc-v10" for MFC v10 present in Exynos7880 SoC
 
   - reg : Physical base address of the IP registers and length of memory
 	  mapped region.
-- 
2.17.1


WARNING: multiple messages have this Message-ID (diff)
From: Aakarsh Jain <aakarsh.jain@samsung.com>
To: linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Cc: m.szyprowski@samsung.com, andrzej.hajda@intel.com,
	mchehab@kernel.org, hverkuil-cisco@xs4all.nl,
	ezequiel@vanguardiasur.com.ar, jernej.skrabec@gmail.com,
	benjamin.gaignard@collabora.com,
	krzysztof.kozlowski+dt@linaro.org, stanimir.varbanov@linaro.org,
	dillon.minfei@gmail.com, david.plowman@raspberrypi.com,
	mark.rutland@arm.com, robh+dt@kernel.org, krzk+dt@kernel.org,
	andi@etezian.org, alim.akhtar@samsung.com,
	aswani.reddy@samsung.com, pankaj.dubey@samsung.com,
	smitha.t@samsung.com, aakarsh.jain@samsung.com
Subject: [PATCH 1/3] arm64: exynos: Add new compatible string for Exynos3250 SoC.
Date: Wed,  2 Nov 2022 18:36:00 +0530	[thread overview]
Message-ID: <20221102130602.48969-1-aakarsh.jain@samsung.com> (raw)
In-Reply-To: CGME20221102125810epcas5p36e6caf41f602debe17f25f13969fd6dc@epcas5p3.samsung.com

Exynos3250 uses the same compatible as Exynos5420, but both
the MFC IPs found in these SoC are different interms of clock
property. So using same compatible for both SoC is not correct.
Lets have a separate compatible for Exynos3250 and Exynos5420
to differentiate these SoCs.

Suggested-by: Alim Akhtar <alim.akhtar@samsung.com> 
Signed-off-by: Aakarsh Jain <aakarsh.jain@samsung.com>
---
 Documentation/devicetree/bindings/media/s5p-mfc.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

We are already in process of converting this txt file to yaml.
https://patchwork.kernel.org/project/linux-media/patch/
20221011122516.32135-2-aakarsh.jain@samsung.com/
modifying this txt binding for completeness.

diff --git a/Documentation/devicetree/bindings/media/s5p-mfc.txt b/Documentation/devicetree/bindings/media/s5p-mfc.txt
index aa54c8159d9f..4ff1898e5a51 100644
--- a/Documentation/devicetree/bindings/media/s5p-mfc.txt
+++ b/Documentation/devicetree/bindings/media/s5p-mfc.txt
@@ -11,9 +11,10 @@ Required properties:
 	(a) "samsung,mfc-v5" for MFC v5 present in Exynos4 SoCs
 	(b) "samsung,mfc-v6" for MFC v6 present in Exynos5 SoCs
 	(c) "samsung,mfc-v7" for MFC v7 present in Exynos5420 SoC
-	(d) "samsung,mfc-v8" for MFC v8 present in Exynos5800 SoC
-	(e) "samsung,exynos5433-mfc" for MFC v8 present in Exynos5433 SoC
-	(f) "samsung,mfc-v10" for MFC v10 present in Exynos7880 SoC
+	(d) "samsung,exynos3250-mfc" for MFC v7 present in Exynos3250 SoC
+	(e) "samsung,mfc-v8" for MFC v8 present in Exynos5800 SoC
+	(f) "samsung,exynos5433-mfc" for MFC v8 present in Exynos5433 SoC
+	(g) "samsung,mfc-v10" for MFC v10 present in Exynos7880 SoC
 
   - reg : Physical base address of the IP registers and length of memory
 	  mapped region.
-- 
2.17.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

       reply	other threads:[~2022-11-03  5:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221102125810epcas5p36e6caf41f602debe17f25f13969fd6dc@epcas5p3.samsung.com>
2022-11-02 13:06 ` Aakarsh Jain [this message]
2022-11-02 13:06   ` [PATCH 1/3] arm64: exynos: Add new compatible string for Exynos3250 SoC Aakarsh Jain
     [not found]   ` <CGME20221102125813epcas5p40a38f17a267276ff8b2bc5861b5d450d@epcas5p4.samsung.com>
2022-11-02 13:06     ` [PATCH 2/3] media: s5p-mfc:Add variant data for MFC v7 hardware for Exynos 3250 SOC Aakarsh Jain
2022-11-02 13:06       ` Aakarsh Jain
2022-11-03 10:54       ` Tommaso Merciai
2022-11-03 10:54         ` Tommaso Merciai
2022-11-03 12:35       ` Krzysztof Kozlowski
2022-11-03 12:35         ` Krzysztof Kozlowski
2022-11-03 12:44         ` Marek Szyprowski
2022-11-03 12:44           ` Marek Szyprowski
2022-11-03 12:46           ` Krzysztof Kozlowski
2022-11-03 12:46             ` Krzysztof Kozlowski
2022-11-09  4:02             ` Aakarsh Jain
2022-11-09  4:02               ` Aakarsh Jain
     [not found]   ` <CGME20221102125816epcas5p23e16fefd6b820e7dd7d9a93f0d48f40d@epcas5p2.samsung.com>
2022-11-02 13:06     ` [PATCH 3/3] arm64: dts: exynos: Rename compatible string property from version to SOC specific Aakarsh Jain
2022-11-02 13:06       ` Aakarsh Jain
2022-11-03 10:56       ` Tommaso Merciai
2022-11-03 10:56         ` Tommaso Merciai
2022-11-03 12:33       ` Krzysztof Kozlowski
2022-11-03 12:33         ` Krzysztof Kozlowski
2022-11-04 10:49         ` Aakarsh Jain
2022-11-04 10:49           ` Aakarsh Jain
2022-11-04 12:53           ` Krzysztof Kozlowski
2022-11-04 12:53             ` Krzysztof Kozlowski
2022-11-03  9:24   ` [PATCH 1/3] arm64: exynos: Add new compatible string for Exynos3250 SoC Marek Szyprowski
2022-11-03  9:24     ` Marek Szyprowski
2022-11-03 10:41   ` Tommaso Merciai
2022-11-03 10:41     ` Tommaso Merciai
2022-11-03 12:32   ` Krzysztof Kozlowski
2022-11-03 12:32     ` 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=20221102130602.48969-1-aakarsh.jain@samsung.com \
    --to=aakarsh.jain@samsung.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andi@etezian.org \
    --cc=andrzej.hajda@intel.com \
    --cc=aswani.reddy@samsung.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=david.plowman@raspberrypi.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dillon.minfei@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=pankaj.dubey@samsung.com \
    --cc=robh+dt@kernel.org \
    --cc=smitha.t@samsung.com \
    --cc=stanimir.varbanov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.