From: Tony Lindgren <tony@atomide.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
devicetree@vger.kernel.org, Dave Gerlach <d-gerlach@ti.com>,
Keerthy <j-keerthy@ti.com>,
linux-kernel@vger.kernel.org, Tero Kristo <t-kristo@ti.com>,
Faiz Abbas <faiz_abbas@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: omap5: Add l4 interconnect hierarchy and ti-sysc data
Date: Wed, 12 Dec 2018 17:19:50 -0800 [thread overview]
Message-ID: <20181213011950.GM6707@atomide.com> (raw)
In-Reply-To: <20181212171143.GG6707@atomide.com>
* Tony Lindgren <tony@atomide.com> [181212 17:12]:
> * Peter Ujfalusi <peter.ujfalusi@ti.com> [181212 02:44]:
> > On 12/12/2018 12.12, Peter Ujfalusi wrote:
> > > Reverting this patch in linux-next-20181210 will make the ethernet
> > > working again.
> > >
> > > bootlog w/ revert: https://pastebin.com/dpRk1xWv
> > > bootlog w/o revert: https://pastebin.com/PWrBttxd
> >
> > on omap5-uevm.
>
> Thanks for testing. Looks like it works for me with
> loadable modules. And looks like changing just the phy to
> use CONFIG_NOP_USB_XCEIV=y in my .config is not enough to
> make it fail, I see it fail too with EHCI built-in.
>
> It's probably some -EPROBE_DEFER type issues, but I need
> to debug more.
Yes there's an issue where nop_reset() for phy-generic is
not called by ehci-omap. I'll post a fix for that separately.
I also noticed that sata phy reg entries need fixing up
for omap5, will also post a patch for that.
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-12-13 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 22:45 [PATCH] ARM: dts: omap5: Add l4 interconnect hierarchy and ti-sysc data Tony Lindgren
[not found] ` <9b7e07ae-66f9-cedf-937d-b1c5c510e018@ti.com>
2018-12-12 10:46 ` Peter Ujfalusi
2018-12-12 17:11 ` Tony Lindgren
2018-12-13 1:19 ` 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=20181213011950.GM6707@atomide.com \
--to=tony@atomide.com \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=faiz_abbas@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=j-keerthy@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=peter.ujfalusi@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).