Hi,
On Tue, 4 Oct 2016 15:26:28 +0200 (CEST)
Jiri Kosina wrote:
> On Tue, 4 Oct 2016, Jörg Otte wrote:
>
> > With kernel 4.8.0-01558-g21f54dd I get thousands of
> > "dvb-usb: bulk message failed: -11 (1/0)"
> > messages in the logs and the DVB adapter is not working.
> >
> >
Hi,
On Tue, 4 Oct 2016 15:26:28 +0200 (CEST)
Jiri Kosina wrote:
> On Tue, 4 Oct 2016, Jörg Otte wrote:
>
> > With kernel 4.8.0-01558-g21f54dd I get thousands of
> > "dvb-usb: bulk message failed: -11 (1/0)"
> > messages in the logs and the DVB adapter is not working.
> >
> > It tourned out
On 28/09/16 14:41, Adrian Hunter wrote:
> In cycle-accurate mode, timestamps can be calculated from CYC packets. The
> decoder also estimates timestamps based on the number of instructions since
> the last timestamp. For that to work in cycle-accurate mode, the
> instruction count needs to be
On 28/09/16 14:41, Adrian Hunter wrote:
> In cycle-accurate mode, timestamps can be calculated from CYC packets. The
> decoder also estimates timestamps based on the number of instructions since
> the last timestamp. For that to work in cycle-accurate mode, the
> instruction count needs to be
This patchset aims to support the legacy SCPI firmware implementation that was
delivered as early technology preview for the JUNO platform.
Finally a stable, maintained and public implementation for the SCPI protocol
has been upstreamed part of the JUNO support and it is the recommended way
of
From: Sudeep Holla
Add indirection table to permit multiple command values for legacy support.
[narmstr...@baylibre.com: Added cmd check in scpi_send_message]
Signed-off-by: Neil Armstrong
---
drivers/firmware/arm_scpi.c | 81
This patchset aims to support the legacy SCPI firmware implementation that was
delivered as early technology preview for the JUNO platform.
Finally a stable, maintained and public implementation for the SCPI protocol
has been upstreamed part of the JUNO support and it is the recommended way
of
From: Sudeep Holla
Add indirection table to permit multiple command values for legacy support.
[narmstr...@baylibre.com: Added cmd check in scpi_send_message]
Signed-off-by: Neil Armstrong
---
drivers/firmware/arm_scpi.c | 81 +++--
1 file changed, 64
Acked-by: Rob Herring
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/arm/arm,scpi.txt | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/arm,scpi.txt
This patch adds support for the Legacy SCPI protocol in early JUNO versions and
shipped Amlogic ARMv8 based SoCs. Some Rockchip SoC are also known to use this
version of protocol with extended vendor commands
.
In order to support the legacy SCPI protocol variant, add back the structures
and
Acked-by: Rob Herring
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/arm/arm,scpi.txt | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/arm,scpi.txt
b/Documentation/devicetree/bindings/arm/arm,scpi.txt
index
This patch adds support for the Legacy SCPI protocol in early JUNO versions and
shipped Amlogic ARMv8 based SoCs. Some Rockchip SoC are also known to use this
version of protocol with extended vendor commands
.
In order to support the legacy SCPI protocol variant, add back the structures
and
On Wed, 5 Oct 2016 09:26:29 +0200 (CEST)
Jiri Kosina wrote:
> On Tue, 4 Oct 2016, Jörg Otte wrote:
>
> > Thanks for the quick response.
> > Drivers are:
> > dvb_core, dvb_usb, dbv_usb_cynergyT2
>
> This dbv_usb_cynergyT2 is not from Linus' tree, is it? I don't seem
> to be
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 443811b..88f98f5 100644
---
On Amlogic SCPI legacy implementation, the GET_CAPABILITIES is not
supported, failover by using 0.0.0 version.
Signed-off-by: Neil Armstrong
---
drivers/firmware/arm_scpi.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/firmware/arm_scpi.c
On Wed, 5 Oct 2016 09:26:29 +0200 (CEST)
Jiri Kosina wrote:
> On Tue, 4 Oct 2016, Jörg Otte wrote:
>
> > Thanks for the quick response.
> > Drivers are:
> > dvb_core, dvb_usb, dbv_usb_cynergyT2
>
> This dbv_usb_cynergyT2 is not from Linus' tree, is it? I don't seem
> to be able to find it,
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 443811b..88f98f5 100644
---
On Amlogic SCPI legacy implementation, the GET_CAPABILITIES is not
supported, failover by using 0.0.0 version.
Signed-off-by: Neil Armstrong
---
drivers/firmware/arm_scpi.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/firmware/arm_scpi.c b/drivers/firmware/arm_scpi.c
index
Since Amlogic SoCs reports more than 8 OPPs per domains, grow the structure
size to 16.
Signed-off-by: Neil Armstrong
---
drivers/firmware/arm_scpi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/arm_scpi.c
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 48 +
1 file changed, 48 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 48 +
1 file changed, 48 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
index 88f98f5..3fdb2d7 100644
---
Since Amlogic SoCs reports more than 8 OPPs per domains, grow the structure
size to 16.
Signed-off-by: Neil Armstrong
---
drivers/firmware/arm_scpi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/arm_scpi.c b/drivers/firmware/arm_scpi.c
index
Currently the different governors are stored in the subdir
'governors'. That is not a problem.
However, that forces to declare some private structure in the
include/linux/cpuidle.h header because these governor files
don't have access to the private 'cpuidle.h' located in
drivers/cpuidle.
The governor's code use try_module_get() and put_module() to refcount
the governor's module. But the governors are not compiled as module.
The refcount does not prevent to switch the governor or unload a module
as they aren't compiled as modules. So the code is pointless, removing
it.
Currently the different governors are stored in the subdir
'governors'. That is not a problem.
However, that forces to declare some private structure in the
include/linux/cpuidle.h header because these governor files
don't have access to the private 'cpuidle.h' located in
drivers/cpuidle.
The governor's code use try_module_get() and put_module() to refcount
the governor's module. But the governors are not compiled as module.
The refcount does not prevent to switch the governor or unload a module
as they aren't compiled as modules. So the code is pointless, removing
it.
Add new DT match table to setup the is_legacy boolean value across
the scpi functions.
Add the Amlogic GXBB SoC compatible for platform and as legacy match entry.
Signed-off-by: Neil Armstrong
---
drivers/firmware/arm_scpi.c | 9 +
1 file changed, 9
Add new DT match table to setup the is_legacy boolean value across
the scpi functions.
Add the Amlogic GXBB SoC compatible for platform and as legacy match entry.
Signed-off-by: Neil Armstrong
---
drivers/firmware/arm_scpi.c | 9 +
1 file changed, 9 insertions(+)
diff --git
On 2016-10-03 11:12:37 [+0200], Peter Zijlstra wrote:
> These are unused and clutter up the code.
it seems that it has been like that since day one (Ingo's patches from
2006 [0] are like that). I assume we never had real code behind this
functions, right? Not even in -RT?
[0]
On 2016-10-03 11:12:37 [+0200], Peter Zijlstra wrote:
> These are unused and clutter up the code.
it seems that it has been like that since day one (Ingo's patches from
2006 [0] are like that). I assume we never had real code behind this
functions, right? Not even in -RT?
[0]
On Tue, 4 Oct 2016, Jörg Otte wrote:
> Thanks for the quick response.
> Drivers are:
> dvb_core, dvb_usb, dbv_usb_cynergyT2
This dbv_usb_cynergyT2 is not from Linus' tree, is it? I don't seem to be
able to find it, and the only google hit I am getting is your very mail to
LKML :)
--
Jiri
On Tue, 4 Oct 2016, Jörg Otte wrote:
> Thanks for the quick response.
> Drivers are:
> dvb_core, dvb_usb, dbv_usb_cynergyT2
This dbv_usb_cynergyT2 is not from Linus' tree, is it? I don't seem to be
able to find it, and the only google hit I am getting is your very mail to
LKML :)
--
Jiri
Hi Felipe,
>> But you do!
>> The mA number from the USB configuration is passed to usb_gadget_vbus_draw.
>> Your patch passes that to usb_charger_set_cur_limit_by_type()
>> which calls __usb_charger_set_cur_limit_by_type() which will set the
>> cur_limit for whichever type uchger->type currently
Hi Felipe,
>> But you do!
>> The mA number from the USB configuration is passed to usb_gadget_vbus_draw.
>> Your patch passes that to usb_charger_set_cur_limit_by_type()
>> which calls __usb_charger_set_cur_limit_by_type() which will set the
>> cur_limit for whichever type uchger->type currently
On 2016-10-05 08:20:58 [+0200], Peter Zijlstra wrote:
> > pi_stress.
>
> Where does one find that? Link?
https://git.kernel.org/cgit/utils/rt-tests/rt-tests.git/tree/src/pi_tests/pi_stress.c
Take the whole package :)
Sebastian
On 2016-10-05 08:20:58 [+0200], Peter Zijlstra wrote:
> > pi_stress.
>
> Where does one find that? Link?
https://git.kernel.org/cgit/utils/rt-tests/rt-tests.git/tree/src/pi_tests/pi_stress.c
Take the whole package :)
Sebastian
On 05/10/2016 02:34, r...@redhat.com wrote:
> From: Andy Lutomirski
>
> Since commit 58122bf1d856 ("x86/fpu: Default eagerfpu=on on all
> CPUs") in Linux 4.6, eager FPU mode has been the default on all x86
> systems, and no one has reported any regressions.
>
> This patch
On 05/10/2016 02:34, r...@redhat.com wrote:
> From: Andy Lutomirski
>
> Since commit 58122bf1d856 ("x86/fpu: Default eagerfpu=on on all
> CPUs") in Linux 4.6, eager FPU mode has been the default on all x86
> systems, and no one has reported any regressions.
>
> This patch removes the ability
Explicitly state that enabling RCU_TRACE enables more
tracepoints and not just "additional tracing".
Signed-off-by: Nikolay Borisov
---
Hello Paul,
Following our latest conversation re. enabling RCU tracing
I had to actually go and look into the code to see which
option
Explicitly state that enabling RCU_TRACE enables more
tracepoints and not just "additional tracing".
Signed-off-by: Nikolay Borisov
---
Hello Paul,
Following our latest conversation re. enabling RCU tracing
I had to actually go and look into the code to see which
option enables the
On Tue, Oct 4, 2016 at 8:06 PM, Andrew Kim wrote:
> According to ACPI specification, the century field data
> should be ranged 0-63. so if it's over this range, it could
> cause system RTC settings error including alarmwakeup settings.
> So it's required to have this
On Tue, Oct 4, 2016 at 8:06 PM, Andrew Kim wrote:
> According to ACPI specification, the century field data
> should be ranged 0-63. so if it's over this range, it could
> cause system RTC settings error including alarmwakeup settings.
> So it's required to have this boundary for safe RTC init
Hi Neil,
On Tue, Oct 4, 2016 at 12:21 PM, Neil Armstrong wrote:
> On 10/04/2016 12:14 PM, Yegor Yefremov wrote:
>> On Tue, Oct 4, 2016 at 12:11 PM, Neil Armstrong
>> wrote:
>>> On 10/04/2016 12:09 PM, Yegor Yefremov wrote:
Hi Neil,
Hi Neil,
On Tue, Oct 4, 2016 at 12:21 PM, Neil Armstrong wrote:
> On 10/04/2016 12:14 PM, Yegor Yefremov wrote:
>> On Tue, Oct 4, 2016 at 12:11 PM, Neil Armstrong
>> wrote:
>>> On 10/04/2016 12:09 PM, Yegor Yefremov wrote:
Hi Neil,
On Tue, Oct 4, 2016 at 11:40 AM, Neil Armstrong
On Wed, Oct 05, 2016 at 02:23:22AM +0530, Harman Kalra wrote:
> 2 errors "open brace { should be on the previous line" are fixed.
> Warning "Prefer "pr_debug over printk(KERN_DEBUG... " fixed
> Few line more tahn 80 character warnings fixed
That's three different things, please make three
On Wed, Oct 05, 2016 at 02:23:22AM +0530, Harman Kalra wrote:
> 2 errors "open brace { should be on the previous line" are fixed.
> Warning "Prefer "pr_debug over printk(KERN_DEBUG... " fixed
> Few line more tahn 80 character warnings fixed
That's three different things, please make three
On Wed, Oct 05, 2016 at 01:40:05AM +0100, Alasdair G Kergon wrote:
> On Tue, Oct 04, 2016 at 04:39:28PM -0700, Andy Grover wrote:
> > devicemapper is using uevents for:
> > a. dm-verity detected corruption
> > b. dm-multipath: path failed or reinstated
> > c. dm device renamed
> > d. there's also
On Wed, Oct 05, 2016 at 01:40:05AM +0100, Alasdair G Kergon wrote:
> On Tue, Oct 04, 2016 at 04:39:28PM -0700, Andy Grover wrote:
> > devicemapper is using uevents for:
> > a. dm-verity detected corruption
> > b. dm-multipath: path failed or reinstated
> > c. dm device renamed
> > d. there's also
On Tue, Oct 04, 2016 at 11:06:15AM +0200, Jan Kara wrote:
> On Tue 04-10-16 10:53:40, Pierre Morel wrote:
> > When triggering thaw-filesystems via magic sysrq, the system enters a
> > loop in do_thaw_one(), as thaw_bdev() still returns success if
> > bd_fsfreeze_count == 0. To fix this, let
On Tue, Oct 04, 2016 at 11:06:15AM +0200, Jan Kara wrote:
> On Tue 04-10-16 10:53:40, Pierre Morel wrote:
> > When triggering thaw-filesystems via magic sysrq, the system enters a
> > loop in do_thaw_one(), as thaw_bdev() still returns success if
> > bd_fsfreeze_count == 0. To fix this, let
FYI, the patches look fine to me:
Acked-by: Christoph Hellwig
but we're past the merge window for 4.9 now unfortunately.
FYI, the patches look fine to me:
Acked-by: Christoph Hellwig
but we're past the merge window for 4.9 now unfortunately.
On Tue, Oct 04, 2016 at 07:55:12PM -0300, Mauricio Faria de Oliveira wrote:
> Hi Benjamin, Kent, and others,
>
> Would you please comment / answer about this possible problem?
> Any feedback is appreciated.
>
> Since commit e1bdd5f27a5b ("aio: percpu reqs_available") the maximum
> number of aio
On Tue, Oct 04, 2016 at 07:55:12PM -0300, Mauricio Faria de Oliveira wrote:
> Hi Benjamin, Kent, and others,
>
> Would you please comment / answer about this possible problem?
> Any feedback is appreciated.
>
> Since commit e1bdd5f27a5b ("aio: percpu reqs_available") the maximum
> number of aio
On 10/05/16 09:21, Mugunthan V N wrote:
> On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote:
>> On 10/03/16 16:03, Mugunthan V N wrote:
>>> +static int tiadc_request_dma(struct platform_device *pdev,
>>> +struct tiadc_device *adc_dev)
>>> +{
>>> + struct tiadc_dma
On 10/05/16 09:21, Mugunthan V N wrote:
> On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote:
>> On 10/03/16 16:03, Mugunthan V N wrote:
>>> +static int tiadc_request_dma(struct platform_device *pdev,
>>> +struct tiadc_device *adc_dev)
>>> +{
>>> + struct tiadc_dma
On 10/05/2016 02:40 AM, Alasdair G Kergon wrote:
> On Tue, Oct 04, 2016 at 04:39:28PM -0700, Andy Grover wrote:
>> devicemapper is using uevents for:
>> a. dm-verity detected corruption
>> b. dm-multipath: path failed or reinstated
>> c. dm device renamed
>> d. there's also some use in md and
On 10/05/2016 02:40 AM, Alasdair G Kergon wrote:
> On Tue, Oct 04, 2016 at 04:39:28PM -0700, Andy Grover wrote:
>> devicemapper is using uevents for:
>> a. dm-verity detected corruption
>> b. dm-multipath: path failed or reinstated
>> c. dm device renamed
>> d. there's also some use in md and
On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote:
> On 10/03/16 16:03, Mugunthan V N wrote:
>> +static int tiadc_request_dma(struct platform_device *pdev,
>> + struct tiadc_device *adc_dev)
>> +{
>> +struct tiadc_dma*dma = _dev->dma;
>> +
On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote:
> On 10/03/16 16:03, Mugunthan V N wrote:
>> +static int tiadc_request_dma(struct platform_device *pdev,
>> + struct tiadc_device *adc_dev)
>> +{
>> +struct tiadc_dma*dma = _dev->dma;
>> +
On Tue, Oct 04, 2016 at 06:02:14PM -0700, Davidlohr Bueso wrote:
> On Mon, 03 Oct 2016, Peter Zijlstra wrote:
> >Do people have more/better futex-pi test cases?
>
> pi_stress.
Where does one find that? Link?
On Tue, Oct 04, 2016 at 06:02:14PM -0700, Davidlohr Bueso wrote:
> On Mon, 03 Oct 2016, Peter Zijlstra wrote:
> >Do people have more/better futex-pi test cases?
>
> pi_stress.
Where does one find that? Link?
On Tue, Oct 04, 2016 at 08:57:55PM -0700, Davidlohr Bueso wrote:
> On Mon, 03 Oct 2016, Peter Zijlstra wrote:
>
> >Since the futex_q can dissapear the instruction after assigning NULL,
> >this really should be a RELEASE barrier. That stops loads from hitting
> >dead memory too.
> >
>
On Tue, Oct 04, 2016 at 08:57:55PM -0700, Davidlohr Bueso wrote:
> On Mon, 03 Oct 2016, Peter Zijlstra wrote:
>
> >Since the futex_q can dissapear the instruction after assigning NULL,
> >this really should be a RELEASE barrier. That stops loads from hitting
> >dead memory too.
> >
>
On 05/10/16 05:07, Adam Ford wrote:
> Make "HDMI for OMAP4" and "HDMI for OMAP5" depend on ARCH_OMAP4
> and SOC_OMAP5/DRA7XX respectively.
>
> Signed-off-by: Adam Ford
>
> Changes in v2: Add dependancy for DRA7XX or OMAP5
You don't say it, but I presume this is just to make
On 05/10/16 05:07, Adam Ford wrote:
> Make "HDMI for OMAP4" and "HDMI for OMAP5" depend on ARCH_OMAP4
> and SOC_OMAP5/DRA7XX respectively.
>
> Signed-off-by: Adam Ford
>
> Changes in v2: Add dependancy for DRA7XX or OMAP5
You don't say it, but I presume this is just to make those kconfig
On 4 October 2016 at 11:46, Mylène Josserand
wrote:
> Add the audio card for sun8i SoC. This card links the codec driver
> (digital part) with the DAI driver. The analog codec driver is
> added as an aux_device.
>
> Signed-off-by: Mylène Josserand
On 4 October 2016 at 11:46, Mylène Josserand
wrote:
> Add the audio card for sun8i SoC. This card links the codec driver
> (digital part) with the DAI driver. The analog codec driver is
> added as an aux_device.
>
> Signed-off-by: Mylène Josserand
> ---
> sound/soc/sunxi/Kconfig | 14 +++
901 - 968 of 968 matches
Mail list logo