From: IgorMitsyanko <igor.mitsyanko.os@quantenna.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: <johannes@sipsolutions.net>, <linux-wireless@vger.kernel.org>,
"Avinash Patil" <avinashp@quantenna.com>,
Dmitrii Lebed <dlebed@quantenna.com>,
"Sergei Maksimenko" <smaksimenko@quantenna.com>,
Sergey Matyukevich <smatyukevich@quantenna.com>,
Bindu Therthala <btherthala@quantenna.com>,
Huizhao Wang <hwang@quantenna.com>,
Kamlesh Rath <krath@quantenna.com>
Subject: Re: [PATCH v2 RESEND] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets
Date: Tue, 20 Sep 2016 22:05:07 +0300 [thread overview]
Message-ID: <dfdaca87-dfbd-4677-fbff-45127ccd2e0c@quantenna.com> (raw)
In-Reply-To: <87a8f68wae.fsf@kamboji.qca.qualcomm.com>
On 09/17/2016 04:56 PM, Kalle Valo wrote:
> <igor.mitsyanko.os@quantenna.com> writes:
>
>> From: Avinash Patil <avinashp@quantenna.com>
>>
>> This patch adds support for new FullMAC WiFi driver for Quantenna
>> QSR10G chipsets.
>>
>> QSR10G is Quantenna's 8x8, 160M, 11ac offering.
>> QSR10G supports 2 simultaneous WMACs- one 5G and one 2G. 5G WMAC
>> supports 160M, 8x8 configuration.
>> FW supports 8 concurrent virtual interfaces on each WMAC.
>>
>> Patch introduces 2 new drivers- qtnfmac.ko for interfacing with
>> kernel/cfg80211 and qtnfmac_pcie.ko for PCIe bus interface.
>>
>> Signed-off-by: Dmitrii Lebed <dlebed@quantenna.com>
>> Signed-off-by: Sergei Maksimenko <smaksimenko@quantenna.com>
>> Signed-off-by: Sergey Matyukevich <smatyukevich@quantenna.com>
>> Signed-off-by: Bindu Therthala <btherthala@quantenna.com>
>> Signed-off-by: Huizhao Wang <hwang@quantenna.com>
>> Signed-off-by: Kamlesh Rath <krath@quantenna.com>
>> Signed-off-by: Avinash Patil <avinashp@quantenna.com>
>> Signed-off-by: Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>
> More comments:
>
>> +/* FW names */
>> +
>> +#define QTN_PCI_FW_NAME "pearl-linux.lzma.img"
> The firmware name gives no indication what this file is about (remember
> that linux-firmware.git has a lot of files). Please name it properly,
> don't just use what is used in by firmware build scripts :) Take into
> account also future hw support, all firmware files need to coexist in
> the same repository without user invention. In a way the firmware
> filename is part of kernel/userspace interface and needs to be stable.
>
> For example, you could use something like "qtnfmac/qsr10g.img" (assuming
> qsr10g is the name of chip).
Ok, we will reconsider our naming conventions, take into account more
devices that we need to support in the future.
I'm thinking about something like:
qtn/fmac_qsr10g.img <---- FullMAC QSR10G device
qtn/fmac_qsr1000.img <---- FullMAC QSR1000 device
qtn/smac_qsr10g.img <---- SoftMAC QSR10G
qtn/smac_qsr10000.img <----- SoftMAC QSR1000
etc
>
> I forgot already, is the firmware image ready for submission to
> linux-firmware.git?
Yes, we have firmware binary license prepared by our legal department
and its ready for submitting. Will send in parallel with next patch
revision (only to linux-wireless for now, not to linux-firmware, as was
discussed).
>
>> + pr_info("%s: %sregistered mgmt frame type 0x%x\n", __func__,
>> + reg ? "" : "un", frame_type);
> The driver seems to be quite spammy with info messages:
>
> qtnfmac/cfg80211.c: pr_info("%s: %sregistered mgmt frame type 0x%x\n", __func__,
> qtnfmac/cfg80211.c: pr_info("QTNF: %s cipher=%x, idx=%u, pairwise=%u\n", __func__,
> qtnfmac/cfg80211.c: pr_info("QTNF: %s idx=%u, pairwise=%u\n", __func__, key_index,
> qtnfmac/cfg80211.c: pr_info("QTNF: %s idx=%u, unicast=%u, multicast=%u\n", __func__,
> qtnfmac/cfg80211.c: pr_info("QTNF: %s idx=%u\n", __func__, key_index);
> qtnfmac/cfg80211.c: pr_info("%s: initiator=%d, alpha=%c%c, macid=%d\n", __func__,
> qtnfmac/cfg80211.c: pr_info("%s: MAX_IF: %zu; MODES: %.4X; RADAR WIDTHS: %.2X\n", __func__,
> qtnfmac/cfg80211.c: pr_info("macid=%d, phymode=%#x\n", mac->macid, mac->macinfo.phymode);
> qtnfmac/commands.c: pr_info("%s: unexpected TLV type: %.4X\n",
> qtnfmac/commands.c: pr_info("%s: STA %pM not found\n", __func__, sta_mac);
> qtnfmac/commands.c: pr_info("country-code from EP: %c%c\n", hwinfo->country_code[0],
> qtnfmac/commands.c: pr_info("fw_version = %d, num_mac=%d, mac_bitmap=%#x\n",
> qtnfmac/commands.c: pr_info("iface limit record count=%zu\n", record_count);
> qtnfmac/commands.c: pr_info("MAC%d reported channels %d\n",
> qtnfmac/init.c: pr_info("%s: macid=%d\n", __func__, macid);
> qtnfmac/pcie.c: pr_info("enabled PCIE MSI interrupt\n");
> qtnfmac/pcie.c: pr_info("%s: BAR[%u] vaddr=0x%p busaddr=0x%p len=%u\n",
> qtnfmac/pcie.c: pr_info("%s: set mps to %d (was %d, max %d)\n",
> qtnfmac/pcie.c: pr_info("fw download started: fw start addr = 0x%p, size=%d\n",
> qtnfmac/pcie.c: pr_info("fw download completed: totally sent %d blocks\n", blk);
> qtnfmac/pcie.c: pr_info("RC is ready to boot EP...\n");
> qtnfmac/pcie.c: pr_info("starting download firmware %s...\n", bus->fwname);
> qtnfmac/pcie.c: pr_info("successful init of PCI device %x\n", pdev->device);
> qtnfmac/pcie.c: pr_info("Register Quantenna FullMAC PCIE driver\n");
> qtnfmac/pcie.c: pr_info("Unregister Quantenna FullMAC PCIE driver\n");
> qtnfmac/trans.c: pr_info("%s: interrupted\n", __func__);
> qtnfmac/trans.c: pr_info("%s: skb dropped\n", __func__);
>
> Usualle the preference is that driver is quiet until something goes
> wrong. I hope some of these could be debug messages.
We will reduce noise generated by driver.
>
>> --- /dev/null
>> +++ b/drivers/net/wireless/quantenna/qtnfmac/pcie.c
>> @@ -0,0 +1,1374 @@
>> +/**
>> + * Copyright (c) 2015-2016 Quantenna Communications, Inc.
>> + * All rights reserved.
>> + *
>> + * This program is free software; you can redistribute it and/or
>> + * modify it under the terms of the GNU General Public License
>> + * as published by the Free Software Foundation; either version 2
>> + * of the License, or (at your option) any later version.
>> + *
>> + * This program is distributed in the hope that it will be useful,
>> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
>> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>> + * GNU General Public License for more details.
>> + *
>> + **/
>> +
>> +#undef DEBUG
> Why?
Good question) Will remove.
>
next prev parent reply other threads:[~2016-09-20 19:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 22:11 [PATCH v2 RESEND] qtnfmac: announcement of new FullMAC driver for Quantenna chipsets igor.mitsyanko.os
2016-06-21 2:12 ` kbuild test robot
2016-06-21 12:22 ` Johannes Berg
2016-07-11 18:57 ` Igor Mitsyanko
2016-08-01 9:37 ` Johannes Berg
2016-09-17 13:59 ` Kalle Valo
2016-07-19 7:39 ` [v2, " Kalle Valo
2016-09-17 13:46 ` [PATCH v2 " Kalle Valo
2016-09-17 14:50 ` Johannes Berg
2016-09-17 15:01 ` Kalle Valo
2016-09-17 15:11 ` Johannes Berg
2016-09-17 15:14 ` Kalle Valo
2016-09-20 18:51 ` IgorMitsyanko
2016-09-20 18:51 ` IgorMitsyanko
2016-09-26 10:56 ` Kalle Valo
2016-09-26 12:45 ` IgorMitsyanko
2016-09-26 18:16 ` Kalle Valo
2016-09-17 13:56 ` Kalle Valo
2016-09-20 19:05 ` IgorMitsyanko [this message]
2016-09-26 10:45 ` 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=dfdaca87-dfbd-4677-fbff-45127ccd2e0c@quantenna.com \
--to=igor.mitsyanko.os@quantenna.com \
--cc=avinashp@quantenna.com \
--cc=btherthala@quantenna.com \
--cc=dlebed@quantenna.com \
--cc=hwang@quantenna.com \
--cc=johannes@sipsolutions.net \
--cc=krath@quantenna.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=smaksimenko@quantenna.com \
--cc=smatyukevich@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.