From: Igor Grinberg <grinberg@compulab.co.il>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Stanislav Brabec <utx@penguin.cz>,
Marek Vasut <marek.vasut@gmail.com>,
linux-arm-kernel@lists.infradead.org,
zaurus-devel@lists.linuxtogo.org,
spi-devel-general@lists.sourceforge.net, 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: kernel panic in spi_complete() on spitz (PXA270)
Date: Thu, 30 Jun 2011 23:50:17 +0300 [thread overview]
Message-ID: <4E0CE189.1020000@compulab.co.il> (raw)
In-Reply-To: <20110630180105.GA5064@opensource.wolfsonmicro.com>
On 06/30/11 21:01, Mark Brown wrote:
> On Thu, Jun 30, 2011 at 08:40:40PM +0300, Igor Grinberg wrote:
>> On 06/30/11 19:13, Stanislav Brabec wrote:
>
>>> I seen two
>>> proposals:
>>> - As ADS7846 hardware does not require dedicated regulator, don't
>>> require it in driver and fail only on platforms that have a dedicated
>>> regulator.
>> The thing is that ads7846 chip itself just requires power supply
> Right, and the regulator API hides the non-switchability of the supply
> from the driver so there's no need for the driver to worry about how the
> supplies are wired up. It just turns the regulator on when it needs it
> and turns it off when it doesn't.
>
>>>> 1) add regulator definition for ads7846 into the board file
>>> There is no dedicated regulator on spitz, ADS7846 uses common always-on
>>> power supply.
>> Is there a kind of regulator for this case (except dummy)?
>> Some kind of fixed regulator which is not binded to any supply?
> This is just a fixed voltage regulator, support for that has been in the
> kernel since the regulator API was merged. This is the best solution,
> it ensures that you don't mistakenly activate dummy reglators for
> supplies that really need software control.
Right, just as I thought (I still haven't made myself familiar with all the
regulator API aspects).
Stanislav,
Can't you define a fixed voltage regulator for the ads7846 in spitz board file?
This shouldn't be a hard task and is the right solution from the regulator API POV.
--
Regards,
Igor.
WARNING: multiple messages have this Message-ID (diff)
From: grinberg@compulab.co.il (Igor Grinberg)
To: linux-arm-kernel@lists.infradead.org
Subject: kernel panic in spi_complete() on spitz (PXA270)
Date: Thu, 30 Jun 2011 23:50:17 +0300 [thread overview]
Message-ID: <4E0CE189.1020000@compulab.co.il> (raw)
In-Reply-To: <20110630180105.GA5064@opensource.wolfsonmicro.com>
On 06/30/11 21:01, Mark Brown wrote:
> On Thu, Jun 30, 2011 at 08:40:40PM +0300, Igor Grinberg wrote:
>> On 06/30/11 19:13, Stanislav Brabec wrote:
>
>>> I seen two
>>> proposals:
>>> - As ADS7846 hardware does not require dedicated regulator, don't
>>> require it in driver and fail only on platforms that have a dedicated
>>> regulator.
>> The thing is that ads7846 chip itself just requires power supply
> Right, and the regulator API hides the non-switchability of the supply
> from the driver so there's no need for the driver to worry about how the
> supplies are wired up. It just turns the regulator on when it needs it
> and turns it off when it doesn't.
>
>>>> 1) add regulator definition for ads7846 into the board file
>>> There is no dedicated regulator on spitz, ADS7846 uses common always-on
>>> power supply.
>> Is there a kind of regulator for this case (except dummy)?
>> Some kind of fixed regulator which is not binded to any supply?
> This is just a fixed voltage regulator, support for that has been in the
> kernel since the regulator API was merged. This is the best solution,
> it ensures that you don't mistakenly activate dummy reglators for
> supplies that really need software control.
Right, just as I thought (I still haven't made myself familiar with all the
regulator API aspects).
Stanislav,
Can't you define a fixed voltage regulator for the ads7846 in spitz board file?
This shouldn't be a hard task and is the right solution from the regulator API POV.
--
Regards,
Igor.
WARNING: multiple messages have this Message-ID (diff)
From: Igor Grinberg <grinberg@compulab.co.il>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Stanislav Brabec <utx@penguin.cz>,
Marek Vasut <marek.vasut@gmail.com>,
linux-arm-kernel@lists.infradead.org,
zaurus-devel@www.linuxtogo.org,
spi-devel-general@lists.sourceforge.net, 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: kernel panic in spi_complete() on spitz (PXA270)
Date: Thu, 30 Jun 2011 23:50:17 +0300 [thread overview]
Message-ID: <4E0CE189.1020000@compulab.co.il> (raw)
In-Reply-To: <20110630180105.GA5064@opensource.wolfsonmicro.com>
On 06/30/11 21:01, Mark Brown wrote:
> On Thu, Jun 30, 2011 at 08:40:40PM +0300, Igor Grinberg wrote:
>> On 06/30/11 19:13, Stanislav Brabec wrote:
>
>>> I seen two
>>> proposals:
>>> - As ADS7846 hardware does not require dedicated regulator, don't
>>> require it in driver and fail only on platforms that have a dedicated
>>> regulator.
>> The thing is that ads7846 chip itself just requires power supply
> Right, and the regulator API hides the non-switchability of the supply
> from the driver so there's no need for the driver to worry about how the
> supplies are wired up. It just turns the regulator on when it needs it
> and turns it off when it doesn't.
>
>>>> 1) add regulator definition for ads7846 into the board file
>>> There is no dedicated regulator on spitz, ADS7846 uses common always-on
>>> power supply.
>> Is there a kind of regulator for this case (except dummy)?
>> Some kind of fixed regulator which is not binded to any supply?
> This is just a fixed voltage regulator, support for that has been in the
> kernel since the regulator API was merged. This is the best solution,
> it ensures that you don't mistakenly activate dummy reglators for
> supplies that really need software control.
Right, just as I thought (I still haven't made myself familiar with all the
regulator API aspects).
Stanislav,
Can't you define a fixed voltage regulator for the ads7846 in spitz board file?
This shouldn't be a hard task and is the right solution from the regulator API POV.
--
Regards,
Igor.
next prev parent reply other threads:[~2011-06-30 20:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 16:09 kernel panic in spi_complete() on spitz (PXA270) Stanislav Brabec
2011-06-23 16:09 ` Stanislav Brabec
2011-06-30 11:52 ` Marek Vasut
2011-06-30 11:52 ` Marek Vasut
2011-06-30 11:52 ` Marek Vasut
[not found] ` <201106301352.21684.marek.vasut-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-30 14:45 ` Stanislav Brabec
2011-06-30 14:45 ` Stanislav Brabec
2011-06-30 14:45 ` Stanislav Brabec
2011-06-30 15:09 ` Marek Vasut
2011-06-30 15:09 ` Marek Vasut
2011-06-30 15:09 ` Marek Vasut
2011-06-30 15:36 ` Pavel Herrmann
2011-06-30 15:36 ` Pavel Herrmann
2011-06-30 15:36 ` Pavel Herrmann
2011-06-30 16:22 ` Stanislav Brabec
2011-06-30 16:22 ` Stanislav Brabec
2011-06-30 16:22 ` Stanislav Brabec
2011-06-30 15:25 ` Igor Grinberg
2011-06-30 15:25 ` Igor Grinberg
2011-06-30 15:25 ` Igor Grinberg
2011-06-30 15:59 ` Mark Brown
2011-06-30 15:59 ` Mark Brown
2011-06-30 15:59 ` Mark Brown
[not found] ` <4E0C957F.8080807-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2011-06-30 16:13 ` Stanislav Brabec
2011-06-30 16:13 ` Stanislav Brabec
2011-06-30 16:13 ` Stanislav Brabec
2011-06-30 17:40 ` Igor Grinberg
2011-06-30 17:40 ` Igor Grinberg
2011-06-30 17:40 ` Igor Grinberg
2011-06-30 18:01 ` Mark Brown
2011-06-30 18:01 ` Mark Brown
2011-06-30 18:01 ` Mark Brown
2011-06-30 20:50 ` Igor Grinberg [this message]
2011-06-30 20:50 ` Igor Grinberg
2011-06-30 20:50 ` Igor Grinberg
[not found] ` <4E0CE189.1020000-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
2011-06-30 22:20 ` Stanislav Brabec
2011-06-30 22:20 ` Stanislav Brabec
2011-06-30 22:20 ` Stanislav Brabec
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=4E0CE189.1020000@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=akpm@linux-foundation.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dmitry.torokhov@gmail.com \
--cc=eric.y.miao@gmail.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=pavel@ucw.cz \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=utx@penguin.cz \
--cc=vapier@gentoo.org \
--cc=zaurus-devel@lists.linuxtogo.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.