Steve Sakoman | 1 May 02:36 2011
Picon

Re: sakoman-linux-omap-2.6/omap-2.6.38 branch: mmcblk0: retrying using single block read

On Sat, Apr 30, 2011 at 1:21 AM, Elvis Dowson <elvis.dowson <at> mac.com> wrote:
> Hi,
>       I'm using a Gumstix Overo Fire COM module (TI OMAP 3530 ES2.1) with Chestnut43 expansion board.
>
> I built the linux kernel using the omap-2.6.38 branch located here:
>
> http://www.sakoman.com/cgi-bin/gitweb.cgi?p=linux-omap-2.6.git;a=shortlog;h=refs/heads/omap-2.6.38
>
> I use the omap3_defconfig supplied in this branch. When I boot, I get the following mmc errors:
>
> Freeing init memory: 180K
> omap_device: omap_i2c.1: new worst case deactivate latency 0: 61035
> mmcblk0: retrying using single block read
> mmcblk0: retrying using single block read
> mmc1: new SDIO card at address 0001
> mmcblk0: retrying using single block read
> mmcblk0: retrying using single block read
> mmcblk0: retrying using single block read
> mmcblk0: retrying using single block read
> mmcblk0: retrying using single block read
> mmcblk0: retrying using single block read
>
> Does anyone have a patch or fix for this issue?

I haven't seen this issue.  Perhaps a bad card?  Have you tried a different one?

Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo <at> vger.kernel.org
(Continue reading)

Paul Walmsley | 1 May 15:24 2011

Re: [GIT PULL] OMAP hwmod/PRCM/clock: patches for 2.6.39-rc

Hi

On Fri, 29 Apr 2011, Paul Walmsley wrote:

> The following changes since commit 8e10cd74342c7f5ce259cceca36f6eba084f5d58:
> 
>   Linux 2.6.39-rc5 (2011-04-26 20:48:50 -0700)
> 
> are available in the git repository at:
>   git://git.pwsan.com/linux-2.6 for_tony_a_2.6.39rc

Please disregard these.  I just saw that Linus merged these patches from 
your branch the same day that I sent this.

- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

kalle.jokiniemi | 2 May 06:42 2011
Picon

RE: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions

Hi,

 > -----Original Message-----
 > From: ext Jarkko Nikula [mailto:jhnikula <at> gmail.com]
 > Sent: 29. huhtikuuta 2011 17:04
 > To: Jokiniemi Kalle (Nokia-SD/Tampere)
 > Cc: tony <at> atomide.com; Ailus Sakari (Nokia-SD/Helsinki); linux-
 > omap <at> vger.kernel.org; lrg <at> slimlogic.co.uk;
 > broonie <at> opensource.wolfsonmicro.com
 > Subject: Re: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions
 > 
 > On Fri, 29 Apr 2011 15:47:44 +0300
 > Kalle Jokiniemi <kalle.jokiniemi <at> nokia.com> wrote:
 > 
 > > +static struct regulator_init_data rx51_vintana1 = {
 > > +	.constraints = {
 > > +		.name			= "VINTANA1",
 > > +		.min_uV			= 1500000,
 > > +		.max_uV			= 1500000,
 > > +		.always_on		= true,
 > ...
 > > +static struct regulator_init_data rx51_vintdig = {
 > > +	.constraints = {
 > > +		.name			= "VINTDIG",
 > > +		.min_uV			= 1500000,
 > > +		.max_uV			= 1500000,
 > > +		.always_on		= true,
 > 
 > Are these two used at all? According to public schematics they are
 > connected to just one capasitor. Could be some needed filtering/charge
(Continue reading)

kalle.jokiniemi | 2 May 06:54 2011
Picon

RE: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions

Hi,

 > -----Original Message-----
 > From: ext Mark Brown [mailto:broonie <at> opensource.wolfsonmicro.com]
 > Sent: 30. huhtikuuta 2011 22:24
 > To: Jokiniemi Kalle (Nokia-SD/Tampere)
 > Cc: tony <at> atomide.com; Ailus Sakari (Nokia-SD/Helsinki); linux-
 > omap <at> vger.kernel.org; lrg <at> slimlogic.co.uk
 > Subject: Re: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions
 > 
 > On Fri, Apr 29, 2011 at 03:47:44PM +0300, Kalle Jokiniemi wrote:
 > 
 > > +		.always_on		= true,
 > > +		.valid_modes_mask	= REGULATOR_MODE_NORMAL
 > > +					| REGULATOR_MODE_STANDBY,
 > > +		.valid_ops_mask		= REGULATOR_CHANGE_MODE
 > > +					| REGULATOR_CHANGE_STATUS,
 > 
 > _CHANGE_STATUS doesn't make much sense in conjunction with always_on.
 > Otherwise this looks OK to me.

Ok, I'll remove those. Thanks.

- Kalle
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

(Continue reading)

kalle.jokiniemi | 2 May 07:19 2011
Picon

RE: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions


 > -----Original Message-----
 > From: Jokiniemi Kalle (Nokia-SD/Tampere)
> 
 > Hi,
 > 
 >  > -----Original Message-----
 >  > From: ext Jarkko Nikula [mailto:jhnikula <at> gmail.com]
 >  > Sent: 29. huhtikuuta 2011 17:04
 >  > To: Jokiniemi Kalle (Nokia-SD/Tampere)
 >  > Cc: tony <at> atomide.com; Ailus Sakari (Nokia-SD/Helsinki); linux-
 >  > omap <at> vger.kernel.org; lrg <at> slimlogic.co.uk;
 >  > broonie <at> opensource.wolfsonmicro.com
 >  > Subject: Re: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions
 >  >
 >  > On Fri, 29 Apr 2011 15:47:44 +0300
 >  > Kalle Jokiniemi <kalle.jokiniemi <at> nokia.com> wrote:
 >  >
 >  > > +static struct regulator_init_data rx51_vintana1 = {
 >  > > +	.constraints = {
 >  > > +		.name			= "VINTANA1",
 >  > > +		.min_uV			= 1500000,
 >  > > +		.max_uV			= 1500000,
 >  > > +		.always_on		= true,
 >  > ...
 >  > > +static struct regulator_init_data rx51_vintdig = {
 >  > > +	.constraints = {
 >  > > +		.name			= "VINTDIG",
 >  > > +		.min_uV			= 1500000,
 >  > > +		.max_uV			= 1500000,
(Continue reading)

Kalle Jokiniemi | 2 May 08:28 2011
Picon

[PATCH v2 0/1] RX-51: add full regulator definitions

Adding regulator definitions to correctly shut down unneeded
regulators. Needed, but previously undefined regulators were
marked "always_on".

Tested on top of MeeGo N900 DE daily release (.37 kernel) and
with linux-omap. Patch based on linux-omap HEAD.

v2: updated as per comments from Jarkko Nikula and Mark Brown.

Kalle Jokiniemi (1):
  OMAP3: rx-51: Add full regulator definitions

 arch/arm/mach-omap2/board-rx51-peripherals.c |   69 ++++++++++++++++++++++++++
 1 files changed, 69 insertions(+), 0 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Kalle Jokiniemi | 2 May 08:28 2011
Picon

[PATCH v2 1/1] OMAP3: rx-51: Add full regulator definitions

The vaux2 (VCSI) regulator is left on by the bootloader
in rx-51. Since there the product has shipped and there
won't be any bootloader updates to fix this issue, we
need to define all the regulators and declare full
constraints for the regulator FW. This will allow the
regulator FW to disable unused regulators.

Also this helps in adding more fine grain regulator
support for rx-51 in the future.

Thanks for Mark Brown for pointing out the correct
solution.

Signed-off-by: Kalle Jokiniemi <kalle.jokiniemi <at> nokia.com>
Cc: Mark Brown <broonie <at> opensource.wolfsonmicro.com>
---
 arch/arm/mach-omap2/board-rx51-peripherals.c |   69 ++++++++++++++++++++++++++
 1 files changed, 69 insertions(+), 0 deletions(-)

diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c b/arch/arm/mach-omap2/board-rx51-peripherals.c
index bbcb677..4026b4b 100644
--- a/arch/arm/mach-omap2/board-rx51-peripherals.c
+++ b/arch/arm/mach-omap2/board-rx51-peripherals.c
 <at>  <at>  -475,6 +475,32  <at>  <at>  static struct regulator_init_data rx51_vmmc2 = {
 	.consumer_supplies	= rx51_vmmc2_supplies,
 };

+static struct regulator_init_data rx51_vpll1 = {
+	.constraints = {
+		.name			= "VPLL",
(Continue reading)

Jarkko Nikula | 2 May 08:57 2011
Picon

Re: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions

On Mon, 2 May 2011 05:19:46 +0000
<kalle.jokiniemi <at> nokia.com> wrote:

> It seems I was not answering your question quite rightly... So these are used
> to power some internal blocks inside the TWL5030. The dependencies there
> are not very well documented, so it's best to leave them be. I think these
> could be turned off via the power scripts during OFF mode (if we would be
> using that).
> 
Sounds safe assumption for those two. Also I don't point out from
public schematics where are the vintana2 and vpll2 routed so looks like
need keep them on as well.

--

-- 
Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Jarkko Nikula | 2 May 08:58 2011
Picon

Re: [PATCH v2 1/1] OMAP3: rx-51: Add full regulator definitions

On Mon,  2 May 2011 09:28:53 +0300
Kalle Jokiniemi <kalle.jokiniemi <at> nokia.com> wrote:

> The vaux2 (VCSI) regulator is left on by the bootloader
> in rx-51. Since there the product has shipped and there
> won't be any bootloader updates to fix this issue, we
> need to define all the regulators and declare full
> constraints for the regulator FW. This will allow the
> regulator FW to disable unused regulators.
> 
> Also this helps in adding more fine grain regulator
> support for rx-51 in the future.
> 
> Thanks for Mark Brown for pointing out the correct
> solution.
> 
> Signed-off-by: Kalle Jokiniemi <kalle.jokiniemi <at> nokia.com>
> Cc: Mark Brown <broonie <at> opensource.wolfsonmicro.com>
> ---

Reviewed-by: Jarkko Nikula <jhnikula <at> gmail.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

kalle.jokiniemi | 2 May 10:48 2011
Picon

RE: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions

Hi,

 > -----Original Message-----
 > From: ext Jarkko Nikula [mailto:jhnikula <at> gmail.com]
 > Sent: 2. toukokuuta 2011 9:57
 > To: Jokiniemi Kalle (Nokia-SD/Tampere)
 > Cc: tony <at> atomide.com; Ailus Sakari (Nokia-SD/Helsinki); linux-
 > omap <at> vger.kernel.org; lrg <at> slimlogic.co.uk;
 > broonie <at> opensource.wolfsonmicro.com
 > Subject: Re: [PATCH 1/1] OMAP3: rx-51: Add full regulator definitions
 > 
 > On Mon, 2 May 2011 05:19:46 +0000
 > <kalle.jokiniemi <at> nokia.com> wrote:
 > 
 > > It seems I was not answering your question quite rightly... So these are used
 > > to power some internal blocks inside the TWL5030. The dependencies there
 > > are not very well documented, so it's best to leave them be. I think these
 > > could be turned off via the power scripts during OFF mode (if we would be
 > > using that).
 > >
 > Sounds safe assumption for those two. Also I don't point out from
 > public schematics where are the vintana2 and vpll2 routed so looks like
 > need keep them on as well.

In case you're interested, the high level routings are listed in the TPS65950
TRM: http://focus.ti.com/lit/ug/swcu050g/swcu050g.pdf 
See chapter 6.3, figure 6-3.

- Kalle

(Continue reading)


Gmane