From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Jaewon Kim" <jaewon02.kim@samsung.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Alim Akhtar" <alim.akhtar@samsung.com>
Cc: linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Chanho Park <chanho61.park@samsung.com>
Subject: Re: [PATCH v2 2/3] pwm: samsung: Add compatible for ExynosAutov9 SoC
Date: Mon, 17 Jul 2023 07:58:53 +0200 [thread overview]
Message-ID: <31af3a96-7e98-8bb1-f9e9-53ccb0441310@linaro.org> (raw)
In-Reply-To: <20230714100929.94563-3-jaewon02.kim@samsung.com>
On 14/07/2023 12:09, Jaewon Kim wrote:
> Add new compatible string to support ExynosAutov9 SoC.
>
> Signed-off-by: Jaewon Kim <jaewon02.kim@samsung.com>
> ---
> drivers/pwm/pwm-samsung.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/pwm/pwm-samsung.c b/drivers/pwm/pwm-samsung.c
> index e8828f57ab15..50a88565c440 100644
> --- a/drivers/pwm/pwm-samsung.c
> +++ b/drivers/pwm/pwm-samsung.c
> @@ -513,6 +513,7 @@ static const struct of_device_id samsung_pwm_matches[] = {
> { .compatible = "samsung,s5p6440-pwm", .data = &s5p64x0_variant },
> { .compatible = "samsung,s5pc100-pwm", .data = &s5pc100_variant },
> { .compatible = "samsung,exynos4210-pwm", .data = &s5p64x0_variant },
> + { .compatible = "samsung,exynosautov9-pwm", .data = &s5p64x0_variant },
That's not what I asked for. You do not need entry here. Devices are
compatible.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-07-17 5:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230714101433epcas2p29094f5fa3c41e39a51a0010124ebea73@epcas2p2.samsung.com>
2023-07-14 10:09 ` [PATCH v2 0/3] support PWM for exynosautov9 Jaewon Kim
[not found] ` <CGME20230714101434epcas2p1e0788544f244e59861f45b10e450075c@epcas2p1.samsung.com>
2023-07-14 10:09 ` [PATCH v2 1/3] dt-bindings: pwm: samsung: add exynosautov9 compatible Jaewon Kim
2023-07-15 2:46 ` Rob Herring
2023-07-17 5:59 ` Krzysztof Kozlowski
[not found] ` <CGME20230714101434epcas2p3e2475698c527ca72dee797225d3dad37@epcas2p3.samsung.com>
2023-07-14 10:09 ` [PATCH v2 2/3] pwm: samsung: Add compatible for ExynosAutov9 SoC Jaewon Kim
2023-07-15 7:22 ` Uwe Kleine-König
2023-07-17 4:44 ` Jaewon Kim
2023-07-17 6:00 ` Krzysztof Kozlowski
2023-07-17 5:58 ` Krzysztof Kozlowski [this message]
2023-07-17 6:22 ` Jaewon Kim
[not found] ` <CGME20230714101434epcas2p1d52a733cf3d9c5d0d8f2c26ef1a85a00@epcas2p1.samsung.com>
2023-07-14 10:09 ` [PATCH v2 3/3] arm64: dts: exynos: add pwm node for exynosautov9-sadk Jaewon Kim
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=31af3a96-7e98-8bb1-f9e9-53ccb0441310@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jaewon02.kim@samsung.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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).