Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Tushar Behera <trblinux@gmail.com>
To: Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Tushar Behera <tushar.b@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com
Subject: Re: [PATCH] ARM: dts: Add missing clock/pin-control entries for I2S0 on Exynos4
Date: Mon, 09 Jun 2014 16:14:00 +0530	[thread overview]
Message-ID: <53958FF0.40101@gmail.com> (raw)
In-Reply-To: <5395841B.8000702@samsung.com>

On 06/09/2014 03:23 PM, Sylwester Nawrocki wrote:
> Hi Tushar,
> 
> On 07/06/14 11:30, Tushar Behera wrote:
>> I2S driver uses 3 clocks under different conditions. Added two
>> missing clocks.
>>
>> Additionally updated pin-control property for this node.
>>
>> Signed-off-by: Tushar Behera <tushar.b@samsung.com>
>> ---
>> Based on next-20140606.
>>
>> Tested on Exynos4210-based Origen boards with private patches for
>> codec/machine driver.
>>
>>  arch/arm/boot/dts/exynos4.dtsi |    8 ++++++--
>>  1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi
>> index fbaf426..10bb081 100644
>> --- a/arch/arm/boot/dts/exynos4.dtsi
>> +++ b/arch/arm/boot/dts/exynos4.dtsi
>> @@ -55,11 +55,15 @@
>>  	i2s0: i2s@03830000 {
>>  		compatible = "samsung,s5pv210-i2s";
>>  		reg = <0x03830000 0x100>;
>> -		clocks = <&clock_audss EXYNOS_I2S_BUS>;
>> -		clock-names = "iis";
>> +		clocks = <&clock_audss EXYNOS_I2S_BUS>,
>> +			<&clock_audss EXYNOS_I2S_BUS>,
>> +			<&clock_audss EXYNOS_SCLK_I2S>;
>> +		clock-names = "iis", "i2s_opclk0", "i2s_opclk1";
>>  		dmas = <&pdma0 12>, <&pdma0 11>, <&pdma0 10>;
>>  		dma-names = "tx", "rx", "tx-sec";
>>  		samsung,idma-addr = <0x03000000>;
>> +		pinctrl-0 = <&i2s0_bus>;
>> +		pinctrl-names = "default";
>>  		status = "disabled";
>>  	};
> 
> I assumed those properties you're adding here belong to board or
> to SoC type specific dts. It doesn't hurt ot have it like this,
> but what do you think about moving this to  arch/arm/boot/dts/
> exynos4210(4x12).dtsi ? For instance pinctrl definitions are
> in SoC specific dts.
> 

IMHO, the clock entries belong here as the audss clock provider
essentially remains same for all Exynos4 based systems.

As for pin-control entry, I believe we can move them to respective SoC
dtsi files.

Does that sound okay to you?

> --
> Thanks,
> Sylwester
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
Tushar Behera

  reply	other threads:[~2014-06-09 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-07  9:30 [PATCH] ARM: dts: Add missing clock/pin-control entries for I2S0 on Exynos4 Tushar Behera
2014-06-09  9:53 ` Sylwester Nawrocki
2014-06-09 10:44   ` Tushar Behera [this message]
2014-06-09 11:06     ` Sylwester Nawrocki
2014-06-16 11:43       ` Tushar Behera
2014-06-16 11:50         ` Sylwester Nawrocki
2014-06-16 12:03           ` Tushar Behera
2014-06-16 12:24             ` Tomasz Figa

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=53958FF0.40101@gmail.com \
    --to=trblinux@gmail.com \
    --cc=kgene.kim@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=tushar.b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox