Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Jingoo Han <jg1.han@samsung.com>
To: 'Ajay kumar' <ajaynumb@gmail.com>
Cc: linux-samsung-soc@vger.kernel.org,
	'Sean Paul' <seanpaul@google.com>,
	abrestic@chromium.org, 'sunil joshi' <joshi@samsung.com>,
	dri-devel@lists.freedesktop.org, a.hajda@samsung.com,
	'Kyungmin Park' <kyungmin.park@samsung.com>,
	treding@nvidia.com, 'Prashanth G' <prashanth.g@samsung.com>,
	'Ajay Kumar' <ajaykumar.rs@samsung.com>,
	'Rahul Sharma' <rahul.sharma@samsung.com>
Subject: Re: [PATCH 3/7] drm/panel: Add driver for exynos_dp based panels
Date: Mon, 21 Apr 2014 09:34:44 +0900	[thread overview]
Message-ID: <004001cf5cf9$7e2a0990$7a7e1cb0$%han@samsung.com> (raw)
In-Reply-To: <CAEC9eQPU1o4c30_VWJcoC1uwZC1yNNvq7GoKp=JhVMeEuz375g@mail.gmail.com>

On Saturday, April 19, 2014 4:43 AM, Ajay kumar wrote:
> On Fri, Apr 18, 2014 at 2:17 PM, Jingoo Han <jg1.han@samsung.com> wrote:
> > On Wednesday, April 16, 2014 11:33 PM, Ajay Kumar wrote:

[.....]

> > > +struct panel_exynos_dp {
> > > +     struct drm_panel        base;
> > > +     struct regulator        *bck_fet;
> > > +     struct regulator        *lcd_fet;
> > 'bck' means 'backlight'? Then, just use 'backlight_fet'.
> backlight_fet is more meaningful. Will change it.
> > Also, I cannot understand the meaning of 'fet'.
> > What's the meaning of the 'fet'?
>
> FET is an output from the regulator. On exynos5250-snow board,
> FET1 controls power to the backlight unit.
> See more here: https://lkml.org/lkml/2014/4/15/618 

OK, I see.

PS: Please change your mail from 'html' mode to 'text' mode.

Best regards,
Jingoo Han

  reply	other threads:[~2014-04-21  0:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 14:32 [PATCH 0/7] drm: exynos: few patches to enhance bridge chip support Ajay Kumar
2014-04-16 14:33 ` [PATCH 1/7] drm/exynos: dp: support hotplug detection via GPIO Ajay Kumar
2014-04-18  8:23   ` Jingoo Han
2014-04-18 19:33     ` Ajay kumar
2014-04-16 14:33 ` [PATCH 2/7] drm/panel: add pre_enable routine to drm panel Ajay Kumar
2014-04-16 14:33 ` [PATCH 3/7] drm/panel: Add driver for exynos_dp based panels Ajay Kumar
2014-04-18  8:47   ` Jingoo Han
2014-04-18 19:42     ` Ajay kumar
2014-04-21  0:34       ` Jingoo Han [this message]
2014-04-16 14:33 ` [PATCH 4/7] drm/exynos: add exynos_dp_panel driver registration to drm driver Ajay Kumar
2014-04-18  8:57   ` Jingoo Han
2014-04-18 19:50     ` Ajay kumar
2014-04-21  0:29       ` Jingoo Han
2014-04-16 14:33 ` [PATCH 5/7] drm/exynos: dp: modify driver to support drm_panel Ajay Kumar
2014-04-18  9:08   ` Jingoo Han
2014-04-18 19:52     ` Ajay kumar
2014-04-16 14:33 ` [PATCH 6/7] drm/bridge: ptn3460: enable polling based detection Ajay Kumar
2014-04-16 14:33 ` [PATCH 7/7] drm/bridge: ptn3460: add drm_panel controls Ajay Kumar
2014-04-18  9:25   ` Jingoo Han
2014-04-18 19:55     ` 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='004001cf5cf9$7e2a0990$7a7e1cb0$%han@samsung.com' \
    --to=jg1.han@samsung.com \
    --cc=a.hajda@samsung.com \
    --cc=abrestic@chromium.org \
    --cc=ajaykumar.rs@samsung.com \
    --cc=ajaynumb@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=joshi@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=prashanth.g@samsung.com \
    --cc=rahul.sharma@samsung.com \
    --cc=seanpaul@google.com \
    --cc=treding@nvidia.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