linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Forest Bond <forest@alittletooquiet.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] staging: vt6655: Remove unused 5GHz support
Date: Sat, 5 Mar 2022 22:31:56 +0100	[thread overview]
Message-ID: <cover.1646512837.git.philipp.g.hortmann@gmail.com> (raw)

Hardware of vt6655 (PCI) and vt6656 (USB) do only support 2.4GHz band and not 5GHz band.
Both drivers do allow only one vendor id and device id.
So no other devices are covered by those drivers.
Because of this the following priv->byRFType cannot occure:
RF_AIROHA7230
RF_UW2452

Tested with vt6655 on mini PCI Module
Module used for testing is using byRFType: RF_AIROHA (2.4GHz only)
In order to combine vt665x infrastructure it is important
that vt6656 is also not using this code.
vt6656 on mini PCIe card (connected over USB)
is using byRFType: RF_VT3226D0 (2.4GHz only)
vt6656 as USB Plugin Module
is using byRFType: RF_AL2230S (2.4GHz only)

Transferred this patches over vt6655 on mini PCI Module

Checkpatch errors occured because indention was changed. (3x times CamelCase) 
I did not fix that in this patch series as it would make the patch more complicated.



Philipp Hortmann (4):
  staging: vt6655: Remove unused byRFType in channel.c
  staging: vt6655: Remove unused byRFType in baseband.c
  staging: vt6655: Remove unused byRFType in rf.c
  staging: vt6655: Remove unused byRFType in card.c

 drivers/staging/vt6655/baseband.c |  80 ------
 drivers/staging/vt6655/card.c     |  56 +----
 drivers/staging/vt6655/channel.c  |  85 +------
 drivers/staging/vt6655/rf.c       | 404 +-----------------------------
 4 files changed, 3 insertions(+), 622 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-03-05 21:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-05 21:31 Philipp Hortmann [this message]
2022-03-05 21:32 ` [PATCH 1/4] staging: vt6655: Remove unused byRFType in channel.c Philipp Hortmann
2022-03-05 21:32 ` [PATCH 2/4] staging: vt6655: Remove unused byRFType in baseband.c Philipp Hortmann
2022-03-05 21:32 ` [PATCH 3/4] staging: vt6655: Remove unused byRFType in rf.c Philipp Hortmann
2022-03-05 21:32 ` [PATCH 4/4] staging: vt6655: Remove unused byRFType in card.c Philipp Hortmann

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=cover.1646512837.git.philipp.g.hortmann@gmail.com \
    --to=philipp.g.hortmann@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.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;
as well as URLs for NNTP newsgroup(s).