mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <>
To: "Uwe Kleine-König" <>
	Marco Felsch <>,
	Ahmad Fatoum <>
Subject: Re: [PATCH v2] usb: i.MX: warn if vbus regulator isn't available
Date: Tue, 25 May 2021 07:24:59 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Mar 05, 2021 at 10:00:01AM +0100, Uwe Kleine-König wrote:
> Instead of just ignoring errors related to getting the vbus regulator
> yield at least a warning message. This would have saved me some
> debugging time when trying to understand why USB doesn't work without
> the right regulator driver enabled.
> Note that machines that don't define a regulator in their device tree
> don't issue this warning as regulator_get() returns the dummy regulator
> in this case.

Note that this warning appears on machines that do define a regulator in
their device tree (derived from the kernel upstream dts), but do not
actually need it as the regulator was enabled by board code.
Arguably that's the problem of these boards and we'll have to look there
how we can quiesce the warning. The obvious solution is to implement the
missing driver, but we could also add some
add_dummy_regulator_for_this_node() function to tell the regulator core
that we don't need a specific regulator.

First let's see if somebody is annoyed by this message, so applied,


Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       |  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

barebox mailing list

      parent reply	other threads:[~2021-05-25  5:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05  9:00 Uwe Kleine-König
2021-05-22 14:22 ` Uwe Kleine-König
2021-05-25  5:24 ` Sascha Hauer [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox