On 01/26/2015 09:19 AM, Andreas Färber wrote:
Hi Michal,
Am 03.12.2014 um 09:39 schrieb Michal Simek:
quoted
On 12/02/2014 05:07 PM, Soren Brinkmann wrote:
quoted
Add USB nodes to zc702, zc706 and zed device trees.
Signed-off-by: Soren Brinkmann <redacted>
---
v3:
- rename phy nodes: usb_phy -> phy0
- rebased onto zynq/dt
v2:
- remove '@0' from phy node name
- don't add bogus space
---
arch/arm/boot/dts/zynq-7000.dtsi | 20 ++++++++++++++++++++
arch/arm/boot/dts/zynq-zc702.dts | 11 +++++++++++
arch/arm/boot/dts/zynq-zc706.dts | 10 ++++++++++
arch/arm/boot/dts/zynq-zed.dts | 10 ++++++++++
4 files changed, 51 insertions(+)
[...]
quoted
Applied to zynq/dt.
Hm, I don't see this patch in linux-next next-20150123...
And if I apply it to my -next based tree, adding corresponding nodes to
zynq-parallella.dts, I get repeatedly:
[ +0,012242] ci_hdrc ci_hdrc.0: no of_node; not parsing pinctrl DT
[ +0,000157] ci_hdrc ci_hdrc.0: ChipIdea HDRC found, lpm: 0; cap:
f090e100 op: f090e140
[ +0,000081] platform ci_hdrc.0: Driver ci_hdrc requests probe deferral
[ +0,005360] ci_hdrc ci_hdrc.1: no of_node; not parsing pinctrl DT
[ +0,000120] ci_hdrc ci_hdrc.1: ChipIdea HDRC found, lpm: 0; cap:
f0910100 op: f0910140
[ +0,001810] platform ci_hdrc.1: Driver ci_hdrc requests probe deferral
Am I missing any other patches or config options?
(I do notice that the pinctrl v3 patch that got merged has a trivial bug
for usb0, for which I'll send a patch later on.)
Why is it deferred? Is it because of pinmuxing stuff?
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform