linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joakim Tjernlund <joakim.tjernlund@infinera.com>
Cc: linux-bluetooth@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] Bluetooth: btrtl: rename USB fw for RTL8761
Date: Fri, 28 May 2021 17:40:05 +0200	[thread overview]
Message-ID: <YLEO1UzRoZ6aj8UT@kroah.com> (raw)
In-Reply-To: <20210528152645.25577-1-joakim.tjernlund@infinera.com>

On Fri, May 28, 2021 at 05:26:44PM +0200, Joakim Tjernlund wrote:
> From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
> 
> According Realteks own BT drivers firmware RTL8761B is for UART
> and RTL8761BU is for USB.
> 
> Change existing 8761B to UART and add an 8761BU entry for USB
> 
> Signed-off-by: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
> ---
>  drivers/bluetooth/btrtl.c | 9 ++++++++-
>  1 file changed, 8 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/bluetooth/btrtl.c b/drivers/bluetooth/btrtl.c
> index e7fe5fb22753..ccef8b2cfee2 100644
> --- a/drivers/bluetooth/btrtl.c
> +++ b/drivers/bluetooth/btrtl.c
> @@ -132,12 +132,19 @@ static const struct id_table ic_id_table[] = {
>  	  .cfg_name = "rtl_bt/rtl8761a_config" },
>  
>  	/* 8761B */
> -	{ IC_INFO(RTL_ROM_LMP_8761A, 0xb, 0xa, HCI_USB),
> +	{ IC_INFO(RTL_ROM_LMP_8761A, 0xb, 0xa, HCI_UART),
>  	  .config_needed = false,
>  	  .has_rom_version = true,
>  	  .fw_name  = "rtl_bt/rtl8761b_fw.bin",
>  	  .cfg_name = "rtl_bt/rtl8761b_config" },
>  
> +	/* 8761BU */
> +	{ IC_INFO(RTL_ROM_LMP_8761A, 0xb, 0xa, HCI_USB),
> +	  .config_needed = false,
> +	  .has_rom_version = true,
> +	  .fw_name  = "rtl_bt/rtl8761bu_fw.bin",
> +	  .cfg_name = "rtl_bt/rtl8761bu_config" },
> +
>  	/* 8822C with UART interface */
>  	{ IC_INFO(RTL_ROM_LMP_8822B, 0xc, 0xa, HCI_UART),
>  	  .config_needed = true,
> -- 
> 2.31.1
> 

<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.

</formletter>

  parent reply	other threads:[~2021-05-28 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 15:26 [PATCH 1/2] Bluetooth: btrtl: rename USB fw for RTL8761 Joakim Tjernlund
2021-05-28 15:26 ` [PATCH 2/2] Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device Joakim Tjernlund
2021-05-28 15:40   ` Greg KH
2021-06-02 19:49   ` Marcel Holtmann
2021-05-28 15:40 ` Greg KH [this message]
2021-05-28 16:31 ` [1/2] Bluetooth: btrtl: rename USB fw for RTL8761 bluez.test.bot
2021-06-02 19:50 ` [PATCH 1/2] " Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2021-05-28 16:46 Joakim Tjernlund
2021-06-02 15:34 ` Joakim Tjernlund

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=YLEO1UzRoZ6aj8UT@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=joakim.tjernlund@infinera.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=stable@vger.kernel.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).