Some of the code present in ath10k_pci_{probe|remove} are reusable
in ahb case too. To avoid code duplication, move reusable code to
new functions. Later, those new functions can be called from ahb
module's probe and exit functions.
Signed-off-by: Raja Mani
---
drivers/net/wireless/ath/ath10k/pc
ath10k_pci_read32/write32() does work more specific to
PCI by ensuring pci wake/sleep for every read and write.
There is a plan to use most of stuff available in pci.c
(irq stuff, copy engine, etc) for AHB case. Such kind
of pci wake/sleep for every read/write is not required
in AHB case (qca4019).
Resolución 127, 2011 - Reglamento Banda 2,4 GHz.:
http://www.mincom.gob.cu/sites/default/files/marcoregulatorio/R%20127-11%20Reglamento%20banda%202,4%20GHz.pdf
Cc: Seth Forshee
Cc: linux-wireless@vger.kernel.org
Cc: wireless-re...@lists.infradead.org
Signed-off-by: Xose Vazquez Perez
---
db.txt
qca4019 uses ahb instead of pci where it slightly differs in device
enumeration, clock control, reset control, etc. Good thing is that
ahb also uses copy engine for the data transaction. So, the most of
the stuff implemented in pci.c/ce.c are reusable in ahb case too.
Device enumeration in ahb cas
pre qca4019 chipsets has/uses internal clock generator for
the operation. But, qca4019 uses external clocks supplied from
outside of target (ie, outside of wifi core). Three different clocks
(cmd clock, ref clock, rtc clock) comes into picture in qca4019.
All those clocks needs to configured with h
Some of static functions present in pci.c file are reusable
in ahb (qca4019) case. Remove static word for those reusable
functions and have those function prototype declaration in
pci.h file. So that, pci.h header file can be included in
ahb module and reused. There is no functionality changes done
New register table is added for qca4019 to tell about it's
register mapping details.
Nothing much other than this.
Signed-off-by: Raja Mani
---
drivers/net/wireless/ath/ath10k/core.c | 4
drivers/net/wireless/ath/ath10k/hw.c | 39 ++
drivers/net/wireless/
qca4019 deals with below register memory region to control the clock,
reset, etc.
- Memory to control wifi core
- gcc (outside of wifi)
- tcsr (outside of wifi)
Add new helper functions to perform read/write in above registers
spaces. Actual ioremap for above registers are
On 09/08/2015 04:22 PM, Seth Forshee wrote:
> On Tue, Sep 08, 2015 at 03:59:38PM +0200, Xose Vazquez Perez wrote:
>> On 08/13/2015 04:31 PM, Seth Forshee wrote:
>>
>>> On Tue, Aug 11, 2015 at 03:29:55PM +0200, Xose Vazquez Perez wrote:
Resolución 127, 2011 - Reglamento Banda 2,4 GHz.:
htt
This patch series attempts to add ahb support (qca4019) in ath10k.
All ahb related ops are grouped and kept in new file called ahb.c/ahb.h
and will get compiled/linked to ath10k_pci.ko based on kernel config flag
CONFIG_ATH10K_AHB flag. Most of function in pci.c file are reusable and
called as it'
To perform reset on qca4019 wifi, multiple reset lines needs
to be toggled in a sequence with help of reset controller support
in the kernel. This patch adds functions to reset control init/deinit
and release reset.
Signed-off-by: Raja Mani
---
drivers/net/wireless/ath/ath10k/Kconfig | 2 +-
d
Add irq related functions to register,handle,release,disable interrupt.
qca4019 supports msi interrupt, but it has the problem. Until the issue
gets sorted out, only legacy interrupt model is enabled and used.
Signed-off-by: Raja Mani
---
drivers/net/wireless/ath/ath10k/ahb.c | 44 +
Add function to perform chip halt sequence and function to halt axi
bus in ahb module. Mainly used in the scenario like driver unload.
Signed-off-by: Raja Mani
---
drivers/net/wireless/ath/ath10k/ahb.c | 113 ++
drivers/net/wireless/ath/ath10k/ahb.h | 15 +
2
Like how pci.c exposes hif ops for the bus specific operation,
expose similar hif ops table for ahb with all required functions
linked to it. Many ath10k_pci_* functions are reused here in hif ops
table. If something is not sharable, new functions are added for ahb
and linked to hif ops table.
Fin
Add function to gather resources required for qca4019 to operate
(memory, irq, dma setting, clock init , rest control init) and
function release those resources when it's not needed.
Signed-off-by: Raja Mani
---
drivers/net/wireless/ath/ath10k/ahb.c | 122 ++
driv
From: Johannes Berg
Beniamino reported that he was getting an RTM_NEWLINK message for a
given interface, after the RTM_DELLINK for it. It turns out that the
message is a wireless extensions message, which was sent because the
interface had been connected and disconnection while it was deleted
cau
On Wed, 2016-01-27 at 13:14 +0100, Johannes Berg wrote:
>
> +static int wext_netdev_notifier_call(struct notifier_block *nb,
> + unsigned long state, void *ptr)
> +{
> + /*
> + * When a netdev is unregistered, flush all pending messages
> + * to avoid
> > + if (state == NETDEV_UNREGISTER)
> > + wireless_nlevent_flush();
> >
> It could be argued that the state check isn't really necessary and
> should be removed to avoid ordering issues with up/down vs. wext, but
> this fixes the really strange issue where you get an RTM_NEWLINK
> a
"Grumbach, Emmanuel" writes:
> On 01/26/2016 04:01 PM, Johannes Berg wrote:
There's a conflict due to 8f57e4d930d, how should I fix it?
>> I think we can thus drop my patch - that commit fixes the issue that
>> Andrew had reported as well, and that I worked around by casting the
>> result...
https://github.com/0day-ci/linux/commits/Rafa-Mi-ecki/brcmfmac-support-for-new-14e43-4365-card-with-BCM4366/20160127-010149
> base:
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git
> master
> config: x86_64-allmodconfig (attached as .config)
> reproduce
On Wed, 2016-01-27 at 13:18 +0100, Johannes Berg wrote:
> > > + if (state == NETDEV_UNREGISTER)
> > > + wireless_nlevent_flush();
> > >
> > It could be argued that the state check isn't really necessary and
> > should be removed to avoid ordering issues with up/down vs. wext,
> > but
> > t
From: Johannes Berg
Since cfg80211 frequently takes actions from its netdev notifier
call, wireless extensions messages could still be ordered badly
since the wext netdev notifier, since wext is built into the
kernel, runs before the cfg80211 netdev notifier. For example,
the following can happen
From: Johannes Berg
Beniamino reported that he was getting an RTM_NEWLINK message for a
given interface, after the RTM_DELLINK for it. It turns out that the
message is a wireless extensions message, which was sent because the
interface had been connected and disconnection while it was deleted
cau
drop us a note to
>> help improving the system]
>>
>> url:
>> https://github.com/0day-ci/linux/commits/Rafa-Mi-ecki/brcmfmac-support-for-new-14e43-4365-card-with-BCM4366/20160127-010149
>> base:
>> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wir
The driver reads a value from hfa384x_from_bap(), which may fail,
and then assigns the value to a local variable. gcc detects that
in in the failure case, the 'rlen' variable now contains
uninitialized data:
In file included from
../drivers/net/wireless/intersil/hostap/hostap_pci.c:220:0:
drivers
This will allow drivers to make more educated
decisions whether to defer transmission or not.
Relying on wake_tx_queue() call count implicitly
was not possible because it could be called
without queued frame count actually changing on
software tx aggregation start/stop code paths.
It was also not
On Wed, 2016-01-27 at 15:26 +0100, Michal Kazior wrote:
>
> @@ -1294,6 +1298,8 @@ struct sk_buff *ieee80211_tx_dequeue(struct
> ieee80211_hw *hw,
> if (!skb)
> goto out;
>
> + txqi->byte_cnt -= skb->len;
> +
> atomic_dec(&sdata->txqs_len[ac]);
>
This *looks* a bit
Until now all stations (notably in AP mode) would
share 4 AC queues exposed via netdev. This meant
that whenever a single station's AC became full
all other stations' AC were considered full and
stopped as well.
This was suboptimal and could lead to per station
traffic starvation and/or suboptimal
On Wed, 2016-01-27 at 15:28 +0100, Michal Kazior wrote:
> Until now all stations (notably in AP mode) would
> share 4 AC queues exposed via netdev. This meant
> that whenever a single station's AC became full
> all other stations' AC were considered full and
> stopped as well.
>
> This was subopti
On 27 January 2016 at 15:26, Johannes Berg wrote:
> On Wed, 2016-01-27 at 15:26 +0100, Michal Kazior wrote:
>>
>> @@ -1294,6 +1298,8 @@ struct sk_buff *ieee80211_tx_dequeue(struct
>> ieee80211_hw *hw,
>> if (!skb)
>> goto out;
>>
>> + txqi->byte_cnt -= skb->len;
>> +
>>
On Wed, 2016-01-27 at 15:33 +0100, Michal Kazior wrote:
> On 27 January 2016 at 15:26, Johannes Berg > wrote:
> > On Wed, 2016-01-27 at 15:26 +0100, Michal Kazior wrote:
> > >
> > > @@ -1294,6 +1298,8 @@ struct sk_buff *ieee80211_tx_dequeue(struct
> > > ieee80211_hw *hw,
> > > if (!skb)
> >
Until now all stations (notably in AP mode) would
share 4 AC queues exposed via netdev. This meant
that whenever a single station's AC became full
all other stations' AC were considered full and
stopped as well.
This was suboptimal and could lead to per station
traffic starvation and/or suboptimal
problem: it does not connect to any wifi network you can see the time out on
dmesg
>uname -a
Linux DrunkCatPC 4.4.0-4-MANJARO #1 SMP PREEMPT Wed Jan 20 20:22:31 UTC 2016
x86_64 GNU/Linux
>lsusb
Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
802.11n WLAN Adapter
>iwcon
2016-01-27 2:46 GMT-05:00 Grumbach, Emmanuel :
>> Hi
>>
>> 2016-01-26 3:28 GMT-05:00 Grumbach, Emmanuel
>> :
>> >
>> >
>> > On 01/26/2016 12:20 AM, Nikolay Martynov wrote:
>> >> It looks like sometimes firmware returns zero for chain noise and
>> >> signal during calibration period. This seems to b
Use kzalloc instead of kmalloc for struct tid_ampdu_rx. Fixes:
[7.976605] UBSAN: Undefined behaviour in net/mac80211/rx.c:932:29
[7.976608] load of value 2 is not a valid value for type '_Bool'
[7.976611] CPU: 3 PID: 1134 Comm: kworker/u16:7 Not tainted 4.5.0-rc1+ #265
[7.976613] H
Dan Carpenter writes:
> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrote:
>> Hi All,
>>
>> I'm helping Greg do a bit of cleanup in the staging tree, I noticed that
>> wlan-ng driver is maybe ready to be moved out of staging. Are there
>> any TODO tasks left to do beside checkpa
* Tony Lindgren [160113 09:28]:
> * Igor Grinberg [160112 22:01]:
> > Hi Kalle Valo,
> >
> > On 01/07/16 11:02, Kalle Valo wrote:
> > > Uri Mashiach writes:
> > >
> > >> Device tree modifications:
> > >> - Pinmux for SPI0 and WiFi GPIOs.
> > >> - SPI0 node with wlcore as a child node.
> > >>
>
* Igor Grinberg [160112 22:09]:
>
>
> On 12/30/15 15:35, Uri Mashiach wrote:
> > Device tree modifications:
> > - Pinmux for SPI0 and WiFi GPIOs.
> > - SPI0 node with wlcore as a child node.
> >
> > Cc: Tony Lindgren
> > Signed-off-by: Uri Mashiach
>
> Acked-by: Igor Grinberg
Applying into
Update 10.4 WMI service map to sync to the latest 10.4 firmware
as of 1/20/2016.
Signed-off-by: Peter Oh
---
drivers/net/wireless/ath/ath10k/wmi.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/wmi.h
b/drivers/net/wireless/ath/ath10k/wmi.h
ind
Abstraction layer for vdev subtype is added to solve
subtype mismatch and to give flexible compatibility
among different firmware revisions.
For instance, 10.2 and 10.4 firmware has different
definition of their vdev subtypes for Mesh.
10.4 defined subtype 6 for 802.11s Mesh while 10.2 uses 5.
Hen
Interface type P2P_GO can be checked by either arvif->vdev_type
and arvif->vdev_subtype or vif->type and vif->p2p.
Use later one to avoid more cpu consumption that could happen
when subtype abstraction layer change is introduced.
Signed-off-by: Peter Oh
---
drivers/net/wireless/ath/ath10k/mac.c
WMI_10_4_SERVICE_MESH bit is for non IEEE802.11s Mesh.
Hence rename it to WMI_10_4_SERVICE_MESH_NON_11S.
Also add _11S as post-fix to each of WMI_SERVICE_MESH and
WMI_VDEV_SUBTYPE_MESH specifying the service is for 11s Mesh.
This will help users to distinguish 11s Mesh from non 11s Mesh.
Signed-of
Split Mesh service to 11s Mesh and non-11s Mesh according to
firmware service bit to help users distinguish 11s Mesh from
non 11s Mesh.
And add abstraction layer for vdev subtype to solve subtype mismatch
and to give flexible compatibility among different firmware revisions.
Peter Oh (4):
ath10k
On 01/27/2016 10:55 AM, Peter Oh wrote:
Abstraction layer for vdev subtype is added to solve
subtype mismatch and to give flexible compatibility
among different firmware revisions.
For instance, 10.2 and 10.4 firmware has different
definition of their vdev subtypes for Mesh.
10.4 defined subtype
On Wed, Jan 27, 2016 at 02:45:26PM +0100, Arnd Bergmann wrote:
> To ensure we get consistent error handling here, this changes the code
> to only set rlen if we actually read data correctly, which also takes
> care of the warning.
It may be a good idea to do the job better. Looking at the code:
On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote:
> Split Mesh service to 11s Mesh and non-11s Mesh according to
> firmware service bit to help users distinguish 11s Mesh from
> non 11s Mesh.
> And add abstraction layer for vdev subtype to solve subtype mismatch
> and to give flexible compa
On Tue, Jan 26, 2016 at 6:23 PM, Eric Dumazet wrote:
> On Tue, 2016-01-26 at 15:12 -0800, Cong Wang wrote:
>> On Tue, Jan 26, 2016 at 2:55 PM, Julian Calaby
>> wrote:
>> > Hi Cong,
>> >
>> > On Wed, Jan 27, 2016 at 4:53 AM, Cong Wang
>> > wrote:
>> >
>> > A commit message would be nice. A brie
On Wed, 2016-01-27 at 11:50 -0800, Cong Wang wrote:
> Hmm? I think nfc_llcp_send_ui_frame() needs to do some fragmention
> with this temporary memory, or you are saying msg_iter has some
> API available to seek the pointer? Even if so, it doesn't look like
> suitable for -stable.
>
memcpy_from_m
On 01/27/2016 11:11 AM, Ben Greear wrote:
On 01/27/2016 10:55 AM, Peter Oh wrote:
Abstraction layer for vdev subtype is added to solve
subtype mismatch and to give flexible compatibility
among different firmware revisions.
For instance, 10.2 and 10.4 firmware has different
definition of their
On 26-1-2016 14:56, Johannes Berg wrote:
> On Tue, 2016-01-26 at 14:06 +0100, Arend van Spriel wrote:
>>
>> + * @behaviour: requested BSS selection behaviour.
>> + * @param: parameters for requestion behaviour.
>> + * @band_pref: preferred band for
>> %NL80211_BSS_SELECT_ATTR_BAND_PREF.
>> + *
On 01/27/2016 11:39 AM, Bob Copeland wrote:
On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote:
Split Mesh service to 11s Mesh and non-11s Mesh according to
firmware service bit to help users distinguish 11s Mesh from
non 11s Mesh.
And add abstraction layer for vdev subtype to solve subty
Hi all,
I'm having trouble with driver r8xxxu. My device has a realtek usb
wifi+bt combo (0bda:0724) built-in.
I can connect to a wifi network but if I open something that uses
connections the driver stops working with a mac80211 crash message.
OS used is Android-x86 with kernel 4.4.0.
I'm also
Hi Glen,
On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo wrote:
> Dan Carpenter writes:
>
>> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrote:
>>> Hi All,
>>>
>>> I'm helping Greg do a bit of cleanup in the staging tree, I noticed that
>>> wlan-ng driver is maybe ready to be moved
t; [also build test ERROR on v4.5-rc1 next-20160125]
>>> [if your patch is applied to the wrong git tree, please drop us a note to
>>> help improving the system]
>>>
>>> url:
>>> https://github.com/0day-ci/linux/commits/Rafa-Mi-ecki/brcmfmac-support-for-
On Thu, Jan 28, 2016 at 09:48:16AM +1100, Julian Calaby wrote:
> Hi Glen,
>
> On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo wrote:
> > Dan Carpenter writes:
> >
> >> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrote:
> >>> Hi All,
> >>>
> >>> I'm helping Greg do a bit of cleanup i
Hi Chris,
On Thu, Jan 28, 2016 at 2:46 AM, Chris Bainbridge
wrote:
> Use kzalloc instead of kmalloc for struct tid_ampdu_rx. Fixes:
>
> [7.976605] UBSAN: Undefined behaviour in net/mac80211/rx.c:932:29
> [7.976608] load of value 2 is not a valid value for type '_Bool'
> [7.976611] CPU
Hi Greg,
On Thu, Jan 28, 2016 at 10:07 AM, Greg KH wrote:
> On Thu, Jan 28, 2016 at 09:48:16AM +1100, Julian Calaby wrote:
>> Hi Glen,
>>
>> On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo wrote:
>> > Dan Carpenter writes:
>> >
>> >> On Mon, Jan 25, 2016 at 01:16:56PM +0100, Ksenija Stanojević wrot
On Thu, Jan 28, 2016 at 10:28:38AM +1100, Julian Calaby wrote:
> Hi Greg,
>
> On Thu, Jan 28, 2016 at 10:07 AM, Greg KH wrote:
> > On Thu, Jan 28, 2016 at 09:48:16AM +1100, Julian Calaby wrote:
> >> Hi Glen,
> >>
> >> On Thu, Jan 28, 2016 at 5:27 AM, Kalle Valo wrote:
> >> > Dan Carpenter write
problem: it does not connect to any wifi network you can see the time out on
dmesg
>lsusb
Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
802.11n WLAN Adapter
>iwconfig
wlp0s20u1 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-
Some callers of strtobool were passing a pointer to unterminated strings.
This fixes the issue and consolidates some logic in cifs.
Signed-off-by: Kees Cook
Cc: Amitkumar Karwar
Cc: Nishant Sarmukadam
Cc: Kalle Valo
Cc: Steve French
Cc: linux-c...@vger.kernel.org
---
This is preparation for a
On Wed, 2016-01-27 at 16:45 -0800, Kees Cook wrote:
> Some callers of strtobool were passing a pointer to unterminated strings.
> This fixes the issue and consolidates some logic in cifs.
This may be incomplete as it duplicates the behavior for
the old number of characters, but this is not a solut
On Wed, Jan 27, 2016 at 4:58 PM, Joe Perches wrote:
> On Wed, 2016-01-27 at 16:45 -0800, Kees Cook wrote:
>> Some callers of strtobool were passing a pointer to unterminated strings.
>> This fixes the issue and consolidates some logic in cifs.
>
> This may be incomplete as it duplicates the behavi
On Thu, Jan 28, 2016 at 5:53 AM, Peter Oh wrote:
>
> On 01/27/2016 11:39 AM, Bob Copeland wrote:
>>
>> On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote:
>>>
>>> Split Mesh service to 11s Mesh and non-11s Mesh according to
>>> firmware service bit to help users distinguish 11s Mesh from
>>>
Dear Sir/Madam,
Clean tested working pulls CPUs and QTYs in stock.
115 X X5650
65 X E5410
75 X X5660
145 X E5530
100 X E5645
40 X X5680
75 X X5690
Brand new sealed IP phones and QTYs in stock.
55 x CP-7937G
77 x CP-7942G
54 x CP-7945G
75 x CP-7962G
..
45 x Avaya 9630
6
On 01/27/2016 06:04 PM, Yeoh Chun-Yeow wrote:
On Thu, Jan 28, 2016 at 5:53 AM, Peter Oh wrote:
On 01/27/2016 11:39 AM, Bob Copeland wrote:
On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote:
Split Mesh service to 11s Mesh and non-11s Mesh according to
firmware service bit to help users
Hmm. So my daughter has a little Gigabyte Brix that has rtl8821ae
wireless in it. Yeah, nasty, I know, but it has actually worked
reasonably well.
.. except now I upgraded the nearest access point, and now wireless on
that machine no longer works.
Or rather, it actually *does* work in the sense t
There are over-commenting in the coreconfigurator.c file and most of them
are not helpful to explain what the code does and generate 80 ending
line over warnings. So, all of comments are removed in this patch and the
comments will later be added if necessary with the preferred Linux style.
Signed-
This patch renames u16RxLen variable to rx_len to avoid camelcase.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers/staging/wilc1000
This patch renames u16TagParamOffset variable to tag_param_offset
to avoid camelcase.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers/staging/wilc
This patch renames u16index variable to index
to remove the prefix variable defined name.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers
This patch renames to avoid camelcase, changes follow are:
- pu8Buffer to buffer
- u32BufferLen to buffer_len
- ppstrConnectRespInfo to ret_connect_resp_info
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 16
drivers/staging/wilc1000/coreconfigurator
This patch renames to avoid camelcase, changes follow are:
- pstrConnectRespInfo to connect_resp_info
- u16AssocRespLen to assoc_resp_len
- pu8IEs to ies
- u16IEsLen to ies_len
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 34 ++---
1 file c
This patch renames to avoid camelcase, changes follow are:
- pstrNetworkInfo to network_info
- u8MsgType to msg_type
- u8MsgID to msg_id
- u16MsgLen to msg_len
- u16WidID to wid_id
- u16WidLen to wid_len
- pu8WidVal to wid_val
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfig
This patch renames to avoid camelcase, changes follow are:
- pstrConnectRespInfo to connect_resp_info
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 14 +++---
drivers/staging/wilc1000/coreconfigurator.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
This patch renames variable s32Error to result
to avoid CamelCase naming convention.
Also, remove the unused variable s32Error and replace with direct return.
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 19 +--
1 file changed, 9 insertions(+), 10 dele
This patch renames to avoid camelcase, changes follow are:
- pu8MsgBuffer to msg_buffer
- ppstrNetworkInfo to ret_network_info
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 16
drivers/staging/wilc1000/coreconfigurator.h | 2 +-
2 files changed, 9 i
This patch renames to avoid camelcase, changes follow are:
- pstrNetworkInfo to network_info
Signed-off-by: Leo Kim
---
drivers/staging/wilc1000/coreconfigurator.c | 14 +++---
drivers/staging/wilc1000/coreconfigurator.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions(-)
diff --
This patch renames to avoid camelcase, changes follow are:
- pu8TimElm to tim_elm
- pu8IEs to ies
- u16IEsLen to ies_len
- u32Tsf_Lo to tsf_lo
- u32Tsf_Hi to tsf_hi
And, remove the prefix variable defined name, below are:
- u8index to index
- pu8msa to msa
Signed-off-by: Leo Kim
---
driv
>
> 2016-01-27 2:46 GMT-05:00 Grumbach, Emmanuel
> :
> >> Hi
> >>
> >> 2016-01-26 3:28 GMT-05:00 Grumbach, Emmanuel
> >> :
> >> >
> >> >
> >> > On 01/26/2016 12:20 AM, Nikolay Martynov wrote:
> >> >> It looks like sometimes firmware returns zero for chain noise and
> >> >> signal during calibratio
79 matches
Mail list logo