smsc9514 - waiting for devices (Re: Pandaboard ES)

Hi,
my test steps:
smsc9514 is activated in u-boot first
=> usb info
1: Hub,  USB Revision 2.0
 - u-boot EHCI Host Controller
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0000  Product 0x0000 Version 1.0
   Configuration: 1
   - Interfaces: 1 Self Powered 0mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Hub,  USB Revision 2.0
 - Class: Hub
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0424  Product 0x9514 Version 2.0
   Configuration: 1
   - Interfaces: 1 Self Powered Remote Wakeup 2mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 1
     - Class Hub
     - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms
     - Endpoint 1 In Interrupt MaxPacket 1 Interval 12ms

3: Vendor specific,  USB Revision 2.0
 - Class: Vendor specific
 - PacketSize: 64  Configurations: 1
 - Vendor: 0x0424  Product 0xec00 Version 2.0
   Configuration: 1
   - Interfaces: 1 Self Powered Remote Wakeup 2mA
     Interface: 0
     - Alternate Setting 0, Endpoints: 3
     - Class Vendor specific
     - Endpoint 1 In Bulk MaxPacket 512
     - Endpoint 2 Out Bulk MaxPacket 512
     - Endpoint 3 In Interrupt MaxPacket 16 Interval 4ms

then booting kernel and I get such related debug messages:
[   2.0001780] uhub0 at usb0: NetBSD (0x0000) EHCI root hub (0x0000), class 9/0, rev 2.00/1.00, addr 1
[   2.0099135] uhub0: 3 ports with 3 removable, self powered
[   2.0419450] uhub1 at usb1: NetBSD (0x0000) MOTG root hub (0x0000), class 9/0, rev 2.00/1.00, addr 1
[   2.0579597] uhub1: 1 port with 1 removable, self powered
[   2.0739677] WARNING: system needs entropy for security; see entropy(7)
[   2.6273143] IPsec: Initialized Security Association Processing.
[   2.6657300] sdmmc1: couldn't enable card: 60
[   2.6913199] aes: ARM NEON vpaes
[   2.6977225] chacha: ARM NEON ChaCha
[   2.7041246] adiantum: self-test passed
[   2.7116708] aes_ccm: self-test passed
[   2.7201230] blake2s: self-test passed
[   2.7457158] sdmmc0: SD card status: 4-bit, C10
[   2.7521158] ld0 at sdmmc0: <0x03:0x5344:SU16G:0x80:0x1bec8779:0x0c8>
[   2.7649147] ld0: 15193 MB, 7717 cyl, 64 head, 63 sec, 512 bytes/sect x 31116288 sectors
[   2.7841226] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz
[   3.1105168] waiting for devices: usb0 uhub0
[   3.4369144] waiting for devices: usb0 uhub0
[...]
[  22.6945067] waiting for devices: usb0 uhub0
[  23.0209050] waiting for devices: usb0 uhub0
[  23.2257045] uhub0: device problem, disabling port 1
[  23.2333415] waiting for devices: usb0

Any ideas?

-rxg

On Wed, Apr 09, 2025 at 12:51:51PM +0800, Rui-Xiang Guo wrote:
> On Tue, Apr 08, 2025 at 04:06:24PM -0400, Lwazi Dube wrote:
> > >
> > > > > Some known issues:
> > > > > 1. a9ptmr manually obtains frequency, not sure if this is a good
> > > solution.
> > > > > 2. armpmu failed to be attached, it seems to be a problem with dts.
> > > > > 3. ti_prcm doesn't support multiple instances so we can get the last
> > > attached
> > > > >    PRCM (CM2) clocks only, this causes tiwdt to not work.
> > > >
> > > > Issue 3 should be my misunderstanding, tiwdt is attached if I comment out
> > > > wd_timer3 clock in omap4_prcm.
> > >
> > > Issue 1 is fixed by changing a9ptmr pass 2 to 3 so a9ptmr.diff is no need.
> > >
> > 
> > I see this in your original dmesg: arma9ptmr0 at a9ptmr0: A9 Private Timer
> > (349 MHz)
> > Are the private timers still 349MHz after your change?
> 
> Hi,
> it becomes
> [   1.0000000] arma9ptmr0 at a9ptmr0: A9 Private Timer (174 MHz)
> which comes from mpu_periphclk.
> 
> The updated boot log:
> https://dmesgd.nycbug.org/index.cgi?do=view&id=8308
> 
> BTW, the cause of Issue 2 is the default loading omap4-panda.dtb has no
> interrupts definition. I will try to force load omap4-panda-es.dtb.
> 
> -rxg
>