linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org,
	lkml <linux-kernel@vger.kernel.org>,
	MSM <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 0/4] Bluetooth: hci_qca: Regulator usage cleanup
Date: Fri, 18 Oct 2019 08:52:43 -0600	[thread overview]
Message-ID: <CAOCk7NpHVFBiWTh0Wk2fPAJDQxg8e36vGSP5mXRUUuOf8a57CA@mail.gmail.com> (raw)
In-Reply-To: <739222E4-F173-42A9-8D67-1BD8FEE227EC@holtmann.org>

On Fri, Oct 18, 2019 at 1:59 AM Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Bjorn,
>
> > Clean up the regulator usage in hci_qca and in particular don't
> > regulator_set_voltage() for fixed voltages. It cleans up the driver, but more
> > important it makes bluetooth work on my Lenovo Yoga C630, where the regulator
> > for vddch0 is defined with a voltage range that doesn't overlap the values in
> > the driver.
> >
> > Bjorn Andersson (4):
> >  Bluetooth: hci_qca: Update regulator_set_load() usage
> >  Bluetooth: hci_qca: Don't vote for specific voltage
> >  Bluetooth: hci_qca: Use regulator bulk enable/disable
> >  Bluetooth: hci_qca: Split qca_power_setup()
> >
> > drivers/bluetooth/hci_qca.c | 135 +++++++++++++++---------------------
> > 1 file changed, 55 insertions(+), 80 deletions(-)
>
> all 4 patches have been applied to bluetooth-next tree.

I know this is already applied, but I just wanted to follow up and indicate:

Tested-by: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Reviewed-by: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>

Thanks for the cleanups Bjorn.

  reply	other threads:[~2019-10-18 14:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-18  5:24 [PATCH 0/4] Bluetooth: hci_qca: Regulator usage cleanup Bjorn Andersson
2019-10-18  5:24 ` [PATCH 1/4] Bluetooth: hci_qca: Update regulator_set_load() usage Bjorn Andersson
2019-10-18 11:18   ` Harish Bandi
2019-10-18  5:24 ` [PATCH 2/4] Bluetooth: hci_qca: Don't vote for specific voltage Bjorn Andersson
2019-10-18 11:18   ` Harish Bandi
2019-10-18 18:22   ` Matthias Kaehlcke
2019-10-21  6:37     ` Harish Bandi
2019-10-22  6:05       ` Balakrishna Godavarthi
2019-10-22 17:15         ` Matthias Kaehlcke
2019-10-30  6:18           ` Balakrishna Godavarthi
2019-10-18  5:24 ` [PATCH 3/4] Bluetooth: hci_qca: Use regulator bulk enable/disable Bjorn Andersson
2019-10-18 11:18   ` Harish Bandi
2019-10-18  5:24 ` [PATCH 4/4] Bluetooth: hci_qca: Split qca_power_setup() Bjorn Andersson
2019-10-18 11:19   ` Harish Bandi
2019-10-18  7:59 ` [PATCH 0/4] Bluetooth: hci_qca: Regulator usage cleanup Marcel Holtmann
2019-10-18 14:52   ` Jeffrey Hugo [this message]
2019-10-18 11:17 ` Harish Bandi

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=CAOCk7NpHVFBiWTh0Wk2fPAJDQxg8e36vGSP5mXRUUuOf8a57CA@mail.gmail.com \
    --to=jeffrey.l.hugo@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.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).