Hi Anders,
> On 30 Oct 2018, at 08:38, Anders Roxell wrote:
>
> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
> pages")
> has successfully identified code that leaves a page with W+X
> permissions.
>
> [3.245140] arm64/mm: Found insecure W+X mapping at
Hi Anders,
> On 30 Oct 2018, at 08:38, Anders Roxell wrote:
>
> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
> pages")
> has successfully identified code that leaves a page with W+X
> permissions.
>
> [3.245140] arm64/mm: Found insecure W+X mapping at
On Tue, Oct 30, 2018 at 12:38:50PM +0100, Anders Roxell wrote:
> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
> pages")
> has successfully identified code that leaves a page with W+X
> permissions.
>
> [3.245140] arm64/mm: Found insecure W+X mapping at address
On Tue, Oct 30, 2018 at 12:38:50PM +0100, Anders Roxell wrote:
> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
> pages")
> has successfully identified code that leaves a page with W+X
> permissions.
>
> [3.245140] arm64/mm: Found insecure W+X mapping at address
On Tue 30-10-18 18:47:43, Tetsuo Handa wrote:
> On 2018/10/30 15:31, Michal Hocko wrote:
> > On Tue 30-10-18 13:45:22, Tetsuo Handa wrote:
> >> Michal Hocko wrote:
> >>> @@ -3156,6 +3166,13 @@ void exit_mmap(struct mm_struct *mm)
> >>> vma = remove_vma(vma);
> >>> }
> >>>
On Tue 30-10-18 18:47:43, Tetsuo Handa wrote:
> On 2018/10/30 15:31, Michal Hocko wrote:
> > On Tue 30-10-18 13:45:22, Tetsuo Handa wrote:
> >> Michal Hocko wrote:
> >>> @@ -3156,6 +3166,13 @@ void exit_mmap(struct mm_struct *mm)
> >>> vma = remove_vma(vma);
> >>> }
> >>>
Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
pages")
has successfully identified code that leaves a page with W+X
permissions.
[3.245140] arm64/mm: Found insecure W+X mapping at address
(ptrval)/0x00d9
[3.245771] WARNING: CPU: 0 PID: 1
Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
pages")
has successfully identified code that leaves a page with W+X
permissions.
[3.245140] arm64/mm: Found insecure W+X mapping at address
(ptrval)/0x00d9
[3.245771] WARNING: CPU: 0 PID: 1
This happened while running in qemu-system-aarch64, the AMBA PL011 UART
driver when enabling CONFIG_DEBUG_TEST_DRIVER_REMOVE.
arch_initcall(pl011_init) came before subsys_initcall(default_bdi_init),
devtmpfs' handle_remove() crashes because the reference count is a NULL
pointer only because
This happened while running in qemu-system-aarch64, the AMBA PL011 UART
driver when enabling CONFIG_DEBUG_TEST_DRIVER_REMOVE.
arch_initcall(pl011_init) came before subsys_initcall(default_bdi_init),
devtmpfs' handle_remove() crashes because the reference count is a NULL
pointer only because
When the test 'CONFIG_DEBUG_TEST_DRIVER_REMOVE=y' is enabled,
arch_initcall(pl011_init) came before subsys_initcall(default_bdi_init).
devtmpfs gets killed because we try to remove a file and decrement the
wb reference count before the noop_backing_device_info gets initialized.
[0.332075]
When the test 'CONFIG_DEBUG_TEST_DRIVER_REMOVE=y' is enabled,
arch_initcall(pl011_init) came before subsys_initcall(default_bdi_init).
devtmpfs gets killed because we try to remove a file and decrement the
wb reference count before the noop_backing_device_info gets initialized.
[0.332075]
From: Colin Ian King
Trivial fix to clean up an indentation issue, remove spaces
Signed-off-by: Colin Ian King
---
drivers/bluetooth/hci_intel.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/bluetooth/hci_intel.c b/drivers/bluetooth/hci_intel.c
index
From: Colin Ian King
Trivial fix to clean up an indentation issue, remove spaces
Signed-off-by: Colin Ian King
---
drivers/bluetooth/hci_intel.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/bluetooth/hci_intel.c b/drivers/bluetooth/hci_intel.c
index
Paolo Bonzini writes:
>> If you "have to enable or disable anything" it means you have to
>> override the default. But the default in this patches is "no change
>> compared to before the patches", leaving tracing of both host and guest
>> entirely to the host, so I don't understand your remark.
Paolo Bonzini writes:
>> If you "have to enable or disable anything" it means you have to
>> override the default. But the default in this patches is "no change
>> compared to before the patches", leaving tracing of both host and guest
>> entirely to the host, so I don't understand your remark.
On Fri, 26 Oct 2018, Tomas Winkler wrote:
Remove redundant lines in the kdoc:
Fixes kdoc warnings:
drivers/char/tpm/tpm_ibmvtpm.c:42: warning: Cannot understand *
on line 42 - I thought it was a doc line
drivers/char/tpm/tpm_ibmvtpm.c:57: warning: Cannot understand *
on line 57 - I thought
On 30.10.2018 12:48, Cherian, George wrote:
Implement workaround for ThunderX2 Errata-129 (documented in
CN99XX Known Issues" available at Cavium support site).
As per ThunderX2errata-129, USB 2 device may come up as USB 1
if a connection to a USB 1 device is followed by another connection to
a
On Fri, 26 Oct 2018, Tomas Winkler wrote:
Remove redundant lines in the kdoc:
Fixes kdoc warnings:
drivers/char/tpm/tpm_ibmvtpm.c:42: warning: Cannot understand *
on line 42 - I thought it was a doc line
drivers/char/tpm/tpm_ibmvtpm.c:57: warning: Cannot understand *
on line 57 - I thought
On 30.10.2018 12:48, Cherian, George wrote:
Implement workaround for ThunderX2 Errata-129 (documented in
CN99XX Known Issues" available at Cavium support site).
As per ThunderX2errata-129, USB 2 device may come up as USB 1
if a connection to a USB 1 device is followed by another connection to
a
On Tue, Oct 30, 2018 at 12:49 AM Stephen Rothwell wrote:
>
> Hi all,
>
> On Tue, 30 Oct 2018 10:46:37 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the compiler-attributes tree got a conflict
> > in:
> >
> > include/linux/compiler-gcc.h
> >
> > between commit:
> >
> >
On Tue, Oct 30, 2018 at 12:49 AM Stephen Rothwell wrote:
>
> Hi all,
>
> On Tue, 30 Oct 2018 10:46:37 +1100 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the compiler-attributes tree got a conflict
> > in:
> >
> > include/linux/compiler-gcc.h
> >
> > between commit:
> >
> >
On Tue, Oct 30, 2018 at 11:00:51AM +0800, Peter Xu wrote:
> On Mon, Oct 29, 2018 at 12:29:22PM -0600, Alex Williamson wrote:
> > On Mon, 29 Oct 2018 17:14:46 +0800
> > Jason Wang wrote:
> >
> > > On 2018/10/29 上午10:42, Simon Guo wrote:
> > > > Hi,
> > > >
> > > > I am using network device pass
On Tue, Oct 30, 2018 at 11:00:51AM +0800, Peter Xu wrote:
> On Mon, Oct 29, 2018 at 12:29:22PM -0600, Alex Williamson wrote:
> > On Mon, 29 Oct 2018 17:14:46 +0800
> > Jason Wang wrote:
> >
> > > On 2018/10/29 上午10:42, Simon Guo wrote:
> > > > Hi,
> > > >
> > > > I am using network device pass
On Tue, Oct 30, 2018 at 12:12 PM Daniel Colascione wrote:
>
> On Tue, Oct 30, 2018 at 11:04 AM, Christian Brauner
> wrote:
> > On Tue, Oct 30, 2018 at 11:48 AM Daniel Colascione
> > wrote:
> >>
> >> On Tue, Oct 30, 2018 at 10:40 AM, Christian Brauner
> >> wrote:
> >> > On Tue, Oct 30, 2018 at
On Tue, Oct 30, 2018 at 12:12 PM Daniel Colascione wrote:
>
> On Tue, Oct 30, 2018 at 11:04 AM, Christian Brauner
> wrote:
> > On Tue, Oct 30, 2018 at 11:48 AM Daniel Colascione
> > wrote:
> >>
> >> On Tue, Oct 30, 2018 at 10:40 AM, Christian Brauner
> >> wrote:
> >> > On Tue, Oct 30, 2018 at
Hi Dean,
Attached are 2 different attempts at fixing this.
When trying these patches do not forget to remove the revert of the
"Stop-marking-clocks-as-CLK_IS_CRITICAL" commit.
Please first try the
0001-ASoC-intel-cht_bsw_max98090_ti-Use-pmc_plt_clk_0-ins.patch
patch I expect that one to do
Hi Dean,
Attached are 2 different attempts at fixing this.
When trying these patches do not forget to remove the revert of the
"Stop-marking-clocks-as-CLK_IS_CRITICAL" commit.
Please first try the
0001-ASoC-intel-cht_bsw_max98090_ti-Use-pmc_plt_clk_0-ins.patch
patch I expect that one to do
From: Colin Ian King
Trivial fix to clean up an indentation issue
Signed-off-by: Colin Ian King
---
drivers/staging/xgifb/XGI_main_26.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/xgifb/XGI_main_26.c
b/drivers/staging/xgifb/XGI_main_26.c
index
From: Colin Ian King
Trivial fix to clean up an indentation issue
Signed-off-by: Colin Ian King
---
drivers/staging/xgifb/XGI_main_26.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/xgifb/XGI_main_26.c
b/drivers/staging/xgifb/XGI_main_26.c
index
Wenwen Wang writes:
> Hello,
>
> Can anyone confirm this bug? Thanks!
Commonly this burden lies with the author of the patch. If you fix a
bug, you need to be able to demonstrate it. If it's a mere hypothesis,
there needs to be a detailed analysis of how exactly can this be
exploited and what
Wenwen Wang writes:
> Hello,
>
> Can anyone confirm this bug? Thanks!
Commonly this burden lies with the author of the patch. If you fix a
bug, you need to be able to demonstrate it. If it's a mere hypothesis,
there needs to be a detailed analysis of how exactly can this be
exploited and what
From: Colin Ian King
Trivial fix to clean up indentation issues
Signed-off-by: Colin Ian King
---
drivers/staging/vt6656/firmware.c | 2 +-
drivers/staging/vt6656/main_usb.c | 8
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/vt6656/firmware.c
From: Colin Ian King
Trivial fix to clean up indentation issues
Signed-off-by: Colin Ian King
---
drivers/staging/vt6656/firmware.c | 2 +-
drivers/staging/vt6656/main_usb.c | 8
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/vt6656/firmware.c
On Tue, Oct 30, 2018 at 11:04 AM, Christian Brauner
wrote:
> On Tue, Oct 30, 2018 at 11:48 AM Daniel Colascione wrote:
>>
>> On Tue, Oct 30, 2018 at 10:40 AM, Christian Brauner
>> wrote:
>> > On Tue, Oct 30, 2018 at 11:39:11AM +0100, Christian Brauner wrote:
>> >> On Tue, Oct 30, 2018 at
On 30/10/18 11:45, Peter Zijlstra wrote:
[...]
> Hurm.. right. We knew of this issue back when we did it.
> I suppose now it hurts and we need to figure something out.
>
> By virtue of being a real-time class, we do indeed need to have deadline
> on the wall-clock. But if we then don't account
On Tue, Oct 30, 2018 at 11:04 AM, Christian Brauner
wrote:
> On Tue, Oct 30, 2018 at 11:48 AM Daniel Colascione wrote:
>>
>> On Tue, Oct 30, 2018 at 10:40 AM, Christian Brauner
>> wrote:
>> > On Tue, Oct 30, 2018 at 11:39:11AM +0100, Christian Brauner wrote:
>> >> On Tue, Oct 30, 2018 at
On 30/10/18 11:45, Peter Zijlstra wrote:
[...]
> Hurm.. right. We knew of this issue back when we did it.
> I suppose now it hurts and we need to figure something out.
>
> By virtue of being a real-time class, we do indeed need to have deadline
> on the wall-clock. But if we then don't account
The Keystone QMSS driver is pretty damaged, in the sense that it
does things like this:
irq_set_affinity_hint(irq, to_cpumask(_map));
where cpu_map is a local variable. As we leave the function, this
will point to nowhere-land, and things will end-up badly.
Instead, let's use a proper
The Keystone QMSS driver is pretty damaged, in the sense that it
does things like this:
irq_set_affinity_hint(irq, to_cpumask(_map));
where cpu_map is a local variable. As we leave the function, this
will point to nowhere-land, and things will end-up badly.
Instead, let's use a proper
From: Colin Ian King
Trivial fix to clean up indentation issues across the driver
Signed-off-by: Colin Ian King
---
drivers/staging/speakup/kobjects.c | 2 +-
drivers/staging/speakup/speakup_decpc.c | 6 +++---
drivers/staging/speakup/speakup_keypc.c | 2 +-
3 files changed, 5
From: Colin Ian King
Trivial fix to clean up indentation issues across the driver
Signed-off-by: Colin Ian King
---
drivers/staging/speakup/kobjects.c | 2 +-
drivers/staging/speakup/speakup_decpc.c | 6 +++---
drivers/staging/speakup/speakup_keypc.c | 2 +-
3 files changed, 5
Hi Peter,
On Tue, 30 Oct 2018 11:45:54 +0100
Peter Zijlstra wrote:
[...]
> > 2. This is related to perf_event_open syscall reproducer does
> > before becoming DEADLINE and entering the busy loop. Enabling of
> > perf swevents generates lot of hrtimers load that happens in the
> > reproducer
Hi Peter,
On Tue, 30 Oct 2018 11:45:54 +0100
Peter Zijlstra wrote:
[...]
> > 2. This is related to perf_event_open syscall reproducer does
> > before becoming DEADLINE and entering the busy loop. Enabling of
> > perf swevents generates lot of hrtimers load that happens in the
> > reproducer
The reason of including here is just for BIT() and
GENMASK() macros.
Since commit 8bd9cb51daac8 ("locking/atomics, asm-generic: Move some
macros from to a new file"),
is enough for such compile-time macros.
Signed-off-by: Masahiro Yamada
---
drivers/mmc/host/sdhci-cadence.c | 2 +-
1 file
The reason of including here is just for BIT() and
GENMASK() macros.
Since commit 8bd9cb51daac8 ("locking/atomics, asm-generic: Move some
macros from to a new file"),
is enough for such compile-time macros.
Signed-off-by: Masahiro Yamada
---
drivers/mmc/host/sdhci-cadence.c | 2 +-
1 file
On Tue, Oct 30, 2018 at 11:48 AM Daniel Colascione wrote:
>
> On Tue, Oct 30, 2018 at 10:40 AM, Christian Brauner
> wrote:
> > On Tue, Oct 30, 2018 at 11:39:11AM +0100, Christian Brauner wrote:
> >> On Tue, Oct 30, 2018 at 08:50:22AM +, Daniel Colascione wrote:
> >> > On Tue, Oct 30, 2018 at
On Tue, Oct 30, 2018 at 11:48 AM Daniel Colascione wrote:
>
> On Tue, Oct 30, 2018 at 10:40 AM, Christian Brauner
> wrote:
> > On Tue, Oct 30, 2018 at 11:39:11AM +0100, Christian Brauner wrote:
> >> On Tue, Oct 30, 2018 at 08:50:22AM +, Daniel Colascione wrote:
> >> > On Tue, Oct 30, 2018 at
Hi,
On 30-10-18 11:17, Hans de Goede wrote:
Hi Pierre-Louis,
On 29-10-18 23:03, Pierre-Louis Bossart wrote:
On 10/29/18 2:08 PM, Dean Wallace wrote:
On 29-10-18, Andy Shevchenko wrote:
On Mon, Oct 29, 2018 at 7:52 PM Andy Shevchenko
wrote:
Cc: Pierre as well.
On Mon, Oct 29, 2018 at
Hi,
On 30-10-18 11:17, Hans de Goede wrote:
Hi Pierre-Louis,
On 29-10-18 23:03, Pierre-Louis Bossart wrote:
On 10/29/18 2:08 PM, Dean Wallace wrote:
On 29-10-18, Andy Shevchenko wrote:
On Mon, Oct 29, 2018 at 7:52 PM Andy Shevchenko
wrote:
Cc: Pierre as well.
On Mon, Oct 29, 2018 at
Hi Pavan,
On Tue, 30 Oct 2018 at 10:19, Pavan Kondeti wrote:
>
> Hi Vincent,
>
> On Fri, Oct 26, 2018 at 06:11:43PM +0200, Vincent Guittot wrote:
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index 6806c27..7a69673 100644
> > --- a/kernel/sched/fair.c
> > +++
Hi Pavan,
On Tue, 30 Oct 2018 at 10:19, Pavan Kondeti wrote:
>
> Hi Vincent,
>
> On Fri, Oct 26, 2018 at 06:11:43PM +0200, Vincent Guittot wrote:
> > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> > index 6806c27..7a69673 100644
> > --- a/kernel/sched/fair.c
> > +++
On Tue, Oct 30, 2018 at 10:40 AM, Christian Brauner
wrote:
> On Tue, Oct 30, 2018 at 11:39:11AM +0100, Christian Brauner wrote:
>> On Tue, Oct 30, 2018 at 08:50:22AM +, Daniel Colascione wrote:
>> > On Tue, Oct 30, 2018 at 3:21 AM, Joel Fernandes wrote:
>> > > On Mon, Oct 29, 2018 at 3:11 PM
On Tue, Oct 30, 2018 at 10:40 AM, Christian Brauner
wrote:
> On Tue, Oct 30, 2018 at 11:39:11AM +0100, Christian Brauner wrote:
>> On Tue, Oct 30, 2018 at 08:50:22AM +, Daniel Colascione wrote:
>> > On Tue, Oct 30, 2018 at 3:21 AM, Joel Fernandes wrote:
>> > > On Mon, Oct 29, 2018 at 3:11 PM
On RZ/N1 devices, there are 3 Synopsys DesignWare GPIO blocks each
configured to have 32 interrupt outputs, so we have a total of 96 GPIO
interrupts. All of these are passed to the GPIO IRQ Muxer, which selects
8 of the GPIO interrupts to pass onto the GIC. The interrupt signals
aren't latched, so
On RZ/N1 devices, there are 3 Synopsys DesignWare GPIO blocks each
configured to have 32 interrupt outputs, so we have a total of 96 GPIO
interrupts. All of these are passed to the GPIO IRQ Muxer, which selects
8 of the GPIO interrupts to pass onto the GIC. The interrupt signals
aren't latched, so
On Wed, Oct 24, 2018 at 02:03:35PM +0200, Juri Lelli wrote:
> Pain points:
>
> 1. Granularity of enforcement (at each tick) is huge compared with
> the task runtime. This makes starting the replenishment timer,
> when runtime is depleted, always to fail (because old deadline
> is way
On Wed, Oct 24, 2018 at 02:03:35PM +0200, Juri Lelli wrote:
> Pain points:
>
> 1. Granularity of enforcement (at each tick) is huge compared with
> the task runtime. This makes starting the replenishment timer,
> when runtime is depleted, always to fail (because old deadline
> is way
Commit-ID: c6ee7a548e2c291398b4f32c1f741c66b9f98e1c
Gitweb: https://git.kernel.org/tip/c6ee7a548e2c291398b4f32c1f741c66b9f98e1c
Author: Dave Jiang
AuthorDate: Thu, 25 Oct 2018 13:26:45 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 30 Oct 2018 11:36:43 +0100
x86/numa_emulation: Fix
Commit-ID: c6ee7a548e2c291398b4f32c1f741c66b9f98e1c
Gitweb: https://git.kernel.org/tip/c6ee7a548e2c291398b4f32c1f741c66b9f98e1c
Author: Dave Jiang
AuthorDate: Thu, 25 Oct 2018 13:26:45 -0700
Committer: Thomas Gleixner
CommitDate: Tue, 30 Oct 2018 11:36:43 +0100
x86/numa_emulation: Fix
On Tue, Oct 30, 2018 at 11:39:11AM +0100, Christian Brauner wrote:
> On Tue, Oct 30, 2018 at 08:50:22AM +, Daniel Colascione wrote:
> > On Tue, Oct 30, 2018 at 3:21 AM, Joel Fernandes wrote:
> > > On Mon, Oct 29, 2018 at 3:11 PM Daniel Colascione
> > > wrote:
> > >>
> > >> Add a simple
On Tue, Oct 30, 2018 at 11:39:11AM +0100, Christian Brauner wrote:
> On Tue, Oct 30, 2018 at 08:50:22AM +, Daniel Colascione wrote:
> > On Tue, Oct 30, 2018 at 3:21 AM, Joel Fernandes wrote:
> > > On Mon, Oct 29, 2018 at 3:11 PM Daniel Colascione
> > > wrote:
> > >>
> > >> Add a simple
On Tue, Oct 30, 2018 at 08:50:22AM +, Daniel Colascione wrote:
> On Tue, Oct 30, 2018 at 3:21 AM, Joel Fernandes wrote:
> > On Mon, Oct 29, 2018 at 3:11 PM Daniel Colascione wrote:
> >>
> >> Add a simple proc-based kill interface. To use /proc/pid/kill, just
> >> write the signal number in
On Tue, Oct 30, 2018 at 08:50:22AM +, Daniel Colascione wrote:
> On Tue, Oct 30, 2018 at 3:21 AM, Joel Fernandes wrote:
> > On Mon, Oct 29, 2018 at 3:11 PM Daniel Colascione wrote:
> >>
> >> Add a simple proc-based kill interface. To use /proc/pid/kill, just
> >> write the signal number in
On 29 October 2018 at 23:36, Thomas Gleixner wrote:
> Raju,
>
> On Thu, 11 Oct 2018, Raju P.L.S.S.S.N wrote:
>>
>> +/**
>> + * tick_nohz_get_next_wakeup - return the next wake up of the CPU
>
> Lacks documentation of @cpu. Please include kernel docs into your test
> builds.
Good point!
>
>> +
On 29 October 2018 at 23:36, Thomas Gleixner wrote:
> Raju,
>
> On Thu, 11 Oct 2018, Raju P.L.S.S.S.N wrote:
>>
>> +/**
>> + * tick_nohz_get_next_wakeup - return the next wake up of the CPU
>
> Lacks documentation of @cpu. Please include kernel docs into your test
> builds.
Good point!
>
>> +
Hi,
On 26/09/2018 16:12, Valentin Schneider wrote:
> The alignment of the condition is off, clean that up.
>
> Also, logical operators have lower precedence than bitwise/relational
> operators, so remove one layer of parentheses to make the condition a
> bit simpler to follow.
>
>
Hi,
On 26/09/2018 16:12, Valentin Schneider wrote:
> The alignment of the condition is off, clean that up.
>
> Also, logical operators have lower precedence than bitwise/relational
> operators, so remove one layer of parentheses to make the condition a
> bit simpler to follow.
>
>
Hi!
> > https://github.com/hackerspace/olpc-xo175-linux/wiki/How-to-run-an-up-to-date-Linux-on-a-XO-1.75
> >
> > I didn't test it yet -- will do when I get home in the evening. But
> > chances are it's good enough and I guess you'd be able to get it
> > working even if I messed up some details.
Hi!
> > https://github.com/hackerspace/olpc-xo175-linux/wiki/How-to-run-an-up-to-date-Linux-on-a-XO-1.75
> >
> > I didn't test it yet -- will do when I get home in the evening. But
> > chances are it's good enough and I guess you'd be able to get it
> > working even if I messed up some details.
On Tue, 30 Oct 2018, Kang, Luwei wrote:
> > >> This part is in the " Intel® Architecture Instruction Set Extensions and
> > >> Future Features Programming Reference"
> > >> https://software.intel.com/sites/default/files/managed/c5/15/architec
> > >>
On Tue, 30 Oct 2018, Kang, Luwei wrote:
> > >> This part is in the " Intel® Architecture Instruction Set Extensions and
> > >> Future Features Programming Reference"
> > >> https://software.intel.com/sites/default/files/managed/c5/15/architec
> > >>
The efuse found in gx SoC requires a peripheral clock to properly operate.
We have been able to work without it until now because the clock was on by
default, and left on by the CCF. Soon, it will not be the case anymore, so
the device needs to claim the clock it needs
Signed-off-by: Jerome
The first change of this patchset just adds add error message in case
of failure. If there is problem with the secure monitor, the
SM_EFUSE_USER_MAX call will be first one to fail so it is better if it
give us a clue to help debugging, instead af silently failing.
Next this series adds the
Add an explicit error message when SM_EFUSE_USER_MAX command fails
Signed-off-by: Jerome Brunet
---
drivers/nvmem/meson-efuse.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/nvmem/meson-efuse.c b/drivers/nvmem/meson-efuse.c
index d769840d1e18..40b9df1d030d
Get and enable the peripheral clock required by the efuse device.
The driver has been handle to work without it so far because the
clock was left enabled by default but it won't be the case soon.
Signed-off-by: Jerome Brunet
---
drivers/nvmem/meson-efuse.c | 25 +
1 file
The first change of this patchset just adds add error message in case
of failure. If there is problem with the secure monitor, the
SM_EFUSE_USER_MAX call will be first one to fail so it is better if it
give us a clue to help debugging, instead af silently failing.
Next this series adds the
Add an explicit error message when SM_EFUSE_USER_MAX command fails
Signed-off-by: Jerome Brunet
---
drivers/nvmem/meson-efuse.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/nvmem/meson-efuse.c b/drivers/nvmem/meson-efuse.c
index d769840d1e18..40b9df1d030d
Get and enable the peripheral clock required by the efuse device.
The driver has been handle to work without it so far because the
clock was left enabled by default but it won't be the case soon.
Signed-off-by: Jerome Brunet
---
drivers/nvmem/meson-efuse.c | 25 +
1 file
The efuse found in gx SoC requires a peripheral clock to properly operate.
We have been able to work without it until now because the clock was on by
default, and left on by the CCF. Soon, it will not be the case anymore, so
the device needs to claim the clock it needs
Signed-off-by: Jerome
Add the required peripheral clock for the efuse device.
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 4
arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 4
2 files changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
Add the required peripheral clock for the efuse device.
Signed-off-by: Jerome Brunet
---
arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 4
arch/arm64/boot/dts/amlogic/meson-gxl.dtsi | 4
2 files changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
Hi Matias,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11743c56785c751c087eecdb98713eef796609e0
commit: 73569e11032fc5a9b314b6351632cfca7793afd5 lightnvm: remove dependencies
on BLK_DEV_NVME and PCI
date: 3
Hi Matias,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 11743c56785c751c087eecdb98713eef796609e0
commit: 73569e11032fc5a9b314b6351632cfca7793afd5 lightnvm: remove dependencies
on BLK_DEV_NVME and PCI
date: 3
Hi Pierre-Louis,
On 29-10-18 23:03, Pierre-Louis Bossart wrote:
On 10/29/18 2:08 PM, Dean Wallace wrote:
On 29-10-18, Andy Shevchenko wrote:
On Mon, Oct 29, 2018 at 7:52 PM Andy Shevchenko
wrote:
Cc: Pierre as well.
On Mon, Oct 29, 2018 at 7:48 PM Stephen Boyd wrote:
Quoting Dean
Hi Pierre-Louis,
On 29-10-18 23:03, Pierre-Louis Bossart wrote:
On 10/29/18 2:08 PM, Dean Wallace wrote:
On 29-10-18, Andy Shevchenko wrote:
On Mon, Oct 29, 2018 at 7:52 PM Andy Shevchenko
wrote:
Cc: Pierre as well.
On Mon, Oct 29, 2018 at 7:48 PM Stephen Boyd wrote:
Quoting Dean
From: Ludovic Barre
The mmc framework follows the requirement of SD_Specification:
the STOP_TRANSMISSION is sent on multiple write/read commands
and the stop command (alone), not needed on other ADTC commands.
But, if an error happens on command or data step, some variants
require a stop
From: Ludovic Barre
The mmc framework follows the requirement of SD_Specification:
the STOP_TRANSMISSION is sent on multiple write/read commands
and the stop command (alone), not needed on other ADTC commands.
But, if an error happens on command or data step, some variants
require a stop
RK809 and RK817 are power management IC chips for multimedia products.
Most of their functions and registers are same, including the rtc.
Signed-off-by: Tony Xie
Acked-by: Alexandre Belloni
---
drivers/rtc/Kconfig | 4 +--
drivers/rtc/rtc-rk808.c | 68
RK809 and RK817 are power management IC chips for multimedia products.
Most of their functions and registers are same, including the rtc.
Signed-off-by: Tony Xie
Acked-by: Alexandre Belloni
---
drivers/rtc/Kconfig | 4 +--
drivers/rtc/rtc-rk808.c | 68
RK809 and RK817 are power management IC chips for multimedia products.
most of their functions and registers are same, including the clkout
funciton.
Signed-off-by: Tony Xie
Acked-by: Stephen Boyd
---
drivers/clk/Kconfig | 9 ---
drivers/clk/clk-rk808.c | 64
RK809 and RK817 are power management IC chips for multimedia products.
most of their functions and registers are same, including the clkout
funciton.
Signed-off-by: Tony Xie
Acked-by: Stephen Boyd
---
drivers/clk/Kconfig | 9 ---
drivers/clk/clk-rk808.c | 64
> >> This part is in the " Intel® Architecture Instruction Set Extensions and
> >> Future Features Programming Reference"
> >> https://software.intel.com/sites/default/files/managed/c5/15/architec
> >> ture-instruction-set-extensions-programming-reference.pdf
> >>
> > Yet another PDF which will
> >> This part is in the " Intel® Architecture Instruction Set Extensions and
> >> Future Features Programming Reference"
> >> https://software.intel.com/sites/default/files/managed/c5/15/architec
> >> ture-instruction-set-extensions-programming-reference.pdf
> >>
> > Yet another PDF which will
PMS405 also features PON block, so add PON and PWRKEY nodes
Signed-off-by: Vinod Koul
---
arch/arm64/boot/dts/qcom/pms405.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/pms405.dtsi
b/arch/arm64/boot/dts/qcom/pms405.dtsi
index
RNG hardware in QCS404 features (Execution Environment) EE for
HLOS to use, add the node for prng-ee for QCS404.
Signed-off-by: Vinod Koul
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi
PMS405 also features PON block, so add PON and PWRKEY nodes
Signed-off-by: Vinod Koul
---
arch/arm64/boot/dts/qcom/pms405.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/pms405.dtsi
b/arch/arm64/boot/dts/qcom/pms405.dtsi
index
RNG hardware in QCS404 features (Execution Environment) EE for
HLOS to use, add the node for prng-ee for QCS404.
Signed-off-by: Vinod Koul
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi
RTC is found on PMIC PMS405 and is same as other PMIC used, so add the
rtc node with compatible as qcom,pm8941-rtc
Signed-off-by: Vinod Koul
---
arch/arm64/boot/dts/qcom/pms405.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/pms405.dtsi
From: Bjorn Andersson
Add the scm firmware node to QCS404
Signed-off-by: Bjorn Andersson
Signed-off-by: Vinod Koul
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi
b/arch/arm64/boot/dts/qcom/qcs404.dtsi
901 - 1000 of 1220 matches
Mail list logo
