All of lore.kernel.org
 help / color / mirror / Atom feed
From: martin.blumenstingl@googlemail.com (Martin Blumenstingl)
To: linus-amlogic@lists.infradead.org
Subject: Testing.
Date: Sun, 7 May 2017 23:08:48 +0200	[thread overview]
Message-ID: <CAFBinCAktR94_3diH1NqAL4uXbLkL_cThaj7WtXgODe0LMQ88A@mail.gmail.com> (raw)
In-Reply-To: <f1cfbf25-08a8-46c1-a6bc-886a850ca8c2@yandex.ru>

On Sun, May 7, 2017 at 10:57 PM, Oleg <balbes-150@yandex.ru> wrote:
> [    5.784393] tegra-ehci: Tegra EHCI driver
> [    5.788381] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
> [    5.794471] ohci-pci: OHCI PCI platform driver
> [    5.798903] ohci-platform: OHCI generic platform driver
> [    5.804174] ohci-omap3: OHCI OMAP3 driver
> [    5.808132] SPEAr-ohci: OHCI SPEAr driver
> [    5.812119] ohci-st: OHCI STMicroelectronics driver
> [    5.816989] ohci-atmel: OHCI Atmel driver
> [    5.821290] usbcore: registered new interface driver usb-storage
> [    5.829289] i2c /dev entries driver
> [    5.835640] meson_wdt c1109900.watchdog: Watchdog enabled (timeout=8 sec,
> nowayout=0)
> [    5.839928] sdhci: Secure Digital Host Controller Interface driver
> [    5.844316] sdhci: Copyright(c) Pierre Ossman
> [    5.849477] Synopsys Designware Multimedia Card Interface Driver
> [    5.856562] sdhci-pltfm: SDHCI platform and OF driver helper
> [    5.861442] of_pwm_get(): PWM chip not found
> [    5.864538] leds_pwm pwmleds: unable to request PWM for m8s:blue:power:
> -517
> [    5.871728] ledtrig-cpu: registered to indicate activity on CPUs
> [    5.877766] usbcore: registered new interface driver usbhid
> [    5.883048] usbhid: USB HID core driver
> [    5.944209] NET: Registered protocol family 10
> [    5.944923] Segment Routing with IPv6
> [    5.946713] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
> [    5.953100] NET: Registered protocol family 17
> [    5.956991] can: controller area network core (rev 20120528 abi 9)
> [    5.963199] NET: Registered protocol family 29
> [    5.967561] can: raw protocol (rev 20120528)
> [    5.971808] can: broadcast manager protocol (rev 20161123 t)
> [    5.977457] can: netlink gateway (rev 20130117) max_hops=1
> [    5.983198] Key type dns_resolver registered
> [    5.987424] ThumbEE CPU extension supported.
> [    5.991403] Registering SWP/SWPB emulation handler
> [    5.997855] Btrfs loaded, crc32c=crc32c-generic
> [    6.005513] dwc2 c9040000.usb: c9040000.usb supply vusb_d not found,
> using dummy regulator
> [    6.008952] dwc2 c9040000.usb: c9040000.usb supply vusb_a not found,
> using dummy regulator
> [    6.018320] phy phy-c1108800.phy.0: USB ID detect failed!
> [    6.022538] phy phy-c1108800.phy.0: phy poweron failed --> -22
> [    6.028450] dwc2: probe of c9040000.usb failed with error -22
I assume your device has an internal USB hub? this probably has to be
turned on before the controller starts working

> [    6.035485] dwc2 c90c0000.usb: c90c0000.usb supply vusb_d not found,
> using dummy regulator
> [    6.042337] dwc2 c90c0000.usb: c90c0000.usb supply vusb_a not found,
> using dummy regulator
> [    6.182662] dwc2 c90c0000.usb: DWC OTG Controller
> [    6.182732] dwc2 c90c0000.usb: new USB bus registered, assigned bus
> number 1
> [    6.188786] dwc2 c90c0000.usb: irq 23, io mem 0xc90c0000
> [    6.194739] hub 1-0:1.0: USB hub found
> [    6.197804] hub 1-0:1.0: 1 port detected
> [    6.206952] of_pwm_get(): PWM chip not found
this sounds innocent at first but actually it's crucial for MMC (at
least in the current M8S configuration). PWM_E is used to generate the
32.768 kHz clock for the wifi chip. so without CONFIG_PWM_MESON the
pwm_ef node won't get probed, meaning that a dependency of the mmc
controller is missing.
I'll fix that as well next weekend (it also has to be enabled in
multi_v7_defconfig)

> [    6.207005] leds_pwm pwmleds: unable to request PWM for m8s:blue:power:
> -517
> [    6.213401] hctosys: unable to open rtc device (rtc0)
> [    6.218262] VCC3V3: disabling
> [    6.222866] Freeing unused kernel memory: 2048K
> [    6.622590] usb 1-1: new high-speed USB device number 2 using dwc2
> [    6.832594] usb 1-1: device descriptor read/64, error -32
> [    7.162580] usb 1-1: device descriptor read/64, error -32
> [    7.492542] usb 1-1: new high-speed USB device number 3 using dwc2
> [    7.702535] usb 1-1: device descriptor read/64, error -32
> [    8.032534] usb 1-1: device descriptor read/64, error -32
> [    8.362547] usb 1-1: new high-speed USB device number 4 using dwc2
> [    8.802534] usb 1-1: device not accepting address 4, error -32
> [    9.012535] usb 1-1: new high-speed USB device number 5 using dwc2
> [    9.452534] usb 1-1: device not accepting address 5, error -32
> [    9.452767] usb usb1-port1: unable to enumerate USB device
this looks suspicious, do you have anything connected to that port?
I've seen that when connecting a 2.5" HDD when the PSU doesn't have
enough power to spin up the HDD as well.


Martin

  reply	other threads:[~2017-05-07 21:08 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  6:37 Testing Oleg
2017-05-07 16:38 ` Testing Martin Blumenstingl
2017-05-07 17:36   ` Testing Oleg
2017-05-07 18:05     ` Testing Martin Blumenstingl
2017-05-07 18:55       ` Testing Oleg
     [not found]       ` <e7eb7d12-8fa8-5507-5d7b-53ef9ce3e300@yandex.ru>
2017-05-07 18:59         ` Testing Martin Blumenstingl
2017-05-07 19:09           ` Testing Oleg
2017-05-07 20:22             ` Testing Martin Blumenstingl
2017-05-07 20:44               ` Testing Oleg
2017-05-07 20:46                 ` Testing Martin Blumenstingl
2017-05-07 20:53                   ` Testing Oleg
2017-05-07 20:57                   ` Testing Oleg
2017-05-07 21:08                     ` Martin Blumenstingl [this message]
2017-05-07 21:23                       ` Testing Oleg
2017-05-07 21:30                         ` Testing Martin Blumenstingl
2017-05-08  9:42                           ` Testing Oleg
2017-05-08 11:47                             ` S805/S812 Device Tree upstreaming (was: Testing.) Andreas Färber
2017-05-12  7:03   ` Testing Oleg
2017-05-25 18:35   ` Testing Tobias Baumann
2017-05-27 14:15     ` Testing Martin Blumenstingl
2017-05-27 14:57       ` Testing raptorsds
2017-05-27 16:08         ` Testing Martin Blumenstingl
2017-05-27 18:06           ` Testing raptorsds
2017-05-27 18:18             ` Testing Martin Blumenstingl
  -- strict thread matches above, loose matches on Subject: below --
2023-09-21 17:44 Testing Turritopsis Dohrnii Teo En Ming
2019-05-27 13:42 Testing Turritopsis Dohrnii Teo En Ming
2018-12-14 19:23 Testing Tyler Baker
2015-12-01 23:50 Testing Cyril Bur
2015-12-03  4:58 ` Testing Stewart Smith
2015-03-15  8:57 Testing Teo En Ming (Zhang Enming)
2013-09-18 16:48 Testing Juan Casse
2013-09-18 16:45 Testing Juan Casse
2013-08-28 21:41 Testing David.Darrington
2012-12-27 18:38 testing Qin, Xiaohong
2012-04-18 14:11 testing simple w8
2011-03-26  3:16 Testing Martin Owens
2011-03-27  3:37 ` Testing Didier Spaier
     [not found]   ` <4D8EB10D.9060305-GqzDj6/B2j8@public.gmane.org>
2011-03-27 14:54     ` Testing Martin Owens
2011-03-27 15:49       ` Testing Didier Spaier
2011-04-01  6:54 ` Testing Christopher James Halse Rogers
2009-09-26 21:11 Testing Hal Rosenstock
2008-12-18 16:02 testing Bill O'Donnell
2007-09-28 14:11 Testing Richard Geddes
2003-03-16 11:54 testing Silvester Verdonskchot
2003-03-06 14:14 testing berthiaume_wayne
2003-03-06  9:16 testing Anders Widman
2003-03-06  9:14 testing Anders Widman
2003-02-13 21:43 testing Alan Powell
2003-02-13 21:28 testing Alan Powell
2002-11-19 11:58 testing Wasim Bashir
2002-01-15 17:30 Testing Daryl Woods
2002-01-15 17:30 ` Testing Daryl Woods
2001-11-30  9:58 Testing Jacky Costen
2001-11-24  4:07 testing Patrick McFarland
1999-06-06 17:47 testing Benjamin LaHaise
1999-03-12  1:36 testing David Miller
1999-03-12  1:42 ` testing David Miller
1998-03-19  0:23 testing Jamie Heller-Evans

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=CAFBinCAktR94_3diH1NqAL4uXbLkL_cThaj7WtXgODe0LMQ88A@mail.gmail.com \
    --to=martin.blumenstingl@googlemail.com \
    --cc=linus-amlogic@lists.infradead.org \
    /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.