device_initcall() is too late for bcm63xx.
We need to call of_clk_init() earlier in order to properly boot.
Signed-off-by: Álvaro Fernández Rojas
---
arch/mips/bmips/setup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/bmips/setup.c b/arch/mips/bmips/setup.c
On 2/22/2021 10:31 AM, Mickaël Salaün wrote:
> On 22/02/2021 17:51, Casey Schaufler wrote:
>> On 2/22/2021 7:06 AM, Mickaël Salaün wrote:
>>> From: Mickaël Salaün
>>>
>>> Add a new option CONFIG_LSM_AUTO to enable users to delegate default LSM
>>> stacking order to kernel developers. This enable
On 2/22/21 12:58 PM, Saulo Alessandre wrote:
From: Saulo Alessandre
* crypto/asymmetric_keys/x509_cert_parser.c
- prepare x509 parser to load nist_secp384r1
* crypto/ecc_curve_defs.h
- add nist_p384 params
* include/crypto/ecdh.h
- add ECC_CURVE_NIST_P384
*
On Mon, Feb 22, 2021 at 10:52:09AM -0800, Linus Torvalds wrote:
> On Mon, Feb 22, 2021 at 9:35 AM Rob Herring wrote:
> >
> > Please pull DT updates for v5.12.
>
> Ugh.
>
> This causes "git status" to be unhappy, because there's a new
> generated file (scripts/dtc/fdtoverlay) without a gitignore
Hi,
On Fri, Jan 29, 2021 at 11:08 AM Sai Prakash Ranjan
wrote:
>
> @@ -1202,6 +1207,13 @@ void etm4_config_trace_mode(struct etmv4_config
> *config)
> /* excluding kernel AND user space doesn't make sense */
> WARN_ON_ONCE(mode == (ETM_MODE_EXCL_KERN | ETM_MODE_EXCL_USER));
>
>
On Wed, Feb 03, 2021 at 09:26:43PM -0800, Atish Patra wrote:
> SBI v0.2 functions can return an error code from SBI implementation.
> We are already processing the SBI error code and coverts it to the Linux
> error code.
>
> Propagate to the error code to the caller as well. As of now, kvm is the
Quoting Matthias Kaehlcke (2021-02-19 18:10:59)
> Lazor rev3 and older are stuffed with a 47k NTC as thermistor for
> the charger temperature which currently isn't supported by the
> PM6150 ADC driver. Delete the charger thermal zone and ADC channel
> to avoid the use of bogus temperature values.
Hamming ECC doesn't cover the OOB data, so reading or writing OOB shall
always be done without ECC enabled.
This is a problem when adding JFFS2 cleanmarkers to erased blocks. If JFFS2
clenmarkers are added to the OOB with ECC enabled, OOB bytes will be changed
from ff ff ff to 00 00 00, reporting
Le lundi 22 février 2021 à 17:28 +0100, Benjamin Gaignard a écrit :
>
> Le 22/02/2021 à 17:16, John Cox a écrit :
> > > The HEVC HANTRO driver needs to know the number of bits to skip at
> > > the beginning of the slice header.
> > > That is a hardware specific requirement so create a dedicated
Some BCM6358 devices start with Core #1 instead of Core #0.
Apart from that, SMP is restricted to 1 CPU since BCM6358 has a shared TLB,
which makes it impossible for the current SMP support to start both CPUs.
The problem is that smp_processor_id() returns 0 and then cpu_logical_map()
converts
Quoting Douglas Anderson (2021-02-18 14:55:09)
> At boot time the following happens:
> 1. Device core gets ready to probe our SPI driver.
> 2. Device core applies SPI controller's "default" pinctrl.
> 3. Device core calls the SPI driver's probe() function which will
>eventually setup the chip
On Mon, 2021-02-22 at 17:28 +0100, Benjamin Gaignard wrote:
>
> Le 22/02/2021 à 17:16, John Cox a écrit :
> > > The HEVC HANTRO driver needs to know the number of bits to skip at
> > > the beginning of the slice header.
> > > That is a hardware specific requirement so create a dedicated control
>
>From QPIC version 2.0 onwards new register got added to read last
codeword. This change will add the READ_LOCATION_LAST_CW_n register.
For first three code word READ_LOCATION_n register will be
use.For last code word READ_LOCATION_LAST_CW_n register will be
use.
Signed-off-by: Md Sadre Alam
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any
issue:
Reported-and-tested-by: syzbot+429d3f82d757c211b...@syzkaller.appspotmail.com
Tested on:
commit: 2b31ee47 nbd: handle device refs for DESTROY_ON_DISCONNECT..
git tree:
bcm7038_wdt can be used on bmips (bcm63xx) devices too.
Signed-off-by: Álvaro Fernández Rojas
---
drivers/watchdog/bcm7038_wdt.c | 30 --
1 file changed, 24 insertions(+), 6 deletions(-)
diff --git a/drivers/watchdog/bcm7038_wdt.c b/drivers/watchdog/bcm7038_wdt.c
Hi John,
Le lundi 22 février 2021 à 17:39 +0100, Benjamin Gaignard a écrit :
>
> Le 22/02/2021 à 17:24, John Cox a écrit :
> > > The H.265 ITU specification (section 7.4) define the general
> > > slice segment header semantics.
> > > Modified/added fields are:
> > > - video_parameter_set_id:
config: powerpc64-randconfig-r014-20210222 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project
c9439ca36342fb6013187d0a69aef92736951476)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
Hi!
> From: Stefano Garzarella
>
> commit cf1a3b35382c10ce315c32bd2b3d7789897fbe13 upstream.
>
> As preparation for the next patches, we store the MAC address,
> parsed during the vdpasim_create(), in a buffer that will be used
> to fill 'config' together with other configurations.
I'm not
This allows devices without a high precission timer to speed up boot from
more than 100s to lest than 30s.
BCM2835 rngtest:
root@OpenWrt:/# cat /dev/hwrng | rngtest -c 1000
rngtest 6.10
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions.
On 2/22/21 11:09 AM, Michal Hocko wrote:
>>
>> I actually have tried adjusting the threshold but found that it doesn't work
>> well for
>> the case with unenven memory access frequency between cgroups. The soft
>> limit for the low memory event cgroup could creep up quite a lot, exceeding
>>
Hi Sharath,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net-next/master]
url:
https://github.com/0day-ci/linux/commits/Sharath-Chandra-Vurukala/net-qualcomm-rmnet-Enable-Mapv5/20210223-010109
base:
Hi Kishon,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on linus/master v5.11 next-20210222]
[cannot apply to phy/next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest
BCM6368 devices need to reset the in order to generate true random numbers.
This is what BCM6368 produces without a reset:
root@OpenWrt:/# cat /dev/hwrng | rngtest -c 1000
rngtest 6.10
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions.
This driver is missing module_exit hook. Add proper driver exit function
which unregisters the platform device and cleans up the data.
Signed-off-by: Pali Rohár
Tested-by: Tomasz Maciej Nowak
Tested-by: Anders Trier Olesen
Tested-by: Philip Soares
---
drivers/cpufreq/armada-37xx-cpufreq.c |
When current CPU load is not L0 then loading armada-37xx-cpufreq.ko driver
fails with following error:
# modprobe armada-37xx-cpufreq
[ 502.702097] Unsupported CPU frequency 250 MHz
This issue was partially fixed by commit 8db82563451f ("cpufreq:
armada-37xx: fix frequency calculation
Commit 8db82563451f ("cpufreq: armada-37xx: fix frequency calculation for
opp") changed calculation of frequency passed to the dev_pm_opp_add()
function call. But the code for dev_pm_opp_remove() function call was not
updated, so the driver cleanup phase does not work when registration fails.
When CPU frequency is at 250 MHz and set_rate() is called with 500 MHz (L1)
quickly followed by a call with 1 GHz (L0), the CPU does not necessarily
stay in L1 for at least 20ms as is required by Marvell errata.
This situation happens frequently with the ondemand cpufreq governor and
can be also
Variable cur_frequency in armada37xx_cpufreq_driver_init() is unused.
Signed-off-by: Pali Rohár
Tested-by: Tomasz Maciej Nowak
Tested-by: Anders Trier Olesen
Tested-by: Philip Soares
---
drivers/cpufreq/armada-37xx-cpufreq.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
It was observed that the workaround introduced by commit 61c40f35f5cd
("clk: mvebu: armada-37xx-periph: Fix switching CPU rate from 300Mhz to
1.2GHz") when base CPU frequency is 1.2 GHz is also required when base
CPU frequency is 1 GHz. Otherwise switching CPU frequency directly from
L2 (250 MHz)
From: Marek Behún
Remove the .set_parent method in clk_pm_cpu_ops.
This method was supposed to be needed by the armada-37xx-cpufreq driver,
but was never actually called due to wrong assumptions in the cpufreq
driver. After this was fixed in the cpufreq driver, this method is not
needed
From: Marek Behún
With CPU frequency determining software [1] we have discovered that
after this driver does one CPU frequency change, the base frequency of
the CPU is set to the frequency of TBG-A-P clock, instead of the TBG
that is parent to the CPU.
This can be reproduced on EspressoBIN and
The original CPU voltage value for load L1 is too low for Armada 37xx SoC
when base CPU frequency is 1000 or 1200 MHz. It leads to instabilities
where CPU gets stuck soon after dynamic voltage scaling from load L1 to L0.
Update the CPU voltage value for load L1 accordingly when base frequency is
Hello!
This is third version of patches for Armada 37xx cpufreq driver which
fix CPU scaling with 1 GHz base frequency.
The only change in this third version is modified patch 04/10 with fixes
for 1.2 GHz variant of Espressobin. Minimal CPU voltage in L1 load for
1.2 GHz variant was increased to
fixing ERROR: "foo * bar" should be "foo *bar"
fixing WARNING: Missing a blank line after declarations
Signed-off-by: Rajesh Kumbhakar
---
sound/core/hwdep_compat.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/sound/core/hwdep_compat.c b/sound/core/hwdep_compat.c
index
From: Marek Behún
Add "syscon" compatible to the North Bridge clocks node to allow the
cpufreq driver to access these registers via syscon API.
This is needed for a fix of cpufreq driver.
Signed-off-by: Marek Behún
Tested-by: Pali Rohár
Tested-by: Tomasz Maciej Nowak
Tested-by: Anders Trier
On Mon, 22 Feb 2021 at 17:43, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.11.1 release.
> There are 12 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.
>
>
On Tue, Feb 23, 2021 at 01:01:16AM +0530, Naresh Kamboju wrote:
> Following test regressions reported after upgrade to clang-12 from clang-10.
> Regression detected on Linux mainline and stable-rc 5.4, 5.10 and 5.11.
>
> qemu-x86_64-clang-12 failed test cases,
> ltp-containers-tests:
> *
On 2/5/21 2:13 AM, Yang Yang wrote:
> Hang occurs when user changes the scheduler queue depth, by writing to
> the 'nr_requests' sysfs file of that device.
>
> The details of the environment that we found the problem are as follows:
> an eMMC block device
> total driver tags: 16
> default
On Fri, Feb 05, 2021 at 01:13:10AM -0800, Yang Yang wrote:
> Hang occurs when user changes the scheduler queue depth, by writing to
> the 'nr_requests' sysfs file of that device.
>
> The details of the environment that we found the problem are as follows:
> an eMMC block device
> total driver
On 16/02/2021 03.09, Marc Zyngier wrote:
On Mon, 15 Feb 2021 12:17:03 +,
Hector Martin wrote:
This patch introduces basic UP irqchip support, without SMP/IPI support.
This last comment seems outdated now.
Heh, I forgot to reword this one. Thanks :)
+config APPLE_AIC
+ bool
Following test regressions reported after upgrade to clang-12 from clang-10.
Regression detected on Linux mainline and stable-rc 5.4, 5.10 and 5.11.
qemu-x86_64-clang-12 failed test cases,
ltp-containers-tests:
* netns_breakns_ip_ipv4_ioctl
* netns_breakns_ip_ipv4_netlink
*
On Sat, Feb 20, 2021 at 05:10:18PM +0800, Yang Li wrote:
> fixed the following coccicheck:
> ./drivers/nvme/host/core.c:3440:60-61: WARNING opportunity for
> kobj_to_dev()
> ./drivers/nvme/host/core.c:3679:60-61: WARNING opportunity for
> kobj_to_dev()
>
> Reported-by: Abaci Robot
>
> @@ -7447,8 +7452,14 @@ static int ufs_get_device_desc(struct ufs_hba *hba)
>
> if (dev_info->wspecversion >= UFS_DEV_HPB_SUPPORT_VERSION &&
> (b_ufs_feature_sup & UFS_DEV_HPB_SUPPORT)) {
> - dev_info->hpb_enabled = true;
> -
>> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:9804:38:
>> warning: variable 'i' is uninitialized when used here
>> [-Wuninitialized]
timing = >detailed_timings[i];
^
On 2021-02-20 1:30 a.m., ZhiJie.Zhang wrote:
Signed-off-by: ZhiJie.Zhang
---
drivers/gpu/drm/amd/display/dc/core/dc_stream.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
b/drivers/gpu/drm/amd/display/dc/core/dc_stream.c
index
On 2/22/21 11:09 AM, Michal Hocko wrote:
> On Mon 22-02-21 09:41:00, Tim Chen wrote:
>>
>>
>> On 2/22/21 12:40 AM, Michal Hocko wrote:
>>> On Fri 19-02-21 10:59:05, Tim Chen wrote:
>> occurrence.
>
> Soft limit is evaluated every THRESHOLDS_EVENTS_TARGET *
>
On Mon, Feb 22, 2021 at 07:12:29PM +, Al Viro wrote:
> On Mon, Feb 22, 2021 at 07:06:00PM +, Al Viro wrote:
> > On Sat, Feb 20, 2021 at 09:08:56PM +, Al Viro wrote:
> >
> > > *shrug*
> > >
> > > If anything, __unix_complete_bind() might make a better name for that,
> > > with
On Mon, 2021-02-22 at 11:17 -0800, Dan Williams wrote:
> On Mon, Feb 22, 2021 at 2:24 AM Mike Rapoport
> wrote:
> > On Mon, Feb 22, 2021 at 07:34:52AM +, Matthew Garrett wrote:
> > > On Mon, Feb 08, 2021 at 10:49:18AM +0200, Mike Rapoport wrote:
> > >
> > > > It is unsafe to allow saving of
Linus,
please pull the latest timers/urgent branch from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-2021-02-22
up to: 8acb54abc1db: Merge tag 'timers-v5.11-rc5' of
https://git.linaro.org/people/daniel.lezcano/linux into timers/urgent
A small set of clockevent
On Mon, Feb 22, 2021 at 2:24 AM Mike Rapoport wrote:
>
> On Mon, Feb 22, 2021 at 07:34:52AM +, Matthew Garrett wrote:
> > On Mon, Feb 08, 2021 at 10:49:18AM +0200, Mike Rapoport wrote:
> >
> > > It is unsafe to allow saving of secretmem areas to the hibernation
> > > snapshot as they would be
On Mon, 22 Feb 2021 at 00:47, Adrien Grassein wrote:
>
> Le sam. 20 févr. 2021 à 20:19, Krzysztof Kozlowski a écrit :
> >
> > On Fri, Feb 19, 2021 at 03:03:55PM +0100, Adrien Grassein wrote:
> > > Le ven. 19 févr. 2021 à 14:18, Krzysztof Kozlowski a
> > > écrit :
> > > >
> > > > On Wed, Feb
The pull request you sent on Mon, 22 Feb 2021 15:27:52 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/livepatching/livepatching.git
> tags/livepatching-for-5.12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/54ab35d6bbc0d3175b0a74282c3365c80a43a93c
Thank
The pull request you sent on Wed, 17 Feb 2021 17:10:51 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-kunit-5.12-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/783955f03de770e94a1200b8f719975f8768e76c
Thank
The pull request you sent on Mon, 22 Feb 2021 17:24:24 +:
> git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git/
> tags/kgdb-5.12-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/899cbb0e53c6b66c3fb98d8745aa4b0b41cd94f2
Thank you!
--
The pull request you sent on Wed, 17 Feb 2021 16:39:47 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
> tags/linux-kselftest-next-5.12-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/80215095cefefa3bebf6e57971d0f1211e17153e
Thank
On Mon, Feb 22, 2021 at 11:02:34AM -0800, Nick Desaulniers wrote:
> Did this happen to get picked up already? EOM
I have not gotten an email saying it has been picked up nor does it
appear to be in -next.
Cheers,
Nathan
> On Thu, Feb 11, 2021 at 11:43 AM Nathan Chancellor wrote:
> >
> >
The pull request you sent on Mon, 22 Feb 2021 14:35:08 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git
> tags/printk-for-5.12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b2bec7d8a42a3885d525e821d9354b6b08fd6adf
Thank you!
--
Signed-off-by: Al Viro
---
net/unix/af_unix.c | 39 +++
1 file changed, 15 insertions(+), 24 deletions(-)
diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
index 56443f05ed9d..5e04e16e6b88 100644
--- a/net/unix/af_unix.c
+++ b/net/unix/af_unix.c
@@ -983,45
unix_bind_bsd() and unix_bind_abstract() respectively.
Signed-off-by: Al Viro
---
net/unix/af_unix.c | 147 +++--
1 file changed, 74 insertions(+), 73 deletions(-)
diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
index
We only care about exclusive or of those, so pass that directly.
Makes life simpler for callers as well...
Signed-off-by: Al Viro
---
net/unix/af_unix.c | 23 ++-
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
index
Duplicated logics in all bind variants (autobind, bind-to-path,
bind-to-abstract) gets taken into a common helper.
Signed-off-by: Al Viro
---
net/unix/af_unix.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/net/unix/af_unix.c
On Mon, Feb 22, 2021 at 07:06:00PM +, Al Viro wrote:
> On Sat, Feb 20, 2021 at 09:08:56PM +, Al Viro wrote:
>
> > *shrug*
> >
> > If anything, __unix_complete_bind() might make a better name for that,
> > with dropping ->bindlock also pulled in, but TBH I don't have sufficiently
> >
Hi Linus,
On 22/02/2021 18:44, Linus Torvalds wrote:
> On Fri, Feb 19, 2021 at 3:54 AM Daniel Lezcano
> wrote:
>>
>> Note a set of changes for the qcom adc driver rely on an immutable
>> branch from the iio tree:
>
> That part is fine, but what _isn't_ great is the merge commit message.
>
>
Final preparations for doing unlink on failure past the successful
mknod. We can't hold ->bindlock over ->mknod() or ->unlink(), since
either might do sb_start_write() (e.g. on overlayfs). However, we
can do it while holding filesystem and VFS locks - doing
kern_path_create()
We can do that more or less safely, since the parent is
held locked all along. Yes, somebody might observe the
object via dcache, only to have it disappear afterwards,
but there's really no good way to prevent that. It won't
race with other bind(2) or attempts to move the sucker
elsewhere, or
makes it easier to massage; we do pay for that by extra work
(kmalloc+memcpy+kfree) in some error cases, but those are not
on the hot paths anyway.
Signed-off-by: Al Viro
---
net/unix/af_unix.c | 28 +++-
1 file changed, 15 insertions(+), 13 deletions(-)
diff --git
From: Mirela Rabulea
These are optional in struct v4l2_jpeg_header, so skip DHT/DQT segment
parsing if huffman_tables/quantization_tables were not requested by user,
to save time.
However, do count them (num_dht/num_dqt).
Signed-off-by: Mirela Rabulea
Reviewed-by: Philipp Zabel
---
From: Mirela Rabulea
Use v4l2_jpeg_parse_header in mxc_jpeg_parse, remove the old
parsing way, which was duplicated in other jpeg drivers.
Signed-off-by: Mirela Rabulea
Reviewed-by: Philipp Zabel
---
Changes in v8:
Move the app14_tf fixup in mxc_jpeg_get_image_format() and let this function
We do get some duplication that way, but it's minor compared to
parts that are different. What we get is an ability to change
locking in BSD case without making failure exits very hard to
follow.
Signed-off-by: Al Viro
---
net/unix/af_unix.c | 55
From: Mirela Rabulea
In the case we get an invalid stream, such as from v4l2-compliance
streaming test, jpeg_next_marker will end up parsing the entire
stream. The standard describes the high level syntax of a jpeg
as starting with SOI, ending with EOI, so return error if the very
first 2 bytes
From: Mirela Rabulea
The driver is located in drivers/media/platform/imx-jpeg,
and it applies to the JPEG decoder from i.MX QXP and QM.
Signed-off-by: Mirela Rabulea
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
On Mon 22-02-21 09:41:00, Tim Chen wrote:
>
>
> On 2/22/21 12:40 AM, Michal Hocko wrote:
> > On Fri 19-02-21 10:59:05, Tim Chen wrote:
> occurrence.
> >>>
> >>> Soft limit is evaluated every THRESHOLDS_EVENTS_TARGET *
> >>> SOFTLIMIT_EVENTS_TARGET.
> >>> If all events correspond with a newly
From: Mirela Rabulea
According to Rec. ITU-T T.872 (06/2012) 6.5.3
APP14 segment is for color encoding, it contains a transform flag, which
may have values of 0, 1 and 2 and are interpreted as follows:
0 - CMYK for images that are encoded with four components
- RGB for images that are encoded
From: Mirela Rabulea
Add jpeg decoder/encoder nodes, for now on imx8qxp only.
The same should work on imx8qm, but it was not tested.
Signed-off-by: Mirela Rabulea
---
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 35 ++
1 file changed, 35 insertions(+)
diff --git
From: Mirela Rabulea
V4L2 driver for the JPEG encoder/decoder from i.MX8QXP/i.MX8QM application
processors.
The multi-planar buffers API is used.
Baseline and extended sequential jpeg decoding is supported.
Progressive jpeg decoding is not supported by the IP.
Supports encode and decode of
On Mon, 22 Feb 2021 at 10:09, Heiko Thiery wrote:
> > > > > +
> > > > > + pcie0_refclk: pcie0-refclk {
> > > >
> > > > Generic node names (from the dt spec candidate is "clock").
> > >
> > > Should I simply set the node name to pcie0-clock? And pcie1-clock for
> > > the next one?
> >
> > I am
From: Mirela Rabulea
Add bindings documentation for i.MX8QXP/QM JPEG decoder & encoder driver.
Signed-off-by: Mirela Rabulea
Reviewed-by: Rob Herring
---
.../bindings/media/nxp,imx8-jpeg.yaml | 84 +++
1 file changed, 84 insertions(+)
create mode 100644
From: Mirela Rabulea
The added format is V4L2_PIX_FMT_YUV24, this is a packed
YUV 4:4:4 format, with 8 bits for each component, 24 bits
per sample.
This format is used by the i.MX 8QuadMax and i.MX 8DualXPlus/8QuadXPlus
JPEG encoder/decoder.
Signed-off-by: Mirela Rabulea
Reviewed-by: Paul
This patch set adds the V4L2 driver for i.MX8QXP/QM JPEG encoder/decoder
and it's dependencies.
The driver was tested on i.MX8QXP, using a unit test application and
the v4l2-compliance tool, including the streaming tests for decoder & encoder.
The output of latest v4l2-compliance on i.MX8QXP,
On Mon, Feb 22, 2021 at 10:16:08AM -0800, Paul E. McKenney wrote:
> On Mon, Feb 22, 2021 at 06:16:05PM +0100, Uladzislau Rezki wrote:
> > On Mon, Feb 22, 2021 at 07:09:03AM -0800, Paul E. McKenney wrote:
> > > On Mon, Feb 22, 2021 at 01:54:31PM +0100, Uladzislau Rezki wrote:
> > > > On Mon, Feb
On Sat, Feb 20, 2021 at 09:08:56PM +, Al Viro wrote:
> *shrug*
>
> If anything, __unix_complete_bind() might make a better name for that,
> with dropping ->bindlock also pulled in, but TBH I don't have sufficiently
> strong preferences - might as well leave dropping the lock to caller.
>
>
From: Rafael J. Wysocki
The ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() macros are used for
message printing in the ACPICA code and they should not be used
elsewhere. Special configuration (either kernel command line or
sysfs-based) is needed to see the messages printed by them and
the format of
On Thu, Jan 28, 2021 at 05:09:28PM +, Mike Leach wrote:
> API for individual devices to register with the syscfg management
> system is added.
>
> Devices register with matching information, and any features or
> configurations that match will be loaded into the device.
>
> The feature and
Hi All,
This series replaces ACPI_DEBUG_PRINT() and ACPI_EXCEPTION() in the ACPI
processor driver and sysfs code and drops definitions of related symbols
that are not used for anything meaningful any more.
Please refer to the patch changelogs for details.
Thanks!
Did this happen to get picked up already? EOM
On Thu, Feb 11, 2021 at 11:43 AM Nathan Chancellor wrote:
>
> fw_cfg_showrev() is called by an indirect call in kobj_attr_show(),
> which violates clang's CFI checking because fw_cfg_showrev()'s second
> parameter is 'struct attribute', whereas the
Hi Krzysztof,
Am Mo., 22. Feb. 2021 um 19:39 Uhr schrieb Krzysztof Kozlowski
:
>
> On Mon, 22 Feb 2021 at 10:09, Heiko Thiery wrote:
> > > > > > +
> > > > > > + pcie0_refclk: pcie0-refclk {
> > > > >
> > > > > Generic node names (from the dt spec candidate is "clock").
> > > >
> > > > Should
From: Rafael J. Wysocki
Replace the only ACPI_EXCEPTION() instance in sysfs.c with a
pr_warn() call, drop the _COMPONENT and ACPI_MODULE_NAME()
definitions that are not used any more and drop the
ACPI_SYSTEM_COMPONENT definition that would not be used any
more in a meaningful way after the above
From: Rafael J. Wysocki
Drop the definitions of the following symbols:
ACPI_SBS_COMPONENT
ACPI_FAN_COMPONENT
ACPI_CONTAINER_COMPONENT
ACPI_MEMORY_DEVICE_COMPONENT
that are not used in a meaningful way any more and update the ACPI
debug documentation to avoid confusing users by making the
From: Rafael J. Wysocki
ACPI_MODULE_NAME() is only used by ACPICA message printing which in
turn is not used by the ACPI HED driver, so drop that definition from
there.
No functional impact.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/hed.c |1 -
1 file changed, 1 deletion(-)
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 724c8a23d589d8a002d2e39633c2f9a5a429616f
Gitweb:
https://git.kernel.org/tip/724c8a23d589d8a002d2e39633c2f9a5a429616f
Author:Peter Zijlstra
AuthorDate:Thu, 18 Feb 2021 17:14:10 +01:00
Yilun,
Is there anything outstanding or remaining to be done ?
Tom
On 2/3/21 5:59 PM, Xu Yilun wrote:
> This patchset supports some dfl device drivers written in userspace.
>
> In the patchset v1, the "driver_override" interface should be used to bind
> the DFL UIO driver to DFL devices. But
On Sun, 21 Feb 2021 14:44:26 -0500, Liam Beguin wrote:
> From: Liam Beguin
>
> The LMK04832 is an ultra-high performance clock conditioner with JEDEC
> JESD204B support and is also pin compatible with the LMK0482x family of
> devices.
>
> Signed-off-by: Liam Beguin
> ---
>
Hi,
Am 20.02.21 um 21:01 schrieb Álvaro Fernández Rojas:
> This allows khwrngd to make use of iproc-rng200.
>
> Justification:
> cat /dev/hwrng | rngtest -c 1000
> rngtest 6.10
> Copyright (c) 2004 by Henrique de Moraes Holschuh
> This is free software; see the source for copying conditions.
On Mon, Feb 22, 2021 at 9:35 AM Rob Herring wrote:
>
> Please pull DT updates for v5.12.
Ugh.
This causes "git status" to be unhappy, because there's a new
generated file (scripts/dtc/fdtoverlay) without a gitignore entry.
This was added by commit 79edff12060f ("scripts/dtc: Update to
upstream
On 22.02.2021 17:30:59, Johannes Berg wrote:
> On Mon, 2021-02-22 at 16:12 +0100, Oleksij Rempel wrote:
> > This code is trying to clone the skb with optional skb->sk. But this
> > will fail to clone the skb if socket was closed just after the skb was
> > pushed into the networking stack.
>
>
On 2/17/21 10:40 PM, Lizhi Hou wrote:
> group driver that manages life cycle of a bunch of leaf driver instances
> and bridges them with root.
>
> Signed-off-by: Sonal Santan
> Signed-off-by: Max Zhen
> Signed-off-by: Lizhi Hou
> ---
> drivers/fpga/xrt/include/group.h | 27
>
On Thu, Jan 28, 2021 at 05:09:27PM +, Mike Leach wrote:
> Creates an system management API to allow complex configurations and
> features to be programmed into a CoreSight infrastructure.
>
> A feature is defined as a programming set for a device or class of
> devices.
>
> A configuration is
On Mon, Feb 22, 2021 at 12:40:36PM -0500, Konrad Rzeszutek Wilk wrote:
> On Mon, Feb 22, 2021 at 05:39:29PM +0100, David Hildenbrand wrote:
> > On 22.02.21 17:13, David Hildenbrand wrote:
> > > On 22.02.21 16:13, George Kennedy wrote:
> > > >
> > > >
> > > > On 2/22/2021 4:52 AM, David
On Fri, Feb 19, 2021 at 4:34 PM Johannes Weiner wrote:
>
> On Fri, Feb 19, 2021 at 02:44:05PM -0800, Shakeel Butt wrote:
> > Currently the kernel adds the page, allocated for swapin, to the
> > swapcache before charging the page. This is fine but now we want a
> > per-memcg swapcache stat which
The pull request you sent on Mon, 22 Feb 2021 10:59:21 -0400:
> git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3672ac8ac0d8bece188f82c48770bbe40f234f1e
Thank you!
--
Deet-doot-dot, I am a
401 - 500 of 1414 matches
Mail list logo