Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Lu (陸稚泓)" <Chris.Lu@mediatek.com>
To: "pmenzel@molgen.mpg.de" <pmenzel@molgen.mpg.de>
Cc: "marcel@holtmann.org" <marcel@holtmann.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
	"Steve Lee (李視誠)" <steve.lee@mediatek.com>,
	"Aaron Hou (侯俊仰)" <Aaron.Hou@mediatek.com>,
	"Hao Qin (秦浩)" <Hao.Qin@mediatek.com>,
	"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>
Subject: Re: [PATCH] Bluetooth: btmtk: add quirk to support HCI_QUIRK_SIMULTANEOUS_DISCOVERY
Date: Mon, 16 Dec 2024 02:44:15 +0000	[thread overview]
Message-ID: <aa8b24291fd5c88f65e6e196796c16de6102b27a.camel@mediatek.com> (raw)
In-Reply-To: <6bbe0989-babd-4a99-85ad-fdeea47deb09@molgen.mpg.de>

Hi Paul,

Thanks for your input,

On Fri, 2024-12-13 at 10:46 +0100, Paul Menzel wrote:
> External email : Please do not click links or open attachments until
> you have verified the sender or the content.
> 
> 
> Dear Chris,
> 
> 
> Thank you for your patch.
> 
> 
> Am 13.12.24 um 10:41 schrieb Chris Lu:
> > Add quirk to support HCI_QUIRK_SIMULTANEOUS_DISCOVERY feature for
> > MT79xx
> > series chipset.
> 
> It’d be great if you elaborated. What is the problem. Why is a quirk
> needed? Is a firmware update going to fix it?

This quirk is related to do BR/EDR inquiry and LE scan simultaneously.
More detailed was described in hci.h.

Due to requirement from customer and other chip vendors also enable
HCI_QUIRK_SIMULTANEOUS_DISCOVERY, MediaTek upload this patch to enable
the feature as well. There is no need to update firmware.

> 
> > Signed-off-by: Chris Lu <chris.lu@mediatek.com>
> > ---
> >   drivers/bluetooth/btmtk.c | 3 +++
> >   1 file changed, 3 insertions(+)
> > 
> > diff --git a/drivers/bluetooth/btmtk.c b/drivers/bluetooth/btmtk.c
> > index 8a3f7c3fcfec..562d6ecf0b71 100644
> > --- a/drivers/bluetooth/btmtk.c
> > +++ b/drivers/bluetooth/btmtk.c
> > @@ -1367,6 +1367,9 @@ int btmtk_usb_setup(struct hci_dev *hdev)
> >                       return err;
> >               }
> > 
> > +             /* Apply common HCI quirks for MediaTek chipset */
> > +             set_bit(HCI_QUIRK_SIMULTANEOUS_DISCOVERY, &hdev-
> > >quirks);
> > +
> 
> The commit message only talks about MT79xx series chipset. The
> comment
> talks about all MediaTek chipsets.
I'll modify commit message to avoid ambiguity and upload another
version.

Thanks a lot,
Chris Lu
> 
> >               hci_set_msft_opcode(hdev, 0xFD30);
> >               hci_set_aosp_capable(hdev);
> 
> 
> Kind regards,
> 
> Paul

      reply	other threads:[~2024-12-16  2:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  9:41 [PATCH] Bluetooth: btmtk: add quirk to support HCI_QUIRK_SIMULTANEOUS_DISCOVERY Chris Lu
2024-12-13  9:46 ` Paul Menzel
2024-12-16  2:44   ` Chris Lu (陸稚泓) [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:
  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=aa8b24291fd5c88f65e6e196796c16de6102b27a.camel@mediatek.com \
    --to=chris.lu@mediatek.com \
    --cc=Aaron.Hou@mediatek.com \
    --cc=Hao.Qin@mediatek.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=steve.lee@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox