The 2C hysteresis is a bit too high, although CPU never gets hot on A500.
Nevertheless, let's reduce thermal throttling hysteresis to 0.2C, which is
a much more reasonable value.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-acer-a500-picasso.dts | 2 +-
1 file changed, 1
If CPU0 is unplugged the cooling device can not rebind to CPU1. And if
CPU0 is plugged in again, the cooling device may fail to initialize.
If the CPUs are mapped with the physical CPU0 to Linux numbering
CPU1, the cooling device mapping will fail.
Hence specify all CPU cores as a cooling
Allow lower core voltages on Acer A500.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-acer-a500-picasso.dts | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
b/arch/arm/boot/dts/tegra20-acer-a500-picasso.dts
Specify CPU suspend OPP in a device-tree, just for consistency. Now CPU
will always suspend on the same frequency.
Tested-by: Peter Geis # Ouya T30
Tested-by: Nicolas Chauvet # PAZ00 T20
Tested-by: Matt Merhar # Ouya T30
Tested-by: Dmitry Osipenko # A500 T20 and Nexus7 T30
Signed-off-by:
If CPU0 is unplugged the cooling device can not rebind to CPU1. And if
CPU0 is plugged in again, the cooling device may fail to initialize.
If the CPUs are mapped with the physical CPU0 to Linux numbering
CPU1, the cooling device mapping will fail.
Hence specify all CPU cores as a cooling
Specify memory suspend OPP in a device-tree, just for consistency.
Now memory will always suspend on the same frequency.
Tested-by: Peter Geis # Ouya T30
Tested-by: Matt Merhar # Ouya T30
Tested-by: Dmitry Osipenko # A500 T20 and Nexus7 T30
Signed-off-by: Dmitry Osipenko
---
diff --git a/drivers/soundwire/debugfs.c b/drivers/soundwire/debugfs.c
index b6cad0d59b7b..f22868614f09 100644
--- a/drivers/soundwire/debugfs.c
+++ b/drivers/soundwire/debugfs.c
@@ -19,13 +19,14 @@ void sdw_bus_debugfs_init(struct sdw_bus *bus)
return;
/* create
On Thu, Jan 21, 2021 at 04:47:37PM +0800, 慕冬亮 wrote:
> Dear kernel developers,
>
> I found that on the syzbot dashboard, “KMSAN: uninit-value in
> rt2500usb_bbp_read” [1] and "KMSAN: uninit-value in
> rt2500usb_probe_hw" [2] should share the same root cause.
>
> ## Duplication
>
> The reasons
Enable CPU thermal throttling on Tegra30 Cardhu board.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-cardhu.dtsi | 43 ++-
1 file changed, 42 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/tegra30-cardhu.dtsi
Hi Linus,
here are some pin control fixes for the v5.11 kernel cycle.
Only driver fixes. The details are in the signed tag.
Please pull it in!
Yours,
Linus Walleij
The following changes since commit 5c8fe583cce542aa0b84adc939ce85293de36e5e:
Linux 5.11-rc1 (2020-12-27 15:30:22 -0800)
are
Hi Yury!
On 1/21/21 1:06 AM, Yury Norov wrote:
> m68k and sh include bitmap/find.h prior to ffs/fls headers. New
> fast-path implementation in find.h requires ffs/fls. Reordering
> the order of headers inclusion helps to prevent compile-time
> implicit-function-declaration error.
Can you fix the
On 21-01-14 17:25:31, Jonathan Cameron wrote:
> On Mon, 11 Jan 2021 14:51:18 -0800
> Ben Widawsky wrote:
>
> > CXL devices must implement the Device Command Interface (described in
> > 8.2.9 of the CXL 2.0 spec). While the driver already maintains a list of
> > commands it supports, there is
On Thu, 21 Jan 2021 at 05:13, Arvind Sankar wrote:
>
> On Wed, Jan 20, 2021 at 03:09:53PM -0800, Nick Desaulniers wrote:
> > On Tue, Jan 19, 2021 at 1:35 PM Arnd Bergmann wrote:
> > >
> > > On Tue, Jan 19, 2021 at 10:18 PM 'Nick Desaulniers' via Clang Built
> > > Linux wrote:
> > > >
> > > > On
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/qib/qib_mad.c:896: warning: Function parameter or member
'ppd' not described in 'rm_pkey'
drivers/infiniband/hw/qib/qib_mad.c:896: warning: Excess function parameter
'dd' description in 'rm_pkey'
On Thu, Jan 21, 2021 at 9:28 AM Christoph Hellwig wrote:
>
> On Thu, Jan 21, 2021 at 09:25:40AM +0100, Daniel Vetter wrote:
> > On Thu, Jan 21, 2021 at 8:55 AM Christoph Hellwig wrote:
> > >
> > > drm_fb_helper_modinit has a lot of boilerplate for what is not very
> > > simple functionality.
This patch adds description for UIO support for dfl devices on DFL
bus.
Signed-off-by: Xu Yilun
---
v2: no doc in v1, add it for v2.
v3: some documentation fixes.
v4: documentation change since the driver matching is changed.
v5: no change.
v6: improve the title of the userspace driver support
On 21/01/2021 17.58, Heiner Litz wrote:
I don't think that ZNS supersedes OCSSD. OCSSDs provide much more
flexibility and device control and remain valuable for academia. For
us, PBLK is the most accurate "SSD Emulator" out there that, as
another benefit, enables real-time performance
We haven't yet implemented support for backlights that need to be
enabled/disabled via PWM instead of AUX, which means we'll break things if
we enable DPCD backlight control on these machines. Luckily though since
most of these machines work fine just using the plain PWM backlight
controls anyway,
On Wed, 20 Jan 2021 21:29:12 -0800, Sudarshan Rajagopalan wrote:
> This patch is the follow-up from the discussions in the thread [1].
> Reducing the section size has the merit of reducing wastage of reserved memory
> for vmmemmap mappings for sections with large memory holes. Also with smaller
>
On Thu, Jan 21, 2021 at 06:15:06PM +, Marc Zyngier wrote:
> On 2021-01-21 17:55, Will Deacon wrote:
> > On Thu, Jan 21, 2021 at 04:25:54PM +, Marc Zyngier wrote:
> > > On 2021-01-21 15:12, Mohamed Mediouni wrote:
> > > > Please ignore that patch.
> > > >
> > > > It turns out that the PCIe
On Thu, Jan 21, 2021 at 5:36 PM Maxime Ripard wrote:
>
> Only planes' prepare_fb and cleanup_fb, and encoders' atomic_check and
> atomic_mode_set hooks remain with an object state and not the global
> drm_atomic_state.
>
> prepare_fb and cleanup_fb operate by design on a given state and
>
On Thu, Jan 21, 2021 at 5:11 AM Linus Walleij wrote:
>
> On Wed, Jan 20, 2021 at 9:05 AM Saravana Kannan wrote:
>
> > To provide backward compatibility for boards that use deprecated DT
> > bindings, we need to add fw_devlink support for "gpio" and "gpios".
>
> You do some more stuff in the
On Thu, 21 Jan 2021 17:03:11 +0900
William Breathitt Gray wrote:
> On Tue, Jan 19, 2021 at 10:20:22AM +0100, Oleksij Rempel wrote:
> > On Sun, Nov 22, 2020 at 03:29:54PM -0500, William Breathitt Gray wrote:
> > > This patch introduces a character device interface for the Counter
> > >
Enable full voltage scaling ranges for CPU and Core power domains.
Tested-by: Nicolas Chauvet
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-paz00.dts | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/arch/arm/boot/dts/tegra20-paz00.dts
Support CPU and Core voltage scaling on Tegra20 Ventana board.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-ventana.dts | 37 ---
1 file changed, 28 insertions(+), 9 deletions(-)
diff --git a/arch/arm/boot/dts/tegra20-ventana.dts
syzbot has found a reproducer for the following issue on:
HEAD commit:9791581c Merge tag 'for-5.11-rc4-tag' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13cd09a4d0
kernel config:
On Thu, 21 Jan 2021 10:07:48 +0800 (GMT+08:00)
司延腾 wrote:
> Sorry, I apologize for the inconvenience caused to you, I do not
> quibble, but I have been studying for nearly a week, please pay
> attention to my future patches.
Please don't worry, mistakes happen; we just have to learn from them.
Hi,
On 18/01/21 11:25, Song Bao Hua wrote:
>> -Original Message-
>> From: Vincent Guittot [mailto:vincent.guit...@linaro.org]
>> Sent: Tuesday, January 19, 2021 12:14 AM
>> To: Song Bao Hua (Barry Song)
>> Cc: Ingo Molnar ; Peter Zijlstra ;
>> Dietmar Eggemann ; Morten Rasmussen
>> ;
On Mon, 18 Jan 2021 21:16:08 +0800
Keqian Zhu wrote:
> On 2021/1/16 3:14, Alex Williamson wrote:
> > On Fri, 15 Jan 2021 17:26:43 +0800
> > Keqian Zhu wrote:
> >
> >> vfio_sanity_check_pfn_list() is used to check whether pfn_list of
> >> vfio_dma is empty when remove the external domain, so
Enable CPU thermal throttling on Tegra20 Ventana board.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra20-ventana.dts | 41 +--
1 file changed, 39 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/tegra20-ventana.dts
Hi,
This series is partially factored out from [1] since the DT patches
could be applied separately. In addition I added couple more new
patches and implemented suggestion given by Daniel Lezcano to [1],
see "Specify all CPU cores as cooling devices" patches.
[1]
> On 21 Jan 2021, at 19:15, Marc Zyngier wrote:
>
> On 2021-01-21 17:55, Will Deacon wrote:
>> On Thu, Jan 21, 2021 at 04:25:54PM +, Marc Zyngier wrote:
>>> On 2021-01-21 15:12, Mohamed Mediouni wrote:
Please ignore that patch.
It turns out that the PCIe controller on Apple
Enable CPU frequency and voltage scaling on all Tegra30 Cardhu board variants.
Signed-off-by: Dmitry Osipenko
---
arch/arm/boot/dts/tegra30-cardhu-a04.dts | 48
arch/arm/boot/dts/tegra30-cardhu.dtsi| 40 ++--
2 files changed, 37 insertions(+), 51
On 2021-01-21 17:55, Will Deacon wrote:
On Thu, Jan 21, 2021 at 04:25:54PM +, Marc Zyngier wrote:
On 2021-01-21 15:12, Mohamed Mediouni wrote:
> Please ignore that patch.
>
> It turns out that the PCIe controller on Apple M1 expects posted
> writes and so the memory range for it ought to be
On 21-01-14 17:10:38, Jonathan Cameron wrote:
> On Mon, 11 Jan 2021 14:51:14 -0800
> Ben Widawsky wrote:
>
> > The send command allows userspace to issue mailbox commands directly to
> > the hardware. The driver will verify basic properties of the command and
> > possible inspect the input (or
On 21/01/21 19:39, Meelis Roos wrote:
>> Could you paste the output of the below?
>>
>>$ cat /sys/devices/system/node/node*/distance
>
> 10 12 12 14 14 14 14 16
> 12 10 14 12 14 14 12 14
> 12 14 10 14 12 12 14 14
> 14 12 14 10 12 12 14 14
> 14 14 12 12 10 14 12 14
> 14 14 12 12 14 10 14 12
>
On 1/21/21 11:01 AM, Christoph Lameter wrote:
> On Thu, 21 Jan 2021, Bharata B Rao wrote:
>
>> > The problem is that calculate_order() is called a number of times
>> > before secondaries CPUs are booted and it returns 1 instead of 224.
>> > This makes the use of num_online_cpus() irrelevant for
Fix below warnings reported by coccicheck:
./drivers/block/rsxx/dma.c:948:3-8: WARNING: NULL check
before some freeing functions is not needed.
Reported-by: Abaci Robot
Signed-off-by: Yang Li
---
drivers/block/rsxx/dma.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/mlx5/odp.c:1062: warning: Function parameter or member
'dev' not described in 'pagefault_data_segments'
drivers/infiniband/hw/mlx5/odp.c:1062: warning: Function parameter or member
'pfault' not described in
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
This is set 2 of 3 (hopefully) sets required to fully clean-up.
Lee Jones (30):
RDMA/hw/mlx5/odp: Fix formatting and add missing descriptions in
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/hns/hns_roce_mr.c:1003: warning: Function parameter or
member 'hr_dev' not described in 'hns_roce_mtr_create'
Cc: Lijun Ou
Cc: "Wei Hu
Cc: Weihang Li
Cc: Doug Ledford
Cc: Jason Gunthorpe
Cc: linux-r...@vger.kernel.org
From: kernel test robot
Breaking out of for_each_child_of_node requires a put on the
child value.
Generated by: scripts/coccinelle/iterators/for_each_child.cocci
Fixes: 82c2d81361ec ("coccinelle: iterators: Add for_each_child.cocci script")
CC: Sumera Priyadarsini
Reported-by: kernel test
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/hns/hns_roce_hw_v1.c:1398: warning: Function parameter
or member 'dereset' not described in 'hns_roce_v1_reset'
drivers/infiniband/hw/hns/hns_roce_hw_v1.c:1398: warning: Excess function
parameter 'enable' description in
> On 21 Jan 2021, at 18:37, Rob Herring wrote:
>
> On Thu, Jan 21, 2021 at 10:43 AM Mohamed Mediouni
> wrote:
>>> On 21 Jan 2021, at 17:40, Rob Herring wrote:
>>> On Thu, Jan 21, 2021 at 6:52 AM Mohamed Mediouni
>>> wrote:
> On 21 Jan 2021, at 13:44, Arnd Bergmann wrote:
> On Wed,
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/qib/qib_eeprom.c:55: warning: Function parameter or
member 'buff' not described in 'qib_eeprom_read'
drivers/infiniband/hw/qib/qib_eeprom.c:55: warning: Excess function parameter
'buffer' description in 'qib_eeprom_read'
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/qib/qib_intr.c:48: warning: Function parameter or member
'msg' not described in 'qib_format_hwmsg'
drivers/infiniband/hw/qib/qib_intr.c:48: warning: Function parameter or member
'msgl' not described in 'qib_format_hwmsg'
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/hfi1/chip.c:1335: warning: Function parameter or member
'dd' not described in 'hfi1_addr_from_offset'
drivers/infiniband/hw/hfi1/chip.c:1335: warning: Function parameter or member
'offset' not described in
On Thu, Jan 21, 2021 at 5:34 PM Daniel Scally wrote:
>
>
> On 21/01/2021 14:39, Rafael J. Wysocki wrote:
> > On Thu, Jan 21, 2021 at 1:04 PM Daniel Scally wrote:
> >>
> >> On 21/01/2021 11:58, Rafael J. Wysocki wrote:
> >>> On Thu, Jan 21, 2021 at 10:47 AM Daniel Scally
> >>> wrote:
> Hi
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/qib/qib_tx.c:383: warning: Function parameter or member
'rcd' not described in 'qib_chg_pioavailkernel'
Cc: Dennis Dalessandro
Cc: Mike Marciniszyn
Cc: Doug Ledford
Cc: Jason Gunthorpe
Cc: linux-r...@vger.kernel.org
Hi Max,
On Mon, Jan 18, 2021 at 10:07 PM wrote:
>
> From: Max Chou
>
> By this change, it will enable WBS supported on the specific Realtek BT
> devices, such as RTL8822C and RTL8852A.
> In the future, it's able to maintain what the Realtek devices support WBS
> here.
>
> Tested-by: Hilda Wu
>
On Wed, 20 Jan 2021, Pan Bian wrote:
Release master that have been previously allocated if the number of
chipselect is invalid.
Fixes: 8e04187c1bc7 ("spi: altera: add SPI core parameters support via platform
data.")
Signed-off-by: Pan Bian
Acked-by: Matthew Gerlach
---
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/qib/qib_uc.c:49: warning: Function parameter or member
'flags' not described in 'qib_make_uc_req'
Cc: Dennis Dalessandro
Cc: Mike Marciniszyn
Cc: Doug Ledford
Cc: Jason Gunthorpe
Cc: linux-r...@vger.kernel.org
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/hw/qib/qib_user_pages.c:60: warning: Function parameter or
member 'hwdev' not described in 'qib_map_page'
drivers/infiniband/hw/qib/qib_user_pages.c:60: warning: Function parameter or
member 'page' not described in
On Mon, 18 Jan 2021 20:25:09 +0800
Keqian Zhu wrote:
> On 2021/1/16 2:01, Alex Williamson wrote:
> > On Fri, 15 Jan 2021 17:26:42 +0800
> > Keqian Zhu wrote:
> >
> >> If a group with non-pinned-page dirty scope is detached with dirty
> >> logging enabled, we should fully populate the dirty
Fixes the following W=1 kernel build warning(s):
drivers/infiniband/sw/rdmavt/mad.c:75: warning: Function parameter or member
'in' not described in 'rvt_process_mad'
drivers/infiniband/sw/rdmavt/mad.c:75: warning: Function parameter or member
'in_mad_size' not described in 'rvt_process_mad'
Origin DT binding just specify driver but wasn't aligned with DT binding
which came later. Extend description for zcu102 and zcu106 to cover latest
binding.
Signed-off-by: Michal Simek
---
Changes in v2: None
.../boot/dts/xilinx/zynqmp-zcu102-revA.dts| 17 ++
Hi folks,
I am testing new kernels under high load and KASAN found some troubles:
BUG: KASAN: use-after-free in __list_add_valid+0x81/0xa0
Read of size 8 at addr 8881f2cda008 by task ThreadPoolForeg/110220
CPU: 22 PID: 110220 Comm: ThreadPoolForeg Tainted: GW
- ---
Enable psgtr driver and write clocks property to get sata to work.
Signed-off-by: Michal Simek
---
Changes in v2: None
.../boot/dts/xilinx/zynqmp-zcu102-revA.dts| 10 +++
.../boot/dts/xilinx/zynqmp-zcu104-revA.dts| 28 +++
.../boot/dts/xilinx/zynqmp-zcu106-revA.dts
Enable si5341 driver is the main chip for providing preprogrammed clocks
for the whole platform.
# cat /sys/kernel/debug/clk/clk_summary
...
refhdmi 110 114285000
0 0 5
xtal_0000
Enable reset controller to be prepared for use.
Signed-off-by: Michal Simek
---
Changes in v2:
- Remove reset description for IPs from this patch. IPs will be enabled
separately with DT binding update.
- Change patch subject
arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 5 +
1 file changed,
For non-DMA usage, we have an easy way to associate a timestamp with a
sample: iio_pollfunc_store_time stores a timestamp in the primary
trigger IRQ handler and stm32_adc_trigger_handler runs in the IRQ thread
to push out the buffer along with the timestamp.
For this to work, the driver needs to
On Wed, Jan 20, 2021 at 05:41:18PM -0800, Rick Edgecombe wrote:
> When VM_MAP_PUT_PAGES was added, it was defined with the same value as
> VM_FLUSH_RESET_PERMS. This doesn't seem like it will cause any big
> functional problems other than some excess flushing for VM_MAP_PUT_PAGES
> allocations.
>
On Wed, Jan 20, 2021 at 02:15:59PM +0100, Ard Biesheuvel wrote:
> On Wed, 20 Jan 2021 at 14:01, Will Deacon wrote:
> >
> > On Wed, 6 Jan 2021 10:34:48 +, Andre Przywara wrote:
> > > a fix to v5, now *really* fixing the wrong priority of SMCCC vs. RNDR
> > > in
On 1/21/21 9:41 AM, Srinivas Kandagatla wrote:
On 21/01/2021 14:56, Pierre-Louis Bossart wrote:
Port allocations are something like this:
RX: (Simple)
Port 1 -> HPH L/R
Port 2 -> CLASS H Amp
Port 3 -> COMP
Port 4 -> DSD.
TX: (This get bit more complicated)
Port 1: PCM
Port 2: ADC 1 &
On 1/21/21 10:56 AM, Trond Myklebust wrote:
On Wed, 2021-01-20 at 16:52 -0700, Shuah Khan wrote:
Hi Anna and Trond,
I came across the following while reviewing atomic_inc_return()
usages
that cast return value to unsigned
rpc_xprt_debugfs_register()'s atomic_inc_return() usage looks a bit
This patchset introduces a new dma heap, "chunk-heap" that makes it
easy to perform the bulk allocation of high order pages.
It has been created to help optimize the 4K/8K HDR video playback
with secure DRM HW to protect contents on memory. The HW needs
physically contiguous memory chunks(e.g,
The upcoming patch will introduce __GFP_NORETRY semantic
in alloc_contig_range which is a failfast mode of the API.
Instead of adding a additional parameter for gfp, replace
no_warn with gfp flag.
To keep old behaviors, it follows the rule below.
no_warn gfp_flags
On Thu, Jan 21, 2021 at 09:46:58AM -0800, Linus Torvalds wrote:
> On Thu, Jan 21, 2021 at 3:02 AM Jiri Slaby wrote:
> >
> > n_hdlc_tty_read will return EOVERFLOW when size is 0, so this EFAULT is
> > never propagated, if I am looking correctly? n_tty seems to be fine
> > (returns zero for zeroed
On Fri, Jan 15, 2021 at 10:59:15PM +0300, Alexander Shishkin wrote:
> Hi Greg,
>
> Here are updates that I have for v5.11. These are: one minor bugfix and
> a new PCI ID.
>
> Alexander Shishkin (1):
> intel_th: pci: Add Alder Lake-P support
>
> Wang Hui (1):
> stm class: Fix module init
Contiguous memory allocation can be stalled due to waiting
on page writeback and/or page lock which causes unpredictable
delay. It's a unavoidable cost for the requestor to get *big*
contiguous memory but it's expensive for *small* contiguous
memory(e.g., order-4) because caller could retry the
On Thu, Jan 21, 2021 at 09:44:17AM -0800, Linus Torvalds wrote:
> On Thu, Jan 21, 2021 at 1:40 AM Jiri Slaby wrote:
> >
> > Ok, here belongs my earlier note: "if ld == NULL => crash here." That is
> > if hangup happens during the ldisc wait, the kernel will crash in
> > tty_ldisc_deref.
>
>
On Wed, 2021-01-20 at 16:52 -0700, Shuah Khan wrote:
> Hi Anna and Trond,
>
> I came across the following while reviewing atomic_inc_return()
> usages
> that cast return value to unsigned
>
> rpc_xprt_debugfs_register()'s atomic_inc_return() usage looks a bit
> odd.
>
> - cur_id isn't
On Thu, Jan 21, 2021 at 04:25:54PM +, Marc Zyngier wrote:
> On 2021-01-21 15:12, Mohamed Mediouni wrote:
> > Please ignore that patch.
> >
> > It turns out that the PCIe controller on Apple M1 expects posted
> > writes and so the memory range for it ought to be set nGnRE.
> > So, we need to
From: Hyesoo Yu
This patch supports chunk heap that allocates the buffers that
arranged into a list a fixed size chunks taken from CMA.
The chunk heap driver is bound directly to a reserved_memory
node by following Rob Herring's suggestion in [1].
[1]
On Thu, Jan 21, 2021 at 12:58 AM Jiri Slaby wrote:
>
> Which is weird as you Cced me. Let me check what is wrong with my e-mail
> setup.
Yeah, I think you were cc'd on not just the patches, but on all the
discussion that preceded them.
But better late than never. I was actually much more
From: Hyesoo Yu
Document devicetree binding for chunk cma heap on dma heap framework.
The DMA chunk heap supports the bulk allocation of higher order pages.
The chunk heap's allocator allocates from the CMA area. It is optimized
to perform bulk allocation of higher order pages in an efficient
On Thu, 5 Nov 2020 16:29:44 +0100, Ard Biesheuvel wrote:
> When reseeding the CRNG periodically, arch_get_random_seed_long() is
> called to obtain entropy from an architecture specific source if one
> is implemented. In most cases, these are special instructions, but in
> some cases, such as on
From: Konstantin Khlebnikov
For disk filesystems result of every negative lookup is cached, content of
directories is usually cached too. Production of negative dentries isn't
limited with disk speed. It's really easy to generate millions of them if
system has enough memory. Negative dentries
On Sat, Jan 9, 2021 at 11:33 AM Lecopzer Chen wrote:
>
> Linux supports KAsan for VMALLOC since commit 3c5c3cfb9ef4da9
> ("kasan: support backing vmalloc space with real shadow memory")
>
> Acroding to how x86 ported it [1], they early allocated p4d and pgd,
> but in arm64 I just simulate how
Clear struct snd_ctl_elem_value before calling ->put() to avoid any data
leak.
Reviewed-by: Andy Shevchenko
Reviewed-by: Cezary Rojewski
Signed-off-by: Ricardo Ribalda
---
sound/soc/intel/skylake/skl-topology.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
If dobj->control is not initialized we end up in an OOPs during
skl_tplg_complete:
[ 26.553358] BUG: kernel NULL pointer dereference, address:
0078
[ 26.561151] #PF: supervisor read access in kernel mode
[ 26.566897] #PF: error_code(0x) - not-present page
[ 26.572642] PGD
On Thu, Jan 21, 2021 at 10:57:09AM -0600, Bjorn Helgaas wrote:
> On Mon, Jan 18, 2021 at 04:58:36PM +0800, Zhangfei Gao wrote:
> > HiSilicon KunPeng920 and KunPeng930 have devices appear as PCI but are
> > actually on the AMBA bus. These fake PCI devices can support SVA via
> > SMMU stall feature,
On Thu, Jan 21, 2021 at 12:13 AM Greg KH wrote:
>
> On Wed, Jan 20, 2021 at 11:38:57AM -0800, Dan Williams wrote:
> > -void cdev_del(struct cdev *p)
> > +void cdev_del(struct cdev *cdev)
> > {
> > - cdev_unmap(p->dev, p->count);
> > - kobject_put(>kobj);
> > + cdev_unmap(cdev->dev,
On Thu, Jan 21, 2021 at 06:16:44PM +0100, Ricardo Ribalda wrote:
> Clear struct snd_ctl_elem_value before calling ->put() to avoid any data
> leak.
Reviewed-by: Andy Shevchenko
> Signed-off-by: Ricardo Ribalda
> ---
> sound/soc/intel/skylake/skl-topology.c | 2 +-
> 1 file changed, 1
On Wed, Jan 20, 2021 at 08:58:30PM -0800, Pan Bian wrote:
> Instead of directly return, goto the error handling label to free
> allocated page.
>
> Fixes: 5f29458b77d5 ("net/mlx5e: Support dump callback in TX reporter")
> Signed-off-by: Pan Bian
> ---
>
>
> On Thu, Jan 21, 2021 at 11:00:20AM +0100, Christophe Leroy wrote:
> > > +bool module_loaded(const char *name);
> >
> > Maybe module_is_loaded() would be a better name.
>
> Fine with me.
It does look like both callers aren't 'unsafe'.
But it is a bit strange returning a stale value.
It did
On Thu, Jan 21, 2021 at 3:02 AM Jiri Slaby wrote:
>
> n_hdlc_tty_read will return EOVERFLOW when size is 0, so this EFAULT is
> never propagated, if I am looking correctly? n_tty seems to be fine
> (returns zero for zeroed size).
I'll fix that up too.
Greg - same question - do you want an
On Thu, Jan 21, 2021 at 09:44:50AM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/infiniband/hw/mlx5/odp.c:1062: warning: Function parameter or member
> 'dev' not described in 'pagefault_data_segments'
> drivers/infiniband/hw/mlx5/odp.c:1062: warning:
On Thu, Jan 21, 2021 at 09:44:51AM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/infiniband/hw/mlx5/qp.c:5384: warning: Function parameter or member
> 'qp' not described in 'mlx5_ib_qp_set_counter'
> drivers/infiniband/hw/mlx5/qp.c:5384: warning:
On Thu, Jan 21, 2021 at 4:38 AM Arnd Bergmann wrote:
>
> On Thu, Jan 21, 2021 at 10:48 AM Linus Walleij
> wrote:
> >
> > Hi Mohamed,
> >
> > thanks for your patch!
> >
> > On Wed, Jan 20, 2021 at 2:31 PM Mohamed Mediouni
> > wrote:
> >
> > > +properties:
> > > + compatible:
> > > +items:
On Thu, Jan 21, 2021 at 06:16:43PM +0100, Ricardo Ribalda wrote:
> If dobj->control is not initialized we end up in an OOPs during
> skl_tplg_complete:
>
> [ 26.553358] BUG: kernel NULL pointer dereference, address:
> 0078
> [ 26.561151] #PF: supervisor read access in kernel mode
On Thu, Jan 21, 2021 at 10:21:50PM +0530, Prathu Baronia wrote:
> This patch removes the unnecessary kmap calls in the hugepage zeroing path and
> improves the timing by 62%.
>
> I had proposed a similar change in Apr-May'20 timeframe in memory.c where I
> proposed to clear out a hugepage by
Add support for the msg26xx touchscreen IC from MStar.
This driver reuses zinitix.c structure, while the checksum and irq handler
functions are based on out-of-tree driver for Alcatel Idol 3 (4.7").
Signed-off-by: Vincent Knecht
---
Changed in v3:
- no change
Changed in v2:
- don't use bitfields
This adds dts bindings for the mstar msg26xx touchscreen.
Signed-off-by: Vincent Knecht
---
Changed in v3:
- added `touchscreen-size-x: true` and `touchscreen-size-y: true` properties
Changed in v2:
- changed M-Star to MStar in title line
- changed reset gpio to active-low in example section
---
On 21/01/2021 11:39, Shaokun Zhang wrote:
Hi,
在 2021/1/21 18:54, Shunsuke Nakamura 写道:
Adds L1 data cache refill prefetch, L2 data cache refill prefetch,
and DCZVA instruction events.
A silly question, Does Arm define these events? I checked Arm ARM
document(DDI0487Fc) that these event
On Thu, Jan 21, 2021 at 1:40 AM Jiri Slaby wrote:
>
> Ok, here belongs my earlier note: "if ld == NULL => crash here." That is
> if hangup happens during the ldisc wait, the kernel will crash in
> tty_ldisc_deref.
Right you are, good catch.
> Is there a reason not to convert hung_up_tty_fops
On 1/21/21 6:28 PM, Greg Kroah-Hartman wrote:
> On Thu, Jan 21, 2021 at 06:04:52PM +0100, Niklas Schnelle wrote:
>>
>>
>> On 1/21/21 4:54 PM, Bjorn Helgaas wrote:
>>> [Greg may be able to help compare/contrast this s390 UID with udev
>>> persistent names]
>>>
>>> On Thu, Jan 21, 2021 at
On Thu, Jan 21, 2021 at 5:40 PM Vincenzo Frascino
wrote:
>
> MTE provides a mode that asynchronously updates the TFSR_EL1 register
> when a tag check exception is detected.
>
> To take advantage of this mode the kernel has to verify the status of
> the register at:
> 1. Context switching
> 2.
On Thu, Jan 21, 2021 at 05:02:57PM +, David Howells wrote:
> J. Bruce Fields wrote:
>
> > On Wed, Jan 20, 2021 at 10:21:24PM +, David Howells wrote:
> > > Note that this uses SEEK_HOLE/SEEK_DATA to locate the data available
> > > to be read from the cache. Whilst this is an
On 21/01/2021 10:54, Shunsuke Nakamura wrote:
+ {
+"PublicDescription": "This event counts each correction to the predicted
program flow that occurs because of a misprediction from, or no prediction from, the branch
prediction resources and that relates to instructions that the branch
601 - 700 of 1499 matches
Mail list logo
