Hi Joel,
Unfortunately we don't have full support for ToF on the mainline kernel
yet. But you can try to use one of our Core releases (which is a
backports-based tree) that you can find here:
You could try the release/Core30 branch, for example.
--
Cheers,
Luca.
On Thu, 2017-09-21 at 21:35
On Tue, Oct 03, 2017 at 07:33:08PM -0300, Marcelo Ricardo Leitner wrote:
> On Tue, Oct 03, 2017 at 10:25:22AM +0800, Jia-Ju Bai wrote:
> > The SCTP program may sleep under a spinlock, and the function call path is:
> > sctp_generate_t3_rtx_event (acquire the spinlock)
> > sctp_do_sm
> >
On Tue, Oct 03, 2017 at 01:26:43PM +0800, Herbert Xu wrote:
> On Mon, Oct 02, 2017 at 09:18:24PM -0700, Andy Lutomirski wrote:
> > > On Oct 2, 2017, at 7:25 PM, Jia-Ju Bai wrote:
> > >
> > > The SCTP program may sleep under a spinlock, and the function call path
> > > is:
>
On Tue, Oct 03, 2017 at 10:25:22AM +0800, Jia-Ju Bai wrote:
> The SCTP program may sleep under a spinlock, and the function call path is:
> sctp_generate_t3_rtx_event (acquire the spinlock)
> sctp_do_sm
> sctp_side_effects
> sctp_cmd_interpreter
> sctp_make_init_ack
>
From: Ben Greear
This works around a problem we see when sometimes the wifi NIC does
not respond the first time. This seems to happen especially often on
some of the 9984 NICs in mid-range platforms.
Signed-off-by: Ben Greear
---
v2: Change
From: Ben Greear
This way, we can apply the values when the NIC does come up.
Signed-off-by: Ben Greear
---
drivers/net/wireless/ath/ath10k/hw.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git
On Tue, 3 Oct 2017, Bjorn Helgaas wrote:
> On Tue, Oct 03, 2017 at 11:07:58PM +0200, Thomas Gleixner wrote:
> > On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> > > On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> > > > On Mon, 2 Oct 2017, Daniel Drake wrote:
> > > > 2) The affinity setting of straight
On Tue, Oct 03, 2017 at 11:07:58PM +0200, Thomas Gleixner wrote:
> On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> > On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> > > On Mon, 2 Oct 2017, Daniel Drake wrote:
> > > 2) The affinity setting of straight MSI interrupts (w/o remapping) on
> > > x86
> > >
On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> On Mon, 2 Oct 2017, Thomas Gleixner wrote:
> > On Mon, 2 Oct 2017, Daniel Drake wrote:
> > 2) The affinity setting of straight MSI interrupts (w/o remapping) on x86
> > requires to make the affinity change from the interrupt context of the
> >
On 10/03/2017 11:17 AM, Ben Greear wrote:
We are seeing deadlocks related to wifi in our 4.13.3+ kernels,
so I enabled lockdep and immediately saw this. Anyone know if this
is a known issue? Otherwise, I guess it could be related to some local
patch I have added...
I think I found the fix in
We are seeing deadlocks related to wifi in our 4.13.3+ kernels,
so I enabled lockdep and immediately saw this. Anyone know if this
is a known issue? Otherwise, I guess it could be related to some local
patch I have added...
[ 476.172823]
[
The Allwinner XR819 SDIO Wi-Fi chip supports an out-of-band interrupt line,
and the in-band interrupt is also supported.
However the current out-of-tree driver uses the out-of-band interrupt by
default.
This patchset adds the device tree binding for the chip as well as the
out-of-band interrupt,
Allwinner XR819 is a SDIO Wi-Fi chip, which has the functionality to use
an out-of-band interrupt pin instead of SDIO in-band interrupt.
Add the device tree binding of this chip, in order to make it possible
to add this interrupt pin to device trees.
Signed-off-by: Icenowy Zheng
From: Sergey Matyukevich
The Orange Pi Zero board has Allwinner XR819 SDIO wifi chip. The board
dts file provides a node enabling mmc1 controller, and a out-of-band
interrupt line of the chip is also connected, although the chip also
supports in-band interrupt.
The current
On Mon, Oct 2, 2017 at 10:26 PM, Herbert Xu wrote:
> On Mon, Oct 02, 2017 at 09:18:24PM -0700, Andy Lutomirski wrote:
>> > On Oct 2, 2017, at 7:25 PM, Jia-Ju Bai wrote:
>> >
>> > The SCTP program may sleep under a spinlock, and the function call
From: Douglas Anderson
The sta_list_spinlock looks to be used to control locking of the
list. Specifically when someone has the lock they may be allowed
to modify or delete elements of the list.
That implies that we shouldn't access the fields of the elements
returned by
From: Douglas Anderson
There's absolutely no reason to check to see if a list is empty
before iterating through it. It's just like writing code like
this:
if (count != 0) {
for (i = 0; i < count; i++) {
...
}
}
The loop will already be avoided if "count == 0"
On Tue, Oct 3, 2017 at 4:22 AM, Jérémy Lefaure
wrote:
> On Mon, 2 Oct 2017 16:07:36 +0300
> Andy Shevchenko wrote:
>
>> > + {_lut_core0_rev0, ARRAY_SIZE(gainctrl_lut_core0_rev0),
>> > 26, 192,
>> > +32},
>>
>> For all such
On Mon, 2017-10-02 at 23:09 +0200, Arend van Spriel wrote:
> On 29-09-17 14:21, Johannes Berg wrote:
> > From: Avraham Stern
> >
> > Add an event that indicates that a connection is authorized
> > (i.e. the 4 way handshake was performed by the driver). This event
> >
19 matches
Mail list logo