public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Tom Waldron <tom@baremetal.dev>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/1] wifi: mt76: mt7921: Add a new VID/PID 0b48/7922 for MT7922
Date: Wed, 1 Nov 2023 16:35:03 +0100	[thread overview]
Message-ID: <ZUJwJ+bimXFVcXps@lore-desk> (raw)
In-Reply-To: <CANjHDnBkCW_zQxyCcKcyrZOYnnLNVKT1Z2AJr6x6DT55UZ+A7Q@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1669 bytes --]

> PCI VID 0x0b48 doesn't appear to be listed anywhere I can find, though
> a website named pcilookup.com suggests it belongs to TechnoTrend AG. I
> think it's more likely to be part of AMD RZ600 series - rebranded
> mediatek devices. Not sure how any of this might be verified.

I have just found it here: include/linux/pci_ids.h
but I am not sure if it is related. Anyway:

Acked-by: Lorenzo Bianconi <lorenzo@kernel.org>

> 
> On Wed, 1 Nov 2023 at 15:00, Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> >
> > > Add VID/PID 0b48/7922 for MediaTek MT7922 wifi chip.
> > > Change tested on Redmi Book Pro 15 2023 (Fedora 38).
> > >
> > > Signed-off-by: Tom Waldron <tom@baremetal.dev>
> > > ---
> > >  drivers/net/wireless/mediatek/mt76/mt7921/pci.c | 2 ++
> > >  1 file changed, 2 insertions(+)
> > >
> > > diff --git a/drivers/net/wireless/mediatek/mt76/mt7921/pci.c b/drivers/net/wireless/mediatek/mt76/mt7921/pci.c
> > > index 3dda84a93..ba805cb02 100644
> > > --- a/drivers/net/wireless/mediatek/mt76/mt7921/pci.c
> > > +++ b/drivers/net/wireless/mediatek/mt76/mt7921/pci.c
> > > @@ -21,6 +21,8 @@ static const struct pci_device_id mt7921_pci_device_table[] = {
> > >               .driver_data = (kernel_ulong_t)MT7921_FIRMWARE_WM },
> > >       { PCI_DEVICE(PCI_VENDOR_ID_MEDIATEK, 0x0616),
> > >               .driver_data = (kernel_ulong_t)MT7922_FIRMWARE_WM },
> > > +     { PCI_DEVICE(0x0b48, 0x7922),
> > > +             .driver_data = (kernel_ulong_t)MT7922_FIRMWARE_WM },
> >
> > is PCI VID 0x0b48 PCI_VENDOR_ID_ITTIM?
> >
> > Regards,
> > Lorenzo
> >
> > >       { },
> > >  };
> > >
> > > --
> > > 2.41.0
> > >

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-11-01 15:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  9:55 [PATCH 1/1] wifi: mt76: mt7921: Add a new VID/PID 0b48/7922 for MT7922 Tom Waldron
2023-11-01 13:19 ` Kalle Valo
2023-11-01 14:03   ` Tom Waldron
2023-11-01 15:00 ` Lorenzo Bianconi
2023-11-01 15:26   ` Tom Waldron
2023-11-01 15:35     ` Lorenzo Bianconi [this message]
2023-11-01 15:48       ` Tom Waldron

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=ZUJwJ+bimXFVcXps@lore-desk \
    --to=lorenzo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tom@baremetal.dev \
    /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