On 10/6/19 10:20 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.148 release.
There are 68 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be mad
Hi,
On 07-10-2019 16:22, Ingo Molnar wrote:
* Hans de Goede wrote:
Hi,
On 07-10-2019 16:00, Ingo Molnar wrote:
* Hans de Goede wrote:
The purgatory code now uses the shared lib/crypto/sha256.c sha256
implementation. This needs memzero_explicit, implement this.
Reported-by: Arvind Sank
Hello,
syzbot found the following crash on:
HEAD commit:43b815c6 Merge tag 'armsoc-fixes' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10721dfb60
kernel config: https://syzkaller.appspot.com/x/.config?x=fb0b431ccdf08c1c
da
"#size-cells" entry is not needed for "gpio-keys" driver. Indeed "reg"
entry is not used. This commit will fix a warnings seen by DT validation
tool.
Signed-off-by: Alexandre Torgue
diff --git a/arch/arm/boot/dts/stm32746g-eval.dts
b/arch/arm/boot/dts/stm32746g-eval.dts
index d7bb2027cfaa..fcc8
On 10/6/19 10:18 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.196 release.
There are 36 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
DT validation ("make dtbs_check") has shown that some memory nodes were not
correctly written. This commit fixes this kind of issue:
"stm32f746-disco.dt.yaml: /: memory: False schema does not allow
{'device_type': ['memory'], 'reg': [[3221225472, 8388608]]}"
Signed-off-by: Alexandre Torgue
diff
On 10/6/19 10:20 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.78 release.
There are 106 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be mad
On Sun, 6 Oct 2019 10:18:11 -0700
Linus Torvalds wrote:
> On Sun, Oct 6, 2019 at 9:55 AM Theodore Y. Ts'o wrote:
> >
> > Well, one thing we *can* do is if (a) if we can create a kselftest
> > branch which we know is stable and won't change, and (b) we can get
> > assurances that Linus *will* acc
This series updates STM32 DT files in order to clean some issues seen during
STM32 device trees validation ("make dtbs_check").
Regards
Alex
Alexandre Torgue (4):
ARM: dts: stm32: fix memory nodes to match with DT validation tool
ARM: dts: stm32: fix joystick node on stm32f746 and stm32mp15
On Fri 2019-10-04 18:26:45, Qian Cai wrote:
> It is unsafe to call printk() while zone->lock was held, i.e.,
>
> zone->lock --> console_lock
>
> because the console could always allocate some memory in different code
> paths and form locking chains in an opposite order,
>
> console_lock --> * --
"phy-names" entries are not used. To be compliant with DT validation
tool, those entries have to be remove.
Signed-off-by: Alexandre Torgue
diff --git a/arch/arm/boot/dts/stm32mp157c-ev1.dts
b/arch/arm/boot/dts/stm32mp157c-ev1.dts
index 6287db532e7d..2baae5f25e2c 100644
--- a/arch/arm/boot/dts/
This commit fixes regulator-sd_switch node in order to be compliant to
DT validation schema.
Signed-off-by: Alexandre Torgue
diff --git a/arch/arm/boot/dts/stm32mp157c-ed1.dts
b/arch/arm/boot/dts/stm32mp157c-ed1.dts
index 1d426ea8bdaf..329853d9b1de 100644
--- a/arch/arm/boot/dts/stm32mp157c-ed1
On 10/6/19 10:19 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.2.20 release.
There are 137 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
On Mon 07-10-19 16:19:59, Vlastimil Babka wrote:
> On 10/2/19 10:43 AM, Michal Hocko wrote:
> > On Wed 02-10-19 06:16:43, Yang Shi wrote:
> >> The commit 87eaceb3faa59b9b4d940ec9554ce251325d83fe ("mm: thp: make
> >> deferred split shrinker memcg aware") makes deferred split queue per
> >> memcg to
Hello,
syzbot found the following crash on:
HEAD commit:43b815c6 Merge tag 'armsoc-fixes' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12165d0b60
kernel config: https://syzkaller.appspot.com/x/.config?x=1ec3be9936e004f6
da
On Fri, Oct 04, 2019 at 09:20:25AM -0400, Rich Felker wrote:
> On Fri, Oct 04, 2019 at 03:00:31PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Oct 03, 2019 at 11:29:11AM +0200, Bartosz Golaszewski wrote:
> > > From: Bartosz Golaszewski
> > >
> > > Some time ago I started a discussion about the ne
* Ingo Molnar wrote:
> > All the other reasons would require a fairly egregious kernel bug, hence
> > the speculation that the #GP is due to a non-canonical address. Something
> > like the following would be more precise, though highly unlikely to ever
> > be exercised, e.g. KVM had a fatal bu
On 9/30/19 12:07 PM, Laura Abbott wrote:
Hi,
Fedora got a bug report https://bugzilla.redhat.com/show_bug.cgi?id=1757104
of a failure to parse options with the context mount option. From the reporter:
$ unshare -rm mount -t tmpfs tmpfs /tmp -o
'context="system_u:object_r:container_file_t:s0:c
On 10/6/19 3:49 AM, Zhenzhong Duan wrote:
> On 2019/10/4 22:52, Boris Ostrovsky wrote:
>
>> On 10/3/19 10:02 AM, Zhenzhong Duan wrote:
>>> void __init kvm_spinlock_init(void)
>>> {
>>> - /* Does host kernel support KVM_FEATURE_PV_UNHALT? */
>>> - if (!kvm_para_has_feature(KVM_FEATURE_PV_U
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: f67001a4a08eb124197ed4376941e1da9cf94b42
Gitweb:
https://git.kernel.org/tip/f67001a4a08eb124197ed4376941e1da9cf94b42
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 30 Sep 2019 10:55:34 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 6bdfd9f118bd59cf0f85d3bf4b72b586adea17c1
Gitweb:
https://git.kernel.org/tip/6bdfd9f118bd59cf0f85d3bf4b72b586adea17c1
Author:Andi Kleen
AuthorDate:Fri, 27 Sep 2019 16:35:45 -07:00
Committer:
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 28f4417c940b242af03d90214f713bbef232
Gitweb:
https://git.kernel.org/tip/28f4417c940b242af03d90214f713bbef232
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 30 Sep 2019 15:11:47 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 42d7a9107d83223a5fcecc6732d626a6c074cbc2
Gitweb:
https://git.kernel.org/tip/42d7a9107d83223a5fcecc6732d626a6c074cbc2
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 30 Sep 2019 15:48:12 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: b7ad6108484221f431372b94763b74e550d16c93
Gitweb:
https://git.kernel.org/tip/b7ad6108484221f431372b94763b74e550d16c93
Author:Arnaldo Carvalho de Melo
AuthorDate:Fri, 27 Sep 2019 12:18:21 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 16ed3c1e91159e28b02f11f71ff4ce4cbc6f99e4
Gitweb:
https://git.kernel.org/tip/16ed3c1e91159e28b02f11f71ff4ce4cbc6f99e4
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 30 Sep 2019 15:53:33 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: b59711e9b0d22fd47abfa00602fd8c365cdd3ab7
Gitweb:
https://git.kernel.org/tip/b59711e9b0d22fd47abfa00602fd8c365cdd3ab7
Author:Steve MacLean
AuthorDate:Sat, 28 Sep 2019 01:41:18
Committer:
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 61e5ddca9c2a312f933bf5b12bc08484189fefe6
Gitweb:
https://git.kernel.org/tip/61e5ddca9c2a312f933bf5b12bc08484189fefe6
Author:Mike Travis
AuthorDate:Tue, 10 Sep 2019 09:58:40 -05:00
Committe
On Mon, Oct 07, 2019 at 05:53:55AM -0700, Guenter Roeck wrote:
> On 10/6/19 10:18 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.4.196 release.
> > There are 36 patches in this series, all will be posted as a response
> > to this one. If anyone has any iss
* Alexander Shishkin wrote:
> Commit
>
> b43762ef010 ("perf: Allow normal events to output AUX data")
Missing 'a', the proper SHA1 is:
ab43762ef010 ("perf: Allow normal events to output AUX data")
:-)
> forgets to configure aux_output relation in the inherited groups, which
> results
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: e3e2cf3d5b1fe800b032e14c0fdcd9a6fb20cf3b
Gitweb:
https://git.kernel.org/tip/e3e2cf3d5b1fe800b032e14c0fdcd9a6fb20cf3b
Author:Ian Rogers
AuthorDate:Wed, 25 Sep 2019 12:59:24 -07:00
Committer:
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 11aad897f6d1a28eae3b7e5b293647c522d65819
Gitweb:
https://git.kernel.org/tip/11aad897f6d1a28eae3b7e5b293647c522d65819
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 30 Sep 2019 16:04:21 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 0d0e5ecec6116db6031829299e74cc71240c9ff3
Gitweb:
https://git.kernel.org/tip/0d0e5ecec6116db6031829299e74cc71240c9ff3
Author:Thomas Richter
AuthorDate:Fri, 27 Sep 2019 10:11:47 +02:00
Commit
On Sat, Oct 05, 2019 at 06:44:08PM +0200, Borislav Petkov wrote:
> On Tue, Sep 03, 2019 at 05:26:40PM +0300, Jarkko Sakkinen wrote:
> > +/**
> > + * __sgx_free_page - Free an EPC page
> > + * @page: pointer a previously allocated EPC page
> > + *
> > + * EREMOVE an EPC page and insert it back to t
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: ee008a19f1c72c37ffa54326a592035dddb66fd6
Gitweb:
https://git.kernel.org/tip/ee008a19f1c72c37ffa54326a592035dddb66fd6
Author:Hans de Goede
AuthorDate:Mon, 07 Oct 2019 15:47:24 +02:00
Committe
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 8785968bce1cc7368ea95c3e1e5b9210f56f6667
Gitweb:
https://git.kernel.org/tip/8785968bce1cc7368ea95c3e1e5b9210f56f6667
Author:Mike Travis
AuthorDate:Tue, 10 Sep 2019 09:58:44 -05:00
Committe
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 9743cb68f736d986481edba4d00de454d2faa0ec
Gitweb:
https://git.kernel.org/tip/9743cb68f736d986481edba4d00de454d2faa0ec
Author:Mike Travis
AuthorDate:Tue, 10 Sep 2019 09:58:42 -05:00
Committe
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: ee212d6ea20887c0ef352be8563ca13dbf965906
Gitweb:
https://git.kernel.org/tip/ee212d6ea20887c0ef352be8563ca13dbf965906
Author:Steve MacLean
AuthorDate:Sat, 28 Sep 2019 01:39:00
Committer:
[Cc s390 maintainers - the lockdep is
http://lkml.kernel.org/r/1570228005-24979-1-git-send-email-...@lca.pw
Petr has explained it is a false positive
http://lkml.kernel.org/r/20191007143002.l37bt2lzqtnqj...@pathway.suse.cz]
On Mon 07-10-19 16:30:02, Petr Mladek wrote:
[...]
> I believe that it c
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 2657983b4c0d81632c6a73bae469951b0d341251
Gitweb:
https://git.kernel.org/tip/2657983b4c0d81632c6a73bae469951b0d341251
Author:Steve MacLean
AuthorDate:Sat, 28 Sep 2019 01:53:08
Committer:
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 2bcf26528787d92333ed0dfd6abc9835b8e97eab
Gitweb:
https://git.kernel.org/tip/2bcf26528787d92333ed0dfd6abc9835b8e97eab
Author:Mike Travis
AuthorDate:Tue, 10 Sep 2019 09:58:43 -05:00
Committe
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: f5a8f0ecb436a15f50215f27ab70a2e8626a6135
Gitweb:
https://git.kernel.org/tip/f5a8f0ecb436a15f50215f27ab70a2e8626a6135
Author:Mike Travis
AuthorDate:Tue, 10 Sep 2019 09:58:45 -05:00
Committe
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 4fb7d08707565d27ec84a364d011043ade8c38b4
Gitweb:
https://git.kernel.org/tip/4fb7d08707565d27ec84a364d011043ade8c38b4
Author:Mike Travis
AuthorDate:Tue, 10 Sep 2019 09:58:47 -05:00
Committe
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 4b0b2b096da9d296e0e5668cdfba8613bd6f5bc8
Gitweb:
https://git.kernel.org/tip/4b0b2b096da9d296e0e5668cdfba8613bd6f5bc8
Author:Ian Rogers
AuthorDate:Wed, 25 Sep 2019 12:59:23 -07:00
Committer:
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: d586ac10ce56b2381b8e1d8ed74660c1b2b8ab0d
Gitweb:
https://git.kernel.org/tip/d586ac10ce56b2381b8e1d8ed74660c1b2b8ab0d
Author:Ian Rogers
AuthorDate:Fri, 20 Sep 2019 21:13:27 -07:00
Committer:
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 0959f8256ada0431c1470d89e5a2811ff2305c88
Gitweb:
https://git.kernel.org/tip/0959f8256ada0431c1470d89e5a2811ff2305c88
Author:Mike Travis
AuthorDate:Tue, 10 Sep 2019 09:58:41 -05:00
Committe
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 7d4c85b7035eb2f9ab217ce649dcd1bfaf0cacd3
Gitweb:
https://git.kernel.org/tip/7d4c85b7035eb2f9ab217ce649dcd1bfaf0cacd3
Author:Ian Rogers
AuthorDate:Thu, 26 Sep 2019 15:00:18 -07:00
Committer:
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: df55029f7ea65d8c653a79dd728918dfe25b1356
Gitweb:
https://git.kernel.org/tip/df55029f7ea65d8c653a79dd728918dfe25b1356
Author:Mike Travis
AuthorDate:Tue, 10 Sep 2019 09:58:46 -05:00
Committe
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 08a96a31474a732fd654575ced843b94bc3212e1
Gitweb:
https://git.kernel.org/tip/08a96a31474a732fd654575ced843b94bc3212e1
Author:Arnaldo Carvalho de Melo
AuthorDate:Fri, 27 Sep 2019 09:28:11 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 02d084792273e8a5f1813dcad988229a45be96ea
Gitweb:
https://git.kernel.org/tip/02d084792273e8a5f1813dcad988229a45be96ea
Author:Thomas Richter
AuthorDate:Fri, 27 Sep 2019 10:11:46 +02:00
Commit
The following commit has been merged into the efi/urgent branch of tip:
Commit-ID: c05f8f92b701576b615f30aac31fabdc0648649b
Gitweb:
https://git.kernel.org/tip/c05f8f92b701576b615f30aac31fabdc0648649b
Author:Ard Biesheuvel
AuthorDate:Wed, 02 Oct 2019 18:58:59 +02:00
Committ
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 05f371f8c55d69e4c04db4473085303291e4e734
Gitweb:
https://git.kernel.org/tip/05f371f8c55d69e4c04db4473085303291e4e734
Author:Arnaldo Carvalho de Melo
AuthorDate:Fri, 27 Sep 2019 11:42:26 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 211f493b611eef012841f795166c38ec7528738d
Gitweb:
https://git.kernel.org/tip/211f493b611eef012841f795166c38ec7528738d
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 30 Sep 2019 15:44:13 -03
The following commit has been merged into the efi/urgent branch of tip:
Commit-ID: e658c82be5561412c5e83b5e74e9da4830593f3e
Gitweb:
https://git.kernel.org/tip/e658c82be5561412c5e83b5e74e9da4830593f3e
Author:Jerry Snitselaar
AuthorDate:Wed, 02 Oct 2019 18:59:02 +02:00
Commi
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 0ae4061223a3d097222cbec6599370e54db17731
Gitweb:
https://git.kernel.org/tip/0ae4061223a3d097222cbec6599370e54db17731
Author:Arnaldo Carvalho de Melo
AuthorDate:Fri, 27 Sep 2019 12:01:26 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: b1ba55cf1cfb9f3e0e00d743534684a25bf66d28
Gitweb:
https://git.kernel.org/tip/b1ba55cf1cfb9f3e0e00d743534684a25bf66d28
Author:Arnaldo Carvalho de Melo
AuthorDate:Fri, 27 Sep 2019 11:30:30 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: e98df280bc2a499fd41d7f9e2d6733884de69902
Gitweb:
https://git.kernel.org/tip/e98df280bc2a499fd41d7f9e2d6733884de69902
Author:Andi Kleen
AuthorDate:Fri, 27 Sep 2019 16:35:44 -07:00
Committer:
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: a66fa0619a0ae3585ef09e9c33ecfb5c7c6cb72b
Gitweb:
https://git.kernel.org/tip/a66fa0619a0ae3585ef09e9c33ecfb5c7c6cb72b
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 30 Sep 2019 15:06:01 -03
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 9db0e3635fb35b6695275774ab909c51221b66ad
Gitweb:
https://git.kernel.org/tip/9db0e3635fb35b6695275774ab909c51221b66ad
Author:Arnaldo Carvalho de Melo
AuthorDate:Mon, 30 Sep 2019 11:48:32 -03
Hi Linus,
On 10/5/19 6:49 PM, Linus Walleij wrote:
On Fri, Oct 4, 2019 at 2:29 PM Amelie Delaunay
wrote:
When an STMFX IO is used as interrupt through the interrupt-controller
binding, the STMFX driver should configure this IO as input. Default
value of STMFX IO direction is input, but if th
* Jonathan Cameron wrote:
> Done in a somewhat different fashion to arm64.
> Here the infrastructure for memoryless domains was already
> in place. That infrastruture applies just as well to
> domains that also don't have a CPU, hence it works for
> Generic Initiator Domains.
>
> In common wi
Em seg, 7 de out de 2019 às 11:15, Julian Wiedmann
escreveu:
>
> On 06.10.19 20:45, jcfara...@gmail.com wrote:
> > From: Julio Faracco
> >
> > For debug purpose of TX timeout events, a tx_timeout entry was added to
> > monitor this special case: when dev_watchdog identifies a tx_timeout and
> >
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: f733c6b508bcaa3441ba1eacf16efb9abd47489f
Gitweb:
https://git.kernel.org/tip/f733c6b508bcaa3441ba1eacf16efb9abd47489f
Author:Alexander Shishkin
AuthorDate:Fri, 04 Oct 2019 15:57:29 +03:00
Co
> -Original Message-
> From: Kuldeep Singh
> Sent: Tuesday, October 1, 2019 3:59 AM
> To: Han Xu ; broo...@kernel.org; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Cc: Kuldeep Singh ; Suresh Gupta
>
> Subject: [PATCH] spi: spi-fsl-qspi: Introduce variable to fix differen
On 10/5/19 12:11 AM, Roman Gushchin wrote:
>
> One possible approach to this problem is to switch inodes associated
> with dying wbs to the root wb. Switching is a best effort operation
> which can fail silently, so unfortunately we can't run once over a
> list of associated inodes (even if we'd ha
> -Original Message-
> From: Schrempf Frieder
> Sent: Monday, October 7, 2019 2:23 AM
> To: Han Xu ; Mark Brown
> Cc: Schrempf Frieder ; sta...@vger.kernel.org;
> linux-...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: [EXT] [PATCH] spi: spi-fsl-qspi: Clear TDH bits in FLSHC
Hello,
This patch series aims to bring H.264 support as well as compliance update
to the amlogic stateful video decoder driver.
There is 1 issue that remains currently:
- The following codepath had to be commented out from v4l2-compliance as
it led to stalling:
if (node->codec_mask & STATEFUL_
On Mon, 2019-10-07 at 16:30 +0200, Petr Mladek wrote:
> On Fri 2019-10-04 18:26:45, Qian Cai wrote:
> > It is unsafe to call printk() while zone->lock was held, i.e.,
> >
> > zone->lock --> console_lock
> >
> > because the console could always allocate some memory in different code
> > paths and
Add all the necessary bits to pass v4l2-compliance in stateful decoding
mode.
Mostly includes tracking the state of the decoder, allowing the OUTPUT
queue to stream while the CAPTURE queue is inactive, handling resolution
change events, draining with V4L2_DEC_CMD_STOP, copying more metadata
from t
Add support for the H264 compressed format (V4L2_PIX_FMT_H264).
Signed-off-by: Maxime Jourdan
---
drivers/staging/media/meson/vdec/Makefile | 2 +-
drivers/staging/media/meson/vdec/codec_h264.c | 482 ++
drivers/staging/media/meson/vdec/codec_h264.h | 14 +
.../staging/med
Ingo Molnar writes:
> * Alexander Shishkin wrote:
>
>> Commit
>>
>> b43762ef010 ("perf: Allow normal events to output AUX data")
>
> Missing 'a', the proper SHA1 is:
>
> ab43762ef010 ("perf: Allow normal events to output AUX data")
>
> :-)
Ouch, sorry about that.
> Could this explain we
On 07/10/19 15:26, Vitaly Kuznetsov wrote:
> Because "Untracked files:" are annoying.
>
> Signed-off-by: Vitaly Kuznetsov
> ---
> tools/testing/selftests/kvm/.gitignore | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/.gitignore
> b/tools/testing/selftests
On 07/10/19 15:25, Liang, Kan wrote:
>
>> On 30/09/19 09:22, Like Xu wrote:
>>> -static int perf_event_period(struct perf_event *event, u64 __user *arg)
>>> +static int _perf_event_period(struct perf_event *event, u64 value)
>>
>> __perf_event_period or perf_event_period_locked would be more consi
UNIT_CELL_SIZE is a control that represents the size of a cell (pixel).
We required a bit of boilerplate to add this control :)
- New way to init compount controls
- New control type
Thanks to Hans, Jacopo and Philipp for your help.
You might want to see the series at my github repository if need
From: Ricardo Ribalda Delgado
Currently compound controls do not have a simple way of initializing its
values. This results in ofuscated code with type_ops init.
This patch introduces a new field on the control with the default value
for the compound control that can be set with the brand new
v4
From: Ricardo Ribalda Delgado
Function for initializing compound controls with a default value.
Suggested-by: Hans Verkuil
Reviewed-by: Jacopo Mondi
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/media/kapi/v4l2-controls.rst | 9 +
1 file changed, 9 insertions(+)
diff --gi
This control returns the unit cell size in nanometres. The struct provides
the width and the height in separated fields to take into consideration
asymmetric pixels and/or hardware binning.
This control is required for automatic calibration of sensors/cameras.
Reviewed-by: Philipp Zabel
Signed-of
This helper function simplifies the code by not needing a union
v4l2_ctrl_ptr and an assignment every time we need to use
a ctrl_ptr.
Suggested-by: Hans Verkuil
Signed-off-by: Ricardo Ribalda Delgado
---
include/media/v4l2-ctrls.h | 12
1 file changed, 12 insertions(+)
diff --git
A struct v4l2_area containing the width and the height of a rectangular
area.
Reviewed-by: Jacopo Mondi
Reviewed-by: Philipp Zabel
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/media/uapi/v4l/vidioc-queryctrl.rst | 6 ++
Documentation/media/videodev2.h.rst.exceptions| 1 +
2
New control to pass to userspace the width/height of a pixel. Which is
needed for calibration and lens selection.
Reviewed-by: Philipp Zabel
Signed-off-by: Ricardo Ribalda Delgado
---
.../media/uapi/v4l/ext-ctrls-image-source.rst | 10 ++
1 file changed, 10 insertions(+)
diff
According to the product brief, the unit cell size is 1120 nanometers^2.
https://www.sony-semicon.co.jp/products_en/IS/sensor1/img/products/ProductBrief_IMX214_20150428.pdf
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/i2c/imx214.c | 9 +
1 file changed, 9 insertions(+)
diff
From: Ricardo Ribalda Delgado
This type contains the width and the height of a rectangular area.
Reviewed-by: Jacopo Mondi
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/v4l2-ctrls.c | 21 ++
include/media/v4l2-ctrls.h | 42 +++
A few NULL pointer checks were missing.
Add check with appropriate return code.
Signed-off-by: Benoit Parrot
---
drivers/media/platform/ti-vpe/vpe.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/ti-vpe/vpe.c
b/drivers/media/platform/ti-
v4l2-compliance fails with this message:
warn: v4l2-test-formats.cpp(717): \
TRY_FMT cannot handle an invalid pixelformat.
test VIDIOC_TRY_FMT: FAIL
This causes the following kernel panic:
Unable to handle kernel paging request at virtual address 56595561
pgd = ecd80e00
*pgd=00
From: Ram Prasad
VPE's max height supported MAX_H is set to 1184 which is the
padded height from VC1 decoder output.
In case of 90, 270 degree rotated video processing, input to
VPE will be 1080x1920, 720x1280 etc and MAX_H needs to be set
correct value. Setting MAX_H to 2048 as worst case heigh
Using dma_addr_t as the type to hold address inside of a fix sized
descriptor used by the vpdma firmware is prone to fail when the expected
width is 32 bits and suddenly when CONFIG_LPAE is enabled the data size
is now 64 bits shifted the remaining members of the descriptor in memory
which confuses
v4l2-compliance fails with this message:
fail: v4l2-test-formats.cpp(463): !pfmt.sizeimage
fail: v4l2-test-formats.cpp(736): \
Video Capture Multiplanar is valid, \
but TRY_FMT failed to return a format
test VIDIOC_TRY_FMT: FAIL
This failure is causd by the driver failing
From: Nikhil Devshatwar
In NV21 format, the chroma plane is written to memory such that the U
and V components are swapped for NV12.
Create a new entry in the VPDMA formats to describe the correct data
types used in the data descriptors.
Update all checks for NV12 and add NV21 there as well.
A
commit 52831a418fa6 ("[media] media: ti-vpe: vpe: allow use of user
specified stride") and commit 8c1e4fa17e92 ("[media] media: ti-vpe: vpdma:
add support for user specified stride") resulted in the Motion Vector
stride to be the same as the image stride.
This caused memory corruption in the outpu
v4l2-compliance fails with this message:
fail: v4l2-test-buffers.cpp(294): \
(int)g_sequence() < seq.last_seq + 1
fail: v4l2-test-buffers.cpp(740): \
buf.check(m2m_q, last_m2m_seq)
fail: v4l2-test-buffers.cpp(974): \
captureBufs(node, q, m2m_q, frame_count, true)
VPE uses VPDMA (built-in dma engine) to transfer data to and from the IP
and memory. VPDMA expect 32 bits addresses. To make sure that is always
the case set the DMA mask and coherent mask for the device.
Signed-off-by: Benoit Parrot
---
drivers/media/platform/ti-vpe/vpe.c | 7 +++
1 file ch
Add RGB565 and RGB555 to the v4l2_format_info table.
Signed-off-by: Benoit Parrot
---
drivers/media/v4l2-core/v4l2-common.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/media/v4l2-core/v4l2-common.c
b/drivers/media/v4l2-core/v4l2-common.c
index 09a3915b98a3..d0e5ebc736f9 100644
v4l2-compliance fails with this message:
fail: v4l2-test-buffers.cpp(691): ret == 0
fail: v4l2-test-buffers.cpp(974): captureBufs(node, q, m2m_q,
frame_count, true)
test MMAP: FAIL
This caused the following Kernel Warning:
WARNING: CPU: 0 PID: 961 at
drivers/media/v4l2-core/videobuf2-co
On Mon, 7 Oct 2019 14:55:19 +0200
Ingo Molnar wrote:
> * Peter Zijlstra wrote:
>
> > IIRC the recordmcount variant from Steve was also rewriting JMP8 to NOP2
> > at build time.
> >
> > I dug this here link out of my IRC logs:
> >
> >
> > https://lore.kernel.org/lkml/1318007374.4729.58.ca...
Up to now VPE was relying on the colorspace value of struct v4l2_format
as an indication to perform color space conversion from YUV to RGB or
not.
Instead we should used the source/destination fourcc codes as a more
reliable indication to perform color space conversion or not.
To do so, we rework
It is often useful to figure out if a pixel_format is either YUV or RGB
especially for driver who can perform the pixel encoding conversion.
Instead of having each driver implement its own "is_this_yuv/rgb"
function based on a restricted set of pixel value, it is better to do
this in centralized m
The RGB to YUV HD full range coefficients did not match the TRM values
and appeared to be a cut-n-paste from the YUV to RGB section.
Replace the entries with the values from the TRM.
Signed-off-by: Benoit Parrot
---
drivers/media/platform/ti-vpe/csc.c | 4 ++--
1 file changed, 2 insertions(+),
All 4 of the "colorspace" components were not originally handled.
Causing issue related to xfer_func not being initialized properly.
This was found with v4l2-compliance test.
Signed-off-by: Benoit Parrot
---
drivers/media/platform/ti-vpe/vpe.c | 5 -
1 file changed, 4 insertions(+), 1 delet
For each queue we need to maintain resolutions, pixel format,
bytesperline, sizeimage, colorspace, etc.
Instead of manually adding more entries in the vpe_q_data struct, it is
better to just add a "struct v4l2_format" member and use that to store
all needed information.
Signed-off-by: Benoit Parr
On Thu, Sep 19, 2019 at 04:06:16PM +0200, Rasmus Villemoes wrote:
> The "break-even" point for the two formulas is L==8, which is also
> what the code actually implements. [Incidentally, at that point one
> has Y=0.008856, not 0.08856].
>
> Moreover, all the sources I can find say the linear facto
v4l2-compliance warns with this message:
warn: v4l2-test-formats.cpp(717): \
TRY_FMT cannot handle an invalid pixelformat.
warn: v4l2-test-formats.cpp(718): \
This may or may not be a problem. For more information see:
warn: v4l2-test-formats.cpp(719): \
http://www
901 - 1000 of 1238 matches
Mail list logo