From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 01/14] iwlwifi: mvm: add soc latency support
Date: Thu, 26 Mar 2020 09:32:31 +0200 [thread overview]
Message-ID: <87ftdvk1v4.fsf@codeaurora.org> (raw)
In-Reply-To: <937db1c0c8a1352705f07d7866873efba0d1da44.camel@coelho.fi> (Luca Coelho's message of "Thu, 26 Mar 2020 08:49:11 +0200")
Luca Coelho <luca@coelho.fi> writes:
> On Tue, 2020-03-24 at 17:07 +0200, Kalle Valo wrote:
>> Luca Coelho <luca@coelho.fi> writes:
>>
>> > From: Shahar S Matityahu <shahar.s.matityahu@intel.com>
>> >
>> > Some devices require longer time to stabilize the power and XTAL.
>> > This is especially true for devices integrated in the SoC. Add
>> > support for a new firmware API that allows the driver to set the
>> > latency value accordingly.
>> >
>> > Signed-off-by: Shahar S Matityahu <shahar.s.matityahu@intel.com>
>> > Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
>>
>> [...]
>>
>> > +++ b/drivers/net/wireless/intel/iwlwifi/fw/api/soc.h
>> > @@ -0,0 +1,83 @@
>> > +/******************************************************************************
>> > + *
>> > + * This file is provided under a dual BSD/GPLv2 license. When using or
>> > + * redistributing this file, you may do so under either license.
>>
>> Any chance of getting SPDX tags to iwlwifi soon? They are awesome and
>> make life so much easier.
>
> Hmmm... Most of our files already have it.
Ah, I didn't notice that.
> I'll add the tags to the remaining ones and send it upstream as usual.
Great, thanks. It would be really nice to have consistency within a
driver.
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2020-03-26 7:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 13:19 [PATCH 00/14] iwlwifi: updates intended for v5.7 2020-03-23 Luca Coelho
2020-03-23 13:19 ` [PATCH 01/14] iwlwifi: mvm: add soc latency support Luca Coelho
2020-03-24 15:07 ` Kalle Valo
2020-03-26 6:49 ` Luca Coelho
2020-03-26 7:32 ` Kalle Valo [this message]
2020-03-23 13:19 ` [PATCH 02/14] iwlwifi: yoyo: add PCI config space region type Luca Coelho
2020-03-23 13:19 ` [PATCH 03/14] iwlwifi: pcie: implement read_config32 Luca Coelho
2020-03-23 13:19 ` [PATCH 04/14] iwlwifi: pass trans and NVM data to HE capability parsing Luca Coelho
2020-03-23 13:19 ` [PATCH 05/14] iwlwifi: scan: support scan req cmd ver 14 Luca Coelho
2020-03-23 13:19 ` [PATCH 06/14] iwlwifi: mvm: rs-fw: fix some indentation Luca Coelho
2020-03-23 13:19 ` [PATCH 07/14] iwlwifi: remove redundant iwl9560_2ac_cfg struct Luca Coelho
2020-03-23 13:19 ` [PATCH 08/14] iwlwifi: mvm: enable SF also when we have HE Luca Coelho
2020-03-23 13:19 ` [PATCH 09/14] iwlwifi: move integrated, extra_phy and soc_latency to trans_cfg Luca Coelho
2020-03-23 13:19 ` [PATCH 10/14] iwlwifi: remove some unused extern declarations from iwl-config.h Luca Coelho
2020-03-23 13:19 ` [PATCH 11/14] iwlwifi: add HW step to new cfg device table Luca Coelho
2020-03-23 13:19 ` [PATCH 12/14] iwlwifi: convert all Qu with Jf devices to the new config table Luca Coelho
2020-03-23 13:19 ` [PATCH 13/14] iwlwifi: convert QnJ with Jf devices to " Luca Coelho
2020-03-23 13:19 ` [PATCH 14/14] iwlwifi: remove unnecessary cfg mangling for Qu C and QuZ with Jf Luca Coelho
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=87ftdvk1v4.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luca@coelho.fi \
/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).