This patch adds bindings for wcd9335 audio codec which can support both SLIMbus
and I2S/I2C interface.
Signed-off-by: Srinivas Kandagatla
---
.../devicetree/bindings/sound/qcom,wcd9335.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644
On Mon, Jul 23, 2018 at 08:12:09AM -0700, Nathan Chancellor wrote:
> On Mon, Jul 23, 2018 at 02:25:00PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.115 release.
> > There are 28 patches in this series, all will be posted as a response
> > to this
This patch adds bindings for wcd9335 audio codec which can support both SLIMbus
and I2S/I2C interface.
Signed-off-by: Srinivas Kandagatla
---
.../devicetree/bindings/sound/qcom,wcd9335.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644
On Mon, Jul 23, 2018 at 08:12:09AM -0700, Nathan Chancellor wrote:
> On Mon, Jul 23, 2018 at 02:25:00PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.115 release.
> > There are 28 patches in this series, all will be posted as a response
> > to this
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC,
It has mulitple blocks like Soundwire controller, codec,
Codec processing engine, ClassH controller, interrupt mux.
It supports both I2S/I2C and SLIMbus audio interfaces.
This patch adds support to SLIMbus audio interface.
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC, supports
Qualcomm Technologies, Inc. (QTI) multimedia solutions, including
the MSM8996, MSM8976, and MSM8956 chipsets. It has in-build
Soundwire controller, interrupt mux. It supports both I2S/I2C and
SLIMbus audio interfaces.
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC,
It has mulitple blocks like Soundwire controller, codec,
Codec processing engine, ClassH controller, interrupt mux.
It supports both I2S/I2C and SLIMbus audio interfaces.
This patch adds support to SLIMbus audio interface.
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC, supports
Qualcomm Technologies, Inc. (QTI) multimedia solutions, including
the MSM8996, MSM8976, and MSM8956 chipsets. It has in-build
Soundwire controller, interrupt mux. It supports both I2S/I2C and
SLIMbus audio interfaces.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/wcd9335.c | 189 +
1 file changed, 189 insertions(+)
diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
index a08703681674..b185ed29d0dd 100644
--- a/sound/soc/codecs/wcd9335.c
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/wcd9335.c | 189 +
1 file changed, 189 insertions(+)
diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
index a08703681674..b185ed29d0dd 100644
--- a/sound/soc/codecs/wcd9335.c
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC,
It supports both I2S/I2C and SLIMbus audio interfaces.
On slimbus interface it supports two data lanes; 16 Tx ports
and 8 Rx ports. It has Seven DACs and nine dedicated interpolators,
Seven (six audio ADCs, and one VBAT ADC), Multibutton
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC,
It supports both I2S/I2C and SLIMbus audio interfaces.
On slimbus interface it supports two data lanes; 16 Tx ports
and 8 Rx ports. It has Seven DACs and nine dedicated interpolators,
Seven (six audio ADCs, and one VBAT ADC), Multibutton
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/wcd9335.c | 1802
1 file changed, 1802 insertions(+)
diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
index e1f63d8cc7d4..3bdfa7f4e26e 100644
--- a/sound/soc/codecs/wcd9335.c
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/wcd9335.c | 1802
1 file changed, 1802 insertions(+)
diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
index e1f63d8cc7d4..3bdfa7f4e26e 100644
--- a/sound/soc/codecs/wcd9335.c
This patch adds support Analog audio via WCD9335 Codec connected via SLIMBus.
Tested it on DB820c.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/apq8096.c | 68
1 file changed, 68 insertions(+)
diff --git a/sound/soc/qcom/apq8096.c
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/wcd9335.c | 1451 +++-
1 file changed, 1450 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
index 3bdfa7f4e26e..a08703681674 100644
---
This patch adds basic controls found in wcd9335 codec.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/wcd9335.c | 371 +
1 file changed, 371 insertions(+)
diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
index
On Qualcomm platforms, specifically with SLIMbus interfaced codecs,
the codec slim channel numbers are passed to DSP while configuring
the slim audio path. Having get_channel_map() would allow dais to
share such information across multiple dais.
Signed-off-by: Srinivas Kandagatla
---
This patch adds support Analog audio via WCD9335 Codec connected via SLIMBus.
Tested it on DB820c.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/qcom/apq8096.c | 68
1 file changed, 68 insertions(+)
diff --git a/sound/soc/qcom/apq8096.c
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/wcd9335.c | 1451 +++-
1 file changed, 1450 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
index 3bdfa7f4e26e..a08703681674 100644
---
This patch adds basic controls found in wcd9335 codec.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/wcd9335.c | 371 +
1 file changed, 371 insertions(+)
diff --git a/sound/soc/codecs/wcd9335.c b/sound/soc/codecs/wcd9335.c
index
On Qualcomm platforms, specifically with SLIMbus interfaced codecs,
the codec slim channel numbers are passed to DSP while configuring
the slim audio path. Having get_channel_map() would allow dais to
share such information across multiple dais.
Signed-off-by: Srinivas Kandagatla
---
WCD9335 supports two lines of irqs INTR1 and INTR2.
Mutiple interrupts are muxed via these lines.
INTR1 consists of all possible interrupt sources like:
Ear OCP, HPH OCP, MBHC, MAD, VBAT, and SVA
INTR2 is a subset of first interrupt sources like MAD, VBAT, and SVA
Signed-off-by: Srinivas
CLASS-H controller/Amplifier is common accorss Qualcomm WCD codec series.
This patchset adds basic CLASS-H controller apis for WCD codecs after
wcd9335 to use.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/Makefile |2 +-
sound/soc/codecs/wcd-clsh.c | 1010
CLASS-H controller/Amplifier is common accorss Qualcomm WCD codec series.
This patchset adds basic CLASS-H controller apis for WCD codecs after
wcd9335 to use.
Signed-off-by: Srinivas Kandagatla
---
sound/soc/codecs/Makefile |2 +-
sound/soc/codecs/wcd-clsh.c | 1010
WCD9335 supports two lines of irqs INTR1 and INTR2.
Mutiple interrupts are muxed via these lines.
INTR1 consists of all possible interrupt sources like:
Ear OCP, HPH OCP, MBHC, MAD, VBAT, and SVA
INTR2 is a subset of first interrupt sources like MAD, VBAT, and SVA
Signed-off-by: Srinivas
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC.
It is integrated in multiple Qualcomm SoCs like: MSM8996, MSM8976,
and MSM8956 chipsets.
WCD9335 had multiple functional blocks, like: Soundwire controller,
interrupt mux, pin controller, Audio codec, MBHC, MAD(Mic activity Detection),
Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC.
It is integrated in multiple Qualcomm SoCs like: MSM8996, MSM8976,
and MSM8956 chipsets.
WCD9335 had multiple functional blocks, like: Soundwire controller,
interrupt mux, pin controller, Audio codec, MBHC, MAD(Mic activity Detection),
On Mon, Jul 23, 2018 at 11:43:56AM -0400, Liang, Kan wrote:
> > So I like PEBS_ALL.. what I don't like is that it seems to be mutually
> > exclusive with PEBS Load Latency.
>
> Right, MSR_PEBS_ENABLE:32-35 is model specific.
Doesn't mean they couldn't have avoided conflicting bits.
> For Atom,
On Mon, Jul 23, 2018 at 11:43:56AM -0400, Liang, Kan wrote:
> > So I like PEBS_ALL.. what I don't like is that it seems to be mutually
> > exclusive with PEBS Load Latency.
>
> Right, MSR_PEBS_ENABLE:32-35 is model specific.
Doesn't mean they couldn't have avoided conflicting bits.
> For Atom,
On Fri, Jul 20, 2018 at 11:42:40AM -0700, Doug Anderson wrote:
> Hi,
>
> On Tue, Jul 17, 2018 at 2:08 PM, Matthias Kaehlcke wrote:
> > When the temperature reaches stage 2 the PMIC performs by default a
> > 'partial shutdown', unless software override is enabled. It is not well
> > defined which
On Fri, Jul 20, 2018 at 11:42:40AM -0700, Doug Anderson wrote:
> Hi,
>
> On Tue, Jul 17, 2018 at 2:08 PM, Matthias Kaehlcke wrote:
> > When the temperature reaches stage 2 the PMIC performs by default a
> > 'partial shutdown', unless software override is enabled. It is not well
> > defined which
On 07/23/2018 05:37 PM, Steven Rostedt wrote:
> On Mon, 23 Jul 2018 16:23:09 +0200
> Snild Dolkow wrote:
>
>> On 07/23/2018 03:55 PM, Steven Rostedt wrote:
>>
>>> Can you add a comment here stating something to the affect of:
>>> /* task is now visible to other tasks */
>>>
>>> --
On 07/23/2018 05:37 PM, Steven Rostedt wrote:
> On Mon, 23 Jul 2018 16:23:09 +0200
> Snild Dolkow wrote:
>
>> On 07/23/2018 03:55 PM, Steven Rostedt wrote:
>>
>>> Can you add a comment here stating something to the affect of:
>>> /* task is now visible to other tasks */
>>>
>>> --
On 7/23/2018 11:16 AM, Peter Zijlstra wrote:
On Thu, Mar 08, 2018 at 06:15:39PM -0800, kan.li...@linux.intel.com wrote:
From: Kan Liang
The Extended PEBS feature, introduced in Goldmont Plus
microarchitecture, supports all events as "Extended PEBS".
Introduce flag PMU_FL_PEBS_ALL to
On 7/23/2018 11:16 AM, Peter Zijlstra wrote:
On Thu, Mar 08, 2018 at 06:15:39PM -0800, kan.li...@linux.intel.com wrote:
From: Kan Liang
The Extended PEBS feature, introduced in Goldmont Plus
microarchitecture, supports all events as "Extended PEBS".
Introduce flag PMU_FL_PEBS_ALL to
On 21-Jul 20:05, Suren Baghdasaryan wrote:
> On Mon, Jul 16, 2018 at 1:29 AM, Patrick Bellasi
> wrote:
> > When a task's util_clamp value is configured via sched_setattr(2), this
> > value has to be properly accounted in the corresponding clamp group
> > every time the task is enqueued and
On 21-Jul 20:05, Suren Baghdasaryan wrote:
> On Mon, Jul 16, 2018 at 1:29 AM, Patrick Bellasi
> wrote:
> > When a task's util_clamp value is configured via sched_setattr(2), this
> > value has to be properly accounted in the corresponding clamp group
> > every time the task is enqueued and
On Mon, Jul 23, 2018 at 11:41 AM, Boris Brezillon
wrote:
> On Mon, 23 Jul 2018 11:34:43 +0200
> Arnd Bergmann wrote:
>
>> On Sun, Jul 22, 2018 at 8:29 AM, Boris Brezillon
>> wrote:
>> > +Arnd, Rob and the DT ML.
>> >
>> > On Sat, 21 Jul 2018 14:53:47 -0700
>> > Randy Dunlap wrote:
>> >
>> >>
On Mon, Jul 23, 2018 at 11:41 AM, Boris Brezillon
wrote:
> On Mon, 23 Jul 2018 11:34:43 +0200
> Arnd Bergmann wrote:
>
>> On Sun, Jul 22, 2018 at 8:29 AM, Boris Brezillon
>> wrote:
>> > +Arnd, Rob and the DT ML.
>> >
>> > On Sat, 21 Jul 2018 14:53:47 -0700
>> > Randy Dunlap wrote:
>> >
>> >>
On Mon, Jul 23, 2018 at 06:05:38PM +0300, Ivan Bornyakov wrote:
> Signed-off-by: Ivan Bornyakov
> ---
> drivers/staging/gasket/gasket_page_table.c | 6 ++
> 1 file changed, 2 insertions(+), 4 deletions(-)
I can not take patches without any changelog text at all, sorry.
greg k-h
On Mon, Jul 23, 2018 at 06:05:38PM +0300, Ivan Bornyakov wrote:
> Signed-off-by: Ivan Bornyakov
> ---
> drivers/staging/gasket/gasket_page_table.c | 6 ++
> 1 file changed, 2 insertions(+), 4 deletions(-)
I can not take patches without any changelog text at all, sorry.
greg k-h
On Mon, 23 Jul 2018 16:23:09 +0200
Snild Dolkow wrote:
> On 07/23/2018 03:55 PM, Steven Rostedt wrote:
>
> > Can you add a comment here stating something to the affect of:
> > /* task is now visible to other tasks */
> >
> > -- Steve
> Sure, but isn't that a bit misleading? It
On Mon, 23 Jul 2018 16:23:09 +0200
Snild Dolkow wrote:
> On 07/23/2018 03:55 PM, Steven Rostedt wrote:
>
> > Can you add a comment here stating something to the affect of:
> > /* task is now visible to other tasks */
> >
> > -- Steve
> Sure, but isn't that a bit misleading? It
On 7/15/2018 12:48 PM, Daniel Jurgens wrote:
On 7/14/2018 10:57 AM, Or Gerlitz wrote:
On Sat, Jul 14, 2018 at 2:50 AM, Qing Huang wrote:
When a CX5 device is configured in dual-port RoCE mode, after creating
many VFs against port 1, creating the same number of VFs against port 2
will flood
On 7/15/2018 12:48 PM, Daniel Jurgens wrote:
On 7/14/2018 10:57 AM, Or Gerlitz wrote:
On Sat, Jul 14, 2018 at 2:50 AM, Qing Huang wrote:
When a CX5 device is configured in dual-port RoCE mode, after creating
many VFs against port 1, creating the same number of VFs against port 2
will flood
On 07/23/2018 04:38 AM, Corentin Labbe wrote:
> jz4780-nemc use of_ functions, so it needs to depend on OF
>
> This fix the following build failure on x86
> drivers/memory/jz4780-nemc.c: In function ‘jz4780_nemc_num_banks’:
> drivers/memory/jz4780-nemc.c:72:10: error: implicit declaration of
On 07/23/2018 04:38 AM, Corentin Labbe wrote:
> jz4780-nemc use of_ functions, so it needs to depend on OF
>
> This fix the following build failure on x86
> drivers/memory/jz4780-nemc.c: In function ‘jz4780_nemc_num_banks’:
> drivers/memory/jz4780-nemc.c:72:10: error: implicit declaration of
On Mon, Jul 23, 2018 at 5:23 PM, Johannes Weiner wrote:
> On Mon, Jul 23, 2018 at 03:36:09PM +0200, Arnd Bergmann wrote:
>> On Thu, Jul 12, 2018 at 7:29 PM, Johannes Weiner wrote:
>> In file included from /git/arm-soc/include/linux/kernel.h:10,
>> from
On Mon, Jul 23, 2018 at 5:23 PM, Johannes Weiner wrote:
> On Mon, Jul 23, 2018 at 03:36:09PM +0200, Arnd Bergmann wrote:
>> On Thu, Jul 12, 2018 at 7:29 PM, Johannes Weiner wrote:
>> In file included from /git/arm-soc/include/linux/kernel.h:10,
>> from
On Mon, 2018-07-23 at 08:09 -0700, Srikar Dronamraju wrote:
> * Peter Zijlstra [2018-07-23 15:57:00]:
>
> > On Wed, Jun 20, 2018 at 10:32:41PM +0530, Srikar Dronamraju wrote:
> > > Srikar Dronamraju (19):
> >
> > > sched/numa: Stop multiple tasks from moving to the cpu at the
> > > same time
On Mon, 2018-07-23 at 08:09 -0700, Srikar Dronamraju wrote:
> * Peter Zijlstra [2018-07-23 15:57:00]:
>
> > On Wed, Jun 20, 2018 at 10:32:41PM +0530, Srikar Dronamraju wrote:
> > > Srikar Dronamraju (19):
> >
> > > sched/numa: Stop multiple tasks from moving to the cpu at the
> > > same time
Hello,
On Mon, Jul 16, 2018 at 09:29:02AM +0100, Patrick Bellasi wrote:
> The cgroup's CPU controller allows to assign a specified (maximum)
> bandwidth to the tasks of a group. However this bandwidth is defined and
> enforced only on a temporal base, without considering the actual
> frequency a
Hello,
On Mon, Jul 16, 2018 at 09:29:02AM +0100, Patrick Bellasi wrote:
> The cgroup's CPU controller allows to assign a specified (maximum)
> bandwidth to the tasks of a group. However this bandwidth is defined and
> enforced only on a temporal base, without considering the actual
> frequency a
On Sat, Jul 21, 2018 at 9:38 AM Liu Xiang wrote:
>
> Implement a resource managed irq_of_parse_and_map function.
That is obvious from the diff. Why do you need this?
Anything that is a platform device should use platform_get_irq. The
mapping is created by the core Also, of_irq_get() is
On Sat, Jul 21, 2018 at 9:38 AM Liu Xiang wrote:
>
> Implement a resource managed irq_of_parse_and_map function.
That is obvious from the diff. Why do you need this?
Anything that is a platform device should use platform_get_irq. The
mapping is created by the core Also, of_irq_get() is
On Mon, Jul 23, 2018 at 02:25:34PM +0100, Qais Yousef wrote:
> Hi Morten
>
> On 20/07/18 14:32, Morten Rasmussen wrote:
> >The SD_ASYM_CPUCAPACITY sched_domain flag is supposed to mark the
> >sched_domain in the hierarchy where all cpu capacities are visible for
> >any cpu's point of view on
On Mon, Jul 23, 2018 at 02:25:34PM +0100, Qais Yousef wrote:
> Hi Morten
>
> On 20/07/18 14:32, Morten Rasmussen wrote:
> >The SD_ASYM_CPUCAPACITY sched_domain flag is supposed to mark the
> >sched_domain in the hierarchy where all cpu capacities are visible for
> >any cpu's point of view on
Add a superblock event notification facility whereby notifications about
superblock events, such as I/O errors (EIO), quota limits being hit
(EDQUOT) and running out of space (ENOSPC) can be reported to a monitoring
process asynchronously. Note that this does not cover vfsmount topology
changes.
Add a superblock event notification facility whereby notifications about
superblock events, such as I/O errors (EIO), quota limits being hit
(EDQUOT) and running out of space (ENOSPC) can be reported to a monitoring
process asynchronously. Note that this does not cover vfsmount topology
changes.
This needs to be linked with -lkeyutils.
It is run like:
./watch_test
and watches "/" for mount changes and the current session keyring for key
changes:
# keyctl add user a a @s
1035096409
# keyctl unlink 1035096409 @s
# mount -t tmpfs none
This needs to be linked with -lkeyutils.
It is run like:
./watch_test
and watches "/" for mount changes and the current session keyring for key
changes:
# keyctl add user a a @s
1035096409
# keyctl unlink 1035096409 @s
# mount -t tmpfs none
[*] Note that this needs some cleaning up and not all the events work yet.
Add a mount notification facility whereby notifications about changes in
mount topology and configuration can be received. Note that this only
covers vfsmount topology changes and not superblock events. A separate
[*] Note that this needs some cleaning up and not all the events work yet.
Add a mount notification facility whereby notifications about changes in
mount topology and configuration can be received. Note that this only
covers vfsmount topology changes and not superblock events. A separate
Add a key/keyring change notification facility whereby notifications about
changes in key and keyring content and attributes can be received.
Firstly, an event queue needs to be created:
fd = open("/dev/event_queue", O_RDWR);
then a notification can be set up to report notifications via
Add a key/keyring change notification facility whereby notifications about
changes in key and keyring content and attributes can be received.
Firstly, an event queue needs to be created:
fd = open("/dev/event_queue", O_RDWR);
then a notification can be set up to report notifications via
Implement a misc device that implements a general notification queue as a
ring buffer that can be mmap()'d from userspace.
The way this is done is:
(1) An application opens the device and indicates the size of the ring
buffer that it wants to reserve in pages (this can only be set once):
Implement a misc device that implements a general notification queue as a
ring buffer that can be mmap()'d from userspace.
The way this is done is:
(1) An application opens the device and indicates the size of the ring
buffer that it wants to reserve in pages (this can only be set once):
On Fri, 13 Jul 2018 22:58:06 +0530
Prashant Dhamdhere wrote:
> This patch talks about the 'HardwareCorrupted' field currently missing from
> the 'meminfo' section of 'proc.txt' file. It also includes short description
> of 'HardwareCorrupted' field.
I've gone ahead and applied this. Please
On Fri, 13 Jul 2018 22:58:06 +0530
Prashant Dhamdhere wrote:
> This patch talks about the 'HardwareCorrupted' field currently missing from
> the 'meminfo' section of 'proc.txt' file. It also includes short description
> of 'HardwareCorrupted' field.
I've gone ahead and applied this. Please
Hi Al,
Here's a set of patches to add a general variable-length notification queue
concept and to add sources of events for:
(1) Mount topology and reconfiguration change events.
(2) Superblocks EIO, ENOSPC and EDQUOT events (not complete yet).
(3) Key/keyring changes events
One of the
Hi Al,
Here's a set of patches to add a general variable-length notification queue
concept and to add sources of events for:
(1) Mount topology and reconfiguration change events.
(2) Superblocks EIO, ENOSPC and EDQUOT events (not complete yet).
(3) Key/keyring changes events
One of the
On Mon, Jul 23, 2018 at 08:09:55AM -0700, Srikar Dronamraju wrote:
> > > sched/numa: Stop multiple tasks from moving to the cpu at the same time
>
> This patch has go-ahead from Mel and Rik and no outstanding comments.
I left it out because it's part of the big xchg() mess.
In particular:
+
On Mon, Jul 23, 2018 at 08:09:55AM -0700, Srikar Dronamraju wrote:
> > > sched/numa: Stop multiple tasks from moving to the cpu at the same time
>
> This patch has go-ahead from Mel and Rik and no outstanding comments.
I left it out because it's part of the big xchg() mess.
In particular:
+
Hi Arnd,
On Mon, Jul 23, 2018 at 03:36:09PM +0200, Arnd Bergmann wrote:
> On Thu, Jul 12, 2018 at 7:29 PM, Johannes Weiner wrote:
> > How many page->flags does this leave us with on 32-bit?
> >
> > 20 bits are always page flags
> >
> > 21 if you have an MMU
> >
> > 23
Hi Arnd,
On Mon, Jul 23, 2018 at 03:36:09PM +0200, Arnd Bergmann wrote:
> On Thu, Jul 12, 2018 at 7:29 PM, Johannes Weiner wrote:
> > How many page->flags does this leave us with on 32-bit?
> >
> > 20 bits are always page flags
> >
> > 21 if you have an MMU
> >
> > 23
On Mon, Jul 23, 2018 at 5:09 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
>> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>
>>> Biggest conceptual problem: your definition of fuse-server is weak.
>>> Take the following example: process A is holding
On Mon, Jul 23, 2018 at 5:09 PM, Miklos Szeredi wrote:
> On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
>> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>
>>> Biggest conceptual problem: your definition of fuse-server is weak.
>>> Take the following example: process A is holding
On 20-Jul 19:37, Suren Baghdasaryan wrote:
> On Mon, Jul 16, 2018 at 1:29 AM, Patrick Bellasi
> wrote:
[...]
> > +#ifdef CONFIG_UCLAMP_TASK_GROUP
> > +static int cpu_util_min_write_u64(struct cgroup_subsys_state *css,
> > + struct cftype *cftype, u64 min_value)
>
On 20-Jul 19:37, Suren Baghdasaryan wrote:
> On Mon, Jul 16, 2018 at 1:29 AM, Patrick Bellasi
> wrote:
[...]
> > +#ifdef CONFIG_UCLAMP_TASK_GROUP
> > +static int cpu_util_min_write_u64(struct cgroup_subsys_state *css,
> > + struct cftype *cftype, u64 min_value)
>
Thanks for the response. I'm running 4.4.123-1 from Gentoo. It also
happens on 4.4.87-r1.
Cheers,
- Alex.
On 23/07/18 16:13, Jeff Moyer wrote:
Alex Richman writes:
Hi,
I'm seeing some weirdness with AIO, specifically SYS_io_destroy() is
taking upwards of ~10 microseconds (~100
Thanks for the response. I'm running 4.4.123-1 from Gentoo. It also
happens on 4.4.87-r1.
Cheers,
- Alex.
On 23/07/18 16:13, Jeff Moyer wrote:
Alex Richman writes:
Hi,
I'm seeing some weirdness with AIO, specifically SYS_io_destroy() is
taking upwards of ~10 microseconds (~100
On Thu, Mar 08, 2018 at 06:15:39PM -0800, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> The Extended PEBS feature, introduced in Goldmont Plus
> microarchitecture, supports all events as "Extended PEBS".
>
> Introduce flag PMU_FL_PEBS_ALL to indicate the platforms which support
>
On Thu, Mar 08, 2018 at 06:15:39PM -0800, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> The Extended PEBS feature, introduced in Goldmont Plus
> microarchitecture, supports all events as "Extended PEBS".
>
> Introduce flag PMU_FL_PEBS_ALL to indicate the platforms which support
>
Quoting Christian Brauner (christian.brau...@canonical.com):
> On Wed, Jun 13, 2018 at 10:45:37AM -0500, Serge Hallyn wrote:
> > On Thu, Jun 07, 2018 at 01:43:48PM +0200, Christian Brauner wrote:
> > > When running in a container with a user namespace, if you call getxattr
> > > with name =
Quoting Christian Brauner (christian.brau...@canonical.com):
> On Wed, Jun 13, 2018 at 10:45:37AM -0500, Serge Hallyn wrote:
> > On Thu, Jun 07, 2018 at 01:43:48PM +0200, Christian Brauner wrote:
> > > When running in a container with a user namespace, if you call getxattr
> > > with name =
Alex Richman writes:
> Hi,
>
> I'm seeing some weirdness with AIO, specifically SYS_io_destroy() is
> taking upwards of ~10 microseconds (~100 miliseconds) per call.
> How long is that call expected to take? I can see from the source
Well, it waits for an RCU grace period. I would not
Alex Richman writes:
> Hi,
>
> I'm seeing some weirdness with AIO, specifically SYS_io_destroy() is
> taking upwards of ~10 microseconds (~100 miliseconds) per call.
> How long is that call expected to take? I can see from the source
Well, it waits for an RCU grace period. I would not
On Mon, Jul 23, 2018 at 02:25:00PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.115 release.
> There are 28 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Jul 23, 2018 at 02:25:00PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.115 release.
> There are 28 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Mon, Jul 23, 2018 at 02:40:54PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.144 release.
> There are 107 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, 2018-06-29 at 10:24:32 UTC, Bharat Bhushan wrote:
> Available vector space accounts ipis and timer interrupts
> while spurious vector was not accounted. Also later
> mpic_setup_error_int() escape one more vector, seemingly it
> assumes one spurious vector.
>
> Signed-off-by: Bharat
On Mon, Jul 23, 2018 at 02:40:54PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.144 release.
> There are 107 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri, 2018-06-29 at 10:24:32 UTC, Bharat Bhushan wrote:
> Available vector space accounts ipis and timer interrupts
> while spurious vector was not accounted. Also later
> mpic_setup_error_int() escape one more vector, seemingly it
> assumes one spurious vector.
>
> Signed-off-by: Bharat
* Peter Zijlstra [2018-07-23 15:57:00]:
> On Wed, Jun 20, 2018 at 10:32:41PM +0530, Srikar Dronamraju wrote:
> > Srikar Dronamraju (19):
> > sched/numa: Remove redundant field.
> > sched/numa: Evaluate move once per node
> > sched/numa: Simplify load_too_imbalanced
> > sched/numa: Set
* Peter Zijlstra [2018-07-23 15:57:00]:
> On Wed, Jun 20, 2018 at 10:32:41PM +0530, Srikar Dronamraju wrote:
> > Srikar Dronamraju (19):
> > sched/numa: Remove redundant field.
> > sched/numa: Evaluate move once per node
> > sched/numa: Simplify load_too_imbalanced
> > sched/numa: Set
On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>> Biggest conceptual problem: your definition of fuse-server is weak.
>> Take the following example: process A is holding the fuse device fd
>> and is forwarding requests and replies
On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote:
> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote:
>> Biggest conceptual problem: your definition of fuse-server is weak.
>> Take the following example: process A is holding the fuse device fd
>> and is forwarding requests and replies
Enabling the Interrupts before registering the irq handler is a bad
idea. This patch corrects the same for XADC driver.
Signed-off-by: Manish Narani
---
drivers/iio/adc/xilinx-xadc-core.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
On 20-Jul 18:23, Suren Baghdasaryan wrote:
> Hi Patrick,
Hi Sure,
thank!
> On Mon, Jul 16, 2018 at 1:29 AM, Patrick Bellasi
> wrote:
[...]
> > @@ -977,13 +991,21 @@ static inline void uclamp_cpu_get_id(struct
> > task_struct *p,
> > uc_grp = >uclamp.group[clamp_id][0];
> >
701 - 800 of 1916 matches
Mail list logo
