From: Paolo Pisati <p.pisati@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "menon.nishanth@gmail.com" <menon.nishanth@gmail.com>,
Balaji T K <balajitk@ti.com>, Paul Walmsley <paul@pwsan.com>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
kernel-build-reports@lists.linaro.org
Subject: Re: OMAP baseline test results for v3.14
Date: Thu, 3 Apr 2014 15:32:37 +0200 [thread overview]
Message-ID: <20140403133237.GA6019@luxor.wired.org> (raw)
In-Reply-To: <20140402171513.GE12234@atomide.com>
On Wed, Apr 02, 2014 at 10:15:13AM -0700, Tony Lindgren wrote:
> > Paul uses MMC filesystem, I use NFS. As Felipe Pointed out as well, I
> > did rootcause MMC filesystem mount issue here:
> > http://marc.info/?l=linux-omap&m=139637044425644&w=2
>
> Balaji, care to take a look at the issue for MMC? It may
> be already fixed in next with the PBIAS handling?
it may be related (or not), but i'm experiencing reboot issues with 3.13/.14 on
omap4 (panda), and after a bisection i found out that reverting
commit e002264f7e45d7661b237045577052fd0b40f89c
Author: Balaji T K <balajitk <at> ti.com>
Date: Mon Oct 21 00:25:18 2013 +0530
mmc: omap_hsmmc: Fix pbias_disable for omap4
pbias_disable is set to protect the mmc pbias i/o cells in DT boot
by preventing voltage switch. Currently pbias_disable is enabled only
for omap3 and not for omap4 due to reg_offset difference of 0x100.
Enable pbias_disable for omap4+ too by using res->start
which does not include the reg_offset.
Signed-off-by: Balaji T K <balajitk <at> ti.com>
Signed-off-by: Chris Ball <cjb <at> laptop.org>
made it go away: can you point me to those pbias handling patches (i guess
something about dt-booting handling pbias correctly now)?
Root on mmc in my case.
--
bye,
p.
WARNING: multiple messages have this Message-ID (diff)
From: p.pisati@gmail.com (Paolo Pisati)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.14
Date: Thu, 3 Apr 2014 15:32:37 +0200 [thread overview]
Message-ID: <20140403133237.GA6019@luxor.wired.org> (raw)
In-Reply-To: <20140402171513.GE12234@atomide.com>
On Wed, Apr 02, 2014 at 10:15:13AM -0700, Tony Lindgren wrote:
> > Paul uses MMC filesystem, I use NFS. As Felipe Pointed out as well, I
> > did rootcause MMC filesystem mount issue here:
> > http://marc.info/?l=linux-omap&m=139637044425644&w=2
>
> Balaji, care to take a look at the issue for MMC? It may
> be already fixed in next with the PBIAS handling?
it may be related (or not), but i'm experiencing reboot issues with 3.13/.14 on
omap4 (panda), and after a bisection i found out that reverting
commit e002264f7e45d7661b237045577052fd0b40f89c
Author: Balaji T K <balajitk <at> ti.com>
Date: Mon Oct 21 00:25:18 2013 +0530
mmc: omap_hsmmc: Fix pbias_disable for omap4
pbias_disable is set to protect the mmc pbias i/o cells in DT boot
by preventing voltage switch. Currently pbias_disable is enabled only
for omap3 and not for omap4 due to reg_offset difference of 0x100.
Enable pbias_disable for omap4+ too by using res->start
which does not include the reg_offset.
Signed-off-by: Balaji T K <balajitk <at> ti.com>
Signed-off-by: Chris Ball <cjb <at> laptop.org>
made it go away: can you point me to those pbias handling patches (i guess
something about dt-booting handling pbias correctly now)?
Root on mmc in my case.
--
bye,
p.
next prev parent reply other threads:[~2014-04-03 13:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 16:03 OMAP baseline test results for v3.14 Paul Walmsley
2014-04-02 16:03 ` Paul Walmsley
2014-04-02 16:21 ` Tony Lindgren
2014-04-02 16:21 ` Tony Lindgren
2014-04-02 16:21 ` Felipe Balbi
2014-04-02 16:21 ` Felipe Balbi
2014-04-02 16:33 ` Tony Lindgren
2014-04-02 16:33 ` Tony Lindgren
2014-04-02 16:32 ` Paul Walmsley
2014-04-02 16:32 ` Paul Walmsley
2014-04-02 16:35 ` Tony Lindgren
2014-04-02 16:35 ` Tony Lindgren
2014-04-02 16:59 ` menon.nishanth
2014-04-02 16:59 ` menon.nishanth at gmail.com
2014-04-02 17:15 ` Tony Lindgren
2014-04-02 17:15 ` Tony Lindgren
2014-04-03 13:32 ` Paolo Pisati [this message]
2014-04-03 13:32 ` Paolo Pisati
2014-04-03 13:44 ` Balaji T K
2014-04-03 13:44 ` Balaji T K
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=20140403133237.GA6019@luxor.wired.org \
--to=p.pisati@gmail.com \
--cc=balajitk@ti.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=menon.nishanth@gmail.com \
--cc=paul@pwsan.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.