public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Yuvaraj Kumar <yuvaraj.cd@gmail.com>,
	Doug Anderson <dianders@chromium.org>,
	Seungwon Jeon <tgih.jun@samsung.com>, Chris Ball <cjb@laptop.org>
Cc: Tomasz Figa <t.figa@samsung.com>,
	linux-samsung-soc@vger.kernel.org,
	linux-mmc <linux-mmc@vger.kernel.org>,
	kgene.kim@samsung.com, ks.giri@samsung.com,
	Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>
Subject: Re: [PATCH V2] ARM: dts: Add dwmmc DT nodes for exynos5420 SOC
Date: Fri, 23 Aug 2013 01:06:42 +0200	[thread overview]
Message-ID: <3264029.cracds40W5@flatron> (raw)
In-Reply-To: <CAKuRcOL7Vs=1em8U6rx=ZBRU8j=0A-WiNK44JrFn6jtVRCns0w@mail.gmail.com>

On Thursday 22 of August 2013 12:24:58 Yuvaraj Kumar wrote:
> On Wed, Aug 21, 2013 at 4:00 PM, Tomasz Figa <t.figa@samsung.com> wrote:
> > Hi Yuvaraj,
> > 
> > On Wednesday 21 of August 2013 12:13:53 Yuvaraj Kumar C D wrote:
> >> This patch adds the device tree node entries for exynos5420 SOC.
> >> Exynos5420 has a different version of DWMMC controller,so a new
> >> compatible string is used to distinguish it from the prior SOC's.
> > 
> > What are the difference between both versions? Is there a patch adding
> > the new compatible to the driver somewhere?
> 
> Exynos5250 has DWMMC controller of IP version 2.41a
> Exynos5420 has DWMMC controller of IP version 2.50a
> In addition Exynos5420 has Security Management Unit for eMMC.

OK. What about my second question?

> >> changes since V1:
> >>       1.disable node by status = disabled in SOC file
> >>       2.enable node by status = okay in board specific file
> > 
> > Ahh, so you fixed this already in this version, thanks. Haven't
> > noticed
> > this patch at first and commented on previous one. Sorry for the
> > noise.
> > 
> >> Signed-off-by: Yuvaraj Kumar C D <yuvaraj.cd@samsung.com>
> >> ---
> >> 
> >>  .../devicetree/bindings/mmc/exynos-dw-mshc.txt     |    2 ++
> >>  arch/arm/boot/dts/exynos5420-smdk5420.dts          |   38
> >> 
> >> ++++++++++++++++++++ arch/arm/boot/dts/exynos5420.dtsi
> >> 
> >> |   36 +++++++++++++++++++ 3 files changed, 76 insertions(+)
> >> 
> >> diff --git a/Documentation/devicetree/bindings/mmc/exynos-dw-mshc.txt
> >> b/Documentation/devicetree/bindings/mmc/exynos-dw-mshc.txt index
> >> 6d1c098..84cd56f 100644
> >> --- a/Documentation/devicetree/bindings/mmc/exynos-dw-mshc.txt
> >> +++ b/Documentation/devicetree/bindings/mmc/exynos-dw-mshc.txt
> >> 
> >> @@ -16,6 +16,8 @@ Required Properties:
> >>         specific extensions.
> >>       
> >>       - "samsung,exynos5250-dw-mshc": for controllers with Samsung
> >>       Exynos5250
> >> 
> >> specific extensions.
> >> +     - "samsung,exynos5420-dw-mshc": for controllers with Samsung
> >> Exynos5420 +       specific extensions.
> >> 
> >>  * samsung,dw-mshc-ciu-div: Specifies the divider value for the card
> >> 
> >> interface unit (ciu) clock. This property is applicable only for
> >> Exynos5 SoC's and diff --git
> >> a/arch/arm/boot/dts/exynos5420-smdk5420.dts
> >> b/arch/arm/boot/dts/exynos5420-smdk5420.dts index bafba25..6e65278
> >> 100644
> >> --- a/arch/arm/boot/dts/exynos5420-smdk5420.dts
> >> +++ b/arch/arm/boot/dts/exynos5420-smdk5420.dts
> >> @@ -31,6 +31,44 @@
> >> 
> >>               };
> >>       
> >>       };
> >> 
> >> +     dwmmc0@12200000 {
> >> +             status = "okay";
> >> +             num-slots = <1>;
> > 
> > You don't have to specify this property if there is only one slot.
> > Also are you sure that this is a board specific property?
> 
> Yes,If num-slots property is not defined dw_mmc driver assumes 1 slot
> is available.
> I think yes,its a board specific property as number of card slots is
> board dependent.
> 
> >> +             broken-cd;
> >> +             bypass-smu;
> > 
> > This property doesn't seem to be documented nor used anywhere.
> 
> Sorry. I missed to add in binding document.Will add in next version.

Is there a patch adding support for this property to the driver?

> >> +             supports-highspeed;
> > 
> > Is it a board specific property?
> > 
> >> +             fifo-depth = <0x80>;
> > 
> > Ditto.
> 
> Ideally this can be move to SOC specific dts.But I am just following
> ,already merged smdk5250 board
> dts convensions.

This means that Exynos5250 board dts files need to be fixed as well.

> >> +             card-detect-delay = <200>;
> >> +             samsung,dw-mshc-ciu-div = <3>;
> >> +             samsung,dw-mshc-sdr-timing = <0 4>;
> >> +             samsung,dw-mshc-ddr-timing = <0 2>;
> > 
> > Are the above three properties really board-specific?

Hmm?

Best regards,
Tomasz

  reply	other threads:[~2013-08-22 23:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21  6:43 [PATCH V2] ARM: dts: Add dwmmc DT nodes for exynos5420 SOC Yuvaraj Kumar C D
2013-08-21 10:30 ` Tomasz Figa
2013-08-22  6:54   ` Yuvaraj Kumar
2013-08-22 23:06     ` Tomasz Figa [this message]
2013-08-23  6:16       ` Yuvaraj Cd
2013-08-23 14:12         ` Jaehoon Chung
  -- strict thread matches above, loose matches on Subject: below --
2013-08-21  6:35 Yuvaraj Kumar C D

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=3264029.cracds40W5@flatron \
    --to=tomasz.figa@gmail.com \
    --cc=cjb@laptop.org \
    --cc=dianders@chromium.org \
    --cc=kgene.kim@samsung.com \
    --cc=ks.giri@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=t.figa@samsung.com \
    --cc=tgih.jun@samsung.com \
    --cc=yuvaraj.cd@gmail.com \
    --cc=yuvaraj.cd@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