devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hyungwon Hwang <human.hwang@samsung.com>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: "open list:OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
	"Seung-Woo Kim" <sw0312.kim@samsung.com>,
	이동화 <dh09.lee@samsung.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>, 최찬우 <cw00.choi@samsung.com>
Subject: Re: [PATCH v2 4/6] drm/exynos: dsi: add support for Exynos5433 SoC
Date: Fri, 20 Mar 2015 14:15:31 +0900	[thread overview]
Message-ID: <20150320141531.36e1464c@hwh-ubuntu> (raw)
In-Reply-To: <550A979A.6070102@samsung.com>

Dear Andrej,

On Thu, 19 Mar 2015 10:32:10 +0100
Andrzej Hajda <a.hajda@samsung.com> wrote:

> On 03/19/2015 02:18 AM, Hyungwon Hwang wrote:
> > Dear Daniel,
> > 
> > On Thu, 19 Mar 2015 01:13:21 +0000
> > Daniel Stone <daniel-rLtY4a/8tF1rovVCs/uTlw@public.gmane.org> wrote:
> > 
> >> Hi Hyungwon,
> >>
> >> On 19 March 2015 at 01:02, Hyungwon Hwang
> >> <human.hwang-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org> wrote:
> >>>>> +       /*
> >>>>> +        * The input PLL clock for MIPI DSI in Exynos5433 seems
> >>>>> to be fixed
> >>>>> +        * by OSC CLK.
> >>>>> +        */
> >>>>> +       fin = 24 * MHZ;
> >>>>
> >>>> Er, is this always true on other platforms as well? Shouldn't
> >>>> this be a part of the DeviceTree description?
> >>>
> >>> I forgot to change the comment in development. Finally it is found
> >>> that all exynos mipi dsi's fin is OSC clk which is 24 MHz. So I
> >>> will remove the comment, but remain the code as it is.
> >>
> >> Fair enough. Should pll_clk be removed from the DT description
> >> then, if it's fixed to the oscillator?
> > 
> > Yes. It is redundant to represent pll_clk in DT, and it should be
> > removed.
> 
> Why do you think OSC clk determines value of pll_clk?
> pll_clk is mapped to SCLK_MIPI[01] or SCLK_DSIM0 gate with few
> dividers and muxes above. So at least in theory it can differ from
> osc clk. Additionally this gate should be enabled so you cannot just
> remove it from DT.
> 
> Regards
> Andrzej

As I found, pll clk is not SCLK_MIPI[01] but OSC CLK. SCLK_DSIM0 must
be controlled in this driver as it has been, as a gate clock of MIPI
DSI block, but not as a pll clk. SCLK_DSIM0 is not the input
clock of MIPI DPHY which provides fin in this code. So clock setting
and getting code was wrong, and must be removed.

OSC CLK is not soc-depedendant but board-dependant, even though I have
not seen any board which does not use OSC CLK by 24 MHz. It must be
parsed from board DT file, which in this case, we can use the value in
pll_clk_rate (the variable name must be renamed also).

Because ambiguous description in the technical document, I can be
wrong. Please let me know if I do not understand something. Thanks for
your comment.

Best regards,
Hyungwon Hwang

> 
> > 
> >>
> >>> Thanks for your review. I will send it again with the changes you
> >>> suggested.
> >>
> >> Thanks very much!
> >>
> >> Cheers,
> >> Daniel
> > 
> > Best regards,
> > Hyungwon Hwang
> > --
> > To unsubscribe from this list: send the line "unsubscribe
> > devicetree" in the body of a message to
> > majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo
> > info at  http://vger.kernel.org/majordomo-info.html
> > 
> 

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-03-20  5:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18  8:16 [PATCH v2 0/6] Add drivers for Exynos5433 display Hyungwon Hwang
2015-03-18  8:16 ` [PATCH v2 1/6] drm/exynos: add Exynos5433 decon driver Hyungwon Hwang
2015-03-18 12:24   ` Daniel Stone
2015-03-26  2:14     ` Hyungwon Hwang
2015-03-18  8:16 ` [PATCH v2 2/6] of: add helper for getting endpoint node of specific identifiers Hyungwon Hwang
2015-03-18  8:16 ` [PATCH v2 3/6] drm/exynos: mic: add MIC driver Hyungwon Hwang
2015-03-24  5:51   ` Inki Dae
2015-03-26  2:27     ` Hyungwon Hwang
2015-03-26  2:41     ` Hyungwon Hwang
2015-03-18  8:16 ` [PATCH v2 4/6] drm/exynos: dsi: add support for Exynos5433 SoC Hyungwon Hwang
2015-03-18  9:52   ` Daniel Stone
2015-03-19  1:02     ` Hyungwon Hwang
2015-03-19  1:13       ` Daniel Stone
     [not found]         ` <CAPj87rPeUS9h=GCBR7ccNhugaGoyHw3x6oZ3Spq6P8uEg4ZcUg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-03-19  1:18           ` Hyungwon Hwang
2015-03-19  9:32             ` Andrzej Hajda
2015-03-20  5:15               ` Hyungwon Hwang [this message]
2015-03-23  9:31                 ` Andrzej Hajda
2015-03-23 13:42                   ` Hyungwon Hwang
2015-03-26 10:33     ` Hyungwon Hwang
2015-03-18  8:16 ` [PATCH v2 5/6] drm/exynos: dsi: add support for MIC driver as a bridge Hyungwon Hwang
2015-03-18  8:16 ` [PATCH v2 6/6] drm/exynos: dsi: do not set TE GPIO direction by input Hyungwon Hwang

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=20150320141531.36e1464c@hwh-ubuntu \
    --to=human.hwang@samsung.com \
    --cc=a.hajda@samsung.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dh09.lee@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sw0312.kim@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;
as well as URLs for NNTP newsgroup(s).