From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Kevin Hilman <khilman@kernel.org>
Cc: k.kozlowski.k@gmail.com, devicetree@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Wolfram Sang <wsa@the-dreams.de>,
Ben Gamari <ben@smart-cactus.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
riku.voipio@linaro.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Kukjin Kim <kgene@kernel.org>,
Peter Chen <peter.chen@freescale.com>,
linux-arm-kernel@lists.infradead.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tyler Baker <tyler.baker@linaro.org>
Subject: Re: [RFT 0/3] usb: usb3503: Fix probing on Arndale board (missing phy)
Date: Sat, 10 Oct 2015 12:08:45 +0900 [thread overview]
Message-ID: <5618813D.20502@samsung.com> (raw)
In-Reply-To: <7hoag797gk.fsf@deeprootsystems.com>
W dniu 10.10.2015 o 04:18, Kevin Hilman pisze:
> Hi Krzystof,
>
> Krzysztof Kozlowski <k.kozlowski@samsung.com> writes:
>
>> Introduction
>> ============
>> This patchset tries to fix probing of usb3503 on Arndale board
>> if the Samsung PHY driver is probed later (or built as a module).
>>
>> *The patchset was not tested on Arndale board.*
>> I don't have that board. Please test it and say if the usb3503 deferred probe
>> works fine and the issue is solved.
>
> FYI... I built this series on top of next-20151009 and using
> exynos_defconfig. I booted it on my arndale, and I still don't see the
> networking come up. Full boot log attached.
+cc Tyler
Kevin,
Thanks for testing but I am not sure if this boot failure is related to
the patch. I mean if the patch should fix this particular boot failure.
The board stopped to boot after enabling DWC2 and network USB gadget:
http://www.spinics.net/lists/linux-samsung-soc/msg47009.html
The boot log shows that usb3503 was probed but asix network adapter was
not. I wonder how these things are related to each other...
Nevertheless it would be difficult to debug the issue without the
Arndale board. :)
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: k.kozlowski@samsung.com (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFT 0/3] usb: usb3503: Fix probing on Arndale board (missing phy)
Date: Sat, 10 Oct 2015 12:08:45 +0900 [thread overview]
Message-ID: <5618813D.20502@samsung.com> (raw)
In-Reply-To: <7hoag797gk.fsf@deeprootsystems.com>
W dniu 10.10.2015 o 04:18, Kevin Hilman pisze:
> Hi Krzystof,
>
> Krzysztof Kozlowski <k.kozlowski@samsung.com> writes:
>
>> Introduction
>> ============
>> This patchset tries to fix probing of usb3503 on Arndale board
>> if the Samsung PHY driver is probed later (or built as a module).
>>
>> *The patchset was not tested on Arndale board.*
>> I don't have that board. Please test it and say if the usb3503 deferred probe
>> works fine and the issue is solved.
>
> FYI... I built this series on top of next-20151009 and using
> exynos_defconfig. I booted it on my arndale, and I still don't see the
> networking come up. Full boot log attached.
+cc Tyler
Kevin,
Thanks for testing but I am not sure if this boot failure is related to
the patch. I mean if the patch should fix this particular boot failure.
The board stopped to boot after enabling DWC2 and network USB gadget:
http://www.spinics.net/lists/linux-samsung-soc/msg47009.html
The boot log shows that usb3503 was probed but asix network adapter was
not. I wonder how these things are related to each other...
Nevertheless it would be difficult to debug the issue without the
Arndale board. :)
Best regards,
Krzysztof
next prev parent reply other threads:[~2015-10-10 3:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 0:30 [RFT 0/3] usb: usb3503: Fix probing on Arndale board (missing phy) Krzysztof Kozlowski
2015-10-07 0:30 ` Krzysztof Kozlowski
2015-10-07 0:30 ` [RFT 1/3] dt-bindings: usb: usb5303: Document new 'phys' property Krzysztof Kozlowski
2015-10-07 0:30 ` Krzysztof Kozlowski
2015-10-07 0:30 ` [RFT 2/3] usb: misc: usb3503: Allow usage of device through phy interface Krzysztof Kozlowski
2015-10-07 0:30 ` Krzysztof Kozlowski
2015-10-07 0:30 ` [RFT 3/3] ARM: dts: Fix usb3503 probe by enabling phy on exynos5250-arndale Krzysztof Kozlowski
2015-10-07 0:30 ` Krzysztof Kozlowski
2015-10-07 14:26 ` [RFT 0/3] usb: usb3503: Fix probing on Arndale board (missing phy) Marek Szyprowski
2015-10-07 14:26 ` Marek Szyprowski
2015-10-08 6:02 ` Krzysztof Kozlowski
2015-10-08 6:02 ` Krzysztof Kozlowski
2015-10-08 6:23 ` Marek Szyprowski
2015-10-08 6:23 ` Marek Szyprowski
2015-10-08 9:35 ` Javier Martinez Canillas
2015-10-08 9:35 ` Javier Martinez Canillas
[not found] ` <561638ED.1060503-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2015-10-08 9:58 ` Marek Szyprowski
2015-10-08 9:58 ` Marek Szyprowski
2015-10-08 9:58 ` Marek Szyprowski
2015-10-09 19:18 ` Kevin Hilman
2015-10-09 19:18 ` Kevin Hilman
2015-10-10 3:08 ` Krzysztof Kozlowski [this message]
2015-10-10 3:08 ` Krzysztof Kozlowski
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=5618813D.20502@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=arnd@arndb.de \
--cc=ben@smart-cactus.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=k.kozlowski.k@gmail.com \
--cc=kgene@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=peter.chen@freescale.com \
--cc=riku.voipio@linaro.org \
--cc=tyler.baker@linaro.org \
--cc=wsa@the-dreams.de \
/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.