From: Chanwoo Choi <cw00.choi@samsung.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org, jic23@kernel.org,
ch.naveen@samsung.com, mark.rutland@arm.com,
devicetree@vger.kernel.org, kgene.kim@samsung.com,
pawel.moll@arm.com, ijc+devicetree@hellion.org.uk,
linux-iio@vger.kernel.org, t.figa@samsung.com,
rdunlap@infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
kyungmin.park@samsung.com, robh+dt@kernel.org,
galak@codeaurora.org
Subject: Re: [PATCHv7 0/4] iio: adc: exynos_adc: Support Exynos3250 ADC and code clean
Date: Mon, 21 Jul 2014 17:11:12 +0900 [thread overview]
Message-ID: <53CCCB20.50802@samsung.com> (raw)
In-Reply-To: <14522743.f6oFhEQVv4@wuerfel>
On 07/21/2014 04:38 PM, Arnd Bergmann wrote:
> On Monday 21 July 2014 11:17:44 Chanwoo Choi wrote:
>>
>> This patchset support Exynos3250 ADC (Analog Digital Converter) because
>> Exynos3250 has additional special clock for ADC IP.
>>
>> Changes from v6:
>> - Use "exynos3250-adc" compatible string instead of "exynos3250-adc-v2"
>> - Use "sclk" clock name instead of "sclk_adc"
>> - Remove un-necessary macro for exyno-adc-data-v2 structure.
>> - Remove '(void *)' cast and mark the exynos-adc-data structure as 'const'
>> - Change the number of ADC channels (Exynos3250 has only two channels for ADC)
>>
>
> Looks good to me. Two small requests:
>
> a) if you don't mind, can you add my patch (1/2) to add support for s3c64xx to
> your series, adding your Signed-off-by line in addition to mine? I think
> that one was noncontroversial, while the second patch (2/2) need some more
> work to address the comments and do testing.
OK, I'll add this patch.
But, I have a question.
Your patch add following compatible string.
"s3c64100-adc" is right?
static const struct of_device_id exynos_adc_match[] = {
{
+ .compatible = "samsung,s3c64100-adc",
+ .data = &exynos_adc_s3c64xx_data,
+ }, {
>
> b) For the "compatible" string, I think it makes sense to set a fallback to
> "samsung,exynos-adc-v2" in the case for exynos3250, making the DT
> representation
>
> compatible = "samsung,exynos3250-adc", "samsung,exynos-adc-v2";
>
> It's not entirely compatible because of the addition of the clock, but
> since the register layout is the same, I think it still make sense.
OK, I'll add it in exynos3250.dtsi as following:
adc: adc@126C0000 {
- compatible = "samsung,exynos-adc-v3";
+ compatible = "samsung,exynos3250-adc",
+ "samsung,exynos-adc-v2";
reg = <0x126C0000 0x100>, <0x10020718 0x4>;
interrupts = <0 137 0>;
- clock-names = "adc", "sclk_tsadc";
+ clock-names = "adc", "sclk";
clocks = <&cmu CLK_TSADC>, <&cmu CLK_SCLK_TSADC>;
#io-channel-cells = <1>;
io-channel-ranges;
Thanks,
Chanwoo Choi
>
> Thanks.
>
> For the entire series,
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
WARNING: multiple messages have this Message-ID (diff)
From: Chanwoo Choi <cw00.choi-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
ch.naveen-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kgene.kim-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
t.figa-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kyungmin.park-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org
Subject: Re: [PATCHv7 0/4] iio: adc: exynos_adc: Support Exynos3250 ADC and code clean
Date: Mon, 21 Jul 2014 17:11:12 +0900 [thread overview]
Message-ID: <53CCCB20.50802@samsung.com> (raw)
In-Reply-To: <14522743.f6oFhEQVv4@wuerfel>
On 07/21/2014 04:38 PM, Arnd Bergmann wrote:
> On Monday 21 July 2014 11:17:44 Chanwoo Choi wrote:
>>
>> This patchset support Exynos3250 ADC (Analog Digital Converter) because
>> Exynos3250 has additional special clock for ADC IP.
>>
>> Changes from v6:
>> - Use "exynos3250-adc" compatible string instead of "exynos3250-adc-v2"
>> - Use "sclk" clock name instead of "sclk_adc"
>> - Remove un-necessary macro for exyno-adc-data-v2 structure.
>> - Remove '(void *)' cast and mark the exynos-adc-data structure as 'const'
>> - Change the number of ADC channels (Exynos3250 has only two channels for ADC)
>>
>
> Looks good to me. Two small requests:
>
> a) if you don't mind, can you add my patch (1/2) to add support for s3c64xx to
> your series, adding your Signed-off-by line in addition to mine? I think
> that one was noncontroversial, while the second patch (2/2) need some more
> work to address the comments and do testing.
OK, I'll add this patch.
But, I have a question.
Your patch add following compatible string.
"s3c64100-adc" is right?
static const struct of_device_id exynos_adc_match[] = {
{
+ .compatible = "samsung,s3c64100-adc",
+ .data = &exynos_adc_s3c64xx_data,
+ }, {
>
> b) For the "compatible" string, I think it makes sense to set a fallback to
> "samsung,exynos-adc-v2" in the case for exynos3250, making the DT
> representation
>
> compatible = "samsung,exynos3250-adc", "samsung,exynos-adc-v2";
>
> It's not entirely compatible because of the addition of the clock, but
> since the register layout is the same, I think it still make sense.
OK, I'll add it in exynos3250.dtsi as following:
adc: adc@126C0000 {
- compatible = "samsung,exynos-adc-v3";
+ compatible = "samsung,exynos3250-adc",
+ "samsung,exynos-adc-v2";
reg = <0x126C0000 0x100>, <0x10020718 0x4>;
interrupts = <0 137 0>;
- clock-names = "adc", "sclk_tsadc";
+ clock-names = "adc", "sclk";
clocks = <&cmu CLK_TSADC>, <&cmu CLK_SCLK_TSADC>;
#io-channel-cells = <1>;
io-channel-ranges;
Thanks,
Chanwoo Choi
>
> Thanks.
>
> For the entire series,
>
> Acked-by: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
WARNING: multiple messages have this Message-ID (diff)
From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv7 0/4] iio: adc: exynos_adc: Support Exynos3250 ADC and code clean
Date: Mon, 21 Jul 2014 17:11:12 +0900 [thread overview]
Message-ID: <53CCCB20.50802@samsung.com> (raw)
In-Reply-To: <14522743.f6oFhEQVv4@wuerfel>
On 07/21/2014 04:38 PM, Arnd Bergmann wrote:
> On Monday 21 July 2014 11:17:44 Chanwoo Choi wrote:
>>
>> This patchset support Exynos3250 ADC (Analog Digital Converter) because
>> Exynos3250 has additional special clock for ADC IP.
>>
>> Changes from v6:
>> - Use "exynos3250-adc" compatible string instead of "exynos3250-adc-v2"
>> - Use "sclk" clock name instead of "sclk_adc"
>> - Remove un-necessary macro for exyno-adc-data-v2 structure.
>> - Remove '(void *)' cast and mark the exynos-adc-data structure as 'const'
>> - Change the number of ADC channels (Exynos3250 has only two channels for ADC)
>>
>
> Looks good to me. Two small requests:
>
> a) if you don't mind, can you add my patch (1/2) to add support for s3c64xx to
> your series, adding your Signed-off-by line in addition to mine? I think
> that one was noncontroversial, while the second patch (2/2) need some more
> work to address the comments and do testing.
OK, I'll add this patch.
But, I have a question.
Your patch add following compatible string.
"s3c64100-adc" is right?
static const struct of_device_id exynos_adc_match[] = {
{
+ .compatible = "samsung,s3c64100-adc",
+ .data = &exynos_adc_s3c64xx_data,
+ }, {
>
> b) For the "compatible" string, I think it makes sense to set a fallback to
> "samsung,exynos-adc-v2" in the case for exynos3250, making the DT
> representation
>
> compatible = "samsung,exynos3250-adc", "samsung,exynos-adc-v2";
>
> It's not entirely compatible because of the addition of the clock, but
> since the register layout is the same, I think it still make sense.
OK, I'll add it in exynos3250.dtsi as following:
adc: adc at 126C0000 {
- compatible = "samsung,exynos-adc-v3";
+ compatible = "samsung,exynos3250-adc",
+ "samsung,exynos-adc-v2";
reg = <0x126C0000 0x100>, <0x10020718 0x4>;
interrupts = <0 137 0>;
- clock-names = "adc", "sclk_tsadc";
+ clock-names = "adc", "sclk";
clocks = <&cmu CLK_TSADC>, <&cmu CLK_SCLK_TSADC>;
#io-channel-cells = <1>;
io-channel-ranges;
Thanks,
Chanwoo Choi
>
> Thanks.
>
> For the entire series,
>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
>
> Arnd
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2014-07-21 8:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 2:17 [PATCHv7 0/4] iio: adc: exynos_adc: Support Exynos3250 ADC and code clean Chanwoo Choi
2014-07-21 2:17 ` Chanwoo Choi
2014-07-21 2:17 ` Chanwoo Choi
2014-07-21 2:17 ` [PATCHv7 1/4] iio: adc: exynos_adc: Add exynos_adc_data structure to improve readability Chanwoo Choi
2014-07-21 2:17 ` Chanwoo Choi
2014-07-21 2:17 ` Chanwoo Choi
2014-07-21 2:17 ` [PATCHv7 2/4] iio: adc: exynos_adc: Control special clock of ADC to support Exynos3250 ADC Chanwoo Choi
2014-07-21 2:17 ` Chanwoo Choi
2014-07-21 2:17 ` [PATCHv7 3/4] iio: devicetree: Add DT binding documentation for " Chanwoo Choi
2014-07-21 2:17 ` Chanwoo Choi
2014-07-21 2:17 ` [PATCHv7 4/4] ARM: dts: Fix wrong compatible string " Chanwoo Choi
2014-07-21 2:17 ` Chanwoo Choi
2014-07-21 7:38 ` [PATCHv7 0/4] iio: adc: exynos_adc: Support Exynos3250 ADC and code clean Arnd Bergmann
2014-07-21 7:38 ` Arnd Bergmann
2014-07-21 8:11 ` Chanwoo Choi [this message]
2014-07-21 8:11 ` Chanwoo Choi
2014-07-21 8:11 ` Chanwoo Choi
2014-07-21 8:17 ` Chanwoo Choi
2014-07-21 8:17 ` Chanwoo Choi
2014-07-21 8:58 ` Arnd Bergmann
2014-07-21 8:58 ` Arnd Bergmann
2014-07-22 2:17 ` Chanwoo Choi
2014-07-22 2:17 ` Chanwoo Choi
2014-07-22 2:17 ` Chanwoo Choi
2014-07-21 8:57 ` Arnd Bergmann
2014-07-21 8:57 ` Arnd Bergmann
2014-07-21 8:57 ` Arnd Bergmann
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=53CCCB20.50802@samsung.com \
--to=cw00.choi@samsung.com \
--cc=arnd@arndb.de \
--cc=ch.naveen@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=t.figa@samsung.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 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.