From: Anand Moon <linux.amoon@gmail.com>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Mark Brown <broonie@debian.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
823552@bugs.debian.org, balbi@kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] Re: Endless "supply vcc not found, using dummy regulator"
Date: Wed, 25 May 2016 17:46:51 +0530 [thread overview]
Message-ID: <CANAwSgSS=LPUJ4HXQ_D4tsMYXP=1qG_f_jn-G9xwN6AOKy6QMw@mail.gmail.com> (raw)
In-Reply-To: <20160524192424.GA11690@sesse.net>
Hi Steinar,
On 25 May 2016 at 00:54, Steinar H. Gunderson <sgunderson@bigfoot.com> wrote:
> On Tue, May 24, 2016 at 05:53:34PM +0200, Krzysztof Kozlowski wrote:
>> exynos->clk = devm_clk_get(dev, "usbdrd30");
>> if (IS_ERR(exynos->clk)) {
>> + // On each error path since here we need to
>> + // revert work done by dwc3_exynos_register_phys()
>> dev_err(dev, "couldn't get clock\n");
>> return -EINVAL;
>> }
>> clk_prepare_enable(exynos->clk);
>
> OK, so I took Mark's advice and moved the phy instantiation towards the end
> of the function (after the regulators have successfully come up). It reduced
> the number of probes, even with the original initramfs, dramatically, so
> it seems to work quite well. It also reduces the text for each deferred probe
> by a lot, since we no longer have the dummy regulator message for each one
> (only the message about “no suspend clk specified” is left). Finally, this
> arrangement reduced the need for extra error handling to a minimum.
>
> Cc-ing Felipe and and linux-usb@, and adding the patch as a reply to this
> message.
>
> /* Steinar */
> --
> Homepage: https://www.sesse.net/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Actually their are some missing patches to tune the usb3 phy.
https://lkml.org/lkml/2014/10/31/266
Best Regards
-Anand Moon
next prev parent reply other threads:[~2016-05-25 12:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160515173900.GC21194@sesse.net>
2016-05-21 14:43 ` Endless "supply vcc not found, using dummy regulator" Steinar H. Gunderson
2016-05-23 13:47 ` Steinar H. Gunderson
2016-05-23 14:40 ` Steinar H. Gunderson
2016-05-23 16:24 ` Mark Brown
2016-05-23 17:06 ` Steinar H. Gunderson
2016-05-23 17:46 ` Steinar H. Gunderson
2016-05-23 18:56 ` Mark Brown
2016-05-23 18:44 ` Mark Brown
2016-05-24 15:06 ` Krzysztof Kozlowski
2016-05-24 15:26 ` Steinar H. Gunderson
2016-05-24 15:45 ` Mark Brown
2016-05-24 15:53 ` Krzysztof Kozlowski
2016-05-24 16:44 ` Steinar H. Gunderson
[not found] ` <574478FE.4070800-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-05-24 19:24 ` [PATCH] " Steinar H. Gunderson
2016-05-24 18:13 ` [PATCH v2] dwc3-exynos: Fix deferred probing storm Steinar H. Gunderson
2016-05-24 18:13 ` [PATCH] " Steinar H. Gunderson
2016-05-25 7:54 ` Krzysztof Kozlowski
2016-05-27 9:53 ` Vivek Gautam
2016-05-27 11:46 ` Steinar H. Gunderson
2016-05-27 13:13 ` Krzysztof Kozlowski
[not found] ` <5748480D.8000501-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-05-27 13:12 ` Felipe Balbi
[not found] ` <87bn3rprtw.fsf-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2016-05-27 13:25 ` Steinar H. Gunderson
2016-05-27 13:26 ` Felipe Balbi
2016-05-30 17:46 ` Steinar H. Gunderson
2016-05-25 12:16 ` Anand Moon [this message]
2016-05-25 17:52 ` [PATCH] Re: Endless "supply vcc not found, using dummy regulator" Steinar H. Gunderson
2016-05-26 12:57 ` Steinar H. Gunderson
[not found] ` <20160526125757.GA23797-gdzBep0Ce9heoWH0uzbU5w@public.gmane.org>
2016-05-27 9:32 ` Vivek Gautam
[not found] ` <CAFp+6iE_QW0BDO-Z1Ce5zrUJiToWD_8UtnCFnfKLeaYyys7U8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-27 9:39 ` Steinar H. Gunderson
[not found] ` <20160527093919.GA34987-gdzBep0Ce9heoWH0uzbU5w@public.gmane.org>
2016-05-27 9:43 ` Vivek Gautam
2016-05-24 15:39 ` Mark Brown
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='CANAwSgSS=LPUJ4HXQ_D4tsMYXP=1qG_f_jn-G9xwN6AOKy6QMw@mail.gmail.com' \
--to=linux.amoon@gmail.com \
--cc=823552@bugs.debian.org \
--cc=balbi@kernel.org \
--cc=broonie@debian.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sgunderson@bigfoot.com \
/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.