lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-id: <56152BB2.4020202@samsung.com> Date: Wed, 07 Oct 2015 16:26:58 +0200 From: Marek Szyprowski <m.szyprowski@...sung.com> To: Krzysztof Kozlowski <k.kozlowski@...sung.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Peter Chen <peter.chen@...escale.com>, Ben Gamari <ben@...rt-cactus.org>, Wolfram Sang <wsa@...-dreams.de>, linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, Kukjin Kim <kgene@...nel.org>, linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org Cc: Kevin Hilman <khilman@...nel.org>, Arnd Bergmann <arnd@...db.de>, riku.voipio@...aro.org Subject: Re: [RFT 0/3] usb: usb3503: Fix probing on Arndale board (missing phy) Hello, On 2015-10-07 02:30, Krzysztof Kozlowski wrote: > 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. > > The patchset was tested on Odroid U3 board (which is different!) > in a simulated environment. It is not sufficient testing. > > > Difference > ========== > The usb3503 device driver can be used as a I2C device (on Odroid U3) > or as a platform device connected through phy (on Arndale). In the second > case the necessary phy reference has to be obtained and enabled. > > For some details please look also at thread [0][1]. > > [0] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-June/348524.html > [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2015-June/348875.html > I'm not sure that this is the correct approach. usb3503 chip is simply connected to Exynos USB2 phy, so it visible on the USB bus. The real driver that controls USB2 PHY is Exynos EHCI driver and USB3503 should not mess around it. In my opinion all that is needed in case of Arndale board is forcing reset of usb3503 chip after successful EHCI and USB2 PHY initialization (for some reason initialization of usb3503 chip must be done after usb host initialization). However I have no idea which driver should trigger this reset. Right now I didn't find any good solution for additional control for devices which are on autoprobed bus like usb. Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists