On 3/9/21 4:51 PM, Naveen N. Rao wrote:
On 2021/03/09 08:54PM, Michael Ellerman wrote:
Ravi Bangoria writes:
As per ISA 3.1, prefixed instruction should not cross 64-byte
boundary. So don't allow Uprobe on such prefixed instruction.
There are two ways probed instruction is changed in mappe
2021년 3월 9일 (화) 오후 6:22, Chao Yu 님이 작성:
>
> On 2021/3/5 10:24, Daeho Jeong wrote:
> > From: Daeho Jeong
> >
> > Added acc_compr_inodes to show accumulated compressed inode count and
> > acc_compr_blocks to show accumulated secured block count with
>
> I noticed that these stat numbers are recorded
On Tue, Mar 9, 2021 at 2:18 PM Oleksij Rempel wrote:
>
> On Tue, Mar 09, 2021 at 01:46:55PM +0200, Andy Shevchenko wrote:
> > On Tue, Mar 9, 2021 at 1:42 PM Oleksij Rempel
> > wrote:
> > > On Tue, Mar 09, 2021 at 01:05:27PM +0200, Andy Shevchenko wrote:
> > > > On Fri, Mar 5, 2021 at 9:05 PM Jon
On Tue 09-03-21 12:32:55, Matthew Wilcox wrote:
> On Tue, Mar 09, 2021 at 10:02:00AM +0100, Michal Hocko wrote:
[...]
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index 913c2b9e5c72..d44dea2b8d22 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -3135,8 +3135,21 @@ int __m
On Mon, Mar 08, 2021 at 04:54:58PM +0200, Alexandru Ardelean wrote:
> The intent is the removal of the 'delay_usecs' field from the
> spi_transfer struct, as there is a 'delay' field that does the same
> thing.
>
> The spi_delay_to_ns() can be used to get the transfer delay. It works by
> using th
AM64 SoC has a single Octal SPI (OSPI) instance under Flash SubSystem
(FSS). Add DT entry for the same.
Signed-off-by: Vignesh Raghavendra
---
arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 25
1 file changed, 25 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am64-ma
Both AM64 EVM and SK have a 512Mb S28HS512T Octal SPI NOR flash.
Add DT node for the same.
Signed-off-by: Vignesh Raghavendra
---
Bootlog:
SK: https://pastebin.ubuntu.com/p/gvxg7cFrXH/
EVM: https://pastebin.ubuntu.com/p/jb39GqkB78/
arch/arm64/boot/dts/ti/k3-am642-evm.dts | 36
From: Wei Yongjun
Remove including that don't need it.
Reported-by: Hulk Robot
Signed-off-by: Wei Yongjun
---
sound/soc/codecs/rt715-sdca.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/sound/soc/codecs/rt715-sdca.c b/sound/soc/codecs/rt715-sdca.c
index 92ad6fa408ec..20528afbdc57 100644
On Tue, Mar 09, 2021 at 03:57:06PM +0800, kernel test robot wrote:
> FYI, we noticed a -7.6% regression of
> fxmark.hdd_ext4_no_jnl_DRBM_9_bufferedio.works/sec due to commit:
>
> commit: cbd59c48ae2bcadc4a7599c29cf32fd3f9b78251 ("mm/filemap: use head pages
> in generic_file_buffered_read")
> htt
From: Wei Yongjun
In case of error, the function devm_regmap_init_sdw_mbq() and
devm_regmap_init_sdw() returns ERR_PTR() not NULL. The NULL test
in the return value check should be replaced with IS_ERR().
Fixes: 393c52d2d109 ("ASoC: rt715-sdca: Add RT715 sdca vendor-specific driver")
Reported-by
On Tue, Mar 09, 2021 at 09:55:58AM +0100, Thomas Gleixner wrote:
> Soft interrupt disabled sections can legitimately be preempted or schedule
> out when blocking on a lock on RT enabled kernels so the RCU preempt check
> warning has to be disabled for RT kernels.
>
> Signed-off-by: Thomas Gleixner
Reword the subsystem bindings section to make sense, from a grammatical
point of view.
Signed-off-by: Geert Uytterhoeven
---
Documentation/devicetree/bindings/submitting-patches.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/submitti
AM64 SoC has a single ADC IP with 8 channels. Add DT node for the same.
Default usecase is to control ADC from non Linux core on the system on
AM642 GP EVM, therefore mark the node as reserved in k3-am642-evm.dts
file. ADC lines are not pinned out on AM642 SK board, therefore disable
the node in k
On Thu, Mar 04, 2021 at 10:43:45AM +0100, Jérôme Pouiller wrote:
> Hello Greg,
>
> On Tuesday 2 March 2021 16:01:25 CET Jérôme Pouiller wrote:
> > Hello Muhammad,
> >
> > Sorry, I am a bit late for the review of this patch. Thank you for your
> > contribution.
> >
> > On Thursday 11 February 20
On Mon, Mar 8, 2021 at 5:58 PM Catalin Marinas wrote:
>
> On Mon, Mar 08, 2021 at 04:55:14PM +0100, Andrey Konovalov wrote:
> > @@ -68,10 +69,16 @@ static inline void mte_set_mem_tag_range(void *addr,
> > size_t size, u8 tag)
> >* 'asm volatile' is required to prevent the compiler
A few small fixes and improvements
Dong Aisheng (11):
doc: ABI: devfreq: remove invalid central_polling description
PM / devfreq: remove the invalid description for get_target_freq
PM / devfreq: fix the wrong set_freq path for userspace governor
PM / devfreq: bail out early if no freq chan
no_central_polling has been removed since
commit 7e6fdd4bad03 ("PM / devfreq: Core updates to support devices
which can idle")
Signed-off-by: Dong Aisheng
---
Documentation/ABI/testing/sysfs-class-devfreq | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/Documentation/ABI/t
It's unnecessary to set the same freq again and run notifier calls.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index bf3047896e41..6e80bf70e7b3 100644
---
Use the more accurate returned new_freq as resume_freq.
It's the same as how devfreq->previous_freq was updated.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
ind
drop the unnecessary low variable initialization and make the return
more straightforward.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index ce569bd9adfa..7
On 09/03/21 11:09, Maxim Levitsky wrote:
What happens if mmio generation overflows (e.g if userspace keeps on updating
the memslots)?
In theory if we have a SPTE with a stale generation, it can became valid, no?
I think that we should in the case of the overflow zap all mmio sptes.
What do you
Check .get_dev_status() in devfreq_update_stats in case it's abused
when a device does not provide it.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/governor.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/devfreq/governor.h b/drivers/devfreq/governor.h
index 31af6d072a10..67a
The devfreq monitor depends on the device to provide load information
by .get_dev_status() to calculate the next target freq.
And this will cause changing governor to simple ondemand fail
if device can't support.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 10 +++
First of all, no_central_polling was removed since
commit 7e6fdd4bad03 ("PM / devfreq: Core updates to support devices
which can idle")
Secondly, get_target_freq() is not only called only with update_devfreq()
notified by OPP now, but also min/max freq qos notifier.
So remove this invalid descript
polling_ms is only used by simple ondemand governor which
this driver can't support. Drop it to avoid confusing.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/imx8m-ddrc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/devfreq/imx8m-ddrc.c b/drivers/devfreq/imx8m-ddrc.c
index 0a6b7
no_central_polling has been removed since
commit 7e6fdd4bad03 ("PM / devfreq: Core updates to support devices
which can idle")
Signed-off-by: Dong Aisheng
---
Documentation/ABI/testing/sysfs-class-devfreq | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/Documentation/ABI/t
First of all, no_central_polling was removed since
commit 7e6fdd4bad03 ("PM / devfreq: Core updates to support devices
which can idle")
Secondly, get_target_freq() is not only called only with update_devfreq()
notified by OPP now, but also min/max freq qos notifier.
So remove this invalid descript
A few small fixes and improvements
Dong Aisheng (11):
doc: ABI: devfreq: remove invalid central_polling description
PM / devfreq: remove the invalid description for get_target_freq
PM / devfreq: fix the wrong set_freq path for userspace governor
PM / devfreq: bail out early if no freq chan
Fix the wrong set_freq path for userspace governor.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/devfreq/Kconfig b/drivers/devfreq/Kconfig
index 00704efe6398..20373a893b44 100644
--- a/drivers/devfreq/Kconfig
Use the more accurate returned new_freq as resume_freq.
It's the same as how devfreq->previous_freq was updated.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
ind
It's unnecessary to set the same freq again and run notifier calls.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index bf3047896e41..6e80bf70e7b3 100644
---
devfreq_simple_ondemand_data only needs to be initialized once when
calling devm_devfreq_add_device. It's unnecessary to put the data
check logic in the hot path (.get_target_freq()) where it will be
called all the time during polling. Instead, we only check and initialize
it one time during DEVFRE
Fix the wrong set_freq path for userspace governor.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/devfreq/Kconfig b/drivers/devfreq/Kconfig
index 00704efe6398..20373a893b44 100644
--- a/drivers/devfreq/Kconfig
drop the unnecessary low variable initialization and make the return
more straightforward.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index ce569bd9adfa..7
The devfreq monitor depends on the device to provide load information
by .get_dev_status() to calculate the next target freq.
And this will cause changing governor to simple ondemand fail
if device can't support.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 10 +++
Current driver actually does not support simple ondemand governor
as it's unable to provide device load information. So removing
the unnecessary callback to avoid confusing.
Right now the driver is using userspace governor by default.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/imx8m-ddrc.c
Check .get_dev_status() in devfreq_update_stats in case it's abused
when a device does not provide it.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/governor.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/devfreq/governor.h b/drivers/devfreq/governor.h
index 31af6d072a10..67a
devfreq_simple_ondemand_data only needs to be initialized once when
calling devm_devfreq_add_device. It's unnecessary to put the data
check logic in the hot path (.get_target_freq()) where it will be
called all the time during polling. Instead, we only check and initialize
it one time during DEVFRE
Current driver actually does not support simple ondemand governor
as it's unable to provide device load information. So removing
the unnecessary callback to avoid confusing.
Right now the driver is using userspace governor by default.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/imx8m-ddrc.c
polling_ms is only used by simple ondemand governor which
this driver can't support. Drop it to avoid confusing.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/imx8m-ddrc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/devfreq/imx8m-ddrc.c b/drivers/devfreq/imx8m-ddrc.c
index 0a6b7
On 09/03/21 06:35PM, Vignesh Raghavendra wrote:
> AM64 SoC has a single Octal SPI (OSPI) instance under Flash SubSystem
> (FSS). Add DT entry for the same.
>
> Signed-off-by: Vignesh Raghavendra
Reviewed-by: Pratyush Yadav
> ---
> arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 25 +++
On 09/03/21 06:35PM, Vignesh Raghavendra wrote:
> Both AM64 EVM and SK have a 512Mb S28HS512T Octal SPI NOR flash.
> Add DT node for the same.
>
> Signed-off-by: Vignesh Raghavendra
Reviewed-by: Pratyush Yadav
> ---
>
> Bootlog:
>
> SK: https://pastebin.ubuntu.com/p/gvxg7cFrXH/
> EVM: https:
Duplicate ABIs are not valid, so let's consolidate these sysfs
attributes into the main sysfs-bus-counter documentation file.
Cc: Patrick Havelange
Reviewed-by: David Lechner
Signed-off-by: William Breathitt Gray
---
Documentation/ABI/testing/sysfs-bus-counter | 76 ++-
.../A
Changes in v9:
- Implemented example userspace counter application under tools/counter
- Replaced extension*_name attributes with *_component_id attributes;
this should hopefully be a more intuitive way to find the desired IDs
- Changed to use regular spinlock because raw_spinlock is not need
"Miscellaneous" is the correct spelling.
Reviewed-by: David Lechner
Signed-off-by: William Breathitt Gray
---
Documentation/driver-api/generic-counter.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/driver-api/generic-counter.rst
b/Documentation/driver-api
When the kernel is running in secure boot mode, we lock down the kernel to
prevent userspace from modifying the running kernel image. Whilst this
includes prohibiting access to things like /dev/mem, it must also prevent
access by means of configuring driver modules in such a way as to cause a
devi
Add some safety by qualifying the quad8_preset_register_set() function
parameters as const.
Cc: Syed Nayyar Waris
Signed-off-by: William Breathitt Gray
---
drivers/counter/104-quad-8.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/counter/104-quad-8.c b/drivers
The struct counter_count functions_list member expects a const enum
counter_count_function array. This patch adds the const qualifier to the
quad8_count_functions_list to match functions_list.
Cc: Syed Nayyar Waris
Signed-off-by: William Breathitt Gray
---
drivers/counter/104-quad-8.c | 2 +-
1
The struct counter_count functions_list member expects a const enum
counter_count_function array. This patch adds the const qualifier to the
interrupt__cnt_functions to match functions_list.
Cc: Oleksij Rempel
Signed-off-by: William Breathitt Gray
---
drivers/counter/interrupt-cnt.c | 2 +-
1 f
Here's my take on v5 of Eric Snowberg's patches[1]:
This series of patches adds support for EFI_CERT_X509_GUID entries [2]. It has
been expanded to not only include dbx entries but also entries in the mokx.
Additionally Eric included his patches to preload these certificate [3].
The patches ca
The 104-QUAD-8 only has two count modes where a ceiling value makes
sense: Range Limit and Modulo-N. Outside of these two modes, setting a
ceiling value is an invalid operation -- so let's report it as such by
returning -EINVAL.
Fixes: fc069262261c ("counter: 104-quad-8: Add lock guards - generic
It is obvious that devm_counter_register() is used to register a Counter
device, so a comment stating such is pointless here.
Cc: Syed Nayyar Waris
Signed-off-by: William Breathitt Gray
---
drivers/counter/104-quad-8.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/counter/104-quad-
From: Eric Snowberg
This fixes CVE-2020-26541.
The Secure Boot Forbidden Signature Database, dbx, contains a list of now
revoked signatures and keys previously approved to boot with UEFI Secure
Boot enabled. The dbx is capable of containing any number of
EFI_CERT_X509_SHA256_GUID, EFI_CERT_SHA2
From: Eric Snowberg
Move functionality within load_system_certificate_list to a common
function, so it can be reused in the future.
DH Changes:
- Added inclusion of common.h to common.c (Eric [1]).
Signed-off-by: Eric Snowberg
Acked-by: Jarkko Sakkinen
Signed-off-by: David Howells
cc: keyri
The struct counter_count functions_list member expects a const enum
counter_count_function array. This patch adds the const qualifier to the
stm32_count_functions to match functions_list.
Cc: Fabrice Gasnier
Cc: Benjamin Gaignard
Signed-off-by: William Breathitt Gray
---
drivers/counter/stm32-
The struct counter_synapse actions_list member expects a const enum
counter_synapse_action array. This patch adds the const qualifier to the
quad8_index_actions_list and quad8_synapse_actions_list to match
actions_list.
Cc: Syed Nayyar Waris
Signed-off-by: William Breathitt Gray
---
drivers/cou
From: Eric Snowberg
Add a new Kconfig option called SYSTEM_REVOCATION_KEYS. If set,
this option should be the filename of a PEM-formated file containing
X.509 certificates to be included in the default blacklist keyring.
DH Changes:
- Make the new Kconfig option depend on SYSTEM_REVOCATION_LIST
The struct counter_count functions_list member expects a const enum
counter_count_function array. This patch adds the const qualifier to the
mchp_tc_count_functions to match functions_list.
Cc: Kamel Bouhara
Signed-off-by: William Breathitt Gray
---
drivers/counter/microchip-tcb-capture.c | 2 +
From: Eric Snowberg
During boot the Secure Boot Forbidden Signature Database, dbx,
is loaded into the blacklist keyring. Systems booted with shim
have an equivalent Forbidden Signature Database called mokx.
Currently mokx is only used by shim and grub, the contents are
ignored by the kernel.
Ad
The struct counter_count functions_list member expects a const enum
counter_count_function array. This patch adds the const qualifier to the
stm32_lptim_cnt_functions to match functions_list.
Cc: Fabrice Gasnier
Signed-off-by: William Breathitt Gray
---
drivers/counter/stm32-lptimer-cnt.c | 2 +
The struct counter_synapse actions_list member expects a const enum
counter_synapse_action array. This patch adds the const qualifier to the
interrupt_cnt_synapse_actionss to match actions_list.
Cc: Oleksij Rempel
Signed-off-by: William Breathitt Gray
---
drivers/counter/interrupt-cnt.c | 2 +-
The struct counter_synapse actions_list member expects a const enum
counter_synapse_action array. This patch adds the const qualifier to the
ftm_quaddec_synapse_actions to match actions_list.
Cc: Patrick Havelange
Signed-off-by: William Breathitt Gray
---
drivers/counter/ftm-quaddec.c | 2 +-
1
The struct counter_synapse actions_list member expects a const enum
counter_synapse_action array. This patch adds the const qualifier to the
mchp_tc_synapse_actions to match actions_list.
Cc: Kamel Bouhara
Signed-off-by: William Breathitt Gray
---
drivers/counter/microchip-tcb-capture.c | 2 +-
The struct counter_synapse actions_list member expects a const enum
counter_synapse_action array. This patch adds the const qualifier to the
stm32_lptim_cnt_synapse_actions to match actions_list.
Cc: Fabrice Gasnier
Signed-off-by: William Breathitt Gray
---
drivers/counter/stm32-lptimer-cnt.c |
The struct counter_synapse actions_list member expects a const enum
counter_synapse_action array. This patch adds the const qualifier to the
stm32_synapse_actions to match actions_list.
Cc: Fabrice Gasnier
Cc: Benjamin Gaignard
Signed-off-by: William Breathitt Gray
---
drivers/counter/stm32-ti
Only a select set of modes (function, action, etc.) are valid for a
given device configuration. This patch ensures that invalid modes result
in a return -EINVAL. Such a situation should never occur in reality, but
it's good to define a default switch cases for the sake of making the
intent of the c
ERANGE is a semantically better error code to return when an argument
value falls outside the supported limit range of a device.
Cc: Syed Nayyar Waris
Cc: Oleksij Rempel
Cc: Fabrice Gasnier
Cc: Maxime Coquelin
Cc: Alexandre Torgue
Reviewed-by: David Lechner
Signed-off-by: William Breathitt G
On Fri, Mar 5, 2021 at 3:40 PM Oleksij Rempel wrote:
I have heard it will be a new version, so below a lot of nit-picks.
> Basically the TI TSC2046 touchscreen controller is 8 channel ADC optimized for
> the touchscreen use case. By implementing it as IIO ADC device, we can
an IIO
> make use o
Signal values will always be levels so let's be explicit it about it to
make the intent of the code clear.
Cc: Syed Nayyar Waris
Cc: Oleksij Rempel
Cc: Kamel Bouhara
Reviewed-by: David Lechner
Signed-off-by: William Breathitt Gray
---
drivers/counter/104-quad-8.c| 5 +++--
drive
The phrase "Counter Count function" is verbose and unintentionally
implies that function is a Count extension. This patch adjusts the
Counter subsystem code to use the more direct "Counter function" phrase
to make the intent of this code clearer.
Cc: Syed Nayyar Waris
Cc: Patrick Havelange
Cc: O
The Counter subsystem architecture and driver implementations have
changed in order to handle Counter sysfs interactions in a more
consistent way. This patch updates the Generic Counter interface
header file comments to reflect the changes.
Signed-off-by: William Breathitt Gray
---
drivers/count
This patch introduces a character device interface for the Counter
subsystem. Device data is exposed through standard character device read
operations. Device data is gathered when a Counter event is pushed by
the respective Counter device driver. Configuration is handled via ioctl
operations on th
This is in preparation for a subsequent patch implementing a character
device interface for the Counter subsystem.
Reviewed-by: David Lechner
Signed-off-by: William Breathitt Gray
---
MAINTAINERS | 1 +
include/linux/counter.h | 42 +--
include/uap
The Counter subsystem architecture and driver implementations have
changed in order to handle Counter sysfs interactions in a more
consistent way. This patch updates the Generic Counter interface
documentation to reflect the changes.
Signed-off-by: William Breathitt Gray
---
Documentation/ABI/te
This patch adds high-level documentation about the Counter subsystem
character device interface.
Signed-off-by: William Breathitt Gray
---
Documentation/driver-api/generic-counter.rst | 185 ++
.../userspace-api/ioctl/ioctl-number.rst | 1 +
2 files changed, 145 insertion
This creates an example Counter program under tools/counter/*
to exemplify the Counter character device interface.
Cc: Pavel Machek
Signed-off-by: William Breathitt Gray
---
MAINTAINERS | 1 +
tools/Makefile | 13 ++---
tools/counter/Build | 1
The Generic Counter chrdev interface expects users to supply component
IDs in order to select Synapses for requests. In order for users to know
what component ID belongs to which Synapse this information must be
exposed. The signalZ_action_component_id attribute provides a way for
users to discover
The Generic Counter chrdev interface expects users to supply component
IDs in order to select extensions for requests. In order for users to
know what component ID belongs to which extension this information must
be exposed. The *_component_id attribute provides a way for users to
discover what com
On Sun, Mar 07, 2021 at 09:14:26AM +0800, Zhangkun wrote:
> On 3/7/21 12:25 AM, Greg Kroah-Hartman wrote:
> > On Sat, Mar 06, 2021 at 08:06:44PM +0800, zhangkun...@163.com wrote:
> >> From: Zhang Kun
> >>
> >> The value assigned to len by sg_pcopy_from_buffer() never used for
> >> anything, so rem
This patch replaces the mutex I/O lock with a spinlock. This is in
preparation for a subsequent patch adding IRQ support for 104-QUAD-8
devices; we can't sleep in an interrupt context, so we'll need to use a
spinlock instead.
Cc: Syed Nayyar Waris
Signed-off-by: William Breathitt Gray
---
drive
The events_queue_size sysfs attribute provides a way for users to
dynamically configure the Counter events queue size for the Counter
character device interface. The size is in number of struct
counter_event data structures. The number of elements will be rounded-up
to a power of 2 due to a require
The LSI/CSI LS7266R1 chip provides programmable output via the FLG pins.
When interrupts are enabled on the ACCES 104-QUAD-8, they occur whenever
FLG1 is active. Four functions are available for the FLG1 signal: Carry,
Compare, Carry-Borrow, and Index.
Carry:
Interrupt gene
On Tue, Mar 9, 2021 at 9:35 PM Michal Suchanek wrote:
>
> When using dummy-tools STACKPROTECTOR_PER_TASK is unconditionally
> selected. This defeats the purpose of the all-enabled tool.
>
> Description copied from arm
>
> Cc: Masahiro Yamada
> Signed-off-by: Michal Suchanek
Could you explain w
On 2021-03-05 06:43, Xie He wrote:
X.25 Layer 3 (the Packet Layer) expects layer 2 to provide a reliable
datalink service such that no packets are reordered or dropped. And
X.25 Layer 2 (the LAPB layer) is indeed designed to provide such
service.
However, this reliability is not preserved when
This patch series integrates HW_TAGS KASAN with init_on_alloc/free
by initializing memory via the same arm64 instruction that sets memory
tags.
This is expected to improve HW_TAGS KASAN performance when
init_on_alloc/free is enabled. The exact perfomance numbers are unknown
as MTE-enabled hardware
This change uses the previously added memory initialization feature
of HW_TAGS KASAN routines for page_alloc memory when init_on_alloc/free
is enabled.
With this change, kernel_init_free_pages() is no longer called when
both HW_TAGS KASAN and init_on_alloc/free are enabled. Instead, memory
is init
This change adds an argument to mte_set_mem_tag_range() that allows
to enable memory initialization when settinh the allocation tags.
The implementation uses stzg instruction instead of stg when this
argument indicates to initialize memory.
Combining setting allocation tags with memory initializat
This change uses the previously added memory initialization feature
of HW_TAGS KASAN routines for slab memory when init_on_free is enabled.
With this change, memory initialization memset() is no longer called
when both HW_TAGS KASAN and init_on_free are enabled. Instead, memory
is initialized in K
This change adds an argument to kasan_poison() and kasan_unpoison()
that allows initializing memory along with setting the tags for HW_TAGS.
Combining setting allocation tags with memory initialization will
improve HW_TAGS KASAN performance when init_on_alloc/free is enabled.
This change doesn't
This change uses the previously added memory initialization feature
of HW_TAGS KASAN routines for slab memory when init_on_alloc is enabled.
With this change, memory initialization memset() is no longer called
when both HW_TAGS KASAN and init_on_alloc are enabled. Instead, memory
is initialized in
On Tue, Mar 09, 2021 at 06:24:45PM +0530, Selvakumar Elangovan wrote:
> Removed additional whitspaces and added space around the binary operator in
> the rtl8712_xmit.h file
Please wrap your changelog at 72 columns.
And you are doing 2 different things in this patch, please only do one
"logical"
The mmc driver has some hooks to support rpmb access, but access is
mainly facilitated from user space, e.g. mmc-utils.
The ufs driver has no concept of rpmb access - it is facilitated via
user space, e.g. ufs-utils and similar.
Both for ufs and mmc, rpmb access is defined in their applicable jed
Although in the most platforms, the power of eeprom
and i2c are alway on, some platforms disable the
eeprom and i2c power in order to meet low power request.
This patch add the pm_runtime ops to control power to
support all platforms.
Changes since v16:
- request regulator in device instead of i
On Tue, 2021-03-09 at 14:12 +0100, Paolo Bonzini wrote:
> On 09/03/21 11:09, Maxim Levitsky wrote:
> > What happens if mmio generation overflows (e.g if userspace keeps on
> > updating the memslots)?
> > In theory if we have a SPTE with a stale generation, it can became valid,
> > no?
> >
> > I
Add vbus-supply which provides power to SCL/SDA. Pass this regulator
into core so it can be turned on/off for low power mode support.
Signed-off-by: Hsin-Yi Wang
---
drivers/i2c/busses/i2c-mt65xx.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/i2c/busses/i2c-mt65xx.c b/drive
From: Bibby Hsieh
Although in the most platforms, the bus power of i2c
are alway on, some platforms disable the i2c bus power
in order to meet low power request.
We can control bulk regulator if it is provided in i2c
adapter device.
Signed-off-by: Bibby Hsieh
Signed-off-by: Marek Szyprowski
S
Add vbus-supply property for mt65xx. The regulator can be passed into
core and turned off during suspend/sleep to reduce power consumption.
Signed-off-by: Hsin-Yi Wang
---
Documentation/devicetree/bindings/i2c/i2c-mt65xx.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devic
On 2021/3/9 19:01, Florian Westphal wrote:
Jia-Ju Bai wrote:
When find_table_lock() returns NULL to t, no error return code of
do_update_counters() is assigned.
Its -ENOENT.
t = find_table_lock(net, name, &ret, &ebt_mutex);
^
ret is pa
Latest AMDGPU NAVI cards have USB Type-C interface which can be accessed
over I2C. The Type-C controller has integrated designware i2c which is
exposed as a PCI device to the AMD platform.
Also there exists couple of notable IP problems that are dealt as a
workaround:
- I2C transactions work on a
On 08/03/2021 3:33 pm, Pierre-Louis Bossart wrote:
Hi Pierre-Louis
Thanks a lot for your comments. Since this patch set has been merged we
will address
your comments in a next fix patch.
+/* Enable I2C clocks */
+static void cs8409_enable_i2c_clock(struct hda_codec *codec,
unsigned int fla
401 - 500 of 1438 matches
Mail list logo
