From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-omap@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Tero Kristo <t-kristo@ti.com>
Subject: Re: Errors at boot time from OMAP4430SDP (and a whinge about serial stuff)
Date: Thu, 25 Oct 2012 10:46:27 -0700 [thread overview]
Message-ID: <20121025174627.GU11928@atomide.com> (raw)
In-Reply-To: <871ugm310v.fsf@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [121025 10:39]:
> Kevin Hilman <khilman@deeprootsystems.com> writes:
>
> > Tony Lindgren <tony@atomide.com> writes:
> >
> [...]
>
> >>> omap_hsmmc omap_hsmmc.4: Failed to get debounce clk
> >>> omap_vc_i2c_init: I2C config for vdd_iva does not match other channels (0).
> >>> omap_vc_i2c_init: I2C config for vdd_mpu does not match other channels (0).Power Management for TI OMAP4.
> >>> mmc1: host does not support reading read-only switch. assuming write-enable.
> >>>
> >>> This looks much better compared to the previous set, but we could still
> >>> do with getting a "\n" on at least one of those messages...
> >>
> >> Kevin, do you have a patch for some of this?
> >>
> >
> > I'll fix up the missing newline right away.
>
> Patch sent.
OK thanks.
> > I was planning to leave the VC mismatch problem because it's fixed in
> > Tero's auto retention series. However, I haven't been able to get to
> > that series yet due to all the regressions/bugfixes, so I'll at least
> > pull out the part that fixes up the mistmatch and submit it for v3.7.
>
> On closer look, I don't think a quick fix is right for this one. Those
> I2C config mismatch warnings are legitmate for now, and will be fixed
> when Tero's series is merged.
OK fine with me.
Regards,
Tony
> > [1] http://marc.info/?l=linux-omap&m=134859084918176&w=2
prev parent reply other threads:[~2012-10-25 17:46 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 15:54 Errors at boot time from OMAP4430SDP (and a whinge about serial stuff) Russell King - ARM Linux
2012-10-12 16:24 ` Tony Lindgren
2012-10-12 16:31 ` Russell King - ARM Linux
2012-10-12 16:34 ` Benoit Cousson
2012-10-12 16:56 ` Tony Lindgren
2012-10-12 18:47 ` Kevin Hilman
2012-10-14 18:30 ` Ohad Ben-Cohen
2012-10-16 18:10 ` Tony Lindgren
2012-10-16 18:26 ` Tony Lindgren
2012-10-17 9:10 ` Ohad Ben-Cohen
2012-10-17 12:43 ` Igor Grinberg
2012-10-18 16:58 ` Ohad Ben-Cohen
2012-10-19 17:07 ` Tony Lindgren
2012-10-21 14:54 ` Ohad Ben-Cohen
2012-10-23 7:37 ` Igor Grinberg
2012-10-23 7:51 ` Ohad Ben-Cohen
2012-10-23 9:46 ` Igor Grinberg
2012-10-24 1:54 ` Tony Lindgren
2012-10-24 11:15 ` Ohad Ben-Cohen
2012-10-25 19:03 ` Tony Lindgren
2012-10-15 5:54 ` Mohammed, Afzal
2012-10-16 18:12 ` Tony Lindgren
2012-10-16 19:24 ` Benoit Cousson
2012-10-16 19:53 ` Tony Lindgren
2012-10-15 7:37 ` Péter Ujfalusi
2012-10-23 10:10 ` Russell King - ARM Linux
2012-10-25 1:09 ` Tony Lindgren
2012-10-25 16:05 ` Balaji T K
2012-10-25 17:24 ` Kevin Hilman
2012-10-25 17:38 ` Kevin Hilman
2012-10-25 17:46 ` Tony Lindgren [this message]
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=20121025174627.GU11928@atomide.com \
--to=tony@atomide.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).