linux-tegra.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: "linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
	Terje Bergstrom <tbergstrom@nvidia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 4/4] ARM: tegra: roth: add display DT node
Date: Mon, 21 Jul 2014 09:35:27 -0600	[thread overview]
Message-ID: <53CD333F.2070805@wwwdotorg.org> (raw)
In-Reply-To: <53B4C9C0.4000605@nvidia.com>

On 07/02/2014 09:10 PM, Alexandre Courbot wrote:
> On 07/03/2014 12:55 AM, Stephen Warren wrote:
>> On 07/02/2014 06:19 AM, Alexandre Courbot wrote:
>>> DSI support has been fixed to support continuous clock behavior that the
>>> panel used on SHIELD requires, so finally add its device tree node since
>>> it is functional.
>>
>>> diff --git a/arch/arm/boot/dts/tegra114-roth.dts
>>> b/arch/arm/boot/dts/tegra114-roth.dts
>>
>>> +    host1x@50000000 {
>>> +        dsi@54300000 {
>>
>> That node looks fine, but I wonder why we need to mark a bunch of
>> regulators as always-on? shouldn't the references to vdd-supply and
>> power-supply from this node be enough? If not, perhaps the tree
>> structure of the regulators isn't correct, or the DSI or panel bindings
>> don't allow enough regulators to be referenced?
> 
> regulator-always-on is indeed not needed for vdd_lcd. I actually had a
> patch in my tree removing this line that I forgot to squash. Will post a
> v2 for this patch that fixes this, thanks.
> 
> vdd-2v8-display needs to remain always-on however. Here we may hit a
> limitation of the simple-panel driver, where only one power supply can
> be provided.

Can't we fix the simple-panel driver to allow a list of regulators in
the property?

I suppose that this technique is OK though; we can always simplify the
DT later if the simple-panel binding gets enhanced.

  reply	other threads:[~2014-07-21 15:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 12:19 [PATCH 0/4] drm/dsi/tegra: continuous clock support Alexandre Courbot
2014-07-02 12:19 ` [PATCH 1/4] drm/dsi: Add flag for continuous clock behavior Alexandre Courbot
2014-07-03  8:23   ` Andrzej Hajda
     [not found]     ` <53B5131B.1060702-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-07-04  5:57       ` Alexandre Courbot
     [not found]         ` <CAAVeFu+sTWhwCTd9ntqdJQA1aaFV93zHnyRSj6WA-8VicFuvgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-04  9:53           ` Andrzej Hajda
     [not found]             ` <53B679A0.1060306-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2014-07-06  9:30               ` Alexandre Courbot
2014-07-02 12:19 ` [PATCH 2/4] drm/tegra: dsi - Handle continuous clock flag Alexandre Courbot
2014-07-02 12:19 ` [PATCH 3/4] drm/panel: LG LH500WX1-SD03 uses continuous clock Alexandre Courbot
2014-07-02 12:19 ` [PATCH 4/4] ARM: tegra: roth: add display DT node Alexandre Courbot
2014-07-02 15:55   ` Stephen Warren
     [not found]     ` <53B42B60.1000600-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-07-03  3:10       ` Alexandre Courbot
2014-07-21 15:35         ` Stephen Warren [this message]
     [not found]           ` <53CD333F.2070805-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-07-21 21:16             ` Thierry Reding
2014-07-21 22:51               ` Mark Brown
     [not found]                 ` <20140721225153.GJ17528-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2014-07-22  4:39                   ` Alexandre Courbot
     [not found]                     ` <CAAVeFuKtVYNP5LFXGCEpkUtCCrK6AP+9WEVPDPs45RwAPvKKRg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-22  9:45                       ` Mark Brown
     [not found]   ` <1404303560-32209-5-git-send-email-acourbot-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-07-03  3:15     ` [PATCH v2] " Alexandre Courbot

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=53CD333F.2070805@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=acourbot@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=tbergstrom@nvidia.com \
    --cc=thierry.reding@gmail.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).