From: Felipe Balbi <balbi@ti.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel test robot <fengguang.wu@intel.com>, LKP <lkp@01.org>,
<linux-kernel@vger.kernel.org>, Felipe Balbi <balbi@ti.com>
Subject: Re: [phy] kernel BUG at drivers/base/driver.c:153!
Date: Fri, 10 Jul 2015 14:48:59 -0500 [thread overview]
Message-ID: <20150710194859.GB21051@saruman.tx.rr.com> (raw)
In-Reply-To: <20150709081208.GA30554@kuha.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]
On Thu, Jul 09, 2015 at 11:12:08AM +0300, Heikki Krogerus wrote:
> On Wed, Jul 08, 2015 at 01:02:45AM +0800, kernel test robot wrote:
> > Greetings,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> >
> > commit 1c14905ef951fb968c8da90e4e64be02c309a2ae
> > Author: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > AuthorDate: Wed May 13 15:26:53 2015 +0300
> > Commit: Felipe Balbi <balbi@ti.com>
> > CommitDate: Wed May 13 12:07:01 2015 -0500
> >
> > phy: add driver for TI TUSB1210 ULPI PHY
> >
> > TUSB1210 ULPI PHY has vendor specific register for eye
> > diagram tuning. On some platforms the system firmware has
> > set optimized value to it. In order to not loose the
> > optimized value, the driver stores it during probe and
> > restores it every time the PHY is powered back on.
> >
> > Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > Acked-by: David Cohen <david.a.cohen@linux.intel.com>
> > Acked-by: Kishon Vijay Abraham I <kishon@ti.com>
> > Signed-off-by: Felipe Balbi <balbi@ti.com>
>
> This commit will fix the problem:
> https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/commit/?h=testing/next&id=6c97f002f678d5047bdf8a9e248dc50656c38ae2
>
> I think we should consider it as a fix for this issue. Unfortunately
> Felipe is on vacation at the moment. Greg, could help with this?
>
> I will also be on vacation for the rest of the month and my access to
> internet will be fairly limited.
Oh, I can move that to testing/fixes as soon as I'm back in a few more
days. cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-10 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 17:02 kernel test robot
2015-07-09 8:12 ` Heikki Krogerus
2015-07-10 19:48 ` Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-07 16:00 kernel test robot
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=20150710194859.GB21051@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome