Introduce function rproc_detach() to enable the remoteproc
core to release the resources associated with a remote processor
without stopping its operation.
Signed-off-by: Mathieu Poirier
Reviewed-by: Peng Fan
---
drivers/remoteproc/remoteproc_core.c | 71 +++-
Add an new get_loaded_rsc_table() operation in order to support
scenarios where the remoteproc core has booted a remote processor
and detaches from it. When re-attaching to the remote processor,
the core needs to know where the resource table has been placed
in memory.
Signed-off-by: Mathieu
This patch takes into account scenarios where a remote processor
has been attached to when receiving a "start" command from sysfs.
As with the "running" case, the command can't be carried out if the
remote processor is already in operation.
Signed-off-by: Mathieu Poirier
Reviewed-by: Arnaud
Introduce function __rproc_detach() to perform the same kind of
operation as rproc_stop(), but instead of switching off the
remote processor using rproc->ops->stop(), it uses
rproc->ops->detach(). That way it is possible for the core
to release the resources associated with a remote processor
Add a new RPROC_ATTACHED state to take into account scenarios
where the remoteproc core needs to attach to a remote processor
that is booted by another entity.
Signed-off-by: Mathieu Poirier
Reviewed-by: Peng Fan
Reviewed-by: Arnaud Pouliquen
---
drivers/remoteproc/remoteproc_sysfs.c | 1 +
Rename function rproc_actuate() to rproc_attach(). That way it is
easy to understand that it does the opposite of rproc_detach().
Signed-off-by: Mathieu Poirier
Reviewed-by: Peng Fan
Reviewed-by: Arnaud Pouliquen
---
drivers/remoteproc/remoteproc_core.c | 8
1 file changed, 4
Move the setting of the resource table installed by an external
entity to rproc_ops::get_loaded_rsc_table(). This is to support
scenarios where a remote processor has been started by the core
but is detached at a later stage. To re-attach the remote
processor, the address of the resource table
The state of the remote processor may have changed between the
time a call to rproc_shutdown() was made and the time it is
executed. To avoid moving forward with an operation that may
have been cancelled, recheck while holding the mutex.
Cc:
Signed-off-by: Mathieu Poirier
Reviewed-by: Peng Fan
Whether started at probe() time or thereafter from the command
line, a remote processor needs to be shutdown before the final
cleanup phases can happen. Otherwise the system may be left in
an unpredictable state where the remote processor is expecting
the remoteproc core to be providing services
Following the work done here [1], this set provides support for the
remoteproc core to release resources associated with a remote processor
without having to switch it off. That way a platform driver can be removed
or the application processor power cycled while the remote processor is
still
This patch adds a binding to guide the remoteproc core on how to deal with
remote processors in two cases:
1) When an application holding a reference to a remote processor character
device interface crashes.
2) when the platform driver for a remote processor is removed.
In both cases if
Most notably DM_CRYPT for disk encryption but things like snapshot, etc.
are useful on embedded as well and the others make sense on arm64
servers.
CONFIG_BLK_DEV_MD gets dropped because other config options like
CONFIG_MD_RAID0 depend on it.
Signed-off-by: Guido Günther
---
xfs, f2fs and iso are common enough to have them everywhere.
Signed-off-by: Guido Günther
---
arch/arm64/configs/defconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index e42ba0c8f302..6f5f03237db6 100644
---
specific I have no idea which tree I would target so I
picked next-20201218.
Guido Günther (3):
arm64: defconfig: Enable function tracer
arm64: defconfig: Enable more filesystems
arm64: defconfig: Enable more DM/MD targets as modules
arch/arm64/configs/defconfig | 26
This allows for way easier runtime inspection and debugging.
Signed-off-by: Guido Günther
---
arch/arm64/configs/defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index e7aef72206e3..e42ba0c8f302 100644
---
Cc: Ryder Lee
Cc: Lorenzo Bianconi
Cc: Felix Fietkau
Cc: linux-wirel...@vger.kernel.org
Cc: Kalle Valo
---
drivers/net/wireless/mediatek/mt76/mt7915/init.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20201218.orig/drivers/net/wireless/mediatek/mt76/mt7
On Fri, Dec 18, 2020 at 8:42 AM Kishon Vijay Abraham I wrote:
>
> Hi Rob,
>
> On 16/12/20 10:31 pm, Rob Herring wrote:
> > On Wed, Dec 16, 2020 at 9:01 AM Kishon Vijay Abraham I
> > wrote:
> >>
> >> Hi Rob,
> >>
> >> On 15/12/20 9:23 pm, Rob Herring wrote:
> >>> On Tue, Dec 15, 2020 at 1:00 AM
This documents close_range(2) based on information in
278a5fbaed89dacd04e9d052f4594ffd0e0585de,
60997c3d45d9a67daf01c56d805ae4fec37e0bd8, and
582f1fb6b721facf04848d2ca57f34468da1813e.
Signed-off-by: Stephen Kitt
---
V3: fix synopsis overflow
copy notes from membarrier.2 re the lack of
On 12/17/20 9:33 PM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next releases between Dec 24 and Jan
> 3 inclusive.
>
> Please do not add any v5.12 destined code to your linux-next included
> branches until after v5.11-rc1 has been released.
>
> Changes since 20201217:
>
On Fri, Dec 18, 2020 at 06:35:50PM +0200, Mike Rapoport wrote:
> From: Mike Rapoport
>
> The change of ia64's default memory model to SPARSEMEM causes defconfig
> build to fail:
>
> CC kernel/async.o
> In file included from include/linux/numa.h:25,
> from
On 18/12/2020 12:28:17-0400, Jason Gunthorpe wrote:
> On Fri, Dec 18, 2020 at 03:52:04PM +, Mark Brown wrote:
> > On Fri, Dec 18, 2020 at 10:08:54AM -0400, Jason Gunthorpe wrote:
> > > On Fri, Dec 18, 2020 at 01:17:09PM +, Mark Brown wrote:
> >
> > > > As previously discussed this will
Hi Linus,
Please pull the following branch containing all the new xfs code for
5.11. In this release we add the ability to set a 'needsrepair' flag
indicating that we /know/ the filesystem requires xfs_repair, but other
than that, it's the usual strengthening of metadata validation and
On 12/17/20 2:34 PM, Rob Herring wrote:
> The correct syntax for JSON pointers begins with a '/' after the '#'.
> Without a '/', the string should be interpretted as a subschema
> identifier. The jsonschema module currently doesn't handle subschema
> identifiers and incorrectly allows JSON
The AD5766/AD5767 are 16-channel, 16-bit/12-bit, voltage output dense DACs
Digital-to-Analog converters.
This change adds support for these DACs.
Signed-off-by: Cristian Pop
---
Changelog v4:
- Select output range
- Set possible dither source to: 0 - N0 and 1 for N1.
-
New interface is proposed for dither functionality. This future allows
composing an external signals to the selected output channel.
The dither signal can be turned on/off, scaled, inverted, or it can be
selected from different sources.
Signed-off-by: Cristian Pop
---
Changelog v4:
-
This adds device tree bindings for the AD5766 DAC.
Signed-off-by: Cristian Pop
---
Changelog v4:
- Add range selection
- Reset is GPIO_ACTIVE_LOW
.../bindings/iio/dac/adi,ad5766.yaml | 64 +++
1 file changed, 64 insertions(+)
create mode
On 12/18/20 6:36 AM, Tetsuo Handa wrote:
> On 2020/12/18 21:59, Pavel Machek wrote:
>> On Fri 2020-12-18 19:44:04, Xiaoming Ni wrote:
>> Plus.. is_being_panic is not really english. "is_paniccing" would be
>> closer...?
>
> Or in_panic() ?
>
Yes, or in_panic_state()
--
~Randy
[ TL;DR for the non-ARM folks on CC: disabling softirq processing when using
SIMD in kernel mode could reduce complexity and improve performance, but we
need to decide whether we can do this, and how much softirq processing
latency we can tolerate. If we can find a satisfactory solution for
Now that kernel mode SIMD is guaranteed to be available when executing
in task or softirq context, we no longer need scalar fallbacks to use
when the NEON is unavailable. So get rid of them.
Signed-off-by: Ard Biesheuvel
---
arch/arm64/crypto/ghash-ce-glue.c | 209 +---
1 file
Kernel mode NEON can be used in task or softirq context, but only in
a non-nesting manner, i.e., softirq context is only permitted if the
interrupt was not taken at a point where the kernel was using the NEON
in task context.
This means all users of kernel mode NEON have to be aware of this
GCM mode is typically used for IPsec, but is now also used for software
kTLS, which means that we may end up operating on much larger inputs.
So let's wire up conditional NEON yield support for this driver, to ensure
that it does not cause scheduling blackouts when used with large inputs.
Given
In order to ensure that kernel mode SIMD routines will not need a scalar
fallback if they run with softirqs disabled, disallow any use of the
AEAD encrypt and decrypt routines from outside of task or softirq context.
Signed-off-by: Ard Biesheuvel
---
crypto/aead.c | 10 ++
1 file
In order to ensure that kernel mode SIMD routines will not need a scalar
fallback if they run with softirqs disabled, disallow any use of the
skcipher encrypt and decrypt routines from outside of task or softirq
context.
Signed-off-by: Ard Biesheuvel
---
crypto/skcipher.c | 10 ++
1
Hi,
On 12/18/20 6:25 AM, hejingxian wrote:
> diff --git a/drivers/char/Kconfig b/drivers/char/Kconfig
> index 26956c0..73af2f0 100644
> --- a/drivers/char/Kconfig
> +++ b/drivers/char/Kconfig
> @@ -560,3 +560,10 @@ config RANDOM_TRUST_BOOTLOADER
>booloader is trustworthy so it will be
On Thu, Dec 17, 2020 at 8:05 PM Ira Weiny wrote:
>
> On Thu, Dec 17, 2020 at 12:55:39PM -0800, Dave Hansen wrote:
> > On 11/6/20 3:29 PM, ira.we...@intel.com wrote:
> > > + /* Arm for context switch test */
> > > + write(fd, "1", 1);
> > > +
> > > + /* Context switch
Add the futex test binary introduced by commit a4fd8414659b
("selftests/timens: Add a test for futex()") to .gitignore.
Signed-off-by: Tobias Klauser
---
tools/testing/selftests/timens/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/timens/.gitignore
On Fri, Dec 18, 2020 at 11:28:19AM -0500, Vivek Goyal wrote:
> On Fri, Dec 18, 2020 at 10:02:58AM -0500, Jeff Layton wrote:
> > On Fri, Dec 18, 2020 at 09:44:18AM -0500, Vivek Goyal wrote:
> > > On Thu, Dec 17, 2020 at 03:08:56PM -0500, Jeffrey Layton wrote:
> > > > On Wed, Dec 16, 2020 at
Linus,
ktest.pl: Updates for 5.11
No new features. Just a couple of fixes that I had in my local repository
that fixed issues with sending the result emails.
Please pull the latest ktest-v5.11 tree, which can be found at:
On Sat, Dec 19, 2020 at 12:42:51AM +0900, Masahiro Yamada wrote:
> On Sat, Dec 19, 2020 at 12:33 AM Jon Hunter wrote:
> >
> >
> > On 18/12/2020 15:12, Jon Hunter wrote:
> > >
> > > On 18/12/2020 15:09, Marek Szyprowski wrote:
> > >>
> > >> On 18.12.2020 16:03, Jon Hunter wrote:
> > >>> On
Hi Daniel,
Thank you for the patch.
On Thu, Dec 17, 2020 at 11:43:37PM +, Daniel Scally wrote:
> Currently on platforms designed for Windows, connections between CIO2 and
> sensors are not properly defined in DSDT. This patch extends the ipu3-cio2
> driver to compensate by building
On Friday, December 18, 2020 3:50 PM, Dmitry Torokhov wrote:
> The OF match table is only used when OF is enabled.
>
> Fixes: cd3f609823a5 ("Input: new da7280 haptic driver")
> Reported-by: kernel test robot
> Signed-off-by: Dmitry Torokhov
> ---
> drivers/input/misc/da7280.c | 2 ++
> 1 file
Hi Linus,
Merge window -fixes pull, but bigger: We've somehow missed one subtree
pull (which also contained the amdgpu multihop fix you cherry-pick, oops).
But that pull was pending for almost 3 weeks on the list and most of it
for even longer in linux-next, so really not seeing a reason why it
Hi,
On Thu, Dec 17, 2020 at 04:34:29PM -0600, Rob Herring wrote:
> The correct syntax for JSON pointers begins with a '/' after the '#'.
> Without a '/', the string should be interpretted as a subschema
> identifier. The jsonschema module currently doesn't handle subschema
> identifiers and
Steven Rostedt (VMware) (2):
ktest.pl: If size of log is too big to email, email error message
ktest.pl: Fix the logic for truncating the size of the log file for email
tools/testing/ktest/ktest.pl | 20
1 file changed, 12 insertions(+), 8 deletions(-)
From: "Steven Rostedt (VMware)"
If the size of the error log is too big to send via email, and the sending
fails, it wont email any result. This can be confusing for the user who is
waiting for an email on the completion of the tests.
If it fails to send email, then try again without the log
From: "Steven Rostedt (VMware)"
The logic for truncating the log file for emailing based on the
MAIL_MAX_SIZE option is confusing and incorrect. Simplify it and have the
tail of the log file truncated to the max size specified in the config.
Cc: sta...@vger.kernel.org
Fixes: 855d8abd2e8ff
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an
issue:
KASAN: use-after-free Read in idr_for_each
==
BUG: KASAN: use-after-free in radix_tree_next_slot
include/linux/radix-tree.h:422 [inline]
Hi Stefan
On Mon, Dec 14, 2020 at 03:13:12PM +0100, Stefan Saecherl wrote:
> The problem is that breakpoints that are set early (e.g. via kgdbwait)
> cannot be deleted after boot completed (to be precise after mark_rodata_ro
> ran).
>
> When setting a breakpoint early there are executable pages
On 17/12/2020 03:17, Hillf Danton wrote:
> Wed, 16 Dec 2020 13:14:11 -0800
>> syzbot found the following issue on:
>>
>> HEAD commit:7b1b868e Merge tag 'for-linus' of git://git.kernel.org/pub..
>> git tree: upstream
>> console output:
From: Mike Rapoport
The change of ia64's default memory model to SPARSEMEM causes defconfig
build to fail:
CC kernel/async.o
In file included from include/linux/numa.h:25,
from include/linux/async.h:13,
from kernel/async.c:47:
Systems configured with CONFIG_ZONE_DMA32, CONFIG_ZONE_NORMAL and
!CONFIG_ZONE_DMA will fail to properly setup ARCH_LOW_ADDRESS_LIMIT. The
limit will default to ~0ULL, effectively spanning the whole memory,
which is too high for a configuration that expects low memory to be
capped at 4GB.
Fix
On Fri, Dec 18, 2020 at 10:02:58AM -0500, Jeff Layton wrote:
> On Fri, Dec 18, 2020 at 09:44:18AM -0500, Vivek Goyal wrote:
> > On Thu, Dec 17, 2020 at 03:08:56PM -0500, Jeffrey Layton wrote:
> > > On Wed, Dec 16, 2020 at 06:31:49PM -0500, Vivek Goyal wrote:
> > > > Check for writeback error on
On Fri, Dec 18, 2020 at 03:52:04PM +, Mark Brown wrote:
> On Fri, Dec 18, 2020 at 10:08:54AM -0400, Jason Gunthorpe wrote:
> > On Fri, Dec 18, 2020 at 01:17:09PM +, Mark Brown wrote:
>
> > > As previously discussed this will need the auxilliary bus extending to
> > > support at least
On Fri, Dec 18, 2020 at 5:10 PM Steven Rostedt wrote:
>
> On Thu, 17 Dec 2020 11:03:20 +0100
> Daniel Vetter wrote:
>
> > I think we're tripping over the might_sleep() all the mutexes have,
> > and that's not as good as yours, but good enough to catch a missing
> > rcu_read_unlock(). That's
On Mon, 2020-12-14 at 21:01 +0100, Rafael J. Wysocki wrote:
> Hi,
>
> The timing of this is not perfect (sorry about that), but here's a refresh
> of this series.
>
> The majority of the previous cover letter still applies:
> [...]
Hello,
the series is tested using
-> tbench (packets
Hi Daniel,
Thank you for the patch.
On Thu, Dec 17, 2020 at 11:43:31PM +, Daniel Scally wrote:
> From: Heikki Krogerus
>
> This implements the remaining .graph_* callbacks in the
> fwnode operations structure for the software nodes. That makes
> the fwnode_graph*() functions available in
On Mon, Dec 14, 2020 at 10:01 PM Aaro Koskinen wrote:
> From: Linus Walleij
>
> Commit 45c5775460f3 ("usb: ohci-omap: Fix descriptor conversion") tried to
> fix all issues related to ohci-omap descriptor conversion, but a wrong
> patch was applied, and one needed change to the OSK board file is
We need to lock d_parent->d_lock before dget_dlock, or this may
have d_lockref updated parallelly like calltrace below which will
cause dentry->d_lockref leak and risk a crash.
npm-20576 [028] 5705749.040094:
[28] ovl_set_redirect+0x11c/0x310 //tmp = dget_dlock(d->d_parent);
[28]?
On 12/18, Satya Tangirala wrote:
> On Tue, Dec 08, 2020 at 04:15:54PM +0800, Robin Hsu wrote:
> > From: Robin Hsu
> >
> > Add F2FS compression support for sload
> > * Support file extension filter, either default-accept or default-deny
> > policy
> > * Support choice of compression algorithm,
On Thu, 17 Dec 2020 11:03:20 +0100
Daniel Vetter wrote:
> I think we're tripping over the might_sleep() all the mutexes have,
> and that's not as good as yours, but good enough to catch a missing
> rcu_read_unlock(). That's kinda why I'm baffled, since like almost
> every 2nd function in the
From: Lai Jiangshan
Just move around the code, no functionality changed.
It prepares for later patch protecting wq_online_cpumask
in wq_pool_attach_mutex.
Acked-by: Tejun Heo
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 11 ---
1 file changed, 8 insertions(+), 3
From: Lai Jiangshan
Just move around the code, no functionality changed.
Only wq_pool_attach_mutex protected region becomes a little larger.
It prepares for later patch protecting wq_online_cpumask
in wq_pool_attach_mutex.
Acked-by: Tejun Heo
Signed-off-by: Lai Jiangshan
---
From: Lai Jiangshan
When worker_attach_to_pool() is called, we should not put the workers
to pool->attrs->cpumask when there is not CPU online in it.
We have to use wq_online_cpumask in worker_attach_to_pool() to check
if pool->attrs->cpumask is valid rather than cpu_online_mask or
From: Lai Jiangshan
wq_online_cpumask is the cached result of cpu_online_mask with the
going-down cpu cleared. It is needed for later patches for setting
correct cpumask for workers and break affinity initiatively.
The first usage of wq_online_cpumask is also in this patch.
From: Lai Jiangshan
There might be no online cpu in the pool->attrs->cpumask.
We will set the worker's cpumask later in worker_attach_to_pool().
Cc: Peter Zijlstra
Acked-by: Tejun Heo
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 10 +-
1 file changed, 9 insertions(+), 1
From: Lai Jiangshan
There is possible that a per-node pool/woker's affinity is a single
CPU. It can happen when wq_unbound_cpumask is changed by system adim
via /sys/devices/virtual/workqueue/cpumask. And pool->attrs->cpumask
is wq_unbound_cpumask & possible_cpumask_of_the_node, which can be a
From: Lai Jiangshan
The scheduler won't break affinity for us any more, and we should
"emulate" the same behavior when the scheduler breaks affinity for
us. The behavior is "changing the cpumask to cpu_possible_mask".
And there might be some other CPUs online later while the worker is
still
From: Lai Jiangshan
The pool->attrs->cpumask might be a single CPU and it may go
down after detachment, and the scheduler won't force to break
affinity for us since it is a per-cpu-ktrhead. So we have to
do it on our own and unbind this worker which can't be unbound
by workqueue_offline_cpu()
From: Lai Jiangshan
restore_unbound_workers_cpumask() is called when CPU_ONLINE, where
wq_online_cpumask equals to cpu_online_mask. So no fucntionality
changed.
Acked-by: Tejun Heo
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
From: Lai Jiangshan
06249738a41a ("workqueue: Manually break affinity on hotplug")
said that scheduler will not force break affinity for us.
But workqueue highly depends on the old behavior. Many parts of the codes
relies on it, 06249738a41a ("workqueue: Manually break affinity on hotplug")
is
From: Lai Jiangshan
When we restore workers' cpumask, we should restore them to the
designed pool->attrs->cpumask. And we need to only do it at
the first time.
Cc: Hillf Danton
Reported-by: Hillf Danton
Acked-by: Tejun Heo
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 6 +-
1
The eLCDIF controller on i.MX6UL/i.MX6ULL supports the alpha plane too.
Enable it on these SoCs.
Signed-off-by: Sébastien Szymanski
---
While testing, I have noticed that the alpha plane works but
sometimes the framebuffer is shiftted to the right.
I tested with the following modetest command:
On Fri, Dec 18, 2020 at 01:21:39PM +, Lee Jones wrote:
> On Fri, 18 Dec 2020, Cristian Ciocaltea wrote:
>
> > Hi Lee,
> >
> > Thank you for the detailed review!
> >
> > I will prepare a new revision, but there are still a couple of open
> > points..
>
> Could you please snip your replies,
Hi Linus,
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git
tags/pwm/for-5.11-rc1
for you to fetch
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: 55d2eba8e7cd439c11cdb204898c2d384227629b
Gitweb:
https://git.kernel.org/tip/55d2eba8e7cd439c11cdb204898c2d384227629b
Author:Peter Zijlstra
AuthorDate:Wed, 16 Dec 2020 12:21:36 +01:00
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: 91ea62d58bd661827c328a2c6c02a87fa4aae88b
Gitweb:
https://git.kernel.org/tip/91ea62d58bd661827c328a2c6c02a87fa4aae88b
Author:Peter Zijlstra
AuthorDate:Fri, 18 Dec 2020 16:39:14 +01:00
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: 441fa3409769180df2fd12fcada35441435a120c
Gitweb:
https://git.kernel.org/tip/441fa3409769180df2fd12fcada35441435a120c
Author:Peter Zijlstra
AuthorDate:Wed, 16 Dec 2020 14:19:22 +01:00
Hi Daniel,
Thank you for the patch.
On Thu, Dec 17, 2020 at 11:43:29PM +, Daniel Scally wrote:
> Registering software_nodes with the .parent member set to point to a
> currently unregistered software_node has the potential for problems,
> so enforce parent -> child ordering in arrays passed
On Fri, Dec 18, 2020 at 6:52 AM Drew Fustini wrote:
>
> BeagleBoard.org [0] currently uses an out-of-tree driver called
> bone-pinmux-helper [1] developed by Pantelis Antoniou [2] back in 2013.
> The driver assists users of our BeagleBone and PocketBeagle boards in
> rapid prototyping by allowing
On Wed, Dec 16, 2020 at 12:42 AM Drew Fustini wrote:
> On Tue, Dec 15, 2020 at 09:39:18PM +0200, Andy Shevchenko wrote:
> > On Tue, Dec 15, 2020 at 9:36 PM Andy Shevchenko
> > wrote:
> > > On Mon, Dec 14, 2020 at 11:44 PM Drew Fustini
> > > wrote:
> > > > On Mon, Dec 14, 2020 at 07:55:12PM
On Fri, Dec 18, 2020 at 4:37 PM Enrico Weigelt, metux IT consult
wrote:
> + if (printk_ratelimit())
> + pr_warn("spurious IRQ: irq=%d hwirq=%d nr_irqs=%d\n",
> + irq, hwirq, nr_irqs);
Perhaps you missed pr_warn_ratelimit() macro
On 18/12/2020 15:42, Masahiro Yamada wrote:
...
>> However, if you are saying that this is a problem/bug with our builders,
>> then of course we will have to get this fixed.
>>
>
>
> Yes, please do so.
>
>
> Kconfig evaluates $(CC) capabilities, and
> hides CONFIG options it cannot
On Fri, Dec 18, 2020 at 10:08:54AM -0400, Jason Gunthorpe wrote:
> On Fri, Dec 18, 2020 at 01:17:09PM +, Mark Brown wrote:
> > As previously discussed this will need the auxilliary bus extending to
> > support at least interrupts and possibly also general resources.
> I thought the recent
On 28/11/2020 17:19, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit:c84e1efa Merge tag 'asm-generic-fixes-5.10-2' of git://git..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1251d75950
> kernel config:
On Fri, Dec 18, 2020 at 04:37:16PM +0100, Peter Zijlstra wrote:
> On Fri, Dec 18, 2020 at 04:33:56PM +0100, Heiko Carstens wrote:
>
> > Peter, will you make proper patch out of this?
>
> Yes, let me go do that now, and stick it in the quilt series before I go
> off and don't think for 2 weeks.
It'll be used by the RPi4 family of boards to access its bootloader
configuration.
Signed-off-by: Nicolas Saenz Julienne
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
index
On Sat, Dec 19, 2020 at 12:33 AM Jon Hunter wrote:
>
>
> On 18/12/2020 15:12, Jon Hunter wrote:
> >
> > On 18/12/2020 15:09, Marek Szyprowski wrote:
> >>
> >> On 18.12.2020 16:03, Jon Hunter wrote:
> >>> On 18/12/2020 10:05, Marek Szyprowski wrote:
> On 18.12.2020 10:43, Masahiro Yamada
Firmware/co-processors might use reserved memory areas in order to pass
data stemming from an nvmem device otherwise non accessible to Linux.
For example an EEPROM memory only physically accessible to firmware, or
data only accessible early at boot time.
Introduce the dt-bindings to nvmem's rmem.
Firmware/co-processors might use reserved memory areas in order to pass
data stemming from an nvmem device otherwise non accessible to Linux.
For example an EEPROM memory only physically accessible to firmware, or
data only accessible early at boot time.
In order to expose this data to other
Soon to be released versions of RPi4's firmware will take of care
passing their bootloader's configuration[1] to the OS by copying it into
memory and creating a reserved memory node in the board's DT. By
modeling this reserved memory node as an nvmem device using
'nvmem-rmem', which this series
It'll be used by the RPi4 family of boards to access its bootloader
configuration.
Signed-off-by: Nicolas Saenz Julienne
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index
RPi4's co-processor will copy the board's bootloader[1] configuration
into memory for the OS to consume. Specifically, for the bootloader
configuration and upgrade user-space routines to query it through
nvmem's sysfs interface.
Introduce a reserved-memory area template for the co-processor to
On Thu, Dec 17, 2020 at 08:12:54PM +0800, Muchun Song wrote:
> The HUGETLB_PAGE_FREE_VMEMMAP option is used to enable the freeing
> of unnecessary vmemmap associated with HugeTLB pages. The config
> option is introduced early so that supporting code can be written
> to depend on the option. The
On Thu, Dec 17, 2020 at 10:30:37PM +0100, Donald Buczek wrote:
> On 17.12.20 20:43, Brian Foster wrote:
> > On Thu, Dec 17, 2020 at 06:44:51PM +0100, Donald Buczek wrote:
> > > Dear xfs developer,
> > >
> > > I was doing some testing on a Linux 5.10.1 system with two 100 TB xfs
> > > filesystems
Le 13/12/2020 à 19:35, Ariel Marcovitch a écrit :
This is a bug that can cause early crashes in configurations with a
.exit.text section smaller than a page and a .init.text section that
ends in the beginning of a physical page (this is kinda random, which
might explain why this wasn't really
On Fri, Dec 18, 2020 at 04:33:56PM +0100, Heiko Carstens wrote:
> Peter, will you make proper patch out of this?
Yes, let me go do that now, and stick it in the quilt series before I go
off and don't think for 2 weeks.
On Fri, Dec 18, 2020 at 7:40 AM Calvin Johnson
wrote:
> On Tue, Dec 15, 2020 at 07:53:26PM +0200, Andy Shevchenko wrote:
> > On Tue, Dec 15, 2020 at 6:44 PM Calvin Johnson
> > wrote:
...
> > I would rather see this as simple as
> >
> > if (is_of_node(fwnode))
> >return
Hannes reported a problem with setting up dma transfers on a mcb device.
The problem boiled down to the use of a wrong 'device' for the dma
functions.
Document how to setup dma transfers for a IP core on a mcb carrier.
Reported-by: Hannes Duerr
Signed-off-by: Johannes Thumshirn
---
On Fri, Dec 18, 2020 at 7:34 AM Calvin Johnson
wrote:
>
> On Tue, Dec 15, 2020 at 07:33:40PM +0200, Andy Shevchenko wrote:
> > On Tue, Dec 15, 2020 at 6:44 PM Calvin Johnson
> > wrote:
...
> > > + /* phy->mii_ts may already be defined by the PHY driver. A
> > > +*
On Wed, Dec 16, 2020 at 06:52:59PM +0100, Peter Zijlstra wrote:
> On Tue, Dec 15, 2020 at 02:47:24PM -0500, Steven Rostedt wrote:
> > On Tue, 15 Dec 2020 20:01:52 +0100
> > Heiko Carstens wrote:
> >
> > > Hello,
> > >
> > > the ftrace stack tracer kernel selftest is able to trigger the warning
301 - 400 of 712 matches
Mail list logo
