Re: [PATCH v2] i2c: tegra: Wait for config load atomically while in ISR

11.01.2021 19:08, Mikko Perttunen пишет: > Upon a communication error, the interrupt handler can call > tegra_i2c_disable_packet_mode. This causes a sleeping poll to happen > unless the current transaction was marked atomic. Fix this by > making the poll happen atomically if we are in an IRQ. > >

Re: [PATCH v5 0/5] Unify NUMA implementation between ARM64 & RISC-V

On Sat, Jan 9, 2021 at 12:51 PM Palmer Dabbelt wrote: > > On Sun, 13 Dec 2020 17:02:19 PST (-0800), ati...@atishpatra.org wrote: > > On Wed, Nov 18, 2020 at 4:39 PM Atish Patra wrote: > >> > >> This series attempts to move the ARM64 numa implementation to common > >> code so that RISC-V can lever

[PATCH v7 9/9] media: imx-jpeg: Use v4l2 jpeg helpers in mxc-jpeg

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 --- drivers/media/platform/imx-jpeg/Kconfig| 1 + drivers/media/platform/imx-jpeg/mxc-jpeg.c | 267 ++--

Re: [PATCH v3] kasan: remove redundant config option

On Fri, Jan 8, 2021 at 5:09 AM Walter Wu wrote: > > CONFIG_KASAN_STACK and CONFIG_KASAN_STACK_ENABLE both enable KASAN stack > instrumentation, but we should only need one config, so that we remove > CONFIG_KASAN_STACK_ENABLE and make CONFIG_KASAN_STACK workable. see [1]. > > When enable KASAN sta

Re: KMSAN: kernel-infoleak in move_addr_to_user (4)

Looks like a AF_CAN socket: r0 = socket(0x1d, 0x2, 0x6) getsockname$packet(r0, &(0x7f000100)={0x11, 0x0, 0x0, 0x1, 0x0, 0x6, @broadcast}, &(0x7f00)=0x14) On Sun, 10 Jan 2021 02:19:15 -0800 syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit:73d62e81

[PATCH v7 8/9] media: Avoid parsing quantization and huffman tables

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 --- Changes in

[PATCH v7 7/9] media: Quit parsing stream if doesn't start with SOI

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 a

[PATCH v7 2/9] media: dt-bindings: Add bindings for i.MX8QXP/QM JPEG driver

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 Documentation/

Re: [PATCH v3] kasan: remove redundant config option

On Mon, Jan 11, 2021 at 8:11 PM Nathan Chancellor wrote: > > On Mon, Jan 11, 2021 at 08:03:29PM +0100, Andrey Konovalov wrote: > > On Mon, Jan 11, 2021 at 7:59 PM Nathan Chancellor > > wrote: > > > > > > > > -config KASAN_STACK_ENABLE > > > > > +config KASAN_STACK > > > > > bool "Enable s

[PATCH v7 6/9] media: Add parsing for APP14 data segment in jpeg helpers

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 w

[PATCH v7 4/9] arm64: dts: imx8qxp: Add jpeg encoder/decoder nodes

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 a/arch/arm

[PATCH v7 5/9] Add maintainer for IMX jpeg v4l2 driver

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 f4c94fef4bc6..660b95

[PATCH v7 3/9] media: imx-jpeg: Add V4L2 driver for i.MX8 JPEG Encoder/Decoder

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 vario

Re: [PATCH v1] i2c: tegra: Fix i2c_writesl() to use writel() instead of writesl()

11.01.2021 20:38, Sowjanya Komatineni пишет: > > On 1/11/21 4:09 AM, Dmitry Osipenko wrote: >> 11.01.2021 14:50, Dmitry Osipenko пишет: >>> 20.10.2020 19:37, Sowjanya Komatineni пишет: On 10/20/20 12:48 AM, Thierry Reding wrote: > On Mon, Oct 19, 2020 at 09:03:54PM -0700, Sowjanya Komatin

[PATCH v7 1/9] media: v4l: Add packed YUV444 24bpp pixel format

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 Koci

[PATCH v7 0/9] Add V4L2 driver for i.MX8 JPEG Encoder/Decoder

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, dec

Re: [PATCH V1 resend] dcookies: Make dcookies depend on CONFIG_OPROFILE

On Sun, Jan 10, 2021 at 10:02 PM Viresh Kumar wrote: > > From: Arnd Bergmann > > The dcookies stuff is used only with OPROFILE and there is no need to > build it if CONFIG_OPROFILE isn't enabled. Build it depending on > CONFIG_OPROFILE instead of CONFIG_PROFILING. Umm. I think we should remove C

Re: gdbserver + fsgsbase kaputt

On Mon, Jan 11, 2021 at 10:15 AM Borislav Petkov wrote: > > Hi, > > so there's a breakage of a use case with gdbserver on fsgsbase machines, > see > > https://sourceware.org/bugzilla/show_bug.cgi?id=26804 > > Tom has an even simpler reproducer: > > $ cat test.c > int > main (void) > { > return 0

Re: [PATCH] iommu/arm-smmu-v3: Handle duplicated Stream IDs from other masters

On 2021-01-07 13:03, Will Deacon wrote: On Thu, Jan 07, 2021 at 03:03:40PM +0530, Ajay Kumar wrote: When PCI function drivers(ex:pci-endpoint-test) are probed for already initialized PCIe-RC(Root Complex), and PCIe-RC is already bound to SMMU, then we encounter a situation where the function dri

Re: [PATCH v2 19/34] xlink-core: Add xlink core device tree bindings

On Fri, Jan 08, 2021 at 01:25:45PM -0800, mgr...@linux.intel.com wrote: > From: Seamus Kelly > > Add device tree bindings for keembay-xlink. > > Cc: Rob Herring > Cc: devicet...@vger.kernel.org > Reviewed-by: Mark Gross > Signed-off-by: Seamus Kelly > Signed-off-by: Ryan Carnaghi > --- > ..

Re: [PATCH v2 0/3] Create 'old' ptes for faultaround mappings on arm64 with hardware access flag

On Mon, Jan 11, 2021 at 6:24 AM Kirill A. Shutemov wrote: > > I wonder if it would be acceptable to pass down to faultaround a copy > of vmf, so it mess with it without risking to corrupt the original one? I'd almost prefer to split vmf into two parts: the 'this is the fault info' part and the 't

Re: [PATCH v2 06/34] dt-bindings: Add bindings for Keem Bay VPU IPC driver

On Fri, Jan 08, 2021 at 01:25:32PM -0800, mgr...@linux.intel.com wrote: > From: Paul Murphy > > Add DT bindings documentation for the Keem Bay VPU IPC driver. > > Cc: Rob Herring > Cc: devicet...@vger.kernel.org > Reviewed-by: Mark Gross > Signed-off-by: Paul Murphy > Co-developed-by: Daniele

Re: [drm:dm_plane_helper_prepare_fb [amdgpu]] *ERROR* Failed to pin framebuffer with error -12

On Mon, 11 Jan 2021 at 19:01, Christian König wrote: > Changing the page table attributes while releasing memory might sleep. > So we can't use a spinlock here. > > Thanks for the report, a patch to fix this is on the mailing list now. Can you look also the first trace? Here a same error message

Re: [PATCH 5/7] regulator: qcom-labibb: Implement short-circuit and over-current IRQs

Il 11/01/21 20:14, AngeloGioacchino Del Regno ha scritto: Il 11/01/21 14:57, Mark Brown ha scritto: On Sat, Jan 09, 2021 at 02:29:19PM +0100, AngeloGioacchino Del Regno wrote: +    /* If the regulator is not enabled, this is a fake event */ +    if (!ops->is_enabled(vreg->rdev)) +    retu

[PATCH 08/40] drm/amd/display/dc/gpio/diagnostics/hw_factory_diag: Fix struct declared inside parameter list error

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/diagnostics/hw_factory_diag.h:30:43: warning: ‘struct hw_factory’ declared inside parameter list will not be visible outside of this definition or declaration drivers/gpu/drm/amd/amdgpu/../display/

[PATCH 10/40] drm/amd/display/dc/dce120/dce120_hw_sequencer: Encompass defines in same clause as their use

Ideally someone should strip-out all these garbage 'if 0's. Tempted to carry out the work myself on principle! Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_hw_sequencer.c:53:47: warning: ‘reg_offsets’ defined but not used [-Wunused-con

[PATCH 14/40] drm/amd/display/dc/calcs/dce_calcs: Remove some large variables from the stack

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dce_calcs.c: In function ‘bw_calcs_init’: drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dce_calcs.c:2726:1: warning: the frame size of 1336 bytes is larger than 1024 bytes [-Wframe-larger-than=] C

[PATCH 19/40] drm/amd/display/dc/dce/dce_opp: Remove duplicate entries causing 'field overwritten' issues

Fixes the following W=1 kernel build warning(s): In file included from drivers/gpu/drm/amd/amdgpu/../display/dc/dce112/dce112_resource.c:59: drivers/gpu/drm/amd/amdgpu/../include/asic_reg/dce/dce_11_2_sh_mask.h:10480:62: warning: initialized field overwritten [-Woverride-init] drivers/gpu/dr

Re: [PATCH] usb/c67x00: Replace tasklet with work

On Mon, 11 Jan 2021, Hillf Danton wrote: On Sun, 10 Jan 2021 20:40:50 -0800 Davidlohr Bueso wrote: Tasklets have long been deprecated as being too heavy on the system by running in irq context - and this is not a performance critical path. If a higher priority process wants to run, it must wait

[PATCH 11/40] drm/amd/display/dc/dce120/dce120_timing_generator:

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_timing_generator.c:101:6: warning: no previous prototype for ‘dce120_timing_generator_validate_timing’ [-Wmissing-prototypes] drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_timing_

Re: [PATCH] bpf: Hoise pahole version checks into Kconfig

On Tue, Jan 12, 2021 at 3:06 AM Nathan Chancellor wrote: > > After commit da5fb18225b4 ("bpf: Support pre-2.25-binutils objcopy for > vmlinux BTF"), having CONFIG_DEBUG_INFO_BTF enabled but lacking a valid > copy of pahole results in a kernel that will fully compile but fail to > link. The user th

[PATCH 06/40] drm/amd/display/dc/gpio/diagnostics/hw_translate_diag: Include our own header containing prototypes

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/diagnostics/hw_translate_diag.c:37:6: warning: no previous prototype for ‘dal_hw_translate_diag_fpga_init’ [-Wmissing-prototypes] Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian Kön

[PATCH 17/40] drm/amd/display/dc/dce/dce_aux: Remove duplicate line causing 'field overwritten' issue

Fixes the following W=1 kernel build warning(s): In file included from drivers/gpu/drm/amd/amdgpu/../display/dc/dce112/dce112_resource.c:59: drivers/gpu/drm/amd/amdgpu/../include/asic_reg/dce/dce_11_2_sh_mask.h:10014:58: warning: initialized field overwritten [-Woverride-init] drivers/gpu/dr

[PATCH 07/40] drm/amd/display/dc/irq/irq_service: Make local function static

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/irq/irq_service.c:82:31: warning: no previous prototype for ‘find_irq_source_info’ [-Wmissing-prototypes] Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian König" Cc: David Airlie Cc: Dani

[PATCH 27/40] drm/amd/display/dc/dce110/dce110_compressor: Strip out unused function 'controller_id_to_index'

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_compressor.c:429:14: warning: no previous prototype for ‘controller_id_to_index’ [-Wmissing-prototypes] Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian König" Cc: David Air

[PATCH 29/40] drm/amd/display/dc/dce112/dce112_resource: Make local functions and ones called by reference static

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce112/dce112_resource.c:620:22: warning: no previous prototype for ‘dce112_link_encoder_create’ [-Wmissing-prototypes] drivers/gpu/drm/amd/amdgpu/../display/dc/dce112/dce112_resource.c:674:32: warning:

[PATCH 23/40] drm/amd/display/dc/dce110/dce110_mem_input_v: Make local functions static

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_mem_input_v.c:471:6: warning: no previous prototype for ‘dce_mem_input_v_is_surface_pending’ [-Wmissing-prototypes] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_mem_input_v.c:486:6

[PATCH 31/40] drm/amd/display/dc/dce110/dce110_mem_input_v: Include our own header, containing prototypes

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_mem_input_v.c:1034:6: warning: no previous prototype for ‘dce110_mem_input_v_construct’ [-Wmissing-prototypes] Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian König" Cc: Da

Re: [PATCH 0/1] mm: restore full accuracy in COW page reuse

On Sun, Jan 10, 2021 at 11:27 PM John Hubbard wrote: > > There is at least one way to improve this part of it--maybe. It's problematic.. > IMHO, a lot of the bits in page _refcount are still being wasted (even > after GUP_PIN_COUNTING_BIAS overloading), because it's unlikely that > there are man

[PATCH 32/40] drm/amd/display/dc/dce110/Makefile: Ignore -Woverride-init warning

Fixes the following W=1 kernel build warning(s): In file included from drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_resource.c:66: drivers/gpu/drm/amd/amdgpu/../include/asic_reg/dce/dce_11_0_sh_mask.h:5936:51: warning: initialized field overwritten [-Woverride-init] drivers/gpu/drm/

[PATCH 24/40] drm/amd/pm/swsmu/smu11/vangogh_ppt: Make local function 'vangogh_clk_dpm_is_enabled' static

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../pm/swsmu/smu11/vangogh_ppt.c:613:6: warning: no previous prototype for ‘vangogh_clk_dpm_is_enabled’ [-Wmissing-prototypes] Cc: Alex Deucher Cc: "Christian König" Cc: David Airlie Cc: Daniel Vetter Cc: Xiaojian Du

[PATCH 33/40] drm/amd/display/dc/dce110/dce110_resource: Make local functions invoked by reference static

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_resource.c:262:15: warning: initialized field overwritten [-Woverride-init] drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_resource.c:266:2: note: in expansion of macro ‘stream_enc_r

[PATCH 18/40] drm/amd/display/dc/dce112/Makefile: Ignore -Woverride-init warning

This file uses a complex abstracted set of hierarchical macros to setup its applicable register lists within constant structures. However in the case of TMDS_CNTL we wish to mark it as not applicable for this use-case. One method would be to de-const all of the definitions and users, then manually

[PATCH 34/40] drm/amd/display/dc/dce110/dce110_transform_v: Demote kernel-doc abuse

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_transform_v.c:228: warning: bad line:void drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_transform_v.c:233: warning: Function parameter or member 'xfm_dce' not described in 'pro

[PATCH 40/40] drm/amd/display/dc/core/dc_stream: Demote non-conformant kernel-doc headers

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_stream.c:253: warning: Function parameter or member 'pStream' not described in 'dc_optimize_timing_for_fsft' drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_stream.c:253: warning: Function param

[PATCH 36/40] drm/amd/display/dc/dce100/dce100_resource: Make local functions and ones called by reference static

Fixes the following W=1 kernel build warning(s): In file included from drivers/gpu/drm/amd/amdgpu/../display/dc/dce100/dce100_resource.c:54: drivers/gpu/drm/amd/amdgpu/../display/dc/dce100/dce100_resource.c:614:22: warning: no previous prototype for ‘dce100_link_encoder_create’ [-Wmissing-pro

Re: [PATCH -tip V3 0/8] workqueue: break affinity initiatively

On 11/01/21 18:16, Peter Zijlstra wrote: > Sadly it appears like io_uring() uses kthread_create_on_cpu() without > then having any hotplug crud on, so that needs additinoal frobbing. > I noticed that as well sometime ago, and I believed then (still do) this usage is broken. I don't think usage of

[PATCH 22/40] drm/amd/display/dc/dce110/dce110_hw_sequencer: Demote non-conformant kernel-doc header

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_hw_sequencer.c:1639: warning: Function parameter or member 'dc' not described in 'dce110_enable_accelerated_mode' drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_hw_sequencer.c:1639:

[PATCH 30/40] drm/amd/display/dc/dce110/dce110_timing_generator_v: Demote kernel-doc abuse and line up comments

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_generator_v.c:54: warning: Function parameter or member 'tg' not described in 'dce110_timing_generator_v_enable_crtc' drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_g

[PATCH 28/40] drm/amd/display/dc/calcs/dce_calcs: Demote non-conformant kernel-doc function headers

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dce_calcs.c:2753: warning: Function parameter or member 'vbios' not described in 'is_display_configuration_supported' drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dce_calcs.c:2753: warning: Funct

[PATCH 26/40] drm/amd/display/dc/dce110/dce110_timing_generator: Demote kernel-doc abuses to standard function headers

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_generator.c:79: warning: Cannot understand * drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing

[PATCH 21/40] drm/amd/display/dc/dce110/dce110_compressor: Remove unused function 'dce110_get_required_compressed_surfacesize

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_compressor.c:415:6: warning: no previous prototype for ‘dce110_get_required_compressed_surfacesize’ [-Wmissing-prototypes] Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian Kö

[PATCH 25/40] drm/amd/display/dc/dce120/dce120_timing_generator: Remove unused function 'dce120_timing_generator_get_position'

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_timing_generator.c:602:13: warning: ‘dce120_timing_generator_get_position’ defined but not used [-Wunused-function] Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian König"

[PATCH 39/40] drm/amd/display/dc/core/dc_surface: Demote kernel-doc abuse

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_surface.c:119: warning: Cannot understand * Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian König" Cc

[PATCH 37/40] drm/amd/display/dc/dce60/dce60_resource: Make local functions static

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_resource.c:522:17: warning: no previous prototype for ‘dce60_aux_engine_create’ [-Wmissing-prototypes] drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_resource.c:560:20: warning: no prev

[PATCH 38/40] drm/amd/display/dc/dce80/dce80_resource: Make local functions static

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce80/dce80_resource.c:527:17: warning: no previous prototype for ‘dce80_aux_engine_create’ [-Wmissing-prototypes] drivers/gpu/drm/amd/amdgpu/../display/dc/dce80/dce80_resource.c:565:20: warning: no prev

[PATCH 35/40] drm/amd/display/dc/dce60/dce60_timing_generator: Make 'dce60_configure_crc' invoked by reference static

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce60/dce60_timing_generator.c:192:6: warning: no previous prototype for ‘dce60_configure_crc’ [-Wmissing-prototypes] Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian König" Cc: David Airl

Re: [PATCH 2/4] RISC-V: Set current memblock limit

On Sun, Jan 10, 2021 at 7:59 PM Anup Patel wrote: > > On Thu, Jan 7, 2021 at 2:57 PM Atish Patra wrote: > > > > Currently, linux kernel can not use last 4k bytes of addressable space > > because > > IS_ERR_VALUE macro treats those as an error. This will be an issue for RV32 > > as any memblock a

[PATCH 20/40] drm/amd/display/dc/dce110/dce110_timing_generator: Remove unused variable 'value_crtc_vtotal'

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_generator.c: In function ‘dce110_timing_generator_tear_down_global_swap_lock’: drivers/gpu/drm/amd/amdgpu/../display/dc/dce110/dce110_timing_generator.c:1354:12: warning: variable ‘v

[PATCH 15/40] drm/amd/display/dc/dce120/dce120_resource: Staticify local functions

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_resource.c:426:32: warning: no previous prototype for ‘dce120_opp_create’ [-Wmissing-prototypes] drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_resource.c:440:17: warning: no previou

[PATCH 12/40] drm/amd/display/dc/dce120/Makefile: Ignore -Woverride-init warning

This file uses a complex abstracted set of hierarchical macros to setup its applicable register lists within constant structures. However in the case of TMDS_CNTL we wish to mark it as not applicable for this use-case. One method would be to de-const all of the definitions and users, then manually

[PATCH 09/40] drm/amd/display/dc/gpio/diagnostics/hw_factory_diag: Include our own header containing prototypes

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/diagnostics/hw_factory_diag.c:50:6: warning: no previous prototype for ‘dal_hw_factory_diag_fpga_init’ [-Wmissing-prototypes] Cc: Harry Wentland Cc: Leo Li Cc: Alex Deucher Cc: "Christian König"

[PATCH 13/40] drm/amd/display/dc/calcs/dce_calcs: Move some large variables from the stack to the heap

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dce_calcs.c: In function ‘calculate_bandwidth’: drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dce_calcs.c:2016:1: warning: the frame size of 1216 bytes is larger than 1024 bytes [-Wframe-larger-tha

[PATCH 05/40] drm/amd/display/dc/dce/dce_transform: Demote kernel-doc abuse

The header doesn't provide any additional parameter descriptions. Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_transform.c:1104: warning: Cannot understand * Cc: H

[PATCH 16/40] drm/amd/display/dc/dce120/dce120_timing_generator: Demote non-kerneldoc headers

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_timing_generator.c:602:13: warning: ‘dce120_timing_generator_get_position’ defined but not used [-Wunused-function] drivers/gpu/drm/amd/amdgpu/../display/dc/dce120/dce120_timing_generator.c

[PATCH 02/40] drm/amd/display/dc/dce/dce_link_encoder: Remove unused variable 'value0'

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_link_encoder.c: In function ‘dce110_link_encoder_update_mst_stream_allocation_table’: drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_link_encoder.c:1506:11: warning: variable ‘value0’ set but no

[PATCH 04/40] drm/amd/display/dc/dce/dce_opp: Demote non-compliant kernel-doc headers

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_opp.c:109: warning: Function parameter or member 'opp110' not described in 'set_truncation' drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_opp.c:109: warning: Function parameter or member 'param

[PATCH 03/40] drm/amd/display/dc/gpio/hw_ddc: Remove unused variable 'reg2'

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/hw_ddc.c: In function ‘set_config’: drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/hw_ddc.c:110:13: warning: variable ‘reg2’ set but not used [-Wunused-but-set-variable] Cc: Harry Wentland Cc: Leo L

[PATCH 00/40] [Set 12] Rid W=1 warnings from GPU

MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. Lee Jones (40): drm/amd/display/dc/dce/dce_aux: Mark 'd

[PATCH 01/40] drm/amd/display/dc/dce/dce_aux: Mark 'dce_aux_transfer_raw' as __maybe_unused

Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_aux.c: In function ‘dce_aux_transfer_raw’: drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_aux.c:579:7: warning: variable ‘bytes_replied’ set but not used [-Wunused-but-set-variable] Cc: Harry W

Re: [PATCH v13 05/15] s390/vfio-ap: manage link between queue struct and matrix mdev

On Tue, 22 Dec 2020 20:15:56 -0500 Tony Krowiak wrote: > Let's create links between each queue device bound to the vfio_ap device > driver and the matrix mdev to which the queue's APQN is assigned. The idea > is to facilitate efficient retrieval of the objects representing the queue > devices and

Re: [PATCH 5/7] regulator: qcom-labibb: Implement short-circuit and over-current IRQs

Il 11/01/21 14:57, Mark Brown ha scritto: On Sat, Jan 09, 2021 at 02:29:19PM +0100, AngeloGioacchino Del Regno wrote: + /* If the regulator is not enabled, this is a fake event */ + if (!ops->is_enabled(vreg->rdev)) + return 0; Or handling the interrupt raced with a

[tip: x86/urgent] x86/sev-es: Handle string port IO to kernel memory properly

The following commit has been merged into the x86/urgent branch of tip: Commit-ID: 7024f60d655272bd2ca1d3a4c9e0a63319b1eea1 Gitweb: https://git.kernel.org/tip/7024f60d655272bd2ca1d3a4c9e0a63319b1eea1 Author:Hyunwook (Wooky) Baek AuthorDate:Sat, 09 Jan 2021 23:11:02 -08:00

Re: [PATCH 04/14] mfd: arizona: Allow building arizona MFD-core as module

Hi, First of all thank you for the review and for all your comments (also in the other part of the thread). On 12/29/20 1:00 PM, Charles Keepax wrote: > On Sun, Dec 27, 2020 at 10:12:22PM +0100, Hans de Goede wrote: >> There is no reason why the arizona core,irq and codec model specific >> regmap

Re: [PATCH v3] kasan: remove redundant config option

On Mon, Jan 11, 2021 at 08:03:29PM +0100, Andrey Konovalov wrote: > On Mon, Jan 11, 2021 at 7:59 PM Nathan Chancellor > wrote: > > > > > > -config KASAN_STACK_ENABLE > > > > +config KASAN_STACK > > > > bool "Enable stack instrumentation (unsafe)" if CC_IS_CLANG && > > > > !COMPILE_TEST >

[RELEASE] LTTng-modules 2.11.7 and 2.12.4 (Linux kernel tracer)

Hi, I just released versions 2.11.7 and 2.12.4 of the lttng-modules stable branches. These add support for the 5.10 Linux kernel. Please try them out, and, as usual, feedback is welcome! Thanks, Mathieu Project website: https://lttng.org Documentation: https://lttng.org/docs Download link: htt

Re: [PATCH 06/15] dt_bindings: regulator: Add ROHM BD71815 PMIC regulators

On Fri, Jan 08, 2021 at 03:36:38PM +0200, Matti Vaittinen wrote: > Add binding documentation for regulators on ROHM BD71815 PMIC. > 5 bucks, 7 LDOs and a boost for LED. > > Signed-off-by: Matti Vaittinen > --- > .../regulator/rohm,bd71815-regulator.yaml | 104 ++ > 1 file cha

Re: [PATCH v5 4/4] drm/dp: Revert "drm/dp: Introduce EDID-based quirks"

On Mon, 11 Jan 2021, Jani Nikula wrote: > On Thu, 07 Jan 2021, Lyude Paul wrote: >> This reverts commit 0883ce8146ed6074c76399f4e70dbed788582e12. Originally >> these quirks were added because of the issues with using the eDP >> backlight interfaces on certain laptop panels, which made it impossib

Re: [PATCH v5 4/4] drm/dp: Revert "drm/dp: Introduce EDID-based quirks"

On Thu, 07 Jan 2021, Lyude Paul wrote: > This reverts commit 0883ce8146ed6074c76399f4e70dbed788582e12. Originally > these quirks were added because of the issues with using the eDP > backlight interfaces on certain laptop panels, which made it impossible > to properly probe for DPCD backlight supp

[PATCH V5 3/3] drm/vkms: Add information about module options

Update vkms documentation to contain usage of `modinfo` command and steps to load vkms with module options enabled. Signed-off-by: Sumera Priyadarsini --- Documentation/gpu/vkms.rst | 12 1 file changed, 12 insertions(+) diff --git a/Documentation/gpu/vkms.rst b/Documentation/gpu/v

Re: [PATCH v5 3/4] drm/i915/dp: Allow forcing specific interfaces through enable_dpcd_backlight

On Thu, 07 Jan 2021, Lyude Paul wrote: > Since we now support controlling panel backlights through DPCD using > both the standard VESA interface, and Intel's proprietary HDR backlight > interface, we should allow the user to be able to explicitly choose > between one or the other in the event that

[PATCH V5 2/3] drm/vkms: Add support for writeback module

Add enable_writeback feature to vkms_config as a module. Signed-off-by: Sumera Priyadarsini --- drivers/gpu/drm/vkms/vkms_drv.c| 5 + drivers/gpu/drm/vkms/vkms_drv.h| 1 + drivers/gpu/drm/vkms/vkms_output.c | 9 ++--- 3 files changed, 12 insertions(+), 3 deletions(-) diff --git

Re: [PATCH 05/15] dt_bindings: mfd: Add ROHM BD71815 PMIC

On Fri, Jan 08, 2021 at 03:34:52PM +0200, Matti Vaittinen wrote: > Document DT bindings for ROHM BD71815. > > BD71815 is a single-chip power management IC mainly for battery-powered > portable devices. The IC integrates 5 bucks, 7 LDOs, a boost driver for > LED, a battery charger with a Coulomb co

Re: [PATCH v3] iio: sx9310: Fix semtech,avg-pos-strength setting when > 16

Quoting Stephen Boyd (2020-12-02 12:02:52) > This DT property can be 0, 16, and then 64, but not 32. The math here > doesn't recognize this slight bump in the power of 2 numbers and > translates a DT property of 64 into the register value '3' when it > really should be '2'. Fix it by subtracting on

[PATCH V5 1/3] drm/vkms: Add vkms_config type

Currently, data for the device instance is held by vkms_device. Add a separate type, vkms_config to contain configuration details for the device and various modes to be later used by configfs. This config data stays constant once the device is created. Accordingly, add vkms_create and vkms_destroy

[PATCH V5 0/3] Decouple config data for configfs

This patchset aims to lay down some prep work before configfs can be implemented for the vkms driver. The first patch in the series adds a new type vkms_config to track device configuration. The second and third patch add module testing support for writeback operations. The first patch is develope

Re: [PATCH v5 2/4] drm/i915/dp: Enable Intel's HDR backlight interface (only SDR for now)

On Thu, 07 Jan 2021, Lyude Paul wrote: > So-recently a bunch of laptops on the market have started using DPCD > backlight controls instead of the traditional DDI backlight controls. > Originally we thought we had this handled by adding VESA backlight > control support to i915, but the story ended

Re: [PATCH 5.10 109/145] mm: make wait_on_page_writeback() wait for multiple pending writebacks

On Mon, Jan 11, 2021 at 9:55 AM Hugh Dickins wrote: > > I think it's too early to push this one through to stable: > Linus mentioned on Friday that Michael Larabel of Phoronix > has observed a performance regression from this commit. That turned out to be a red herring. Yes, Michael saw a perform

Re: [PATCH v3] kasan: remove redundant config option

On Mon, Jan 11, 2021 at 7:59 PM Nathan Chancellor wrote: > > > > -config KASAN_STACK_ENABLE > > > +config KASAN_STACK > > > bool "Enable stack instrumentation (unsafe)" if CC_IS_CLANG && > > > !COMPILE_TEST > > > > Does this syntax mean that KASAN_STACK is only present for > > CC_IS_CLANG

Re: [PATCH v5 1/4] drm/i915: Keep track of pwm-related backlight hooks separately

On Thu, 07 Jan 2021, Lyude Paul wrote: > Currently, every different type of backlight hook that i915 supports is > pretty straight forward - you have a backlight, probably through PWM > (but maybe DPCD), with a single set of platform-specific hooks that are > used for controlling it. > > HDR backl

Re: [v3 PATCH 02/11] mm: vmscan: consolidate shrinker_maps handling code

On Wed, Jan 6, 2021 at 4:14 PM Roman Gushchin wrote: > > On Tue, Jan 05, 2021 at 02:58:08PM -0800, Yang Shi wrote: > > The shrinker map management is not really memcg specific, it's just > > allocation > > In the current form it doesn't look so, especially because each name > has a memcg_ prefix

Re: [PATCH V2] x86/sev-es: Fix SEV-ES #VC handler for string port IO

On Mon, Jan 11, 2021 at 12:29:08PM -0600, Tom Lendacky wrote: > Shouldn't this have a Fixes: tag? Yah, moving to x86/urgent after a quick IRC clarification. Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette

Re: [PATCH v3] kasan: remove redundant config option

On Mon, Jan 11, 2021 at 06:49:37PM +0100, Andrey Konovalov wrote: > On Fri, Jan 8, 2021 at 5:09 AM Walter Wu wrote: > > > > CONFIG_KASAN_STACK and CONFIG_KASAN_STACK_ENABLE both enable KASAN stack > > instrumentation, but we should only need one config, so that we remove > > CONFIG_KASAN_STACK_ENA

Re: [PATCH net-next 1/5] skbuff: rename fields of struct napi_alloc_cache to be more intuitive

On Mon, Jan 11, 2021 at 06:28:21PM +, Alexander Lobakin wrote: > skb_cache and skb_count fields are used to store skbuff_heads queued > for freeing to flush them by bulks, and aren't related to allocation > path. Give them more obvious names to improve code understanding and > allow to expand t

Re: [v3 PATCH 03/11] mm: vmscan: use shrinker_rwsem to protect shrinker_maps allocation

On Mon, Jan 11, 2021 at 9:34 AM Kirill Tkhai wrote: > > On 11.01.2021 20:08, Yang Shi wrote: > > On Wed, Jan 6, 2021 at 1:55 AM Kirill Tkhai wrote: > >> > >> On 06.01.2021 01:58, Yang Shi wrote: > >>> Since memcg_shrinker_map_size just can be changd under holding > >>> shrinker_rwsem > >>> exclu

Re: [PATCH bpf-next 1/4] bpf: enable task local storage for tracing programs

On Fri, Jan 08, 2021 at 03:19:47PM -0800, Song Liu wrote: [ ... ] > diff --git a/kernel/bpf/bpf_local_storage.c b/kernel/bpf/bpf_local_storage.c > index dd5aedee99e73..9bd47ad2b26f1 100644 > --- a/kernel/bpf/bpf_local_storage.c > +++ b/kernel/bpf/bpf_local_storage.c > @@ -140,17 +140,18 @@ static

Re: [PATCH v1 (RFC)] docs: discourage users from using bugzilla.kernel.org

Am 11.01.21 um 19:14 schrieb Randy Dunlap: > On 1/10/21 4:10 AM, Thorsten Leemhuis wrote: >> * About 66 of those ~200 components will assign bugs to email addresses >> that look valid, but 125 of them end with @kernel-bugs.osdl.org or >> @kernel-bugs.kernel.org. Those domains do not exist anymo

Re: [PATCH V2] x86/sev-es: Fix SEV-ES #VC handler for string port IO

On Mon, 11 Jan 2021, Tom Lendacky wrote: > > Don't assume dest/source buffers are userspace addresses when manually > > copying data for string I/O or MOVS MMIO, as {get,put}_user() will fail > > if handed a kernel address and ultimately lead to a kernel panic. > > > > Signed-off-by: Hyunwook (Wo

Re: [PATCH 00/14] MFD/extcon/ASoC: Add support for Intel Bay Trail boards with WM5102 codec

Hi, On 12/28/20 3:19 PM, Andy Shevchenko wrote: > On Sun, Dec 27, 2020 at 11:15 PM Hans de Goede wrote: >> >> Hi All, >> >> This patch series adds support for Intel Bay Trail based device which use >> a WM5102 codec for audio output/input. This was developed and tested on a >> Lenovo Yoga Tablet

Re: [PATCH V5 1/8] remoteproc: introduce is_iomem to rproc_mem_entry

On Tue, Dec 29, 2020 at 11:30:12AM +0800, peng@nxp.com wrote: > From: Peng Fan > > Introduce is_iomem to indicate this piece memory is iomem or not. > > Reviewed-by: Bjorn Andersson > Signed-off-by: Peng Fan > --- > include/linux/remoteproc.h | 2 ++ > 1 file changed, 2 insertions(+) Rev

<    2   3   4   5   6   7   8   9   10   11   >