mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Inki Dae <inki.dae@samsung.com>
To: "'Mark Brown'" <broonie@kernel.org>
Cc: "'Olof Johansson'" <olof@lixom.net>,
	"'Sean Paul'" <seanpaul@chromium.org>,
	devicetree@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	"'DRI mailing list'" <dri-devel@lists.freedesktop.org>,
	linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH 3/5] drm/bridge: Add PTN3460 bridge driver
Date: Thu, 10 Oct 2013 20:40:38 +0900	[thread overview]
Message-ID: <063a01cec5ad$8afd1920$a0f74b60$%dae@samsung.com> (raw)
In-Reply-To: <20131010093708.GC21581@sirena.org.uk>



> -----Original Message-----
> From: Mark Brown [mailto:broonie@kernel.org]
> Sent: Thursday, October 10, 2013 6:37 PM
> To: Inki Dae
> Cc: 'Olof Johansson'; 'Sean Paul'; devicetree@vger.kernel.org; linux-
> samsung-soc@vger.kernel.org; linux-doc@vger.kernel.org; linux-
> kernel@vger.kernel.org; 'DRI mailing list'; linux-arm-
> kernel@lists.infradead.org
> Subject: Re: [PATCH 3/5] drm/bridge: Add PTN3460 bridge driver
> 
> On Thu, Oct 10, 2013 at 01:18:05PM +0900, Inki Dae wrote:
> 
> > > > I still think the pin could be replaced with a regulator. But
> > > > lvds-bridge node has "powerdown-gpio" property - it say this board
> > > > will use gpio pin - specific to board.  So it seems no problem.
> 
> > > No, don't model things that aren't regulators as regulators - it's
> > > just confusing from a usability standpoint and causes breakage when
> > > the pins don't behave like regulators.
> 
> > It seems that there was your missing point. That _is not_ what I
> mentioned.
> > I mean that other boards can use a regulator instead of gpio pin.
> 
> What I'm saying is no boards should use a regulator to control that GPIO
> pin, obviously if they're controlling the actual regulators that's fine

That is what I mentioned. Some boards _could control_ the actual regulator
for lvds-bridge, and that would be depended on how HW engineer designs the
board. 

> but the reset signal should not be controlled via the regulator API (there
> are some unfortunate cases where people have done that already but let's
> not have any more).


  reply	other threads:[~2013-10-10 11:40 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-01 23:40 [PATCH 0/5] Add some missing bits for exynos5250-snow Sean Paul
2013-10-01 23:40 ` [PATCH 1/5] ARM: dts: Add fimd display-timings " Sean Paul
2013-10-01 23:40 ` [PATCH 2/5] ARM: dts: Add dp-controller node to exynos5250-snow Sean Paul
2013-10-02 21:10   ` Olof Johansson
2013-10-03 16:06     ` Sean Paul
2013-10-01 23:40 ` [PATCH 3/5] drm/bridge: Add PTN3460 bridge driver Sean Paul
2013-10-02 21:20   ` Olof Johansson
2013-10-03 13:55   ` Inki Dae
2013-10-03 14:57     ` Sean Paul
2013-10-03 17:39       ` Inki Dae
2013-10-03 18:01         ` Olof Johansson
2013-10-04  2:05           ` Inki Dae
2013-10-09 18:29             ` Mark Brown
2013-10-10  4:18               ` Inki Dae
2013-10-10  9:37                 ` Mark Brown
2013-10-10 11:40                   ` Inki Dae [this message]
2013-10-10 12:23                     ` Mark Brown
2013-10-03 18:09         ` Sean Paul
2013-10-03 18:23           ` Inki Dae
2013-10-03 18:32             ` Sean Paul
2013-10-04  1:59               ` Inki Dae
2013-10-01 23:40 ` [PATCH 4/5] drm/exynos: Initialize ptn3460 if present Sean Paul
2013-10-03 14:43   ` Inki Dae
2013-10-03 15:02     ` Sean Paul
2013-10-03 17:18       ` Inki Dae
2013-10-03 17:27         ` Sean Paul
2013-10-03 18:10           ` Inki Dae
2013-10-01 23:41 ` [PATCH 5/5] ARM: dts: Add ptn3460 to exynos5250-snow Sean Paul
2013-10-02 21:07 ` [PATCH 0/5] Add some missing bits for exynos5250-snow Olof Johansson
2013-10-03 22:28 ` [PATCH v2 " Sean Paul
2013-10-03 22:28   ` [PATCH v2 1/5] ARM: dts: Add fimd display-timings " Sean Paul
2013-10-04  2:20     ` Jingoo Han
2013-10-03 22:28   ` [PATCH v2 2/5] ARM: dts: Add dp-controller node to exynos5250-snow Sean Paul
2013-10-04  2:24     ` Jingoo Han
2013-10-03 22:28   ` [PATCH v2 3/5] drm/bridge: Add PTN3460 bridge driver Sean Paul
2013-10-03 22:28   ` [PATCH v2 4/5] drm/exynos: Initialize ptn3460 if present Sean Paul
2013-10-04  2:29     ` Inki Dae
2013-10-04  2:41       ` Sean Paul
2013-10-04  4:18         ` Inki Dae
2013-10-04 14:17           ` Sean Paul
2013-10-04 15:01             ` Inki Dae
2013-10-04 15:04               ` Sean Paul
2013-10-04 16:01                 ` Inki Dae
2013-10-03 22:28   ` [PATCH v2 5/5] ARM: dts: Add ptn3460 to exynos5250-snow Sean Paul
2013-10-03 22:35   ` [PATCH v2 0/5] Add some missing bits for exynos5250-snow Olof Johansson
2013-10-10 22:26   ` [PATCH v3 " Sean Paul
2013-10-10 22:26     ` [PATCH v3 1/5] ARM: dts: Add fimd display-timings " Sean Paul
2013-10-10 22:26     ` [PATCH v3 2/5] ARM: dts: Add dp-controller node to exynos5250-snow Sean Paul
2013-10-10 22:26     ` [PATCH v3 3/5] drm/bridge: Add PTN3460 bridge driver Sean Paul
2013-10-10 22:26     ` [PATCH v3 4/5] drm/exynos: Initialize ptn3460 if present Sean Paul
2013-10-10 22:26     ` [PATCH v3 5/5] ARM: dts: Add ptn3460 to exynos5250-snow Sean Paul

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='063a01cec5ad$8afd1920$a0f74b60$%dae@samsung.com' \
    --to=inki.dae@samsung.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=seanpaul@chromium.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

Powered by JetHome