From: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 2/5] arm: shmobile: r8a7790: Add SATA clock
Date: Thu, 19 Dec 2013 04:58:22 +0000 [thread overview]
Message-ID: <87wqj1v3md.wl%kuninori.morimoto.gx@gmail.com> (raw)
In-Reply-To: <1375892397-5822-3-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Valentine, Laurent
Cc Magnus
> > > On Wednesday 18 December 2013 16:44:17 Valentine Barshak wrote:
> > >> This adds SATA 0/1 clock support. External 100MHz SATA 0/1
> > >>
> > >> reference clock is supposed to be applied to the following pins:
> > >> CICREFP0_SATA/CICREFP1_SATA;
> > >> CICREFN0_SATA/CICREFN1_SATA.
> > >>
> > >> Signed-off-by: Valentine Barshak <valentine.barshak@cogentembedded.com>
> > >> ---
(snip)
> > If understand the h/w manual correctly, the external clock is connected
> > directly to the SATA module:
> >
> > "Pin Name: CICREFP0_SATA CICREFN0_SATA CICREFP1_SATA CICREFN1_SATA
> > Description: Reference clock input to the PLL circuit in the Serial-ATA
> > module (differential input). Apply a 100-MHz clock."
>
> That's my understanding as well, but I suspect that clock to be the PHY clock
> only, not the SATA module functional clock.
I have same opinion with Laurent.
But I'm not sure detail of module parent clock,
since R-Car series datasheet seems doesn't have module clock relationship map.
# SH-mobile series had "Clock Assignment to Modules" in datasheet.
I will ask this to HW people, but maybe p_clk is fine here.
If you need to control CICREFN1_SATAx clocks,
it should be defined as CLKDEV_ICK_ID() and use clk_xx() function
But, hmm...
Current some clock-r8a7790 MSTP clocks have strange parent...
Best regards
---
Kuninori Morimoto
next prev parent reply other threads:[~2013-12-19 4:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 16:19 [PATCH 2/5] ARM: shmobile: r8a7790: Add DU and LVDS clocks Laurent Pinchart
2013-12-18 12:44 ` [PATCH 2/5] arm: shmobile: r8a7790: Add SATA clock Valentine Barshak
2013-12-18 14:19 ` Laurent Pinchart
2013-12-19 1:00 ` Valentine
2013-12-19 1:04 ` Laurent Pinchart
2013-12-19 4:58 ` Kuninori Morimoto [this message]
2013-12-23 21:24 ` Valentine
2013-12-26 14:16 ` Laurent Pinchart
2013-12-26 14:35 ` Valentine
2014-01-06 1:25 ` Kuninori Morimoto
2014-01-06 13:58 ` Valentine
2014-01-07 0:14 ` Kuninori Morimoto
2014-02-12 17:59 ` [PATCH 2/5] ARM: shmobile: r8a7790: add dmac0 dmac1 nodes Ben Dooks
2014-02-12 19:18 ` Geert Uytterhoeven
2014-02-12 19:55 ` Sergei Shtylyov
2014-02-13 18:17 ` Ben Dooks
2014-02-13 18:18 ` Ben Dooks
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=87wqj1v3md.wl%kuninori.morimoto.gx@gmail.com \
--to=kuninori.morimoto.gx@gmail.com \
--cc=linux-sh@vger.kernel.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 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).