Re: [PATCH v2] Input: Make ADS7846 independent on regulator

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Marek Vasut <marek.vasut@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Igor Grinberg <grinberg@compulab.co.il>,
	linux-arm-kernel@lists.infradead.org, vapier@gentoo.org,
	khilman@deeprootsystems.com, dmitry.torokhov@gmail.com,
	linux-kernel@vger.kernel.org, pavel@ucw.cz,
	linux-input@vger.kernel.org, eric.y.miao@gmail.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH v2] Input: Make ADS7846 independent on regulator
Date: Thu, 9 Sep 2010 10:27:17 +0200	[thread overview]
Message-ID: <201009091027.18176.marek.vasut@gmail.com> (raw)
In-Reply-To: <20100907125335.GD25830@sirena.org.uk>

Dne Út 7. září 2010 14:53:35 Mark Brown napsal(a):
> On Tue, Sep 07, 2010 at 03:23:15PM +0300, Igor Grinberg wrote:
> >  Seems that there are some more platforms then Sharp Zaurus
> > 
> > are interested in this patch.
> > 
> > Dmitry, Mike, Pavel,
> > 
> > What's the status of it?
> 
> From a regulator API usage point of view a separate implementation of
> the same thing was nacked - there are regulator API facilties for hiding
> missing regulators from drivers when needed to get systems going, unless
> the device genuinely can cope without supplies it should be relying on
> those.

Maybe these platforms should have been fixed prior to applying the patch adding 
regulator goo into ads7846 driver then. What's the way to go now then ?

Thanks, Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)

From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] Input: Make ADS7846 independent on regulator
Date: Thu, 9 Sep 2010 10:27:17 +0200	[thread overview]
Message-ID: <201009091027.18176.marek.vasut@gmail.com> (raw)
In-Reply-To: <20100907125335.GD25830@sirena.org.uk>

Dne ?t 7. z??? 2010 14:53:35 Mark Brown napsal(a):
> On Tue, Sep 07, 2010 at 03:23:15PM +0300, Igor Grinberg wrote:
> >  Seems that there are some more platforms then Sharp Zaurus
> > 
> > are interested in this patch.
> > 
> > Dmitry, Mike, Pavel,
> > 
> > What's the status of it?
> 
> From a regulator API usage point of view a separate implementation of
> the same thing was nacked - there are regulator API facilties for hiding
> missing regulators from drivers when needed to get systems going, unless
> the device genuinely can cope without supplies it should be relying on
> those.

Maybe these platforms should have been fixed prior to applying the patch adding 
regulator goo into ads7846 driver then. What's the way to go now then ?

Thanks, Cheers

WARNING: multiple messages have this Message-ID (diff)

From: Marek Vasut <marek.vasut@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Igor Grinberg <grinberg@compulab.co.il>,
	linux-arm-kernel@lists.infradead.org, vapier@gentoo.org,
	khilman@deeprootsystems.com, dmitry.torokhov@gmail.com,
	linux-kernel@vger.kernel.org, pavel@ucw.cz,
	linux-input@vger.kernel.org, eric.y.miao@gmail.com,
	akpm@linux-foundation.org
Subject: Re: [PATCH v2] Input: Make ADS7846 independent on regulator
Date: Thu, 9 Sep 2010 10:27:17 +0200	[thread overview]
Message-ID: <201009091027.18176.marek.vasut@gmail.com> (raw)
In-Reply-To: <20100907125335.GD25830@sirena.org.uk>

Dne Út 7. září 2010 14:53:35 Mark Brown napsal(a):
> On Tue, Sep 07, 2010 at 03:23:15PM +0300, Igor Grinberg wrote:
> >  Seems that there are some more platforms then Sharp Zaurus
> > 
> > are interested in this patch.
> > 
> > Dmitry, Mike, Pavel,
> > 
> > What's the status of it?
> 
> From a regulator API usage point of view a separate implementation of
> the same thing was nacked - there are regulator API facilties for hiding
> missing regulators from drivers when needed to get systems going, unless
> the device genuinely can cope without supplies it should be relying on
> those.

Maybe these platforms should have been fixed prior to applying the patch adding 
regulator goo into ads7846 driver then. What's the way to go now then ?

Thanks, Cheers

next prev parent reply	other threads:[~2010-09-09  8:27 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31  7:09 [PATCH v2] Input: Make ADS7846 independent on regulator Marek Vasut
2010-07-31  7:09 ` Marek Vasut
2010-09-07 12:23 ` Igor Grinberg
2010-09-07 12:23   ` Igor Grinberg
2010-09-07 12:53   ` Mark Brown
2010-09-07 12:53     ` Mark Brown
2010-09-09  8:27     ` Marek Vasut [this message]
2010-09-09  8:27       ` Marek Vasut
2010-09-09  8:27       ` Marek Vasut
2010-09-09  9:41       ` Mark Brown
2010-09-09  9:41         ` Mark Brown
2010-09-09  9:41         ` Mark Brown
2010-10-01  0:20         ` Marek Vasut
2010-10-01  0:20           ` Marek Vasut
2010-10-01  0:20           ` Marek Vasut
2010-10-05  6:49         ` Igor Grinberg
2010-10-05  6:49           ` Igor Grinberg
2010-10-05  6:49           ` Igor Grinberg
2010-10-05  8:21           ` Marek Vasut
2010-10-05  8:21             ` Marek Vasut
2010-10-05  8:21             ` Marek Vasut
2010-10-05 16:16           ` Dmitry Torokhov
2010-10-05 16:16             ` Dmitry Torokhov
2010-10-05 16:16             ` Dmitry Torokhov
2010-10-05 16:40             ` Mark Brown
2010-10-05 16:40               ` Mark Brown
2010-10-05 18:07               ` Dmitry Torokhov
2010-10-05 18:07                 ` Dmitry Torokhov
2010-10-05 18:59                 ` Mark Brown
2010-10-05 18:59                   ` Mark Brown
2010-10-05 19:35                   ` Alan Cox
2010-10-05 19:35                     ` Alan Cox
2010-10-05 20:42                     ` Mark Brown
2010-10-05 20:42                       ` Mark Brown
2010-10-05 22:09                     ` Linus Walleij
2010-10-05 22:09                       ` Linus Walleij
2010-10-05 22:52                       ` Mark Brown
2010-10-05 22:52                         ` Mark Brown
2010-10-06  8:01                         ` Linus Walleij
2010-10-06  8:01                           ` Linus Walleij
2010-10-06  8:01                           ` Linus Walleij
2010-10-06 15:14                           ` Mark Brown
2010-10-06 15:14                             ` Mark Brown
2010-10-06 15:14                             ` Mark Brown

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=201009091027.18176.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric.y.miao@gmail.com \
    --cc=grinberg@compulab.co.il \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=vapier@gentoo.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 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.