All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
To: linux-wireless@vger.kernel.org,
	Andrey Shevchenko <ashevchenko@quantenna.com>,
	Sergei Maksimenko <smaksimenko@quantenna.com>
Subject: Re: [PATCH 3/6] qtnfmac: implement cfg80211 power management callback
Date: Mon, 4 Jun 2018 11:58:32 -0700	[thread overview]
Message-ID: <4dfbc70e-831b-e2d3-ae3f-0f0f23c4341c@quantenna.com> (raw)
In-Reply-To: <20180604125021.pvcbnqexrkgqd72q@bars>

On 06/04/2018 05:50 AM, Sergey Matyukevich wrote:
>> I think it's better be moved somewhere out of qtnf_wiphy_allocate() as OPS
>> are global for all MACs, while qtnf_wiphy_allocate() is called for each MAC
>> separately.
> 
> Consider the case of splitting hardware capabilities into two groups:
> global and per-wmac. In this case we may need to register different
> subsets of cfg80211 operations for each wmac. In such a case, function
> qtnf_wiphy_allocate looks like a reasonable point where to merge both
> capability groups and customize cfg80211_ops structure for each wmac.
> 


What I mean is that wiphy_new() will not dup cfg80211_ops that we pass, 
it will just assign a pointer to whatever it gets.
qtn_cfg80211_ops is global right now, if we modify it, it will affect 
all WMACs, not just the one that we're allocating.

Currently it's not a problem as we do not have any per-WMAC 
capabilities. If we to have any, we would have to dup qtn_cfg80211_ops 
in qtnf_wiphy_allocate().

Though I agree that we already have QLINK_HW_CAPAB_DFS_OFFLOAD 
processing in qtnf_wiphy_allocate(), so it makes sense to do a cleanup 
separately.

  reply	other threads:[~2018-06-04 18:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31  9:10 [PATCH 0/6] qtnfmac: enable more features Sergey Matyukevich
2018-05-31  9:10 ` [PATCH 1/6] qtnfmac: implement net_device_ops callback to set MAC address Sergey Matyukevich
2018-06-27 15:54   ` [1/6] " Kalle Valo
     [not found]   ` <20180627155439.481E76034E@smtp.codeaurora.org>
2018-06-29  9:26     ` Sergey Matyukevich
2018-06-29  9:43       ` Kalle Valo
2018-06-29 12:03         ` Sergey Matyukevich
2018-05-31  9:10 ` [PATCH 2/6] qtnfmac: enable source MAC address randomization support Sergey Matyukevich
2018-05-31  9:10 ` [PATCH 3/6] qtnfmac: implement cfg80211 power management callback Sergey Matyukevich
2018-06-01  1:04   ` Igor Mitsyanko
2018-06-04 12:50     ` Sergey Matyukevich
2018-06-04 18:58       ` Igor Mitsyanko [this message]
2018-07-30 13:55   ` Kalle Valo
2018-07-30 14:12   ` Kalle Valo
2018-05-31  9:11 ` [PATCH 4/6] qtnfmac: enable multiple SSIDs scan support Sergey Matyukevich
2018-05-31  9:11 ` [PATCH 5/6] qtnfmac: add support for PTA configuration Sergey Matyukevich
2018-07-30 14:06   ` Kalle Valo
2018-07-31 11:42     ` Arend van Spriel
2018-08-01  8:23       ` Sergey Matyukevich
2018-08-04 22:19         ` Arend van Spriel
2018-08-05 15:22           ` Sergey Matyukevich
2018-08-05 21:34             ` Arend van Spriel
2018-08-01  8:25       ` Kalle Valo
2018-05-31  9:11 ` [PATCH 6/6] qtnfmac: implement basic WoWLAN support Sergey Matyukevich
2018-07-30 14:13   ` Kalle Valo
2018-07-31  9:59     ` Sergey Matyukevich
2018-08-01  8:38       ` Kalle Valo
2018-05-31  9:36 ` [PATCH 0/6] qtnfmac: enable more features Kalle Valo
2018-05-31 10:35   ` Sergey Matyukevich
2018-05-31 11:12     ` Kalle Valo
2018-06-01  1:08 ` Igor Mitsyanko

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=4dfbc70e-831b-e2d3-ae3f-0f0f23c4341c@quantenna.com \
    --to=igor.mitsyanko.os@quantenna.com \
    --cc=ashevchenko@quantenna.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=smaksimenko@quantenna.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.