All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Russ Dill <Russ.Dill@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-omap@vger.kernel.org,
	Robert Nelson <robertcnelson@gmail.com>,
	Jason Kridner <jkridner@beagleboard.org>
Subject: Re: [PATCH] OMAP: Beagle: fix TFP410 powerdown GPIO init
Date: Thu, 14 Jun 2012 11:20:59 +0300	[thread overview]
Message-ID: <1339662059.2229.8.camel@deskari> (raw)
In-Reply-To: <CA+Bv8Xad=9dQw_4a=DZypbR2KN77mb=3thkE6syMt-E6JoDDaw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

On Thu, 2012-06-14 at 01:17 -0700, Russ Dill wrote:
> On Thu, Jun 14, 2012 at 1:13 AM, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:

> > Okay. These are a bit problematic, because we're in the process of
> > removing these kinds of things from the board file, as they cannot be
> > supported with device tree. The tfp410 driver in v3.5 doesn't even have
> > the platform_enable/disable callback anymore.
> >
> > Those do not belong to tfp410 driver, but I don't really know how they
> > should be handled. This is one of the questions about device tree that
> > is unclear to me...
> 
> 
> Are you talking about the AUX_3V3_DIS pin? The boardfile currently
> just initializes that low, that should be too much of a problem to put
> into DT, or if someone is so inclined assign it to a regulator via DT.

Ah, sorry. You are right. The only gpio handled in the
platform_enable/disable calls is the power-down gpio, and that is
handled by the tfp410 driver properly. So there shouldn't be a problem
there.

 Tomi


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-06-14  8:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13  9:20 [PATCH] OMAP: Beagle: fix TFP410 powerdown GPIO init Tomi Valkeinen
2012-06-14  6:58 ` Russ Dill
2012-06-14  7:18   ` Tomi Valkeinen
2012-06-14  7:59     ` Russ Dill
2012-06-14  8:13       ` Tomi Valkeinen
2012-06-14  8:17         ` Russ Dill
2012-06-14  8:20           ` Tomi Valkeinen [this message]
2012-06-14 11:40         ` Russ Dill
2012-06-14 12:20           ` Tomi Valkeinen
2012-06-20 13:48             ` Tony Lindgren

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=1339662059.2229.8.camel@deskari \
    --to=tomi.valkeinen@ti.com \
    --cc=Russ.Dill@ti.com \
    --cc=jkridner@beagleboard.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robertcnelson@gmail.com \
    --cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.