For userspace checkpoint and restore (C/R) some way of getting process
state containing RSEQ configuration is needed.
There are two ways this information is going to be used:
- to re-enable RSEQ for threads which had it enabled before C/R
- to detect if a thread was in a critical section during
Add initial support for the OnePlus 6 (enchilada) and 6T (fajita) based
on the sdm845-mtp DT with the following functionality:
* Touch
* Display
* GPU
* Wlan and Bluetooth
* USB peripheral mode
* Remoteproc
Signed-off-by: Caleb Connolly
---
Changes since v1
* Remove unused pinctrl nodes
On 1/14/21 1:08 AM, Claire Chang wrote:
> On Wed, Jan 13, 2021 at 7:48 AM Florian Fainelli wrote:
>>
>> On 1/5/21 7:41 PM, Claire Chang wrote:
>>> If a device is not behind an IOMMU, we look up the device node and set
>>> up the restricted DMA when the restricted-dma-pool is presented.
>>>
>>>
Hi,
On Mon, Dec 28, 2020 at 07:05:47PM +0300, Dmitry Osipenko wrote:
> This patch adds battery gauge driver for Acer Iconia Tab A500 device.
> The battery gauge function is provided via the Embedded Controller,
> which is found on the Acer A500.
>
> Reviewed-by: Sebastian Reichel
>
Hi,
As per the subject on top of linux-next from today.
Please refer to the patch changelogs for details.
Thanks!
From: Rafael J. Wysocki
The upfront allocation of new_bus_id is done to avoid allocating
memory under acpi_device_lock, but it doesn't really help,
because (1) it leads to many unnecessary memory allocations for
_ADR devices, (2) kstrdup_const() is run under that lock anyway and
(3) it
From: Rafael J. Wysocki
Add empty lines in some places in acpi_device_add() to help
readability and drop leading spaces before the labels in there.
No functional impact.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/scan.c |9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
Hello,
syzbot found the following issue on:
HEAD commit:65f0d241 Merge tag 'sound-5.11-rc4' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1292d4f750
kernel config: https://syzkaller.appspot.com/x/.config?x=ee2266946ed36986
On Thu, Jan 14, 2021 at 08:27:43AM -0800, t...@redhat.com wrote:
> From: Tom Rix
>
> Defining DEBUG should only be done in development.
> So remove DEBUG.
>
> Signed-off-by: Tom Rix
> ---
> arch/x86/kernel/cpu/mtrr/generic.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git
Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> Without crc32, the driver fails to link:
>
> arm-linux-gnueabi-ld: drivers/net/wireless/ath/wil6210/fw.o: in function
> `wil_fw_verify':
> fw.c:(.text+0x74c): undefined reference to `crc32_le'
> arm-linux-gnueabi-ld:
>
Hi Uwe, thanks for the review.
On Tue, 2021-01-12 at 10:18 +0100, Uwe Kleine-König wrote:
[...]
> > +duty_cycle = DIV_ROUND_CLOSEST_ULL(state->duty_cycle *
> > RPI_PWM_MAX_DUTY,
> > + RPI_PWM_PERIOD_NS);
>
> ... and round down here.
Hi Benjamin,
On Thu, Jan 14, 2021 at 10:23:02AM +0100, Benjamin Tissoires wrote:
> Hi Dmitry,
>
> On Thu, Jan 14, 2021 at 7:24 AM Dmitry Torokhov
> wrote:
> >
> > A typical USB keyboard usually splits its keys into several reports:
> >
> > - one for the basic alphanumeric keys, modifier keys, F
On Thu, Jan 14, 2021 at 12:18 AM Ard Biesheuvel wrote:
>
> So if the arguments are piling up, what is holding us back, other than
> inertia?
I think we can most certainly just try increasing the minimum version
to 5.1 in the next merge window and see.
> Note that banning 4.9 for arm64 and
Hi,
On Wed, Jan 13, 2021 at 04:53:52PM -0600, Ricardo Rivera-Matos wrote:
> Corrects BQ256XX_NUM_WD_VAL from value of "8" to "4" and fixes the issue when
> 'i'
> is equal to array size then array index over runs the array
>
> Fixes: 32e4978bb92 ("power: supply: bq256xx: Introduce the BQ256XX
From: Rafael J. Wysocki
When adding a new device link, device_is_dependent() is used to
check whether or not the prospective supplier device does not
depend on the prospective consumer one to avoid adding loops
to the graph of device dependencies.
However, device_is_dependent() does not take
On Thu, Jan 14, 2021 at 07:30:24PM +0100, Borislav Petkov wrote:
> On Thu, Dec 17, 2020 at 09:12:57PM +0800, kernel test robot wrote:
> >ld: arch/x86/kernel/alternative.o: in function `paravirt_set_cap':
> > >> arch/x86/kernel/alternative.c:605: undefined reference to
> > >>
date: 8 months ago
config: arm-randconfig-r002-20210114 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
Hi,
When building perf for RISCV 32 bit (v5.10.7) I got the following
| In file included from bench/futex-hash.c:29:
| bench/futex.h: In function ‘futex_wait’:
| bench/futex.h:37:10: error: ‘SYS_futex’ undeclared (first use in this
function); did you mean ‘SYS_tee’?
This issue is similar to
On Thu, Jan 14, 2021 at 08:20:52AM +, Marc Zyngier wrote:
> On 2021-01-14 07:15, Srinivas Ramana wrote:
> > On 1/11/2021 5:40 AM, Marc Zyngier wrote:
> > > On 2021-01-09 00:29, Srinivas Ramana wrote:
> > > > This patchset adds a control function for cpufeature framework
> > > > so that the
On 1/14/21 9:54 AM, Jarkko Sakkinen wrote:
> On Tue, Jan 12, 2021 at 04:24:01PM -0800, Dave Hansen wrote:
>> We need a bit more information here as well. What's the relationship
>> between NUMA nodes and sections? How does the BIOS tell us which NUMA
>> nodes a section is in? Is it the same or
From: Rafael J. Wysocki
Calling acpi_thermal_check() from acpi_thermal_notify() directly
is problematic if _TMP triggers Notify () on the thermal zone for
which it has been evaluated (which happens on some systems), because
it causes a new acpi_thermal_notify() invocation to be queued up
every
On Thu, 14 Jan 2021 10:59:08 -0500 Jon Maloy wrote:
> On 1/14/21 3:04 AM, Mauro Carvalho Chehab wrote:
> > A function has a different name between their prototype
> > and its kernel-doc markup:
> >
> > ../net/tipc/link.c:2551: warning: expecting prototype for
> > link_reset_stats(). Prototype
On Wed, Jan 13, 2021 at 9:10 PM Palmer Dabbelt wrote:
>
> On Thu, 07 Jan 2021 01:26:51 PST (-0800), Atish Patra wrote:
> > SMP_CACHE_BYTES/L1_CACHE_BYTES should be defined as 32 instead of
> > 64 for RV32. Otherwise, there will be hole of 32 bytes with each memblock
> > allocation if it is
On Thu, 14 Jan 2021 10:13:40 -0800
Ben Widawsky wrote:
> On 21-01-14 18:02:11, Jonathan Cameron wrote:
> > On Mon, 11 Jan 2021 14:51:19 -0800
> > Ben Widawsky wrote:
> >
> > > The Command Effects Log (CEL) is specified in the CXL 2.0 specification.
> > > The CEL is one of two types of logs,
On Thu, Jan 14, 2021 at 7:08 PM Masahiro Yamada wrote:
>
> I unified the similar two scripts, gcc-version.sh and clang-version.sh
> into the new cc-version.sh. The old scripts invoked the compiler multiple
> times (3 times for gcc-version.sh, 4 times for clang-version.sh). I
> refactored the code
On Thu, Dec 17, 2020 at 09:12:57PM +0800, kernel test robot wrote:
>ld: arch/x86/kernel/alternative.o: in function `paravirt_set_cap':
> >> arch/x86/kernel/alternative.c:605: undefined reference to
> >> `pv_is_native_spin_unlock'
> >> ld: arch/x86/kernel/alternative.c:608: undefined reference
Solves the following repetitive warning when building with -Wshadow:
In file included from ./include/linux/bitops.h:32,
from ./include/linux/kernel.h:11,
from ./include/linux/skbuff.h:13,
from ./include/linux/if_ether.h:19,
from
Solves the following repetitive warning when building with -Wshadow:
In file included from ./include/linux/pgtable.h:6,
from ./include/linux/mm.h:33,
from ./include/linux/dax.h:6,
from ./include/linux/mempolicy.h:11,
from
Em Wed, Jan 13, 2021 at 12:07:01PM +0100, Jiri Olsa escreveu:
> On Wed, Jan 13, 2021 at 09:56:31AM +0800, Jin Yao wrote:
>
> SNIP
>
> >
> > root@lkp-csl-2ap4 ~# ./perf stat -a -I 1000 -e llc_misses.mem_read
> > --per-die -- sleep 5
> > 1.001586691 S0-D0 11229440
Fix two -Wshadow warnings coming from the include files and thus
repetitive and very annoying when building lots of sources.
Alexander Lobakin (2):
MIPS: bitops: fix -Wshadow in asm/bitops.h
MIPS: pgtable: fix -Wshadow in asm/pgtable.h
arch/mips/include/asm/bitops.h | 10 +-
Add basic test coverage for files that don't require any config options:
* gcd.c
* lcm.c
* int_sqrt.c
* reciprocal_div.c
(Ignored int_pow.c since it's a simple textbook algorithm.)
These tests aren't particularly interesting, but they
* provide a place to add tests for any new files in this dir
*
config: sh-randconfig-s032-20210114 (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse
d
> support for FIFO peak mode
> date: 4 months ago
> config: mips-randconfig-r026-20210114 (attached as .config)
> compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project
> 68ff52ffead2ba25cca442778ab19286000daad7)
> reproduce (this is a W=1 build):
> wget
&g
On Fri, Jan 15, 2021 at 03:07:09AM +0900, Masahiro Yamada wrote:
> Paul Gortmaker reported a regression in the GCC version check [1].
> If you use GCC 4.8, the build breaks before showing the error message
> "error Sorry, your version of GCC is too old - please use 4.9 or newer."
>
> I do not
On Thu, Jan 14, 2021 at 04:13:23PM +, Stefan Chulski wrote:
> > > From: Stefan Chulski
> > >
> > > This patch doesn't change any functionality, but just extend MIB
> > > counter register and ethtool-statistic names with "err".
> > >
> > > The counter MVPP2_MIB_FRAGMENTS_RCVD in fact is Error
On Thu, Jan 14, 2021 at 10:07 AM Masahiro Yamada wrote:
>
> Paul Gortmaker reported a regression in the GCC version check [1].
> If you use GCC 4.8, the build breaks before showing the error message
> "error Sorry, your version of GCC is too old - please use 4.9 or newer."
>
> I do not want to
Thanks Jessica for the reviews!
--Will
On Tue, Jan 12, 2021 at 7:55 AM Jessica Yu wrote:
>
> +++ Will McVicker [08/01/21 00:30 +]:
> >Config MODULE_SCMVERSION introduces a new module attribute --
> >`scmversion` -- which can be used to identify a given module's SCM
> >version. This is very
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 65f0d2414b7079556fbbcc070b3d1c9f9587606d
commit: b0fc6783d4ae58f796fb183c40dbc7fa3199d51d iio: accel: adxl372: Add
support for FIFO peak mode
date: 4 months ago
config: mips-randconfig-r026-20210114
Hi Sebastian,
On Wed, Dec 16, 2020 at 08:34:15AM -0800, Daisuke Nojiri wrote:
> This patch adds a driver for PCHG (Peripheral CHarGer). PCHG is a
> framework managing power supplies for peripheral devices.
>
> This driver creates a sysfs node for each peripheral charge port:
>
>
Em Thu, Jan 14, 2021 at 02:06:09PM +0900, Namhyung Kim escreveu:
> It was using some bash-specific features and failed to parse when
> running with a different shell like below:
>
> root@kbl-ppc:~/kbl-ws/perf-dev/lck-9077/acme.tmp/tools/perf# ./perf test 83
> -vv
> 83: perf stat metrics
On Tue, Jan 5, 2021 at 2:25 AM Wolfram Sang wrote:
>
> On Fri, Nov 20, 2020 at 10:59:12AM -0800, Evan Green wrote:
> > On Thu, Nov 19, 2020 at 7:24 AM Andy Shevchenko
> > wrote:
> > >
> > > On Thu, Nov 19, 2020 at 1:40 AM Evan Green wrote:
> > > >
> > > > Enable i2c-mux-gpio devices to be
The BPF_FETCH field can be set in bpf_insn.imm, for BPF_ATOMIC
instructions, in order to have the previous value of the
atomically-modified memory location loaded into the src register
after an atomic op is carried out.
Suggested-by: Yonghong Song
Signed-off-by: Brendan Jackman
Acked-by: John
I can't find a reason why this code is in resolve_pseudo_ldimm64;
since I'll be modifying it in a subsequent commit, tidy it up.
Signed-off-by: Brendan Jackman
Acked-by: Yonghong Song
Acked-by: John Fastabend
---
kernel/bpf/verifier.c | 13 ++---
1 file changed, 6 insertions(+), 7
The prog_test that's added depends on Clang/LLVM features added by
Yonghong in commit 286daafd6512 (was https://reviews.llvm.org/D72184).
Note the use of a define called ENABLE_ATOMICS_TESTS: this is used
to:
- Avoid breaking the build for people on old versions of Clang
- Avoid needing
Document new atomic instructions.
Acked-by: Yonghong Song
Signed-off-by: Brendan Jackman
---
Documentation/networking/filter.rst | 31 +
1 file changed, 31 insertions(+)
diff --git a/Documentation/networking/filter.rst
b/Documentation/networking/filter.rst
index
Hi Jiri,
I noticed this hasn't merged yet. So just sending a friendly reminder.
Thanks,
Will
On Thu, Dec 17, 2020 at 10:42 AM Will McVicker wrote:
>
> Great! Thanks for the reply.
>
> --Will
>
> On Thu, Dec 17, 2020 at 2:19 AM Jiri Kosina wrote:
> >
> > On Mon, 14 Dec 2020, Will McVicker
Since the atomic operations that are added in subsequent commits are
all isomorphic with BPF_ADD, pull out a macro to avoid the
interpreter becoming dominated by lines of atomic-related code.
Note that this sacrificies interpreter performance (combining
STX_ATOMIC_W and STX_ATOMIC_DW into single
A subsequent patch will add additional atomic operations. These new
operations will use the same opcode field as the existing XADD, with
the immediate discriminating different operations.
In preparation, rename the instruction mode BPF_ATOMIC and start
calling the zero immediate BPF_ADD.
This is
This adds instructions for
atomic[64]_[fetch_]and
atomic[64]_[fetch_]or
atomic[64]_[fetch_]xor
All these operations are isomorphic enough to implement with the same
verifier, interpreter, and x86 JIT code, hence being a single commit.
The main interesting thing here is that x86 doesn't directly
A later commit will need to lookup a subset of these opcodes. To
avoid duplicating code, pull out a table.
The shift opcodes won't be needed by that later commit, but they're
already duplicated, so fold them into the table anyway.
Signed-off-by: Brendan Jackman
Acked-by: John Fastabend
---
This adds two atomic opcodes, both of which include the BPF_FETCH
flag. XCHG without the BPF_FETCH flag would naturally encode
atomic_set. This is not supported because it would be of limited
value to userspace (it doesn't imply any barriers). CMPXCHG without
BPF_FETCH woulud be an atomic
The case for JITing atomics is about to get more complicated. Let's
factor out some common code to make the review and result more
readable.
NB the atomics code doesn't yet use the new helper - a subsequent
patch will add its use as a side-effect of other changes.
Acked-by: John Fastabend
The JIT case for encoding atomic ops is about to get more
complicated. In order to make the review & resulting code easier,
let's factor out some shared helpers.
Signed-off-by: Brendan Jackman
Acked-by: John Fastabend
---
arch/x86/net/bpf_jit_comp.c | 39 ++---
There's still one unresolved review comment from John[3] which I
will resolve with a followup patch.
Differences from v6->v7 [1]:
* Fixed riscv build error detected by 0-day robot.
Differences from v5->v6 [1]:
* Carried Björn Töpel's ack for RISC-V code, plus a couple more acks from
On Thu, Jan 14, 2021 at 10:01 AM Will Deacon wrote:
>
> Rather than modifying the 'address' field of the 'struct vm_fault_info'
> passed to do_set_pte(), leave that to identify the real faulting address
> and pass in the virtual address to be mapped by the new pte as a
> separate argument.
Ack.
On Thu, Jan 14, 2021 at 10:01 AM Will Deacon wrote:
>
> Try to clean this up by splitting the immutable fault information out
> into a new 'struct vm_fault_info' which is embedded in 'struct vm_fault'
> and will later be made 'const'. The vast majority of this change was
> performed with a
On Thu, Jan 14, 2021 at 5:25 AM Masahiro Yamada wrote:
>
> The cc-version.sh also shows the error if the compiler is old:
>
> $ make defconfig CC=clang-9
> *** Default configuration is based on 'x86_64_defconfig'
> ***
> *** Compiler is too old.
> *** Your Clang version:9.0.1
>
On Thu, 14 Jan 2021 09:50:44 -0800
Ben Widawsky wrote:
> On 21-01-14 17:40:12, Jonathan Cameron wrote:
> > On Mon, 11 Jan 2021 14:51:11 -0800
> > Ben Widawsky wrote:
> >
> > > Provide enough functionality to utilize the mailbox of a memory device.
> > > The mailbox is used to interact with
On 21-01-14 18:02:11, Jonathan Cameron wrote:
> On Mon, 11 Jan 2021 14:51:19 -0800
> Ben Widawsky wrote:
>
> > The Command Effects Log (CEL) is specified in the CXL 2.0 specification.
> > The CEL is one of two types of logs, the other being vendor specific.
> > They are distinguished in
On Wed, Jan 13, 2021 at 04:25:41PM -0600, Josh Poimboeuf wrote:
> On Wed, Jan 13, 2021 at 08:23:15PM +, Mark Brown wrote:
> > On Wed, Jan 13, 2021 at 01:33:13PM -0600, Josh Poimboeuf wrote:
> >
> > > I think it's worth mentioning a little more about objtool. There are a
> > > few passing
Simplify Multi/Single planer API handling by converting to v4l2_ext_pix_format.
Duplicate v4l2_ioctl_ops for touch devices. This is done to force the
framework to use the ext hooks when the classic Api is used from
userspace in Vid devices, and to keep touch devices with classic hook.
On Mon, 11 Jan 2021 14:51:20 -0800
Ben Widawsky wrote:
> The Get Log command returns the actual log entries that are advertised
> via the Get Supported Logs command (0400h). CXL device logs are selected
> by UUID which is part of the CXL spec. Because the driver tries to
> sanitize what is sent
Paul Gortmaker reported a regression in the GCC version check [1].
If you use GCC 4.8, the build breaks before showing the error message
"error Sorry, your version of GCC is too old - please use 4.9 or newer."
I do not want to apply his fix-up since it implies we would not be able
to remove any
On Wed, Jan 13, 2021 at 11:36 PM Marek Szyprowski
wrote:
>
> Hi Saravana,
>
> On 13.01.2021 20:23, Saravana Kannan wrote:
> > On Tue, Jan 12, 2021 at 11:04 PM Marek Szyprowski
> > wrote:
> >> On 12.01.2021 21:51, Saravana Kannan wrote:
> >>> On Mon, Jan 11, 2021 at 11:11 PM Marek Szyprowski
>
Add documentation and update references in current documentation for the
Extended API.
Signed-off-by: Helen Koike
---
Changes in v6:
- Update note saying ext_api should be used for new applications on
newer kernels (Tomasz and Hans)
- Fix typos pointed in v5 (Hand and Tomasz)
- Change order,
Simplify Multi/Single planer API handling by converting to v4l2_ext_pix_format.
Signed-off-by: Boris Brezillon
Signed-off-by: Helen Koike
---
Changes in v6:
- Update with new format and buffer structs
Changes in v4:
- Update with new format and buffer structs
- Rebased on top of media/master
Just a new version of v4l2_fill_mbus_format() and v4l2_fill_ext_pix_format()
to deal with the new v4l2_ext_pix_format struct.
This is needed to convert the VIMC driver to the EXT_FMT/EXT_BUF iocts.
Signed-off-by: Boris Brezillon
Signed-off-by: Helen Koike
---
Changes in v6:
- Rename
On 1/14/21 9:09 AM, Arnd Bergmann wrote:
On Tue, Jan 12, 2021 at 9:32 PM Arnd Bergmann wrote:
---
v2: fix various build issues in the first version, now passes
all randconfig builds I tried
Please disregard this version, while I have a tree that passes
the randconfig builds now,
Add vb2 ext hooks and call vb2_set_pixelformat().
This allows more flexibility with buffer handling.
Signed-off-by: Helen Koike
---
Changes in v6:
- New patch to exemplify how drivers would easily support features from Ext Buf
---
drivers/media/test-drivers/vimc/vimc-capture.c | 3 +++
1 file
To overcome the limitations of Ext ioctls, that is being converted to
classic hooks, add helpers to allow applications support layouts such as
using the same buffer with planes in different offsets.
To use the new hooks, drivers should:
static const struct v4l2_ioctl_ops ioctl_ops = {
...
+
Add vb2 ext hooks and call vb2_set_pixelformat().
This allows more flexibility with buffer handling.
Signed-off-by: Helen Koike
---
Changes in v6:
- New patch to exemplify how drivers would easily support features from Ext Buf
---
drivers/media/test-drivers/vivid/vivid-core.c| 2 ++
On Tue, Dec 29 2020 at 3:55am -0500,
Satya Tangirala wrote:
> DM only allows the table to be swapped if the new table's inline encryption
> capabilities are a superset of the old table's. We only check that this
> constraint is true when the table is actually swapped in (in
> dm_swap_table()).
Reorganize flags handling to be easily reuseble when Ext functions get
added.
No logic is changed, just moving around code.
- Two new functions:
v4l2_clear_buffer_flags()
vb2_fill_vb2_v4l2_buffer_flags()
- set_buffer_cache_hints() receives a pointer to flags instead of the
Those extended buffer ops have several purpose:
1/ Fix y2038 issues by converting the timestamp into an u64 counting
the number of ns elapsed since 1970
2/ Unify single/multiplanar handling
3/ Add a new start offset field to each v4l2 plane buffer info struct
to support the case where a
This is part of the multiplanar and singleplanar unification process.
v4l2_ext_pix_format is supposed to work for both cases.
We also add the concept of modifiers already employed in DRM to expose
HW-specific formats (like tiled or compressed formats) and allow
exchanging this information with
Add normalization to pixelformats, so we can fallback to it when using
Ext API, and eliminating the handling of two variantes (M and non-M
formats).
Signed-off-by: Helen Koike
---
Changes in v6:
- New patch
---
drivers/media/v4l2-core/v4l2-common.c | 16
Hello,
This is v6 of the Extended API for formats and buffers (see below the new API).
The new API comes for free for old drivers through the conversion layer, which
is independent of vb2.
I completly refactored several patches. I would like to request comments not
only in the uAPI, but also
On Thu, Jan 14, 2021 at 4:38 AM 'Dmitry Vyukov' via Clang Built Linux
wrote:
>
> On Thu, Jan 14, 2021 at 12:32 PM Dmitry Vyukov wrote:
> >
> > On Tue, Jan 12, 2021 at 8:41 PM Nathan Chancellor
> > wrote:
> > >
> > > Would it be possible for clang-built-li...@googlegroups.com to be CC'd
> > >
Print capabilities field from struct v4l2_create_buffers for better
debugging.
Signed-off-by: Helen Koike
---
drivers/media/v4l2-core/v4l2-ioctl.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c
Il 14/01/21 18:58, Bjorn Andersson ha scritto:
On Thu 14 Jan 11:49 CST 2021, AngeloGioacchino Del Regno wrote:
Document the new noise rejection properties "qcom,noise-reject-sda"
and "qcom,noise-reject-scl".
I presume these are unit-less levels?
Yes, there is no unit.
Sorry, I've sent
request_fd is validated under media_request_get_by_fd() just below this
check. Thus remove it.
Suggested-by: Tomasz Figa
Signed-off-by: Helen Koike
---
drivers/media/common/videobuf2/videobuf2-v4l2.c | 5 -
1 file changed, 5 deletions(-)
diff --git
sizeimage field should be set to zero for unused planes, even when
v4l2_pix_format_mplane.num_planes is smaller then the index of planes.
Signed-off-by: Helen Koike
---
I caught this with v4l2-compliance, which throws an error if we dirty
planes, even if invalid, so I would like to make it
On 11/20/20 10:20 AM, Hans Verkuil wrote:
> On 20/11/2020 13:40, Tomasz Figa wrote:
>> On Fri, Nov 20, 2020 at 9:24 PM Hans Verkuil wrote:
>>>
>>> On 20/11/2020 12:06, Tomasz Figa wrote:z
Hi Helen,
On Tue, Aug 04, 2020 at 04:29:39PM -0300, Helen Koike wrote:
> Add
This patch series converts the i2c-qup bindings to YAML and then
adds support for noise rejection, which is needed for some noisy
hardware, like the touchscreen on the F(x)Tec Pro1.
After adding noise rejection, the touchscreen stopped showing
ghost touch issues and lockups.
Tested on F(x)Tec
Hello Clemens,
On Thu, Jan 14, 2021 at 06:16:22PM +0100, Clemens Gruber wrote:
> On Mon, Jan 11, 2021 at 09:35:32PM +0100, Uwe Kleine-König wrote:
> > My position here is: A consumer should disable a PWM before calling
> > pwm_put. The driver should however not enforce this and so should not
> >
Convert the qcom,i2c-qup binding to YAML schema.
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/i2c/qcom,i2c-qup.txt | 40 -
.../devicetree/bindings/i2c/qcom,i2c-qup.yaml | 87 +++
2 files changed, 87 insertions(+), 40 deletions(-)
delete mode
Some I2C devices may be glitchy due to electrical noise coming
from the device itself or because of possible board design issues.
To overcome this issue, the QUP's I2C in Qualcomm SoCs supports
a noise rejection setting for both SCL and SDA lines.
Introduce a setting for noise rejection through
Just minor things.
Add capabilities to v4l_print_create_buffers(), clarify docs and remove
a redundant check.
Helen Koike (3):
media: v4l2-ioctl: print capabilities in v4l_print_create_buffers()
media: videodev2.h: clarify v4l2_pix_format_mplane.sizeimage docs when
to set to zero
media:
Document the new noise rejection properties "qcom,noise-reject-sda"
and "qcom,noise-reject-scl".
Signed-off-by: AngeloGioacchino Del Regno
---
.../devicetree/bindings/i2c/qcom,i2c-qup.yaml | 14 ++
1 file changed, 14 insertions(+)
diff --git
On Wed, Jan 13, 2021 at 09:39:26AM +0100, David Hildenbrand wrote:
> On 13.01.21 02:21, Minchan Kim wrote:
> > Contiguous memory allocation can be stalled due to waiting
> > on page writeback and/or page lock which causes unpredictable
> > delay. It's a unavoidable cost for the requestor to get
On Mon, 11 Jan 2021 14:51:19 -0800
Ben Widawsky wrote:
> The Command Effects Log (CEL) is specified in the CXL 2.0 specification.
> The CEL is one of two types of logs, the other being vendor specific.
> They are distinguished in hardware/spec via UUID. The CEL is immediately
> useful for 2
Permissions are necessary to get a tracepoint id. Fail the test when the
read fails.
Signed-off-by: Ian Rogers
---
tools/lib/perf/tests/test-evlist.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/lib/perf/tests/test-evlist.c
b/tools/lib/perf/tests/test-evlist.c
index
If a test fails return -1 rather than 0. This is consistent with the
return value in test-cpumap.c
Signed-off-by: Ian Rogers
---
tools/lib/perf/tests/test-cpumap.c| 2 +-
tools/lib/perf/tests/test-evlist.c| 2 +-
tools/lib/perf/tests/test-evsel.c | 2 +-
On 1/14/21 11:12 AM, Sean Christopherson wrote:
On Thu, Jan 14, 2021, Tom Lendacky wrote:
On 1/13/21 6:36 PM, Sean Christopherson wrote:
Free sev_asid_bitmap if the reclaim bitmap allocation fails, othwerise
KVM will unnecessarily keep the bitmap when SEV is not fully enabled.
Freeing the
On Wed, Jan 13, 2021 at 5:54 PM Marco Elver wrote:
>
> > +/*
> > + * Unlike kasan_check_read/write(), kasan_check_byte() is performed even
> > for
> > + * the hardware tag-based mode that doesn't rely on compiler
> > instrumentation.
> > + */
> > +bool __kasan_check_byte(const void *addr,
On Tue, Dec 29 2020 at 3:55am -0500,
Satya Tangirala wrote:
> Update the device-mapper core to support exposing the inline crypto
> support of the underlying device(s) through the device-mapper device.
>
> This works by creating a "passthrough keyslot manager" for the dm
> device, which
Rather than modifying the 'address' field of the 'struct vm_fault_info'
passed to do_set_pte(), leave that to identify the real faulting address
and pass in the virtual address to be mapped by the new pte as a
separate argument.
This makes FAULT_FLAG_PREFAULT redundant, as a prefault entry can be
Hi Jean,
On 1/14/21 6:33 PM, Jean-Philippe Brucker wrote:
> Hi Eric,
>
> On Thu, Jan 14, 2021 at 05:58:27PM +0100, Auger Eric wrote:
The uacce-devel branches from
> https://github.com/Linaro/linux-kernel-uadk do provide this at the moment
> (they track the latest sva/zip-devel
In preparation for const-ifying the 'info' field of 'struct vm_fault',
rework __collapse_huge_page_swapin() to avoid continously updating
vmf.info.address and instead populate a new 'struct vm_fault' on the
stack for each page being processed.
Cc: Kirill A. Shutemov
Cc: Linus Torvalds
The field is only ever read after being initialised, so mark it 'const'
before somebody tries to modify it again.
Cc: Kirill A. Shutemov
Cc: Linus Torvalds
Signed-off-by: Will Deacon
---
include/linux/mm.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/mm.h
601 - 700 of 1491 matches
Mail list logo
