devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: 'Ajay kumar' <ajaynumb@gmail.com>, 'Andrzej Hajda' <a.hajda@samsung.com>
Cc: "'open list:OPEN FIRMWARE AND...'" <devicetree@vger.kernel.org>,
	linux-samsung-soc@vger.kernel.org,
	'Sean Paul' <seanpaul@google.com>,
	'sunil joshi' <joshi@samsung.com>,
	dri-devel@lists.freedesktop.org,
	'Prashanth G' <prashanth.g@samsung.com>,
	'Ajay Kumar' <ajaykumar.rs@samsung.com>
Subject: Re: [PATCH V3 1/7] drm/exynos: Support DP CLKCON register in FIMD driver
Date: Mon, 30 Jun 2014 10:14:17 +0900	[thread overview]
Message-ID: <00a501cf9400$9d396950$d7ac3bf0$%han@samsung.com> (raw)
In-Reply-To: <CAEC9eQPY+W_Wni7PLtWkHr0QrHW+G8x_+XWapV5tDiKebn=zpA@mail.gmail.com>

On Friday, June 27, 2014 10:03 PM, Ajay kumar wrote:
> On Fri, Jun 27, 2014 at 6:14 PM, Andrzej Hajda <a.hajda@samsung.com> wrote:
> > On 06/27/2014 01:48 PM, Ajay kumar wrote:
> >> On Fri, Jun 27, 2014 at 4:52 PM, Andrzej Hajda <a.hajda@samsung.com> wrote:
> >>> +CC DT
> >>>
> >>> On 06/27/2014 12:12 PM, Ajay Kumar wrote:
> >>>> Add the missing setting for DP CLKCON register.
> >>>>
> >>>> This register is present on Exynos5 based FIMD controllers,
> >>>> and needs to be set if we are using DP.
> >>>>
> >>>> Signed-off-by: Ajay Kumar <ajaykumar.rs@samsung.com>
> >>>> ---
> >>>>  .../devicetree/bindings/video/samsung-fimd.txt     |    1 +
> >>>>  drivers/gpu/drm/exynos/exynos_drm_fimd.c           |   23 ++++++++++++++++++++
> >>>>  include/video/samsung_fimd.h                       |    4 ++++
> >>>>  3 files changed, 28 insertions(+)

[.....]

> >>>>  static const struct of_device_id fimd_driver_dt_match[] = {
> >>>> @@ -331,6 +341,10 @@ static void fimd_commit(struct exynos_drm_manager *mgr)
> >>>>       if (clkdiv > 1)
> >>>>               val |= VIDCON0_CLKVAL_F(clkdiv - 1) | VIDCON0_CLKDIR;
> >>>>
> >>>> +     if (ctx->driver_data->has_dp_clkcon &&
> >>>> +             ctx->exynos_fimd_output_type == EXYNOS_FIMD_OUTPUT_DP)
> >>>> +             writel(DP_CLK_ENABLE, ctx->regs + DP_CLKCON);
> >>>> +
> >>>>       writel(val, ctx->regs + VIDCON0);
> >
> > New code should not split VIDCON0 related code.It should be moved few
> > lines above or few lines below.
> Ok, for better readability.
> 
> > Anyway this code should be rather placed in power related functions of
> > dp encoder, as it enables dp. The only question
> > is if DP_CLKCON update can be performed after VIDCON0 update. If yes the
> > solution of the whole problem
> I will check this.
> 
> > seems to be simple:
> > - fimd should provide function fimd_set_dp_clk_gate or sth similar,
> > - this function should be called in exynos_dp_poweron/exynos_dp_poweroff.
> > I hope I have not missed anything this time.
> But, it won't look good to export a FIMD function which sets a FIMD register,
> and call it in DP driver!
> What does Inki/Jingoo have to say about this?

I agree with Ajay Kumar's opinion.
It doesn't look good to export the function to set FIMD register
and call it by DP driver.

Best regards,
Jingoo Han
> 
> Regards,
> Ajay
> 
[....]

  parent reply	other threads:[~2014-06-30  1:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1403863946-15492-1-git-send-email-ajaykumar.rs@samsung.com>
2014-06-27 10:24 ` [PATCH V3 0/7] drm/exynos: Support DP CLKCON register in FIMD driver Inki Dae
2014-06-27 10:49   ` Mark Rutland
     [not found] ` <1403863946-15492-4-git-send-email-ajaykumar.rs@samsung.com>
2014-06-27 11:17   ` [PATCH V3 3/7] ARM: dts: Add FIMD output property for peach_pit Ajay kumar
     [not found] ` <1403863946-15492-5-git-send-email-ajaykumar.rs@samsung.com>
2014-06-27 11:17   ` [PATCH V3 4/7] ARM: dts: Add FIMD output property for peach_pi Ajay kumar
     [not found] ` <1403863946-15492-3-git-send-email-ajaykumar.rs@samsung.com>
2014-06-27 11:17   ` [PATCH V3 2/7] ARM: dts: Add FIMD output property for snow Ajay kumar
     [not found] ` <1403863946-15492-7-git-send-email-ajaykumar.rs@samsung.com>
2014-06-27 11:18   ` [PATCH V3 6/7] ARM: dts: Add FIMD output property for smdk5420 Ajay kumar
     [not found] ` <1403863946-15492-6-git-send-email-ajaykumar.rs@samsung.com>
2014-06-27 11:18   ` [PATCH V3 5/7] ARM: dts: Add FIMD output property for smdk5250 Ajay kumar
     [not found] ` <1403863946-15492-8-git-send-email-ajaykumar.rs@samsung.com>
2014-06-27 11:18   ` [PATCH V3 7/7] ARM: dts: Add FIMD output property for arndale Ajay kumar
     [not found] ` <1403863946-15492-2-git-send-email-ajaykumar.rs@samsung.com>
2014-06-27 11:22   ` [PATCH V3 1/7] drm/exynos: Support DP CLKCON register in FIMD driver Andrzej Hajda
2014-06-27 11:48     ` Ajay kumar
2014-06-27 12:44       ` Andrzej Hajda
2014-06-27 13:02         ` Ajay kumar
2014-06-27 13:09           ` Tomasz Figa
2014-06-30  1:14           ` Jingoo Han [this message]
2014-06-30  5:31             ` Andrzej Hajda
2014-06-30  9:01               ` Ajay kumar
2014-06-30 16:09               ` Inki Dae
2014-07-09  6:21                 ` Ajay kumar

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='00a501cf9400$9d396950$d7ac3bf0$%han@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=a.hajda@samsung.com \
    --cc=ajaykumar.rs@samsung.com \
    --cc=ajaynumb@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=joshi@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=prashanth.g@samsung.com \
    --cc=seanpaul@google.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).