On Thu, Nov 08, 2018 at 12:01:27PM +0100, Paolo Pisati wrote:
On Wed, Nov 07, 2018 at 07:17:51PM -0500, Sasha Levin wrote:
So why not just take 760db29bdc completely? It looks safer than taking a
partial backport, and will make applying future patches easier.
I tried to do it and it doesn't loo
On 10/04/2018 05:04 AM, Juri Lelli wrote:
> On 03/10/18 15:42, Steven Rostedt wrote:
>> On Mon, 3 Sep 2018 16:28:00 +0200
>> Juri Lelli wrote:
>>
>>
>>> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
>>> index 5b43f482fa0f..8dc26005bb1e 100644
>>> --- a/kernel/cgroup/cpuset.c
>>> ++
On 11/8/2018 3:23 PM, Marc Gonzalez wrote:
>
>
> On November 8, 2018 12:38:10 PM GMT+01:00, Horia Geanta
> wrote:
>> On 11/8/2018 1:23 PM, Horia Geanta wrote:
>>> On 11/7/2018 10:49 PM, Marc Gonzalez wrote:
[ Add interested parties ]
On 07/11/2018 21:18, Marc Gonzalez wrote:
On 2018-11-01 16:02:35 [-0700], Paul E. McKenney wrote:
> > The forcing of an expedited grace period is an expensive and very
> > RT-application unfriendly operation, as it forcibly preempts all running
> > tasks on CPUs which are preventing the gp from expiring.
> >
> > By default, as a policy de
On Thu, Nov 08, 2018 at 03:45:36PM +0200, Nick Kossifidis wrote:
> Στις 2018-11-07 14:06, Mark Rutland έγραψε:
> > On Wed, Nov 07, 2018 at 04:31:34AM +0200, Nick Kossifidis wrote:
> > > Mark and Sundeep thanks a lot for your feedback, I guess you convinced
> > > me that having a device tree binding
> On Nov 7, 2018, at 8:41 PM, NeilBrown wrote:
>
> On Wed, Nov 07 2018, Chuck Lever wrote:
>
>> Hi Neil-
>>
>>
>>> On Nov 6, 2018, at 11:12 PM, NeilBrown wrote:
>>>
>>> 1/ discard 'struct unx_cred'. We don't need any data that
>>> is not already in 'struct rpc_cred'.
>>> 2/ Don't keep t
On Thu, 2018-11-08 at 19:33 +0400, Christian Hewitt wrote:
>
> +&audio {
> + status = "okay";
> +};
> +
> +&aiu_i2s_dma {
> + status = "okay";
> +};
> +
> +&i2s_dai {
> + status = "okay";
> +};
The audio stuff has not made it's way upstream (yet) please drop this
> +
> +&cvbs_vdac_po
All,
Updating Kselftest wiki and providing links to overview and how-to documents
has been on my list of things to do for a while.
It is now updated with the current status and links to documents. I am planning
to write a detailed how-to blog/article.
https://kselftest.wiki.kernel.org
thanks,
-
On 2018-11-01 16:18:04 [-0700], Paul E. McKenney wrote:
> The need for this goes away as of the current merge window because
> RCU-bh has gone away. (Aside from still being able to do things
> like rcu_read_lock_bh() as a documentation device.)
So in -RT rcu_read_lock_bh() does
{ local_bh_disabl
On Thu, Nov 08, 2018 at 02:53:51PM +0100, Jerome Brunet wrote:
> amlogic,meson-gxbb-scpi-sensors is both the driver and DT but is not
> documented. Just add it to amlogic's scpi documentation
>
> Signed-off-by: Jerome Brunet
> ---
> Documentation/devicetree/bindings/arm/amlogic,scpi.txt | 7
On Thu, 8 Nov 2018 at 12:35, Quentin Perret wrote:
>
> On Wednesday 07 Nov 2018 at 11:47:09 (+0100), Dietmar Eggemann wrote:
> > The important bit for EAS is that it only uses utilization in the
> > non-overutilized case. Here, utilization signals should look the same
> > between the two approache
On Thu, 8 Nov 2018, Vince Weaver wrote:
> [91760.326510] BUG: unable to handle kernel NULL pointer dereference at
>
> [91760.334876] PGD 0 P4D 0
> [91760.337596] Oops: [#1] SMP PTI
> [91760.341332] CPU: 6 PID: 0 Comm: swapper/6 Tainted: GW
> 4.20.0-rc1+ #11
On 2018-11-01 16:25:18 [-0700], Paul E. McKenney wrote:
> > --- a/kernel/rcu/Kconfig
> > +++ b/kernel/rcu/Kconfig
> > @@ -36,7 +36,7 @@ config TINY_RCU
> >
> > config RCU_EXPERT
> > bool "Make expert-level adjustments to RCU configuration"
> > - default n
> > + default y if PREEMPT_RT_FU
Linus,
please pull sound fixes for v4.20-rc2 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.20-rc2
The topmost commit is 5e93a125f521efd00d71af31c2a301f3d46af48c
sound fixes for 4.20-rc2
Two
On Thu, Nov 08, 2018 at 08:19:57AM -0700, Jonathan Corbet wrote:
> On Thu, 8 Nov 2018 16:05:17 +0100
> Peter Zijlstra wrote:
>
> > On Thu, Nov 08, 2018 at 07:49:20AM -0700, Jonathan Corbet wrote:
> > > Might it be worth asking Ted for a kernel summit slot to talk about this
> > > next week?
> >
On Thu, Nov 08, 2018 at 04:35:40PM +0100, Peter Zijlstra wrote:
> On Thu, Nov 08, 2018 at 07:31:09AM -0800, Paul E. McKenney wrote:
> > On Thu, Nov 08, 2018 at 10:21:51AM +0100, Peter Zijlstra wrote:
> > > On Wed, Nov 07, 2018 at 03:00:02PM -0800, Paul E. McKenney wrote:
> > > > Hello!
> > > >
> >
The variable capacity_margin local to the source and do not
need to be in global scope, so make it static.
Signed-off-by: Muchun Song
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 340a2d8d49cb..f622fc85
On Thu, Nov 08, 2018 at 04:52:26PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-11-01 16:02:35 [-0700], Paul E. McKenney wrote:
> > > The forcing of an expedited grace period is an expensive and very
> > > RT-application unfriendly operation, as it forcibly preempts all running
> > > tasks on
Vince Weaver writes:
> On Thu, 8 Nov 2018, Vince Weaver wrote:
>
>> [91760.326510] BUG: unable to handle kernel NULL pointer dereference at
>>
>> [91760.334876] PGD 0 P4D 0
>> [91760.337596] Oops: [#1] SMP PTI
>> [91760.341332] CPU: 6 PID: 0 Comm: swapper/6 Tainted: G
On Thu, Nov 08, 2018 at 03:44:28PM +0100, Thomas Bogendoerfer wrote:
> Commit bcec54bf3118 ("mips: switch to NO_BOOTMEM") broke SGI-IP27
> and NUMA enabled loongson3 by doing memblock_set_current_limit()
> before max_low_pfn has been evaluated. Both platforms need to do the
> memblock_set_current_l
The patch
regulator: Document new regulator-max-step-microvolt property
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the n
The patch
regulator: core: Add new max_uV_step constraint
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
regulator: core: Decouple regulators on regulator_unregister()
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
regulator: core: Don't allow to get regulator until all couples resolved
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually someti
The patch
regulator: core: Mutually resolve regulators coupling
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 h
The patch
regulator: lochnagar: Explicitly include register headers
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
regulator: core: Add voltage balancing mechanism
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
regulator: core: Change voltage setting path
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and
The patch
regulator: bd718x7: add missing linux/of.h inclusion (deja-vu)
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
regulator: core: Use ww_mutex for regulators locking
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 ho
The patch
regulator: Change regulator-coupled-max-spread property
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 2
The patch
regulator: core: Limit regulators coupling to a single couple
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the n
"Koenig, Christian" writes:
> Am 08.11.18 um 17:04 schrieb Eric Anholt:
>> This reverts commit 0efd2d2f68cd5dbddf4ecd974c33133257d16a8e. Fixes
>> this failure in V3D GPU reset:
>>
>> [ 1418.227796] Unable to handle kernel NULL pointer dereference at virtual
>> address 0018
>> [ 1418.235947]
On Thu, Nov 08, 2018 at 04:05:17PM +0100, Peter Zijlstra wrote:
> On Thu, Nov 08, 2018 at 07:49:20AM -0700, Jonathan Corbet wrote:
> > Might it be worth asking Ted for a kernel summit slot to talk about this
> > next week?
>
> Ah, on that, let me complain :-)
>
> My plumbers schedule is already 1
Hi,
On 08/11/18 10:49, Waiman Long wrote:
> On 10/04/2018 05:04 AM, Juri Lelli wrote:
[...]
> > +/**
> > + * cpuset_read_only_lock - Grab the callback_lock from cpuset subsystem.
> > + *
> > + * Description: As described in full details the comment above cpuset_mutex
> > + * and callback_lock de
Hi Dinh
On Thu, 8 Nov 2018 at 16:38, Dinh Nguyen wrote:
>
> Hi Clément,
>
> On 11/2/18 10:58 AM, Clément Péron wrote:
> > Hi Dinh,
> >
> > Could you have a look at this serie ?
> >
>
> I've applied 1/3 and 3/3. I need to look over 2/3 to determine if that
> patch is still valid. I think a better
Just booting up the latest git master (b00d209) on an aarch64 server and saw
this.
Nov 8 11:06:36 huawei-t2280-03 kernel: BUG: sleeping function called from
invalid context at mm/slab.h:421
Nov 8 11:06:36 huawei-t2280-03 kernel: in_atomic(): 1, irqs_disabled(): 128,
pid: 0, name: swapper/1
No
On Wed, Nov 7, 2018 at 11:30 PM Chen-Yu Tsai wrote:
>
> On Thu, Nov 8, 2018 at 2:42 PM Vasily Khoruzhick wrote:
> >
> > This commit enables I2S, digital and analog parts of audiocodec on
> > Pinebook
> >
> > Signed-off-by: Vasily Khoruzhick
> > ---
> > .../dts/allwinner/sun50i-a64-pinebook.dts
On Thu, 2018-11-08 at 16:04 +, Sudeep Holla wrote:
> On Thu, Nov 08, 2018 at 02:53:51PM +0100, Jerome Brunet wrote:
> > amlogic,meson-gxbb-scpi-sensors is both the driver and DT but is not
> > documented. Just add it to amlogic's scpi documentation
> >
> > Signed-off-by: Jerome Brunet
> > ---
On Mon, Nov 5, 2018 at 10:05 AM Gustavo Padovan
wrote:
>
> Hi Dhaval,
>
> On 9/19/18 7:13 PM, Dhaval Giani wrote:
> > Hi folks,
> >
> > Sasha and I are pleased to announce the Testing and Fuzzing track at
> > LPC [ 1 ]. We are planning to continue the discussions from last
> > year's microconferen
On Thu, Nov 08, 2018 at 11:21:33AM -0500, Theodore Y. Ts'o wrote:
> On Thu, Nov 08, 2018 at 04:05:17PM +0100, Peter Zijlstra wrote:
> > My plumbers schedule is already 100% booked with MCs and other things.
> > There is no kernel-summit schedule details available as of yet, but it
> > is already a
On Thu, 8 Nov 2018 11:21:33 -0500
"Theodore Y. Ts'o" wrote:
> I thought there was a slot already scheduled on the refereed track,
> "Towards a Linux Kernel Mainainer Handbook" (Tuesday at 4:45pm) for
> this purpose?
My expectation is that this will be an actual talk; it seemed rude to
assume tha
On Thu, Nov 8, 2018 at 9:02 AM Popa, Stefan Serban
wrote:
>
> On Sb, 2018-11-03 at 12:16 +, Jonathan Cameron wrote:
> > On Mon, 29 Oct 2018 18:38:31 +0200
> > Stefan Popa wrote:
> >
> > >
> > > The ad7124-4 and ad7124-8 are a family of 4 and 8 channel sigma-delta
> > > ADCs
> > > with 24-bit
On 2018-11-01 16:12:28 [-0700], Paul E. McKenney wrote:
> > The current check via srcu_online is slightly racy because after looking
> > at srcu_online there could be an interrupt that interrupted us long
> > enough until the CPU we checked against went offline.
>
> I don't see how this can happen
On 2018-11-01 16:21:34 [-0700], Paul E. McKenney wrote:
> > With RT_FULL we get the below wreckage:
>
> The code that this applies to has itself been fully frobbed as of the
> current merge window. I believe that it should now work in -rt as is,
> but who knows? ;-)
I will drop that patch in th
On Thu, Nov 08, 2018 at 05:02:57PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-11-01 16:18:04 [-0700], Paul E. McKenney wrote:
> > The need for this goes away as of the current merge window because
> > RCU-bh has gone away. (Aside from still being able to do things
> > like rcu_read_lock_bh(
On Thu, 8 Nov 2018, Alexander Shishkin wrote:
> Vince Weaver writes:
>
> > On Thu, 8 Nov 2018, Vince Weaver wrote:
> >
> >> [91760.326510] BUG: unable to handle kernel NULL pointer dereference at
> >>
> >> [91760.334876] PGD 0 P4D 0
> >> [91760.337596] Oops: [#1] SMP PTI
Use devm_kstrdup_const() in the tegra-hsp driver. This mostly serves as
an example of how to use this new routine to shrink driver code.
Also use devm_kzalloc() instead of regular kzalloc() to shrink the
driver even more.
Doorbell objects are only removed in the driver's remove callback so
it's s
Two threads can try to fire the irq_sim with different offsets and will
end up fighting for the irq_work asignment. To fix it: add a mutex and
lock it before firing.
Suggested-by: Uwe Kleine-König
Signed-off-by: Bartosz Golaszewski
---
include/linux/irq_sim.h | 1 +
kernel/irq/irq_sim.c| 5
On Jo, 2018-11-08 at 10:34 -0600, Rob Herring wrote:
> On Thu, Nov 8, 2018 at 9:02 AM Popa, Stefan Serban
> wrote:
> >
> >
> > On Sb, 2018-11-03 at 12:16 +, Jonathan Cameron wrote:
> > >
> > > On Mon, 29 Oct 2018 18:38:31 +0200
> > > Stefan Popa wrote:
> > >
> > > >
> > > >
> > > > The
On Tue, May 15, 2018 at 9:26 AM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:e2ab7e8abba4 kmsan: temporarily disable visitAsmInstructio..
> git tree: https://github.com/google/kmsan.git/master
> console output: https://syzkaller.appspot.com/x/log.txt?x
On Tue, May 15, 2018 at 9:26 AM, syzbot
wrote:
Hello,
syzbot found the following crash on:
HEAD commit:e2ab7e8abba4 kmsan: temporarily disable
visitAsmInstructio..
git tree: https://github.com/google/kmsan.git/master
console output: https://syzkaller.appspot.com/x/log.txt?x=158
On Thu, Nov 08, 2018 at 04:52:30PM +0200, Nick Kossifidis wrote:
> Στις 2018-11-07 14:28, Sudeep Holla έγραψε:
> >
> > I agree, but we have kernel code using it(arm64/kernel/topology.c). It's
> > too late to remove it. But we can always keep to optional if we move the
> > ARM64 binding as generic t
On 06.11.2018 0:30, Rob Herring wrote:
> On Sun, Oct 21, 2018 at 11:54:47PM +0300, Dmitry Osipenko wrote:
>> Add device-tree binding that describes CPU frequency-scaling hardware
>> found on NVIDIA Tegra20/30 SoC's.
>>
>> Signed-off-by: Dmitry Osipenko
>> ---
>> .../cpufreq/nvidia,tegra20-cpufreq
Am 08.11.18 um 17:19 schrieb Eric Anholt:
> "Koenig, Christian" writes:
>
>> Am 08.11.18 um 17:04 schrieb Eric Anholt:
>>> This reverts commit 0efd2d2f68cd5dbddf4ecd974c33133257d16a8e. Fixes
>>> this failure in V3D GPU reset:
>>>
>>> [ 1418.227796] Unable to handle kernel NULL pointer dereference
Hi,
This is the second version of my proposal for this helper. The
first version can be checked here:
https://lkml.org/lkml/2018/11/5/326
In order to support also ACPI properly, I decided to change the API.
The function fwnode_name() is now fwnode_get_name(), and instead of
returning pointer to t
This helper returns the name of the node. The name is
primarily expected to be returned from a new fwnode
operation meant for this purpose, but when no name is
returned, the helper will also attempt to read a device
property "name".
Signed-off-by: Heikki Krogerus
---
drivers/base/property.c | 2
This implements the get_name fwnode op for ACPI.
Signed-off-by: Heikki Krogerus
---
drivers/acpi/property.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/drivers/acpi/property.c b/drivers/acpi/property.c
index 8c7c4583b52d..5b4c659c95d4 100644
--- a/drivers/acpi/pr
By using fwnode_get_name() in fwnode_get_named_child_node(),
get_named_child_node implementations become boilerplate.
Removing all of them.
Signed-off-by: Heikki Krogerus
---
drivers/acpi/property.c | 20 +---
drivers/base/property.c | 9 -
drivers/of/property.c | 15 -
This implements get_name fwnode op for DT.
Signed-off-by: Heikki Krogerus
---
drivers/of/property.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/of/property.c b/drivers/of/property.c
index f46828e3b082..9bc8fe136fa3 100644
--- a/drivers/of/property.c
+++ b/drivers/of/
On Thu, 8 Nov 2018 18:18:23 +0200
Mike Rapoport wrote:
> On Thu, Nov 08, 2018 at 03:44:28PM +0100, Thomas Bogendoerfer wrote:
> > Commit bcec54bf3118 ("mips: switch to NO_BOOTMEM") broke SGI-IP27
> > and NUMA enabled loongson3 by doing memblock_set_current_limit()
> > before max_low_pfn has been
On Thu, Nov 8, 2018 at 4:35 PM Sven Van Asbroeck wrote:
> On Thu, Nov 8, 2018 at 9:20 AM Arnd Bergmann wrote:
> > + struct {
> > > + /* addresses IN NETWORK ORDER! */
> > > + __u32 ip_addr;
> > > + __u32 subnet_msk;
> > > + __u32 gate
We already support set_multiple(). Implement get_multiple() as well.
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-mockup.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/gpio/gpio-mockup.c b/drivers/gpio/gpio-mockup.c
index 3cd92912c414..a4c054cf9c5f 1
The first patch is a fix that should go in for 4.20.
Next two patches introduce features for 4.21 - lock protection of the
dummy chip structures and implementation of the get_multiple() callback.
Bartosz Golaszewski (3):
gpio: mockup: fix indicated direction
gpio: mockup: add locking
gpio:
While no user reported any race condition problems with gpio-mockup,
let's be on the safe side and use a mutex when performing any changes
on the dummy chip structures.
Suggested-by: Uwe Kleine-König
Signed-off-by: Bartosz Golaszewski
---
drivers/gpio/gpio-mockup.c | 50
Commit 3edfb7bd76bd ("gpiolib: Show correct direction from the
beginning") fixed an existing issue but broke libgpiod tests by
changing the default direction of dummy lines to output.
We don't break user-space so make gpio-mockup behave as before.
Signed-off-by: Bartosz Golaszewski
---
drivers/
On 08.11.2018 16:07, Mark Brown wrote:
> On Fri, Oct 05, 2018 at 06:36:37PM +0300, Dmitry Osipenko wrote:
>
>> Wait/wound mutex shall be used in order to avoid lockups on locking of
>> coupled regulators.
>
> This breaks the build due to a few of the drivers (wm8350 and da9210 at
> least) taking
On Thu, Nov 8, 2018 at 4:47 PM Sven Van Asbroeck wrote:
> On Thu, Nov 8, 2018 at 9:07 AM Arnd Bergmann wrote:
> > I see this is called from the interrupt handler at the moment, which
> > means you cannot call sleeping functions, but it also means that
> > the timeout may never happen because the
On Thu, Nov 8, 2018 at 8:48 AM, syzbot
wrote:
>> On Tue, May 15, 2018 at 9:26 AM, syzbot
>> wrote:
>>>
>>> Hello,
>
>
>>> syzbot found the following crash on:
>
>
>>> HEAD commit:e2ab7e8abba4 kmsan: temporarily disable
>>> visitAsmInstructio..
>>> git tree: https://github.com/google/kms
On Thu, 08 Nov 2018 02:30:02 PST (-0800), Arnd Bergmann wrote:
On Thu, Nov 8, 2018 at 3:10 AM Palmer Dabbelt wrote:
On Wed, 07 Nov 2018 13:09:39 PST (-0800), Arnd Bergmann wrote:
> On Wed, Nov 7, 2018 at 7:30 PM David Abdurachmanov
> wrote:
>> On Wed, Nov 7, 2018 at 1:08 AM Palmer Dabbelt wr
On Thu, 08 Nov 2018 02:38:22 PST (-0800), david.abdurachma...@gmail.com wrote:
On Thu, Nov 8, 2018 at 3:10 AM Palmer Dabbelt wrote:
On Wed, 07 Nov 2018 13:09:39 PST (-0800), Arnd Bergmann wrote:
> On Wed, Nov 7, 2018 at 7:30 PM David Abdurachmanov
> wrote:
>> On Wed, Nov 7, 2018 at 1:08 AM Pa
On 2018-11-01 16:30:31 [-0700], Paul E. McKenney wrote:
> > (Commit 258ba8e089db23f760139266c232f01bad73f85c from linux-rcu)
> >
> > This commit reverts a series of commits starting with fcc635436501 ("rcu:
> > Make expedited GPs handle CPU 0 being offline") and its successors, thus
> > queueing e
Hi,
* Lukasz Luba [181009 08:36]:
> PROVE_LOCKING enables LOCKDEP, which causes big overhead on cache and
> bus transactions.
>
> On some ARM big.LITTLE architecutres (Exynos 5433) the overhead is really big.
> The overhead can be measures using hackbench which will speed up
> by x3 times (11sec
The SML-5442TW is an STB for O2 Czech IPTV/VOD and DVB-S based on the
Amlogic P231 reference design using the S905D chipset. Specs:
2GB DDR3 RAM
8GB eMMC storage
10/100 Base-T Ethernet
802.11 a/b/g/n/ac + BT 4.1 HS sdio wireless module (QCA9377)
2x single colour and 1x dual colour LEDs on the fron
Smartlabs are a professional integrator of Interactive TV solutions
and IPTV/VOD devices.
[1] (https://www.smartlabs.tv/en/about/)
Signed-off-by: Christian Hewitt
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetr
This series adds new bindings and a device-tree file for the Smartlabs
SML-5442TW set-top box.
v2 - removed audio nodes
- changes soundcard name to "meson-gx-audio"
- added missing uart-has-rtscts;
Christian Hewitt (3):
dt-bindings: Add vendor prefix for Smartlabs
dt-bindings: arm: amlo
The Smartlabs SML-5442TW is broadly similar to the P231 reference design
but with the following differences:
- Yellow and Blue front-panel LEDs are available but disabled
- Red/Green LED is used to signal off/on status
- GPIOX_17 is set high to enable the QCA9377 wireless module
- uart_AO can be a
>
> Move tpm_validate_command() to tpm2-space.c and make it part of the
> tpm2_prepare_space() flow. Make cc resolution as part of the TPM space
> functionality in order to detach it from rest of the tpm_transmit() flow.
>
> Signed-off-by: Jarkko Sakkinen
> Reviewed-by: Stefan Berger
> ---
>
On 26/08/18 16:20, Parthiban Nallathambi wrote:
> Hello Marc,
>
> Thanks for your feedback.
>
> On 8/13/18 1:46 PM, Marc Zyngier wrote:
>> On 12/08/18 13:22, Parthiban Nallathambi wrote:
>>> Actions Semi Owl family SoC's S500, S700 and S900 provides support
>>> for 3 external interrupt controller
On Thu, 2018-11-08 at 21:01 +0400, Christian Hewitt wrote:
> The Smartlabs SML-5442TW is broadly similar to the P231 reference design
> but with the following differences:
>
> - Yellow and Blue front-panel LEDs are available but disabled
> - Red/Green LED is used to signal off/on status
> - GPIOX_
From:Miss:Fatima Yusuf.
For sure this mail would definitely come to you as a surprise, but do take your
good time to go through it, My name is Ms.Fatima Yusuf,i am from Ivory Coast.
I lost my parents a year and couple of months ago. My father was a serving
director of the Agro-exporting boar
Am 08.11.18 um 18:01 schrieb Christian Hewitt:
> Smartlabs are a professional integrator of Interactive TV solutions
> and IPTV/VOD devices.
>
> [1] (https://www.smartlabs.tv/en/about/)
"[1]" is not referenced anywhere, so you could just as well use a plain
link?
>
> Signed-off-by: Christian He
On Thu, 8 Nov 2018 at 02:49, Suzuki K Poulose wrote:
>
> Leo,
>
> On 07/11/2018 03:23, leo@linaro.org wrote:
> > Hi Mathieu,
> >
> > On Mon, Nov 05, 2018 at 03:26:30PM -0700, Mathieu Poirier wrote:
> >> This patch deals with the release of the CLAIM tag when the ETM is
> >> operated from perf.
On Thu, Nov 08, 2018 at 05:38:51PM +0100, Sebastian Andrzej Siewior wrote:
> On 2018-11-01 16:12:28 [-0700], Paul E. McKenney wrote:
> > > The current check via srcu_online is slightly racy because after looking
> > > at srcu_online there could be an interrupt that interrupted us long
> > > enough
pci_root_ops is only written to from within intel_mid_pci_init. This
is linked in only when CONFIG_X86_INTEL_MID is set. If not for this,
pci_root_ops could be marked as const.
Fix this by replacing pci_root_ops usage with pci_root_ops_ptr. If
CONFIG_X86_INTEL_MID is set, pci_root_ops_ptr will be
Hi,
On 07/11/2018 23:08, Mathieu Poirier wrote:
This patch moves access to the CLAIM tag so that no modification to the HW
happens before and after the CLAIM operation has been carried.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-etm3x.c | 16
1
On 2018-11-07 11:18 p.m., Nadav Amit wrote:
>> Apparently gcc will treat them like basic blocks and possibly move them
>> around.
>
> Maybe it is possible to break the compilation of each object into two
> stages: first, compile the source without assembly, and then take the
> generated .s fil
On 2018-11-08 08:42:47 [-0800], Paul E. McKenney wrote:
> On Thu, Nov 08, 2018 at 05:02:57PM +0100, Sebastian Andrzej Siewior wrote:
> > On 2018-11-01 16:18:04 [-0700], Paul E. McKenney wrote:
> > > The need for this goes away as of the current merge window because
> > > RCU-bh has gone away. (Asi
Add driver for Synopsys DesignWare I3C master IP
Signed-off-by: Vitor soares
---
Change in v3:
- Use struct_size() (suggested by Matthew)
Change in v2:
- Rename some variables
- Remove dw_i3c_master_dev_set_info()
- Ajust code to match the changes made of i3c subsystem
- Use readsl/writesl() to
Changes from v2:
* Support for Huawei MBX
* Style and formating issues
[PATCH v3 1/3]
The first patch adds support for missing hotkeys on some models.
[PATCH v3 2/3]
This one enables the front speakers on the Huawei Matebook X Pro (MBXP). This
solves bug 200501 https://bugzilla.kernel.org/show_b
Some of Huawei laptops come with a LED in the micmute key. This patch
enables and disable this LED accordingly.
Signed-off-by: Ayman Bagabas
---
drivers/platform/x86/huawei_wmi.c| 1 +
include/linux/platform_data/x86/huawei_wmi.h | 9
sound/pci/hda/huawei_wmi_helper.c
This patch solves bug 200501 'Only 2 of 4 speakers playing sound.'
https://bugzilla.kernel.org/show_bug.cgi?id=200501
It enables the front speakers on Huawei Matebook X Pro laptops.
These laptops come with Dolby Atmos sound system and these pins
configuration enables the front speakers.
Signed-off
This driver adds support for missing hotkeys on some Huawei laptops.
Currently, only Huawei Matebook X and Matebook X Pro is supported.
Signed-off-by: Ayman Bagabas
---
drivers/platform/x86/Kconfig | 11 ++
drivers/platform/x86/Makefile | 1 +
drivers/platform/x86/huawei_wmi.c | 235
On Thu, Nov 8, 2018 at 1:13 AM Peter Zijlstra wrote:
>
> On Thu, Nov 08, 2018 at 08:40:12AM +0100, Ingo Molnar wrote:
> > > + - Cc: ``cc-ed-person ``
> > > +
> > > + If the patch should be backported to stable, then please add a '``Cc:
> > > + sta...@vger.kernel.org``' tag, but do not Cc stabl
On Thu, Nov 08, 2018 at 03:47:32PM +, Michael Matz wrote:
> What tglx said. If you don't intend such functions to be called
> from other units make them static, if you do intend them to be callable
> declare the properly.
>
> [There's also one subtle issue with argument promotions. prototy
On Thu, Nov 08, 2018 at 09:19:33AM -0800, Dan Williams wrote:
> I know at least StGit mail does not grok that "#"notation. I've
> stopped using it in favor of a "Fixes:" tag. I would think "Fixes:" is
> preferred over "# " if only because it can be used to track
> fixes to commits that have been ba
From: Rafael J. Wysocki
Subject: [PATCH] cpuidle: New timer events oriented governor for tickless
systems
The venerable menu governor does some thigns that are quite
questionable in my view.
First, it includes timer wakeups in the pattern detection data and
mixes them up with wakeups from other
* Janusz Krzysztofik [181107 13:28]:
> While playing with initialization order of modem device, it has been
> discovered that under some circumstances (early console init, I
> believe) its .pm() callback may be called before the
> uart_port->private_data pointer is initialized from
> plat_serial82
On Mon, 5 Nov 2018 11:55:46 -0500
Daniel Jordan wrote:
> Motivates and explains the ktask API for kernel clients.
A couple of quick thoughts:
- Agree with Peter on the use of "task"; something like "job" would be far
less likely to create confusion. Maybe you could even call it a "batch
j
On 07/11/2018 23:08, Mathieu Poirier wrote:
This patch deals with the release of the CLAIM tag when the ETM is
operated from perf. Otherwise the tag is left asserted and subsequent
requests to use the device fail.
Signed-off-by: Mathieu Poirier
---
drivers/hwtracing/coresight/coresight-et
901 - 1000 of 1335 matches
Mail list logo
