From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Sean Wang <sean.wang@kernel.org>
Cc: "Sean Wang (王志亘)" <sean.wang@mediatek.com>,
"Felix Fietkau" <nbd@nbd.name>,
lorenzo.bianconi@redhat.com, Soul.Huang@mediatek.com,
YN.Chen@mediatek.com, Leon.Yen@mediatek.com,
Eric-SY.Chang@mediatek.com, "Deren Wu" <Deren.Wu@mediatek.com>,
km.lin@mediatek.com, jenhao.yang@mediatek.com,
robin.chiu@mediatek.com, Eddie.Chen@mediatek.com,
ch.yeh@mediatek.com, posh.sun@mediatek.com,
ted.huang@mediatek.com, Stella.Chang@mediatek.com,
Tom.Chou@mediatek.com, steve.lee@mediatek.com, jsiuda@google.com,
frankgor@google.com, kuabhs@google.com, druth@google.com,
abhishekpandit@google.com, shawnku@google.com,
linux-wireless@vger.kernel.org,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 8/9] wifi: mt76: mt7921: introduce remain_on_channel support
Date: Thu, 18 Aug 2022 09:39:22 +0200 [thread overview]
Message-ID: <Yv3sqvhXnGiOpKkE@lore-desk> (raw)
In-Reply-To: <CAGp9LzrvVQOrUNPR8aguUTgWo1wZFMR2Y3kdTk8WqxmG=B8--w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 6514 bytes --]
> Hi Lorenzo,
>
> On Wed, Aug 17, 2022 at 12:18 AM Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> >
> > > From: Sean Wang <sean.wang@mediatek.com>
> > >
> > > Introduce remain_on_channel support. Additionally, we add
> > > mt7921_check_offload_capability to disable .remain_on_channel and
> > > .cancel_remain_on_channel and related configuration because those
> > > operations would rely on the fundamental MCU commands that will be only
> > > supported with newer firmware.
> > >
> > > Co-developed-by: Deren Wu <deren.wu@mediatek.com>
> > > Signed-off-by: Deren Wu <deren.wu@mediatek.com>
> > > Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> > > ---
> > > .../net/wireless/mediatek/mt76/mt7921/init.c | 36 ++++++
> > > .../net/wireless/mediatek/mt76/mt7921/main.c | 112 ++++++++++++++++++
> > > .../net/wireless/mediatek/mt76/mt7921/mcu.c | 24 ++++
> > > .../wireless/mediatek/mt76/mt7921/mt7921.h | 34 ++++++
> > > .../net/wireless/mediatek/mt76/mt7921/pci.c | 13 +-
> > > .../net/wireless/mediatek/mt76/mt7921/sdio.c | 11 +-
> > > .../net/wireless/mediatek/mt76/mt7921/usb.c | 1 +
> > > 7 files changed, 225 insertions(+), 6 deletions(-)
> > >
> > > diff --git a/drivers/net/wireless/mediatek/mt76/mt7921/init.c b/drivers/net/wireless/mediatek/mt76/mt7921/init.c
> > > index cd960e23770f..1b7a18d42f5b 100644
> > > --- a/drivers/net/wireless/mediatek/mt76/mt7921/init.c
> > > +++ b/drivers/net/wireless/mediatek/mt76/mt7921/init.c
> > > @@ -44,6 +44,35 @@ mt7921_regd_notifier(struct wiphy *wiphy,
> > > mt7921_mutex_release(dev);
> > > }
> > >
> > > +static int mt7921_check_offload_capability(struct mt7921_dev *dev)
> > > +{
> > > + struct ieee80211_hw *hw = mt76_hw(dev);
> > > + int year, mon, day, hour, min, sec;
> > > + struct wiphy *wiphy = hw->wiphy;
> > > + bool fw_can_roc = false;
> > > + int ret;
> > > +
> > > + ret = sscanf(dev->mt76.hw->wiphy->fw_version + 11, "%4d%2d%2d%2d%2d%2d",
> > > + &year, &mon, &day, &hour, &min, &sec);
> >
> > does the fw have a differnt base version with respect to the previous ones?
> > checking the date is a bit ugly.
>
> I admitted that way was a bit ugly, but I have investigated for a
> while, and that is the only way we can use to distinguish the version
> in current mt7921 firmware.
the fw seems pretty new (2022/7/15), is it already available in linux-firmware
git tree? If not I guess you can increment fw version in a more evident way.
For the future please remember to do it for major fw changes.
>
> >
> > > + if (ret != 6)
> > > + goto out;
> > > +
> > > + /* Old firmware cannot support remained on channel and channel
> > > + * context management.
> > > + */
> > > + fw_can_roc = mktime64(year, mon, day, hour, min, sec) >=
> > > + mktime64(2022, 7, 15, 12, 1, 1);
> > > +out:
> > > + if (!fw_can_roc) {
> > > + dev->ops->remain_on_channel = NULL;
> > > + dev->ops->cancel_remain_on_channel = NULL;
> > > +
> > > + wiphy->flags &= ~WIPHY_FLAG_HAS_REMAIN_ON_CHANNEL;
> > > + }
> > > +
> > > + return 0;
> > > +}
> > > +
>
> <snip>
>
> > > - mdev = mt76_alloc_device(&pdev->dev, sizeof(*dev), &mt7921_ops,
> > > - &drv_ops);
> > > + ops = devm_kmemdup(&pdev->dev, &mt7921_ops, sizeof(mt7921_ops),
> > > + GFP_KERNEL);
> >
> > why do we need to copy mt7921_ops?
> >
>
> As the old fw cannot support the roc and chanctx and considering
> backward compatibility, I need to copy the mt7921_ops here and
> disable related operations for old fw before registering the hw to mac80211.
ack, right.
Regards,
Lorenzo
>
> Sean
>
> > Regards,
> > Lorenzo
> >
> > > + if (!ops) {
> > > + ret = -ENOMEM;
> > > + goto err_free_pci_vec;
> > > + }
> > > +
> > > + mdev = mt76_alloc_device(&pdev->dev, sizeof(*dev), ops, &drv_ops);
> > > if (!mdev) {
> > > ret = -ENOMEM;
> > > goto err_free_pci_vec;
> > > @@ -286,7 +293,7 @@ static int mt7921_pci_probe(struct pci_dev *pdev,
> > >
> > > dev = container_of(mdev, struct mt7921_dev, mt76);
> > > dev->hif_ops = &mt7921_pcie_ops;
> > > -
> > > + dev->ops = ops;
> > > mt76_mmio_init(&dev->mt76, pcim_iomap_table(pdev)[0]);
> > > tasklet_init(&dev->irq_tasklet, mt7921_irq_tasklet, (unsigned long)dev);
> > >
> > > diff --git a/drivers/net/wireless/mediatek/mt76/mt7921/sdio.c b/drivers/net/wireless/mediatek/mt76/mt7921/sdio.c
> > > index 487acd6e2be8..6d27875f41b8 100644
> > > --- a/drivers/net/wireless/mediatek/mt76/mt7921/sdio.c
> > > +++ b/drivers/net/wireless/mediatek/mt76/mt7921/sdio.c
> > > @@ -120,18 +120,23 @@ static int mt7921s_probe(struct sdio_func *func,
> > > .fw_own = mt7921s_mcu_fw_pmctrl,
> > > };
> > >
> > > + struct ieee80211_ops *ops;
> > > struct mt7921_dev *dev;
> > > struct mt76_dev *mdev;
> > > int ret;
> > >
> > > - mdev = mt76_alloc_device(&func->dev, sizeof(*dev), &mt7921_ops,
> > > - &drv_ops);
> > > + ops = devm_kmemdup(&func->dev, &mt7921_ops, sizeof(mt7921_ops),
> > > + GFP_KERNEL);
> > > + if (!ops)
> > > + return -ENOMEM;
> > > +
> > > + mdev = mt76_alloc_device(&func->dev, sizeof(*dev), ops, &drv_ops);
> > > if (!mdev)
> > > return -ENOMEM;
> > >
> > > dev = container_of(mdev, struct mt7921_dev, mt76);
> > > dev->hif_ops = &mt7921_sdio_ops;
> > > -
> > > + dev->ops = ops;
> > > sdio_set_drvdata(func, dev);
> > >
> > > ret = mt76s_init(mdev, func, &mt7921s_ops);
> > > diff --git a/drivers/net/wireless/mediatek/mt76/mt7921/usb.c b/drivers/net/wireless/mediatek/mt76/mt7921/usb.c
> > > index d06cee386acd..cf3ec59a4270 100644
> > > --- a/drivers/net/wireless/mediatek/mt76/mt7921/usb.c
> > > +++ b/drivers/net/wireless/mediatek/mt76/mt7921/usb.c
> > > @@ -217,6 +217,7 @@ static int mt7921u_probe(struct usb_interface *usb_intf,
> > >
> > > dev = container_of(mdev, struct mt7921_dev, mt76);
> > > dev->hif_ops = &hif_ops;
> > > + dev->ops = ops;
> > >
> > > udev = usb_get_dev(udev);
> > > usb_reset_device(udev);
> > > --
> > > 2.25.1
> > >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-08-18 7:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 0:03 [PATCH 0/9] wifi: mt76: mt7921: introduce chanctx support sean.wang
2022-08-16 0:03 ` [PATCH 1/9] wifi: mac80211: allow enabling chanctx until hw registration sean.wang
2022-08-16 8:03 ` Johannes Berg
2022-08-17 8:28 ` Sean Wang
2022-08-17 8:30 ` Johannes Berg
2022-08-18 0:11 ` Sean Wang
2022-08-18 10:49 ` Johannes Berg
2022-08-18 23:40 ` Sean Wang
2022-08-19 17:16 ` Johannes Berg
2022-08-19 17:36 ` Johannes Berg
2022-08-16 0:03 ` [PATCH 2/9] wifi: mt76: connac: add mt76_connac_mcu_uni_set_chctx sean.wang
2022-08-17 7:13 ` Lorenzo Bianconi
2022-08-16 0:03 ` [PATCH 3/9] wifi: mt76: connac: rely on mt76_connac_mcu_uni_set_chctx sean.wang
2022-08-17 7:13 ` Lorenzo Bianconi
2022-08-16 0:03 ` [PATCH 4/9] wifi: mt76: mt7921: add chanctx parameter to mt76_connac_mcu_uni_add_bss signature sean.wang
2022-08-16 0:03 ` [PATCH 5/9] wifi: mt76: mt7921: add unified ROC cmd/event support sean.wang
2022-08-17 7:15 ` Lorenzo Bianconi
2022-08-16 0:03 ` [PATCH 6/9] wifi: mt76: mt7921: drop ieee80211_[start, stop]_queues in driver sean.wang
2022-08-17 7:16 ` Lorenzo Bianconi
2022-08-18 0:44 ` Sean Wang
2022-08-16 0:03 ` [PATCH 7/9] wifi: mt76: connac: accept hw scan request at a time sean.wang
2022-08-16 0:03 ` [PATCH 8/9] wifi: mt76: mt7921: introduce remain_on_channel support sean.wang
2022-08-17 7:12 ` Lorenzo Bianconi
2022-08-18 1:03 ` Sean Wang
2022-08-18 7:39 ` Lorenzo Bianconi [this message]
2022-08-25 0:10 ` Sean Wang
2022-08-30 5:18 ` Kalle Valo
2022-08-16 0:03 ` [PATCH 9/9] wifi: mt76: mt7921: introduce chanctx support sean.wang
2022-08-17 7:24 ` Lorenzo Bianconi
2022-08-18 0:37 ` Sean Wang
2022-08-18 7:43 ` Lorenzo Bianconi
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=Yv3sqvhXnGiOpKkE@lore-desk \
--to=lorenzo@kernel.org \
--cc=Deren.Wu@mediatek.com \
--cc=Eddie.Chen@mediatek.com \
--cc=Eric-SY.Chang@mediatek.com \
--cc=Leon.Yen@mediatek.com \
--cc=Soul.Huang@mediatek.com \
--cc=Stella.Chang@mediatek.com \
--cc=Tom.Chou@mediatek.com \
--cc=YN.Chen@mediatek.com \
--cc=abhishekpandit@google.com \
--cc=ch.yeh@mediatek.com \
--cc=druth@google.com \
--cc=frankgor@google.com \
--cc=jenhao.yang@mediatek.com \
--cc=jsiuda@google.com \
--cc=km.lin@mediatek.com \
--cc=kuabhs@google.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=posh.sun@mediatek.com \
--cc=robin.chiu@mediatek.com \
--cc=sean.wang@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=shawnku@google.com \
--cc=steve.lee@mediatek.com \
--cc=ted.huang@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;
as well as URLs for NNTP newsgroup(s).