From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Mark Brown <broonie@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
lgirdwood@gmail.com, wcheng@codeaurora.org,
linux-arm-msm@vger.kernel.org, dmitry.baryshkov@linaro.org
Subject: Re: [PATCH] regulator: Fix current limit for QCOM PMIC VBUS
Date: Mon, 26 Apr 2021 13:03:49 +0100 [thread overview]
Message-ID: <c7f797da-f5b9-5c95-4664-efadf4e7b86b@linaro.org> (raw)
In-Reply-To: <20210426115548.GA4590@sirena.org.uk>
On 26/04/2021 12:55, Mark Brown wrote:
> It may be out of spec for USB C (though I can see someone choosing a
> limit of 2A to give headroom on a specified 1.5A limit, AIUI the limits
> in USB are on the side drawing the current and there's no requirement
> for the supplier to enforce the limit) but that doesn't mean that the
> hardware has been designed in a way that makes it safe to just increase
> the limit.
I get your point, however, the downstream kernel i.e. the kernel that
ships with the n-million qcom devices sets the limit to 3 amps.
To my knowledge all qcom downstream hardware/software implementations
based on the pm8150b set the 3amp limit so, what we are doing here is
closing the gap in upstream.
---
bod
next prev parent reply other threads:[~2021-04-26 12:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 16:06 [PATCH] regulator: Fix current limit for QCOM PMIC VBUS Bryan O'Donoghue
2021-04-23 16:32 ` Mark Brown
2021-04-23 20:24 ` Bryan O'Donoghue
2021-04-23 20:38 ` Bryan O'Donoghue
2021-04-26 11:55 ` Mark Brown
2021-04-26 12:03 ` Bryan O'Donoghue [this message]
2021-04-26 12:12 ` Mark Brown
2021-04-26 12:50 ` Bryan O'Donoghue
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=c7f797da-f5b9-5c95-4664-efadf4e7b86b@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=wcheng@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).