On 2017/11/7 23:48, Jason Gunthorpe wrote:
> On Tue, Nov 07, 2017 at 10:45:29AM +0800, Wei Hu (Xavier) wrote:
>
>> We reconstruct the code as below:
>> It replaces dma_alloc_coherent with __get_free_pages and
>> dma_map_single functions. So, we can vmap serveral ptrs returned by
On 2017/11/7 23:48, Jason Gunthorpe wrote:
> On Tue, Nov 07, 2017 at 10:45:29AM +0800, Wei Hu (Xavier) wrote:
>
>> We reconstruct the code as below:
>> It replaces dma_alloc_coherent with __get_free_pages and
>> dma_map_single functions. So, we can vmap serveral ptrs returned by
Hi,
On 08/11/2017 at 17:16:15 +0800, Baolin Wang wrote:
> +static int sprd_rtc_read_time(struct device *dev, struct rtc_time *tm)
> +{
> + struct sprd_rtc *rtc = dev_get_drvdata(dev);
> + time64_t secs;
> + int ret;
> +
I would have expected a check for SPRD_RTC_POWER_RESET_FLAG
Hi,
On 08/11/2017 at 17:16:15 +0800, Baolin Wang wrote:
> +static int sprd_rtc_read_time(struct device *dev, struct rtc_time *tm)
> +{
> + struct sprd_rtc *rtc = dev_get_drvdata(dev);
> + time64_t secs;
> + int ret;
> +
I would have expected a check for SPRD_RTC_POWER_RESET_FLAG
On 2017/11/7 23:58, Christoph Hellwig wrote:
> On Tue, Nov 07, 2017 at 08:48:38AM -0700, Jason Gunthorpe wrote:
>> Can't you just use vmalloc and dma_map that? Other drivers follow that
>> approach..
> You can't easily due to the flushing requirements. We used to do that
> in XFS and it led to
On 2017/11/7 23:58, Christoph Hellwig wrote:
> On Tue, Nov 07, 2017 at 08:48:38AM -0700, Jason Gunthorpe wrote:
>> Can't you just use vmalloc and dma_map that? Other drivers follow that
>> approach..
> You can't easily due to the flushing requirements. We used to do that
> in XFS and it led to
On Wed, Nov 08, 2017 at 01:55:05PM +0800, Greentime Hu wrote:
> +static int restore_sigframe(struct pt_regs *regs,
> + struct rt_sigframe __user * sf)
> +{
[snip]
> + err |= !valid_user_regs(regs);
IDGI... Where do you modify ->ipsw at all and how can
On Wed, Nov 08, 2017 at 01:55:05PM +0800, Greentime Hu wrote:
> +static int restore_sigframe(struct pt_regs *regs,
> + struct rt_sigframe __user * sf)
> +{
[snip]
> + err |= !valid_user_regs(regs);
IDGI... Where do you modify ->ipsw at all and how can
Add my name to the list.
Signed-off-by: Kees Cook
---
Documentation/process/kernel-enforcement-statement.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/process/kernel-enforcement-statement.rst
Add my name to the list.
Signed-off-by: Kees Cook
---
Documentation/process/kernel-enforcement-statement.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/process/kernel-enforcement-statement.rst
b/Documentation/process/kernel-enforcement-statement.rst
index
On 2017/11/7 14:32, Leon Romanovsky wrote:
> On Tue, Nov 07, 2017 at 10:45:29AM +0800, Wei Hu (Xavier) wrote:
>>
>> On 2017/11/1 20:26, Robin Murphy wrote:
>>> On 01/11/17 07:46, Wei Hu (Xavier) wrote:
On 2017/10/12 20:59, Robin Murphy wrote:
> On 12/10/17 13:31, Wei Hu (Xavier) wrote:
On 2017/11/7 14:32, Leon Romanovsky wrote:
> On Tue, Nov 07, 2017 at 10:45:29AM +0800, Wei Hu (Xavier) wrote:
>>
>> On 2017/11/1 20:26, Robin Murphy wrote:
>>> On 01/11/17 07:46, Wei Hu (Xavier) wrote:
On 2017/10/12 20:59, Robin Murphy wrote:
> On 12/10/17 13:31, Wei Hu (Xavier) wrote:
>
> On Mon, Oct 30, 2017 at 07:50:09AM +, 冯锐 wrote:
> > Hi Greg
> >
> > I'm sorry to bother you, but can you help to review this patch and the patch
> below if you have time?
> > https://patchwork.kernel.org/patch/10026543/
>
> Hm, I don't use patchwork, so I don't know what to say about
>
> On Mon, Oct 30, 2017 at 07:50:09AM +, 冯锐 wrote:
> > Hi Greg
> >
> > I'm sorry to bother you, but can you help to review this patch and the patch
> below if you have time?
> > https://patchwork.kernel.org/patch/10026543/
>
> Hm, I don't use patchwork, so I don't know what to say about
On 2017年11月08日 05:38, Kees Cook wrote:
> The mutex in sysctl_vm_numa_stat_handler() needs to be a global static, not
> a stack variable, otherwise it doesn't serve any purpose. Also, reading the
> file with CONFIG_LOCKDEP=y will complain:
>
It's my mistake. Kees, thanks for catching it.
> [
On 2017年11月08日 05:38, Kees Cook wrote:
> The mutex in sysctl_vm_numa_stat_handler() needs to be a global static, not
> a stack variable, otherwise it doesn't serve any purpose. Also, reading the
> file with CONFIG_LOCKDEP=y will complain:
>
It's my mistake. Kees, thanks for catching it.
> [
On Wed, Nov 8, 2017 at 11:43 AM, Laura Abbott wrote:
> On 11/07/2017 09:38 AM, Kees Cook wrote:
>>
>> As described in the final patch:
>>
>> Nearly all modern compilers support a stack-protector option, and nearly
>> all modern distributions enable the kernel stack-protector,
On Wed, Nov 8, 2017 at 11:43 AM, Laura Abbott wrote:
> On 11/07/2017 09:38 AM, Kees Cook wrote:
>>
>> As described in the final patch:
>>
>> Nearly all modern compilers support a stack-protector option, and nearly
>> all modern distributions enable the kernel stack-protector, so enabling
>> this
From: Rui Feng
Add support for new chip rts5260.
In order to support rts5260, the definitions of
some internal registers and workflow have to be
modified and are different from its predecessors
and OCP function is added for RTS5260. So we need
this patch to ensure
From: Rui Feng
Add support for new chip rts5260.
In order to support rts5260, the definitions of
some internal registers and workflow have to be
modified and are different from its predecessors
and OCP function is added for RTS5260. So we need
this patch to ensure RTS5260 can work.
From: Rui Feng
Because Realtek card reader drivers are pcie and usb drivers,
and they bridge mmc subsystem and memstick subsystem, they are
not mfd drivers. Greg and Lee Jones had a discussion about
where to put the drivers, the result is that misc is a good
place for
From: Rui Feng
Because Realtek card reader drivers are pcie and usb drivers,
and they bridge mmc subsystem and memstick subsystem, they are
not mfd drivers. Greg and Lee Jones had a discussion about
where to put the drivers, the result is that misc is a good
place for them, so I move all files
On Wed, Nov 8, 2017 at 2:30 PM, Rasmus Villemoes
wrote:
> Consider these strictly RFC/POC.
>
> I tried resurrecting my format_template plugin from two years ago, and
> it rebased pretty cleanly. It also compiles with gcc 6.3, and has the
> expected effect when one tries
On Wed, Nov 8, 2017 at 2:30 PM, Rasmus Villemoes
wrote:
> Consider these strictly RFC/POC.
>
> I tried resurrecting my format_template plugin from two years ago, and
> it rebased pretty cleanly. It also compiles with gcc 6.3, and has the
> expected effect when one tries to trigger it, so it seems
Add a check warning if SPDX-License-Identifier tags are not used in
newly added files.
Cc: Andy Whitcroft
Cc: Joe Perches
Cc: Greg Kroah-Hartman
Signed-off-by: Rob Herring
---
I rewrote my previous version to
Add a check warning if SPDX-License-Identifier tags are not used in
newly added files.
Cc: Andy Whitcroft
Cc: Joe Perches
Cc: Greg Kroah-Hartman
Signed-off-by: Rob Herring
---
I rewrote my previous version to check more than just dts files. It also
now looks for a tag in added files rather
On Wed, Nov 8, 2017 at 2:30 PM, Rasmus Villemoes
wrote:
> We have a few places in the kernel where a *printf function is used with
> a non-constant format string, making the ordinary static type checking
> done by gcc et al. impossible. Some things can still be caught at
On Wed, Nov 8, 2017 at 2:30 PM, Rasmus Villemoes
wrote:
> We have a few places in the kernel where a *printf function is used with
> a non-constant format string, making the ordinary static type checking
> done by gcc et al. impossible. Some things can still be caught at build
> time with
On Wed, Nov 8, 2017 at 4:07 PM, Minchan Kim wrote:
> Hi,
>
> On Wed, Nov 08, 2017 at 09:37:40AM -0800, Shakeel Butt wrote:
>> In our production, we have observed that the job loader gets stuck for
>> 10s of seconds while doing mount operation. It turns out that it was
>> stuck
On Wed, Nov 8, 2017 at 4:07 PM, Minchan Kim wrote:
> Hi,
>
> On Wed, Nov 08, 2017 at 09:37:40AM -0800, Shakeel Butt wrote:
>> In our production, we have observed that the job loader gets stuck for
>> 10s of seconds while doing mount operation. It turns out that it was
>> stuck in
Hello,
Can anyone please try add support for controlling keyboard backlight
via sysfs on Hewlett-Packard notebooks?
Maybe in a similar way as this last year patch for Thinkpad?
https://lkml.org/lkml/2015/12/24/295
BTW: This functionality is already supported (minimaly) on Apple,
ASUS, Dell,
Hello,
Can anyone please try add support for controlling keyboard backlight
via sysfs on Hewlett-Packard notebooks?
Maybe in a similar way as this last year patch for Thinkpad?
https://lkml.org/lkml/2015/12/24/295
BTW: This functionality is already supported (minimaly) on Apple,
ASUS, Dell,
On Wed, Nov 08, 2017 at 12:51:20PM +0100, Greg KH wrote:
> On Wed, Nov 08, 2017 at 11:16:43AM +0100, Petr Mladek wrote:
> > On Wed 2017-11-08 14:37:37, Tobin C. Harding wrote:
> > > Developers may not have the time (or inclination) to investigate script
> > > output. This information is, however,
On Wed, Nov 08, 2017 at 12:51:20PM +0100, Greg KH wrote:
> On Wed, Nov 08, 2017 at 11:16:43AM +0100, Petr Mladek wrote:
> > On Wed 2017-11-08 14:37:37, Tobin C. Harding wrote:
> > > Developers may not have the time (or inclination) to investigate script
> > > output. This information is, however,
On Thu, Nov 9, 2017 at 4:02 AM, Christian Brauner
wrote:
> On Wed, Nov 08, 2017 at 03:09:59AM -0800, Mahesh Bandewar (महेश बंडेवार)
> wrote:
>> Sorry folks I was traveling and seems like lot happened on this thread. :p
>>
>> I will try to response few of these
On Thu, Nov 9, 2017 at 4:02 AM, Christian Brauner
wrote:
> On Wed, Nov 08, 2017 at 03:09:59AM -0800, Mahesh Bandewar (महेश बंडेवार)
> wrote:
>> Sorry folks I was traveling and seems like lot happened on this thread. :p
>>
>> I will try to response few of these comments selectively -
>>
>> > The
Hello Steven,
On (11/08/17 09:29), Steven Rostedt wrote:
> On Wed, 8 Nov 2017 14:19:55 +0900
> Sergey Senozhatsky wrote:
>
> > the change goes further. I did express some of my concerns during the KS,
> > I'll just bring them to the list.
> >
> >
> > we now
Hello Steven,
On (11/08/17 09:29), Steven Rostedt wrote:
> On Wed, 8 Nov 2017 14:19:55 +0900
> Sergey Senozhatsky wrote:
>
> > the change goes further. I did express some of my concerns during the KS,
> > I'll just bring them to the list.
> >
> >
> > we now always shift printing from a save -
On Wed, Nov 8, 2017 at 8:00 AM, Arnd Bergmann wrote:
> I noticed that __getnstimeofday() is a rather odd interface, with
> a number of quirks:
>
> - The caller may come from NMI context, but the implementation is not NMI safe
> - The calling conventions are different from any other
On Wed, Nov 8, 2017 at 8:00 AM, Arnd Bergmann wrote:
> I noticed that __getnstimeofday() is a rather odd interface, with
> a number of quirks:
>
> - The caller may come from NMI context, but the implementation is not NMI safe
> - The calling conventions are different from any other timekeeping
On Wed, Nov 08, 2017 at 11:42:21AM +0100, Petr Mladek wrote:
> On Wed 2017-11-08 14:37:36, Tobin C. Harding wrote:
> > Currently script just dumps all results found. Potentially, this risks
> > loosing single results among multiple duplicate results. We need some
> > way of restricting duplicates
On Wed, Nov 08, 2017 at 11:42:21AM +0100, Petr Mladek wrote:
> On Wed 2017-11-08 14:37:36, Tobin C. Harding wrote:
> > Currently script just dumps all results found. Potentially, this risks
> > loosing single results among multiple duplicate results. We need some
> > way of restricting duplicates
Uprobe is a tracing mechanism for userspace programs.
Typical uprobe will incur overhead of two traps.
First trap is caused by replaced trap insn, and
the second trap is to execute the original displaced
insn in user space.
To reduce the overhead, kernel provides hooks
for architectures to
Uprobe is a tracing mechanism for userspace programs.
Typical uprobe will incur overhead of two traps.
First trap is caused by replaced trap insn, and
the second trap is to execute the original displaced
insn in user space.
To reduce the overhead, kernel provides hooks
for architectures to
Remove CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE and automatically calculate
the amount of CVMSEG space needed.
1st 128-bytes: Use by IOBDMA
2nd 128-bytes: Reserved by kernel for scratch/TLS emulation.
3rd 128-bytes: OCTEON-III LMTLINE
New config variable CONFIG_CAVIUM_OCTEON_EXTRA_CVMSEG provisions
Remove CONFIG_CAVIUM_OCTEON_CVMSEG_SIZE and automatically calculate
the amount of CVMSEG space needed.
1st 128-bytes: Use by IOBDMA
2nd 128-bytes: Reserved by kernel for scratch/TLS emulation.
3rd 128-bytes: OCTEON-III LMTLINE
New config variable CONFIG_CAVIUM_OCTEON_EXTRA_CVMSEG provisions
Previous patch sets USE_ASYNC_IOBDMA to 1 unconditionally. Remove
USE_ASYNC_IOBDMA from all if statements. Remove dead code caused by
the change.
Signed-off-by: David Daney
---
drivers/staging/octeon/ethernet-defines.h | 6 ---
drivers/staging/octeon/ethernet-rx.c
Previous patch sets USE_ASYNC_IOBDMA to 1 unconditionally. Remove
USE_ASYNC_IOBDMA from all if statements. Remove dead code caused by
the change.
Signed-off-by: David Daney
---
drivers/staging/octeon/ethernet-defines.h | 6 ---
drivers/staging/octeon/ethernet-rx.c | 25 -
From: Carlos Munoz
Add a global resource manager to manage tagged pointers within
bootmem allocated memory. This is used by various functional
blocks in the Octeon core like the FPA, Ethernet nexus, etc.
Signed-off-by: Carlos Munoz
Signed-off-by: Steven J.
Signed-off-by: David Daney
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9a24f56e0451..142af33adc35 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3212,6 +3212,12 @@ W: http://www.cavium.com
S:
From: Carlos Munoz
>From the hardware user manual: "The FPA is a unit that maintains
pools of pointers to free L2/DRAM memory. To provide QoS, the pools
are referenced indirectly through 1024 auras. Both core software
and hardware units allocate and free pointers."
From: Carlos Munoz
Add a global resource manager to manage tagged pointers within
bootmem allocated memory. This is used by various functional
blocks in the Octeon core like the FPA, Ethernet nexus, etc.
Signed-off-by: Carlos Munoz
Signed-off-by: Steven J. Hill
Signed-off-by: David Daney
---
Signed-off-by: David Daney
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9a24f56e0451..142af33adc35 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3212,6 +3212,12 @@ W: http://www.cavium.com
S: Supported
F:
From: Carlos Munoz
>From the hardware user manual: "The FPA is a unit that maintains
pools of pointers to free L2/DRAM memory. To provide QoS, the pools
are referenced indirectly through 1024 auras. Both core software
and hardware units allocate and free pointers."
Signed-off-by: Carlos Munoz
From: Carlos Munoz
Add bindings for Common Ethernet Interface (BGX) block.
Signed-off-by: Carlos Munoz
Signed-off-by: Steven J. Hill
Signed-off-by: David Daney
---
From: Carlos Munoz
Add bindings for Common Ethernet Interface (BGX) block.
Signed-off-by: Carlos Munoz
Signed-off-by: Steven J. Hill
Signed-off-by: David Daney
---
.../devicetree/bindings/net/cavium-bgx.txt | 61 ++
1 file changed, 61 insertions(+)
create mode
From: Carlos Munoz
LMTDMA/LMTST operations move data between cores and I/O devices:
* LMTST operations can send an address and a variable length
(up to 128 bytes) of data to an I/O device.
* LMTDMA operations can send an address and a variable length
(up to 128) of data
We are adding the Cavium OCTEON-III network driver. But since
interacting with the input and output queues is done via special CPU
local memory, we also need to add support to the MIPS/Octeon
architecture code. Aren't SoCs nice in this way?
The first six patches add the SoC support needed by
We are adding the Cavium OCTEON-III network driver. But since
interacting with the input and output queues is done via special CPU
local memory, we also need to add support to the MIPS/Octeon
architecture code. Aren't SoCs nice in this way?
The first six patches add the SoC support needed by
From: Carlos Munoz
LMTDMA/LMTST operations move data between cores and I/O devices:
* LMTST operations can send an address and a variable length
(up to 128 bytes) of data to an I/O device.
* LMTDMA operations can send an address and a variable length
(up to 128) of data to the I/O device
Arnd, Olof,
Neil Armstrong writes:
> In the case the VPU power domain has been powered on by the bootloader
> and no driver are attached to this power domain, the genpd will power it
> off after a certain amount of time, but the clocks hasn't been enabled
> by the
Arnd, Olof,
Neil Armstrong writes:
> In the case the VPU power domain has been powered on by the bootloader
> and no driver are attached to this power domain, the genpd will power it
> off after a certain amount of time, but the clocks hasn't been enabled
> by the kernel itself and the
"Tobin C. Harding" writes:
> On Wed, Nov 08, 2017 at 11:10:56PM +1100, Michael Ellerman wrote:
>> "Tobin C. Harding" writes:
> [snip]
>
> Hi Michael,
>
> I'm working an adding support for ppc64 to leaking_addresses.pl, I've
> added the kernel address regular
"Tobin C. Harding" writes:
> On Wed, Nov 08, 2017 at 11:10:56PM +1100, Michael Ellerman wrote:
>> "Tobin C. Harding" writes:
> [snip]
>
> Hi Michael,
>
> I'm working an adding support for ppc64 to leaking_addresses.pl, I've
> added the kernel address regular expression that you suggested.
On Fri, Oct 27, 2017 at 05:11:24PM +0100, Gabriele Paoloni wrote:
> From: "zhichang.yuan"
>
> The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in
> I/O port addresses. This patch implements the LPC host controller driver
> which perform the I/O
On Fri, Oct 27, 2017 at 05:11:24PM +0100, Gabriele Paoloni wrote:
> From: "zhichang.yuan"
>
> The low-pin-count(LPC) interface of Hip06/Hip07 accesses the peripherals in
> I/O port addresses. This patch implements the LPC host controller driver
> which perform the I/O operations on the
On Wed, Nov 8, 2017 at 1:08 PM, Ola Næss Kaldestad wrote:
> Removed unnecessary else statement after return.
>
> Signed-off-by: Ola N. Kaldestad
> ---
> kernel/sysctl.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/sysctl.c
On Wed, Nov 8, 2017 at 1:08 PM, Ola Næss Kaldestad wrote:
> Removed unnecessary else statement after return.
>
> Signed-off-by: Ola N. Kaldestad
> ---
> kernel/sysctl.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/sysctl.c b/kernel/sysctl.c
> index
As of 4.13.11 (and also with 4.14-rc) we have an issue where when
serving nfs4 sometimes we get the following BUG. When this bug happens,
it usually also causes the motherboard to no longer POST until we
externally re-flash the BIOS (using the BMC web interface). If a
motherboard does not have an
As of 4.13.11 (and also with 4.14-rc) we have an issue where when
serving nfs4 sometimes we get the following BUG. When this bug happens,
it usually also causes the motherboard to no longer POST until we
externally re-flash the BIOS (using the BMC web interface). If a
motherboard does not have an
2017-11-09 0:26 GMT+08:00 Radim Krčmář :
> 2017-11-06 04:17-0800, Wanpeng Li:
>> From: Wanpeng Li
>>
>> watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [qemu-system-x86:10185]
>> CPU: 6 PID: 10185 Comm: qemu-system-x86 Tainted: G OE
>>
2017-11-09 0:26 GMT+08:00 Radim Krčmář :
> 2017-11-06 04:17-0800, Wanpeng Li:
>> From: Wanpeng Li
>>
>> watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [qemu-system-x86:10185]
>> CPU: 6 PID: 10185 Comm: qemu-system-x86 Tainted: G OE
>> 4.14.0-rc4+ #4
>> RIP:
On Wed, Nov 08, 2017 at 01:55:06PM +0800, Greentime Hu wrote:
> +#define __range_ok(addr, size) (size <= get_fs() && addr <= (get_fs() -size))
> +
> +#define access_ok(type, addr, size) \
> + __range_ok((unsigned long)addr, (unsigned long)size)
> +#define
On Wed, Nov 08, 2017 at 01:55:06PM +0800, Greentime Hu wrote:
> +#define __range_ok(addr, size) (size <= get_fs() && addr <= (get_fs() -size))
> +
> +#define access_ok(type, addr, size) \
> + __range_ok((unsigned long)addr, (unsigned long)size)
> +#define
2017-11-09 9:11 GMT+09:00 Masahiro Yamada :
> 2017-11-09 1:51 GMT+09:00 Rob Herring :
>> On Mon, Nov 6, 2017 at 5:00 AM, Masahiro Yamada
>> wrote:
>>> 2017-11-06 19:41 GMT+09:00 James Hogan :
2017-11-09 9:11 GMT+09:00 Masahiro Yamada :
> 2017-11-09 1:51 GMT+09:00 Rob Herring :
>> On Mon, Nov 6, 2017 at 5:00 AM, Masahiro Yamada
>> wrote:
>>> 2017-11-06 19:41 GMT+09:00 James Hogan :
Hi,
On Sun, Nov 05, 2017 at 11:11:38PM +0900, Masahiro Yamada wrote:
> +CC Ralf
2017-11-09 5:47 GMT+08:00 Jim Mattson :
> I realize now that there are actually many other problems with
> deferring some control field checks to the hardware VM-entry of
> vmcs02. When there is an invalid control field, the vCPU should just
> fall through to the next
2017-11-09 5:47 GMT+08:00 Jim Mattson :
> I realize now that there are actually many other problems with
> deferring some control field checks to the hardware VM-entry of
> vmcs02. When there is an invalid control field, the vCPU should just
> fall through to the next instruction, without any
On Tue, 7 Nov 2017 18:14:56 +0100
Jessica Yu wrote:
> +++ Steven Rostedt [03/11/17 10:03 -0400]:
> >On Thu, 2 Nov 2017 17:33:33 +0100
> >Jessica Yu wrote:
> >
> >> Improve error handling when arming ftrace-based kprobes. Specifically, if
> >> we fail to arm a
On Tue, 7 Nov 2017 18:14:56 +0100
Jessica Yu wrote:
> +++ Steven Rostedt [03/11/17 10:03 -0400]:
> >On Thu, 2 Nov 2017 17:33:33 +0100
> >Jessica Yu wrote:
> >
> >> Improve error handling when arming ftrace-based kprobes. Specifically, if
> >> we fail to arm a ftrace-based kprobe,
Similar to short circuit detection, when the ADC/DAC is saturated and
overflows poor audio quality can result and should be reported to the
user. This device support Automatic Dynamic Range Compression (DRC)
to reduce this but it is not enabled currently in this driver.
Signed-off-by: Andrew F.
Similar to short circuit detection, when the ADC/DAC is saturated and
overflows poor audio quality can result and should be reported to the
user. This device support Automatic Dynamic Range Compression (DRC)
to reduce this but it is not enabled currently in this driver.
Signed-off-by: Andrew F.
Thomas Gleixner wrote:
> > +extern int reduce_timer(struct timer_list *timer, unsigned long expires);
>
> For new timer functions we really should use the timer_()
> convention. The historic naming convention is horrible.
>
> Aside of that timer_reduce() is kinda ugly
Thomas Gleixner wrote:
> > +extern int reduce_timer(struct timer_list *timer, unsigned long expires);
>
> For new timer functions we really should use the timer_()
> convention. The historic naming convention is horrible.
>
> Aside of that timer_reduce() is kinda ugly but I failed to come
This CODEC supports being the WCLK and/or BCLK slave, add
support for this here.
Signed-off-by: Andrew F. Davis
---
sound/soc/codecs/tlv320aic31xx.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/tlv320aic31xx.c
This CODEC supports being the WCLK and/or BCLK slave, add
support for this here.
Signed-off-by: Andrew F. Davis
---
sound/soc/codecs/tlv320aic31xx.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/tlv320aic31xx.c b/sound/soc/codecs/tlv320aic31xx.c
Currently BCLK inverting is only handled when the DAI format is
DSP, but the BCLK may be inverted in any supported mode. Without
this using this CODEC in any other mode than DSP with the BCLK
inverted leads to bad sampling timing and very poor audio quality.
Fixes: e00447fafbf7 ("ASoC:
Currently BCLK inverting is only handled when the DAI format is
DSP, but the BCLK may be inverted in any supported mode. Without
this using this CODEC in any other mode than DSP with the BCLK
inverted leads to bad sampling timing and very poor audio quality.
Fixes: e00447fafbf7 ("ASoC:
Simple non-functional changes including:
* Fix header copyright tags
* Fix spelling errors
* Reformat code for easier reading
* Move some code blocks to a more natural ordering
* Remove unneeded code
* Remove assignments that are always overridden
* Normalize function return paths
This device can detect the insertion/removal of headphones and headsets.
Enable reporting this status by enabling this interrupt and forwarding
this to upper-layers if a jack has been defined.
This jack definition and the resulting operation from a jack detection
event must currently be defined
Simple non-functional changes including:
* Fix header copyright tags
* Fix spelling errors
* Reformat code for easier reading
* Move some code blocks to a more natural ordering
* Remove unneeded code
* Remove assignments that are always overridden
* Normalize function return paths
This device can detect the insertion/removal of headphones and headsets.
Enable reporting this status by enabling this interrupt and forwarding
this to upper-layers if a jack has been defined.
This jack definition and the resulting operation from a jack detection
event must currently be defined
GPIO1 control register is number 51, fix this here.
Fixes: bafcbfe429eb ("ASoC: tlv320aic31xx: Make the register values human
readable")
Signed-off-by: Andrew F. Davis
---
sound/soc/codecs/tlv320aic31xx.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
GPIO1 control register is number 51, fix this here.
Fixes: bafcbfe429eb ("ASoC: tlv320aic31xx: Make the register values human
readable")
Signed-off-by: Andrew F. Davis
---
sound/soc/codecs/tlv320aic31xx.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed, Nov 8, 2017 at 4:18 PM, Darrick J. Wong wrote:
> Agreed. I guess we'll see you for round X when you get to general
> kmalloc annotating. :)
That should be "fun". :)
-Kees
--
Kees Cook
Pixel Security
This device can optionally detect headset or microphone button presses.
Add support for this by passing this event to the jack layer.
Signed-off-by: Andrew F. Davis
---
sound/soc/codecs/tlv320aic31xx.c | 14 +-
sound/soc/codecs/tlv320aic31xx.h | 3 ++-
2 files changed,
On Wed, Nov 08, 2017 at 04:11:13PM -0800, Tony Lindgren wrote:
> * Joonsoo Kim [171109 00:05]:
> > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote:
> > > * Joonsoo Kim [171108 07:43]:
> > > > On Tue, Nov 07, 2017 at 07:48:42AM -0800,
This device can optionally detect headset or microphone button presses.
Add support for this by passing this event to the jack layer.
Signed-off-by: Andrew F. Davis
---
sound/soc/codecs/tlv320aic31xx.c | 14 +-
sound/soc/codecs/tlv320aic31xx.h | 3 ++-
2 files changed, 15
On Wed, Nov 08, 2017 at 04:11:13PM -0800, Tony Lindgren wrote:
> * Joonsoo Kim [171109 00:05]:
> > On Wed, Nov 08, 2017 at 08:34:13AM -0800, Tony Lindgren wrote:
> > > * Joonsoo Kim [171108 07:43]:
> > > > On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote:
> > > > > So it seems the
On Wed, Nov 8, 2017 at 4:18 PM, Darrick J. Wong wrote:
> Agreed. I guess we'll see you for round X when you get to general
> kmalloc annotating. :)
That should be "fun". :)
-Kees
--
Kees Cook
Pixel Security
401 - 500 of 2418 matches
Mail list logo