linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Cc: igor.mitsyanko.os@quantenna.com, linux-wireless@vger.kernel.org,
	Dmitrii Lebed <dlebed@quantenna.com>,
	Sergei Maksimenko <smaksimenko@quantenna.com>,
	Bindu Therthala <btherthala@quantenna.com>,
	Huizhao Wang <hwang@quantenna.com>,
	Kamlesh Rath <krath@quantenna.com>,
	Avinash Patil <avinashp@quantenna.com>
Subject: Re: [PATCH v6] qtnfmac: introduce new FullMAC driver for Quantenna chipsets
Date: Fri, 19 May 2017 12:18:14 +0200	[thread overview]
Message-ID: <1495189094.3274.2.camel@sipsolutions.net> (raw)
In-Reply-To: <20170518200810.pch7tivugqyjmy4d@bars>

Hi,

> Thanks for the review ! Fixes will be queued to the upcoming patches
> with various cleanups as well as new features.

Great :)

FWIW, regarding the  qtnf_mgmt_frame_register() and
cfg80211_rx_mgmt() thing, I think we'll have to discuss how to do this,
and perhaps you need to think about the firmware API for it.

Right now, I don't see that you can pass filters down, but you probably
also don't want to implement the reject code in the driver? And
cfg80211 doesn't give you that data right now either... So somewhere I
expect we'll need to make changes, unless you just copy (e.g. from
mac80211) the implementation of what happens when cfg80211_rx_mgmt()
returns false.

> BTW, speaking about other backends... During previous reviews of this
> patch we had a question regarding possible support of another
> previous generation SoC connected to host CPU via RGMII interface. Is
> there any legitimate (aka 'upstreamable') way to support such
> wireless cards ?

I'm not really familiar with RGMII, so I can't say how you'd support
this, sorry.

johannes

  reply	other threads:[~2017-05-19 10:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 21:51 [PATCH v6] qtnfmac: introduce new FullMAC driver for Quantenna chipsets igor.mitsyanko.os
2017-05-12 15:18 ` [v6] " Kalle Valo
2017-05-12 15:20   ` Kalle Valo
2017-05-12 15:43     ` Joe Perches
2017-05-12 16:37       ` Kalle Valo
2017-05-12 17:47         ` Igor Mitsyanko
2017-05-17 13:12 ` [PATCH v6] " Johannes Berg
2017-05-18 20:08   ` Sergey Matyukevich
2017-05-19 10:18     ` Johannes Berg [this message]
2017-05-21 17:08       ` Sergey Matyukevich
2017-05-22  6:28         ` Johannes Berg
2017-05-22 21:04           ` Sergey Matyukevich
2017-05-24  7:11             ` Johannes Berg
2017-05-24 11:08               ` Sergey Matyukevich
2017-05-22  9:09   ` Kalle Valo
2017-05-24 14:06 ` [v6] " Kalle Valo

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=1495189094.3274.2.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=avinashp@quantenna.com \
    --cc=btherthala@quantenna.com \
    --cc=dlebed@quantenna.com \
    --cc=hwang@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=krath@quantenna.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sergey.matyukevich.os@quantenna.com \
    --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 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).