Hi Rob,
On 7/16/20 2:43 PM, Stefano Stabellini wrote:
On Thu, 16 Jul 2020, Mathieu Poirier wrote:
Hi Rob,
On Tue, Jul 14, 2020 at 11:15:53AM -0600, Rob Herring wrote:
On Mon, Jun 29, 2020 at 09:49:19PM -0500, Suman Anna wrote:
The Texas Instruments K3 family of SoCs have one or more
On Tue, Jul 21, 2020 at 4:08 AM Thomas Gleixner wrote:
>
> From: Thomas Gleixner
>
> Like the syscall entry/exit code interrupt/exception entry after the real
> low level ASM bits should not be different accross architectures.
>
> Provide a generic version based on the x86 code.
I don't like
On Tue, Jul 21, 2020 at 4:08 AM Thomas Gleixner wrote:
>
> Like syscall entry all architectures have similar and pointlessly different
> code to handle pending work before returning from a syscall to user space.
>
> 1) One-time syscall exit work:
> - rseq syscall exit
> - audit
>
Hi,
On Tue, Jul 21, 2020 at 11:32:04AM -0500, Dan Murphy wrote:
> Add the Texas Instruments BQ27561 battery monitor. The register address
> map is laid out the same as compared to other devices within the file.
> The battery status register has differing bits to determine if the
> battery is
Replace the existing /* fall through */ comments and its variants with
the new pseudo-keyword macro fallthrough[1]. Also, remove unnecessary
fall-through markings when it is the case.
[1]
On Mon, Jul 27, 2020 at 04:16:08PM +0300, Dan Carpenter wrote:
> drivers/block/floppy.c:3132 raw_cmd_copyout() warn: check that 'cmd' doesn't
> leak information (struct has a hole after 'flags')
(Removed some Cc: recipients from the list.)
I'm not very sure, but I think this one is also a false
On Fri, 24 Jul 2020 10:40:25 +0200
Pavel Machek wrote:
> Fix non-existing constant in documentation.
>
> Signed-off-by: Pavel Machek (CIP)
>
> diff --git a/Documentation/input/uinput.rst b/Documentation/input/uinput.rst
> index b8e90b6a126c..10c62e62a0a6 100644
> ---
On Mon, Jul 27, 2020 at 12:23 PM Roman Gushchin wrote:
>
> Include percpu arrays and auxiliary data into the memcg-based memory
> accounting.
>
> Signed-off-by: Roman Gushchin
Acked-by: Song Liu
Error/Warning ids grouped by kconfigs:
recent_errors
|-- i386-allyesconfig
| `-- include-linux-irqflags.h:error:expected-expression-before-)-token
|-- i386-randconfig-c001-20200727
| `-- include-linux-irqflags.h:error:expected-expression-before-)-token
|-- x86_64-allmodconfig
| `-- include
On Thu, Jul 16, 2020 at 12:50 PM Thomas Gleixner wrote:
>
> From: Thomas Gleixner
>
> On syscall entry certain work needs to be done:
>
>- Establish state (lockdep, context tracking, tracing)
>- Conditional work (ptrace, seccomp, audit...)
>
> This code is needlessly duplicated and
On Fri, 24 Jul 2020 18:01:38 -0500
Pierre-Louis Bossart wrote:
> The kbuild bot recently added the W=1 option, which triggered
> documentation cleanups to squelch hundreds of kernel-doc warnings.
>
> To make sure new kernel contributions don't add regressions to
> kernel-doc descriptors, this
On Sun, 26 Jul 2020 07:58:43 +0200
Lukas Bulwahn wrote:
> Commit 2165b82fde82 ("docs: Move kprobes.rst from staging/ to trace/")
> moved kprobes.rst, but missed to adjust the MAINTAINERS entry.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file
On Sun, 26 Jul 2020 09:53:27 +0200
Pavel Machek wrote:
> Document rfkill allocation.
>
> Signed-off-by: Pavel Machek (CIP)
>
> diff --git a/Documentation/admin-guide/devices.txt
> b/Documentation/admin-guide/devices.txt
> index 2a97aaec8b12..763fedd94d7d 100644
> ---
On Sun, 26 Jul 2020 17:47:35 +0200
Julia Lawall wrote:
> RESOURCE_IO does not exist. Rename to IORESOURCE_IO.
>
> Signed-off-by: Julia Lawall
>
> ---
> Just a guess based on the most similar name...
>
> Documentation/filesystems/sysfs-pci.rst |2 +-
> 1 file changed, 1 insertion(+), 1
On Sun, 26 Jul 2020 20:43:40 +0200
Julia Lawall wrote:
> There is no flag REMAP_CAN_SHORTEN. Commit eca3654e3cc7 ("vfs: enable
> remap callers that can handle short operations") that introduces this
> text also introduces the flag REMAP_FILE_CAN_SHORTEN. Change the name
> in the documentation
Hi John,
On Mon, 27 Jul 2020 17:13:44 +0206 John Ogness
wrote:
>
> On 2020-07-27, Stephen Rothwell wrote:
> > In commit
> >
> > 96b917f8e9ec ("printk: ringbuffer: support dataless records")
> >
> > Fixes tag
> >
> > Fixes: ("printk: use the lockless ringbuffer")
> >
> > has these
On Mon, Jul 27, 2020 at 3:01 PM Dmitry Torokhov
wrote:
>
> On Mon, Jul 27, 2020 at 11:29:33PM +0200, Pavel Machek wrote:
> > Hi!
> >
> > > From: Derek Basehore
> > >
> > > [ Upstream commit 966334dfc472bdfa67bed864842943b19755d192 ]
> > >
> > > This moves the wakeup increment for elan devices to
On Sun, 26 Jul 2020 21:22:21 +0200
Julia Lawall wrote:
> Change the nonexistent flag names WBC_SYNC_ALL and WBC_SYNC_NONE to
> WB_SYNC_ALL and WB_SYNC_NONE, respectively, as used in the code with
> wbc->sync_mode.
>
> Signed-off-by: Julia Lawall
>
> ---
> Documentation/filesystems/vfs.rst |
On Mon, Jul 27, 2020 at 12:23 PM Roman Gushchin wrote:
>
> This patch enables memcg-based memory accounting for memory allocated
> by __bpf_map_area_alloc(), which is used by most map types for
> large allocations.
>
> Following patches in the series will refine the accounting for
> some map
On Mon, Jul 27, 2020 at 12:20 PM Roman Gushchin wrote:
>
> Include memory used by bpf programs into the memcg-based accounting.
> This includes the memory used by programs itself, auxiliary data
> and statistics.
>
> Signed-off-by: Roman Gushchin
> ---
> kernel/bpf/core.c | 8
> 1 file
On 7/24/20 7:01 PM, Stefano Stabellini wrote:
> Yes, it does, thank you. I'd rather not introduce unknown regressions so
> I would recommend to add an arch-specific check on registering
> freeze/thaw/restore handlers. Maybe something like the following:
>
> #ifdef CONFIG_X86
> .freeze =
On Mon, Jul 27, 2020 at 7:21 AM Rafael J. Wysocki wrote:
>
> On Fri, Jul 24, 2020 at 8:05 PM Saravana Kannan wrote:
> >
> > The devlink device name is of the form "supplier:consumer". But ":" is
> > fairly common in device names and makes it visually hard to distinguish
> > supplier and
Hi Linus,
I have some last-minute fixes I hope you can still pull in for 5.8.
One is for a boot regression (mmu code broken) and the other fixes a
long-standing broken syscall number bounds check.
Rich
The following changes since commit 92ed301919932f13b9172e525674157e983d:
Linux
Hi all,
ommit
ed944d574cc7 ("ack! virtio: VIRTIO_F_IOMMU_PLATFORM ->
VIRTIO_F_ACCESS_PLATFORM")
is missing a Signed-off-by from its author and committer.
I have never seen an empty commit like this before - I assume it is just
a way to add an Reviewed-by to a previous commit without
On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin wrote:
>
> As bpf is not using memlock rlimit for memory accounting anymore,
> let's remove the related code from libbpf.
>
> Bpf operations can't fail because of exceeding the limit anymore.
>
They can't in the newest kernel, but libbpf will keep
On Mon, Jul 27, 2020 at 04:16:08PM +0300, Dan Carpenter wrote:
> drivers/char/hpet.c:675 hpet_ioctl() warn: check that 'info' doesn't leak
> information (struct has a hole after 'hi_timer')
This one seems like a false positive.
drivers/char/hpet.c:670:
mutex_lock(_mutex);
err =
Hi,
On 2020-07-15 22:22, Ezequiel Garcia wrote:
> Now that slice invariant parameters have been moved,
> the driver no longer needs this control, so drop it.
>
> Signed-off-by: Ezequiel Garcia
> ---
> drivers/staging/media/rkvdec/rkvdec-h264.c | 4
> drivers/staging/media/rkvdec/rkvdec.c
On Mon, Jul 27, 2020 at 11:29:33PM +0200, Pavel Machek wrote:
> Hi!
>
> > From: Derek Basehore
> >
> > [ Upstream commit 966334dfc472bdfa67bed864842943b19755d192 ]
> >
> > This moves the wakeup increment for elan devices to the touch report.
> > This prevents the drivers from incorrectly
On Mon, Jul 27, 2020 at 11:26:23PM +0200, Pavel Machek wrote:
> Hi!
>
> > [ Upstream commit c463bb2a8f8d7d97aa414bf7714fc77e9d3b10df ]
> >
> > This event code represents the state of a removable cover of a device.
> > Value 0 means that the cover is open or removed, value 1 means that the
> >
On 7/27/20 4:07 PM, Joe Perches wrote:
External email: Use caution opening links or attachments
On Mon, 2020-07-27 at 15:58 -0500, Daniel Dadap wrote:
Add an additional regular expression to detect updates to the
MAINTAINERS file as reported in the unified diffs generated by
`git
Since commit
0982adc74673 ("x86/boot/KASLR: Work around firmware bugs by excluding
EFI_BOOT_SERVICES_* and EFI_LOADER_* from KASLR's choice")
process_efi_entries will return true if we have an EFI memmap, not just
if it contained EFI_MEMORY_MORE_RELIABLE regions.
Signed-off-by: Arvind Sankar
Get rid of unnecessary temporary variables and redundant tests in
__process_mem_region.
Fix one minor bug: in case of an overlap, the beginning of the region
should be used even if it is exactly image_size, not just strictly
larger.
Change type of minimum/image_size arguments in
The first 7 patches are cleanup and minor bugfixes on the x86 KASLR
code.
The last one is a bit of an RFC. The memory regions used for KASLR are
stored as 64-bit even on a 32-bit kernel. However there are still a few
local variables that are 32-bit, but should be ok as far as I can see
because
Commit
f28442497b5c ("x86/boot: Fix KASLR and memmap= collision")
converted mem_vector type to use 64-bit on the 32-bit kernel as well,
based on Thomas's review [0]. However:
- the code still doesn't consistently use 64-bit types. For instance,
mem_avoid_overlap uses 32-bit types when checking
Short-circuit the whole function on 32-bit.
Replace the loop to determine the number of 1Gb pages with arithmetic.
Fix one minor bug: if the end of the region is aligned on a 1Gb
boundary, the current code will not use the last available 1Gb page due
to an off-by-one error.
Signed-off-by:
Handle the possibility that the command line is NULL.
Replace open-coded strlen with a function call.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/arch/x86/boot/compressed/kaslr.c
On 64-bit, the kernel must be placed below MAXMEM (64TiB with 4-level
paging or 4PiB with 5-level paging). This is currently not enforced by
KASLR, which thus implicitly relies on physical memory being limited to
less than 64TiB.
On 32-bit, the limit is KERNEL_IMAGE_SIZE (512MiB). This is
The number of slots and slot areas can be unsigned int, since on 64-bit,
the maximum amount of memory is 2^52, the minimum alignment is 2^21, so
the slot number cannot be greater than 2^31. The slot areas are limited
by MAX_SLOT_AREA, currently 100. Replace the type used for slot number,
which is
On Sat, Jul 25, 2020 at 03:12:49PM +0300, Andy Shevchenko wrote:
> On Sat, Jul 25, 2020 at 2:03 AM Serge Semin
> wrote:
> > On Thu, Jul 23, 2020 at 01:03:17PM +0300, Andy Shevchenko wrote:
> > > On Thu, Jul 23, 2020 at 04:38:55AM +0300, Serge Semin wrote:
...
> > > > + /* This will
Drop the warning on seeing "--" in handle_mem_options. This will trigger
whenever one of the memory options is present in the command line
together with "--", but there's no problem if that is the case.
Replace goto with break.
Signed-off-by: Arvind Sankar
---
arch/x86/boot/compressed/kaslr.c
On Mon, Jul 27, 2020 at 08:52:25PM +0100, James Ettle wrote:
> On Mon, 2020-07-27 at 09:14 -0500, Bjorn Helgaas wrote:
> > I don't know the connection between ASPM and package C-states, so I
> > need to simplify this even more. All I want to do right now is
> > verify
> > that if we don't have
On Fri, Jul 24, 2020 at 11:36:51PM +0200, Martin Botka wrote:
> From: Fenglin Wu
>
> Normally, PWM channel has fixed output until software request to change
> its settings. There are some PWM devices which their outputs could be
> changed autonomously according to a predefined pattern programmed
On Mon, Jul 27, 2020 at 10:26:53PM +0200, KP Singh wrote:
> Thanks for this, I was able to update the series with this patch and it works.
> One minor comment though.
>
> I was wondering how should I send it as a part of the series. I will keep the
> original commit description + mention this
On 7/27/20 10:54 AM, Colin King wrote:
From: Colin Ian King
There are a couple of arguments of the boolean flag zero_size_allowed
and the char pointer buf_info when calling to function check_buffer_access
that are swapped by mistake. Fix these by swapping them to correct
the argument
ptrace_get_syscall_info() is copying uninitialized stack memory to
userspace due to the compiler not initializing holes in statically
allocated structures. Fix it by initializing `info` with memset().
Cc: sta...@vger.kernel.org
Fixes: 201766a20e30 ("ptrace: add PTRACE_GET_SYSCALL_INFO request")
* Thomas Gleixner wrote:
> Ingo Molnar writes:
> >> - get_option(, _cpus);
> >> + if (get_option(, _cpus) != 1)
> >> + return -EINVAL;
> >> +
> >>if (nr_cpus > 0 && nr_cpus < nr_cpu_ids)
> >>nr_cpu_ids = nr_cpus;
> >> + else
> >> + return -EINVAL;
> >
> >
On Mon, Jul 27, 2020 at 11:11 PM Mazin Rezk wrote:
>
> On Monday, July 27, 2020 4:29 PM, Daniel Vetter wrote:
>
> > On Mon, Jul 27, 2020 at 9:28 PM Christian König
> > wrote:
> > >
> > > Am 27.07.20 um 16:05 schrieb Kazlauskas, Nicholas:
> > > > On 2020-07-27 9:39 a.m., Christian König wrote:
>
On behalf of the Linux Foundation Technical Advisory Board (TAB), I'd
like to announce the voting procedures for the 2020 TAB elections.
The pool of eligible voters will consist of the following:
1) All attendees of the Linux Plumbers conference (i.e. kernel summit)
2) Anyone who is not a
On Mon 27-07-20 16:56:16, Al Viro wrote:
> On Mon, Jul 27, 2020 at 02:41:27PM +0200, Jan Kara wrote:
> > On Sun 26-07-20 18:04:01, Christoph Hellwig wrote:
> > > Fold the misaligned u64 workarounds into the main quotactl flow instead
> > > of implementing a separate compat syscall handler.
> > >
From: Ankit Baluni
Fixed a coding style issue.
Signed-off-by: Ankit Baluni
---
drivers/staging/media/atomisp/pci/atomisp_cmd.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/media/atomisp/pci/atomisp_cmd.c
Issue ghak120 enabled syscall records to accompany required records when
no rules are present to trigger the storage of syscall context. A
reported issue showed that the cwd was not always initialized. That
issue was already resolved, but a review of all other records that could
be triggered at
Hi!
> From: Derek Basehore
>
> [ Upstream commit 966334dfc472bdfa67bed864842943b19755d192 ]
>
> This moves the wakeup increment for elan devices to the touch report.
> This prevents the drivers from incorrectly reporting a wakeup when the
> resume callback resets then device, which causes an
On Mon, Jul 27, 2020 at 3:01 AM Cixi Geng wrote:
>
> Hi Brendan:
> When I run kunit test in um , it failed on kernel 5.8-rc* while
> succeeded in v5.7 with same configuration. is this a bug?
>
> Here is my operation:
> gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
>
> the kunitconfig:
>
Hi!
> [ Upstream commit c463bb2a8f8d7d97aa414bf7714fc77e9d3b10df ]
>
> This event code represents the state of a removable cover of a device.
> Value 0 means that the cover is open or removed, value 1 means that the
> cover is closed.
This is only needed for N900 cover changes. I don't see them
syzbot suspects this issue was fixed by commit:
commit ce684552a266cb1c7cc2f7e623f38567adec6653
Author: Tetsuo Handa
Date: Sun Jul 12 11:10:12 2020 +
vt: Reject zero-sized screen buffer size.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14357d8c90
start commit:
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: b16d0cb9e2fc ("iommu/vt-d: Always enable PASID/PRI PCI
capabilities before ATS").
The bot has tested the following trees: v5.7.10, v5.4.53, v4.19.134, v4.14.189,
v4.9.231,
Unregister from suspend notifications and cancel suspend preparations
before running hci_dev_do_close. Otherwise, the suspend notifier may
race with unregister and cause cmd_timeout even after hdev has been
freed.
Signed-off-by: Abhishek Pandit-Subedi
Reviewed-by: Miao-chen Chou
---
Hi Marcel,
Hello,
Mo 27. 7. 2020 at 22:10 Uwe Kleine-König wrote:
>
> On Fri, Jul 24, 2020 at 11:36:53PM +0200, Martin Botka wrote:
> > From: Fenglin Wu
> >
> > Add pwm_chip to support QTI LPG module and export LPG channels as
> > PWM devices for consumer drivers' usage.
> >
> > Signed-off-by: Fenglin Wu
On Mon, 2020-07-27 at 22:34 +0200, Lukas Bulwahn wrote:
> On Mon, 27 Jul 2020, Nachiket Naganure wrote:
> > On Sun, Jul 26, 2020 at 11:14:42PM -0700, Joe Perches wrote:
> > > On Mon, 2020-07-27 at 11:24 +0530, Nachiket Naganure wrote:
[]
> > > OK, but the test should be:
> > >
> > >
On Sun, 26 Jul 2020 20:36:53 +0530, Sivaprakash Murugesan wrote:
> From: Sivaprakash Murugesan
>
> Convert QCOM pci bindings to YAML schema
>
> Signed-off-by: Sivaprakash Murugesan
> ---
> [v2]
> - Referenced pci-bus.yaml
> - removed duplicate properties already referenced by pci-bus.yaml
Russell King - ARM Linux admin escreveu no dia
segunda, 27/07/2020 à(s) 18:30:
>
> On Mon, Jul 27, 2020 at 06:16:32PM +0200, Alexandre Belloni wrote:
> > On 27/07/2020 17:55:50+0200, Jon Nettleton wrote:
> > > > So, can we please have that discussion, it is pertinent to this patch.
> > > >
> > >
On Monday, July 27, 2020 4:29 PM, Daniel Vetter wrote:
> On Mon, Jul 27, 2020 at 9:28 PM Christian König
> wrote:
> >
> > Am 27.07.20 um 16:05 schrieb Kazlauskas, Nicholas:
> > > On 2020-07-27 9:39 a.m., Christian König wrote:
> > >> Am 27.07.20 um 07:40 schrieb Mazin Rezk:
> > >>> This patch
The DT node full name is currently being used in regmap_config
which in turn is used to create the regmap debugfs directories.
This name however is not guaranteed to be unique and the regmap
debugfs registration can fail in the cases where the syscon nodes
have the same unit-address but are
If the kernel is built with CONFIG_PROVE_RAW_LOCK_NESTING
option, the lockedp will complain about violation of the
nesting rules:
[ 28.060389] =
[ 28.060389] [ BUG: Invalid wait context ]
[ 28.060389] 5.8.0-rc3-rcu #211 Tainted: GE
[ 28.060389]
Hi Sam,
Le lun. 27 juil. 2020 à 22:31, Sam Ravnborg a
écrit :
Hi Paul.
On Mon, Jul 27, 2020 at 06:46:10PM +0200, Paul Cercueil wrote:
This driver will register a DBI host driver for panels connected
over
SPI.
So this is actually a MIPI DBI host driver.
I personally would love to have
On Mon, Jul 27, 2020 at 10:29 PM Daniel Vetter wrote:
>
> On Mon, Jul 27, 2020 at 9:28 PM Christian König
> wrote:
> >
> > Am 27.07.20 um 16:05 schrieb Kazlauskas, Nicholas:
> > > On 2020-07-27 9:39 a.m., Christian König wrote:
> > >> Am 27.07.20 um 07:40 schrieb Mazin Rezk:
> > >>> This patch
On Fri, 24 Jul 2020 16:44:15 -0700, Saravana Kannan wrote:
> Add support for pinctrl-0 through pinctrl-8 explicitly instead of trying
> to add support for pinctrl-%d properties.
>
> Of all the pinctrl-* properties in dts files (20322), only 47% (9531)
> are pinctrl-%d properties. Of all the
On Mon, 2020-07-27 at 15:58 -0500, Daniel Dadap wrote:
> Add an additional regular expression to detect updates to the
> MAINTAINERS file as reported in the unified diffs generated by
> `git format-patch`. This suppresses the "does MAINTAINERS need
> updating" message when MAINTAINERS is updated
On Fri, 24 Jul 2020 16:44:14 -0700, Saravana Kannan wrote:
> Add support for creating device links out of the following DT bindings:
> - interrupts-extended
> - nvmem-cells
> - phys
> - wakeup-parent
>
> Signed-off-by: Saravana Kannan
> ---
> v1->v2: No changes. Just sending again because v2 has
On Thu, Jul 23, 2020 at 04:09:42PM +0300, Georgi Djakov wrote:
> From: Sibi Sankar
>
> Increase the number of interconnect-cells, as now we can include
> the tag information. The consumers can specify the path tag as an
> additional argument to the endpoints.
>
> Signed-off-by: Sibi Sankar
>
On Sat, 25 Jul 2020 00:59:33 +0900, Katsuhiro Suzuki wrote:
> This patch converts Everest Semiconductor ES8316 low power audio
> CODEC binding to DT schema.
>
> Signed-off-by: Katsuhiro Suzuki
>
> ---
>
> Changes in v2:
> - Change maintainers from Mark to Daniel and me
> ---
>
-20200727
`--
arch-riscv-kernel-ptrace.c:error:too-few-arguments-to-function-secure_computing
elapsed time: 1728m
configs tested: 70
configs skipped: 1
arm defconfig
arm allyesconfig
arm allmodconfig
Many of the challenges of implementing a simple version of exec come
from the fact the code handles execing multi-thread processes.
To the best of my knowledge processes with more than one thread
calling exec are not common, and as all of the threads will be killed
by exec there does not appear
hinfo_to_cinfo() does no operation on `cinfo` when `hinfo` is NULL,
causing kioc_to_mimd() to copy uninitialized stack memory to userspace.
Fix it by initializing `cinfo` with memset().
Cc: sta...@vger.kernel.org
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Suggested-by: Dan Carpenter
Suggested-by:
On Tue 23 Jun 23:56 PDT 2020, Sai Prakash Ranjan wrote:
> Hi Bjorn,
>
> On 2020-06-21 13:39, Sai Prakash Ranjan wrote:
> > Hi Bjorn,
> >
> > On 2020-06-21 12:52, Bjorn Andersson wrote:
> > > On Tue 09 Jun 06:30 PDT 2020, Sai Prakash Ranjan wrote:
> > >
> > > > Define iommus property for
On Mon, 27 Jul 2020 13:13:47 +0530, Sumit Semwal wrote:
> The nt36672a panel from Tianma is a FHD+ panel with a resolution of
> 1080x2246 and 6.18 inches size. It is found in some of the Poco F1
> phones.
>
> Signed-off-by: Sumit Semwal
>
> ---
> v2: remove ports node, making port@0 directly
On Thu, 23 Jul 2020 11:08:37 -0500, Dan Murphy wrote:
> Convert the TAS2562 text file to yaml format.
>
> Signed-off-by: Dan Murphy
> ---
> .../devicetree/bindings/sound/tas2562.yaml| 69 +++
> 1 file changed, 69 insertions(+)
> create mode 100644
On Fri, Jul 24, 2020 at 11:24:58PM +0200, Thomas Gleixner wrote:
> Ira,
>
> Thomas Gleixner writes:
> > Ira Weiny writes:
> >> On Thu, Jul 23, 2020 at 09:53:20PM +0200, Thomas Gleixner wrote:
> >> I think, after fixing my code (see below), using idtentry_state could still
> >> work. If the
On Thu, Jul 23, 2020 at 04:09:41PM +0300, Georgi Djakov wrote:
> From: Sibi Sankar
>
> Use the qcom_icc_xlate_extended() in order to parse tags, that are
> specified as an additional arguments to the path endpoints in DT.
>
> Signed-off-by: Sibi Sankar
> Signed-off-by: Georgi Djakov
On Tue, 2020-07-28 at 04:05 +1000, James Morris wrote:
> On Wed, 1 Jul 2020, Colin King wrote:
>
> > From: Colin Ian King
> >
> > The variable ret is being initialized with a value that is never read
> > and it is being updated later with a new value. The initialization is
> > redundant and
Mo 27. 7. 2020 at 22:10 Uwe Kleine-König wrote:
>
> Hello,
>
> On Fri, Jul 24, 2020 at 11:36:51PM +0200, Martin Botka wrote:
> > From: Fenglin Wu
> >
> > Normally, PWM channel has fixed output until software request to change
>
> "fixed" in the sense of "periodic", not "constant", right?
Hi!
> From: Mikulas Patocka
>
> commit 5df96f2b9f58a5d2dc1f30fe7de75e197f2c25f2 upstream.
>
> Commit adc0daad366b62ca1bce3e2958a40b0b71a8b8b3 ("dm: report suspended
> device during destroy") broke integrity recalculation.
>
> The problem is dm_suspended() returns true not only during suspend,
On Sat, 25 Jul 2020 18:58:16 +0200
Peter Zijlstra wrote:
> On Fri, Jul 24, 2020 at 06:18:46PM -0400, Steven Rostedt wrote:
> > On Fri, 24 Jul 2020 23:50:03 +0200
> > pet...@infradead.org wrote:
> >
> > > - if (producer_fifo < 0)
> > > + if (producer_fifo)
> > > + trace_printk("Running
On Mon, Jul 27, 2020 at 02:31:14PM +0530, Vinod Koul wrote:
> On 23-07-20, 03:58, Serge Semin wrote:
> > In the previous patchset I've written the next message:
> >
> > > Folks, note I've removed the next patches from the series:
> > > [PATCH v7 04/11] dmaengine: Introduce max SG list entries
On Mon, Jul 27, 2020 at 04:28:35PM +0530, Sibi Sankar wrote:
> On 2020-07-23 18:39, Georgi Djakov wrote:
> > Increase the number of interconnect-cells, as now we can include
> > the tag information. The consumers can specify the path tag as an
> > additional argument to the endpoints.
>
>
pet...@infradead.org writes:
> Abuse the SMAP rules to ensure poke_int3_handler() doesn't call out to
> anything.
Yuck. Isn't that what noinstr is for or am I missing something?
Thanks,
tglx
tegra_i2c_runtime_resume does not disable prior enabled clocks
properly.
This patch fixes it.
Reviewed-by: Dmitry Osipenko
Signed-off-by: Sowjanya Komatineni
---
drivers/i2c/busses/i2c-tegra.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git
VI I2C is on host1x bus and is part of VE power domain.
During suspend/resume VE power domain goes through power off/on.
So, controller reset followed by i2c re-initialization is required
after the domain power up.
This patch fixes it.
Reviewed-by: Dmitry Osipenko
Signed-off-by: Sowjanya
Settle time determines the number of cil clock cyles to wait after
LP00 when moving from LP to HS.
This patch computes T-CLK-SETTLE and T-HS-SETTLE times based on cil
clock rate and pixel rate from the sensor and programs them during
streaming.
T-CLK-SETTLE time is the interval during which
Tegra internal TPG mode is only for Tegra vi and csi testing
without a real sensor and driver should default support real
sensor.
So, This patch adds CONFIG_VIDEO_TEGRA_TPG and enables Tegra
internal TPG mode only when this config is selected.
Signed-off-by: Sowjanya Komatineni
---
On 7/26/20 4:53 PM, Dmitry Osipenko wrote:
24.07.2020 02:51, Sowjanya Komatineni пишет:
VI I2C is on host1x bus and is part of VE power domain.
During suspend/resume VE power domain goes through power off/on.
So, controller reset followed by i2c re-initialization is required
after the
This patch adds support to capture from the external sensor
based on device graph in the device tree.
Driver walks through the device graph to create media links
between the entities and registers and unregisters video devices
when the corresponding sub-devices are bound and unbound.
Channel
This patch adds selection v4l2 ioctl operations to allow configuring
a selection rectangle in the sensor through the Tegra video device
node.
Some sensor drivers supporting crop uses try_crop rectangle from
v4l2_subdev_pad_config during try format for computing binning.
So with selection ops
Tegra VI supported video formats are more for non TPG and there
can be multiple pixel formats for the same media bus format.
This patch updates the helper function for format lookup based on
mbus code from pre-defined Tegra supported format list to look from
the specified list index offset.
Update VI and CSI bindings to add port and endpoint nodes as per
media video-interfaces DT binding document.
Acked-by: Rob Herring
Signed-off-by: Sowjanya Komatineni
---
.../display/tegra/nvidia,tegra20-host1x.txt| 92 +-
1 file changed, 90 insertions(+), 2
On Mon, 27 Jul 2020 11:28:40 +0200
Vincent Whitchurch wrote:
> This comment describes the behaviour before commit 2a820bf74918
> ("tracing: Use percpu stack trace buffer more intelligently"). Since
> that commit, interrupts and NMIs do use the per-cpu stacks so the
> comment is no longer
Pixel format width is mistakenly aligned to surface align bytes
and altering width to aligned value may force sensor mode change
other than the requested one and also cause mismatch in width
programmed between sensor and vi which can lead to capture errors.
This patch removes width alignment and
With the split of MIPI calibration into tegra_mipi_calibrate() and
tegra_mipi_wait(), MIPI clock is not kept enabled till the calibration
is done.
So, this patch skips disabling MIPI clock after triggering start of
calibration and disables it only after waiting for done status from
the
On Thu, Jul 23, 2020 at 04:09:39PM +0300, Georgi Djakov wrote:
> Use the qcom_icc_xlate_extended() in order to parse tags, that are
> specified as an additional arguments to the path endpoints in DT.
>
> Signed-off-by: Georgi Djakov
Reviewed-by: Matthias Kaehlcke
CSI MIPI pads need to be enabled and calibrated for capturing from
the external sensor or transmitter.
MIPI CAL unit calibrates MIPI pads pull-up, pull-down and termination
impedances. Calibration is done by co-work of MIPI BIAS pad and MIPI
CAL control unit.
Triggering calibration start can
401 - 500 of 2062 matches
Mail list logo
