Use the regular fbdev helpers for framebuffer I/O instead of DRM's
helpers. Tegra does not use damage handling, so DRM's fbdev helpers
are mere wrappers around the fbdev code.
By using fbdev helpers directly within each DRM fbdev emulation,
we can eventually remove DRM's wrapper functions
Use the regular fbdev helpers for framebuffer I/O instead of DRM's
helpers. Fbdev-dma does not use damage handling, so DRM's fbdev helpers
are mere wrappers around the fbdev code.
By using fbdev helpers directly within each DRM fbdev emulation,
we can eventually remove DRM's wrapper functions
Implement dedicated fbdev helpers for framebuffer I/O instead
of using DRM's helpers. Use an fbdev generator macro for
deferred I/O to create the callbacks. Fbdev-generic was the
only caller of the DRM helpers, so remove them from the helper
module.
v4:
* generate deferred-I/O helpers
Use the regular fbdev helpers for framebuffer I/O instead of DRM's
helpers. Msm does not use damage handling, so DRM's fbdev helpers
are mere wrappers around the fbdev code.
By using fbdev helpers directly within each DRM fbdev emulation,
we can eventually remove DRM's wrapper functions entirely.
Use the regular fbdev helpers for framebuffer I/O instead of DRM's
helpers. Exynos does not use damage handling, so DRM's fbdev helpers
are mere wrappers around the fbdev code.
By using fbdev helpers directly within each DRM fbdev emulation,
we can eventually remove DRM's wrapper functions
Export drm_fb_helper_damage() and drm_fb_helper_damage_range(), which
handle damage areas for fbdev emulation. This is a temporary export
that allows to move the DRM I/O helpers for fbdev into drivers. Only
fbdev-generic and i915 need them. Both will be updated to implement
damage handling by
Use the regular fbdev helpers for framebuffer I/O instead of DRM's
helpers. Omapdrm does not use damage handling, so DRM's fbdev helpers
are mere wrappers around the fbdev code.
By using fbdev helpers directly within each DRM fbdev emulation,
we can eventually remove DRM's wrapper functions
Use the regular fbdev helpers for framebuffer I/O instead of DRM's
helpers. Armada does not use damage handling, so DRM's fbdev helpers
are mere wrappers around the fbdev code.
By using fbdev helpers directly within each DRM fbdev emulation,
we can eventually remove DRM's wrapper functions
DRM provides a number of wrappers around fbdev cfb_() sys_(), fb_io_()
and fb_sys_() helpers. The DRM functions don't provide any additional
functionality for most DRM drivers. So remove them and call the fbdev
I/O helpers directly.
The DRM fbdev I/O wrappers were originally added because
does
Use the regular fbdev helpers for framebuffer I/O instead of DRM's
helpers. Radeon does not use damage handling, so DRM's fbdev helpers
are mere wrappers around the fbdev code.
By using fbdev helpers directly within each DRM fbdev emulation,
we can eventually remove DRM's wrapper functions
For framebuffers in I/O and system memory, add macros that set
struct fb_ops to the respective callback functions.
For deferred I/O, add macros that generate callback functions with
damage handling. Add initializer macros that set struct fb_ops to
the generated callbacks.
These macros can remove
Use the regular fbdev helpers for framebuffer I/O instead of DRM's
helpers. Gma500 does not use damage handling, so DRM's fbdev helpers
are mere wrappers around the fbdev code.
By using fbdev helpers directly within each DRM fbdev emulation,
we can eventually remove DRM's wrapper functions
Many fbdev drivers use the same set of fb_ops helpers. Add Kconfig
options to select them at once. This will help with making DRM's
fbdev emulation code more modular, but can also be used to simplify
fbdev's driver configs.
v3:
* fix select statement (Jingfeng)
Signed-off-by: Thomas
On Tue, May 23, 2023 at 02:53:44PM -0700, Justin Chen wrote:
> Add support for the Broadcom ASP 2.0 Ethernet controller which is first
> introduced with 72165. This controller features two distinct Ethernet
> ports that can be independently operated.
>
> This patch supports:
>
> - Wake-on-LAN
On 23.05.2023 17:19, Ashutosh Dixit wrote:
No functional changes but we can remove some unsightly index computation
and read/write functions if we convert the PMU sample array from a
one-dimensional to a two-dimensional array.
Suggested-by: Tvrtko Ursulin
Signed-off-by: Ashutosh Dixit
On 23.05.2023 17:19, Ashutosh Dixit wrote:
pmu_needs_timer() keeps the timer running even when GT is parked,
ostensibly to sample requested/actual frequencies. However
frequency_sample() has the following:
/* Report 0/0 (actual/requested) frequency while parked. */
if
No functional modification involved.
drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn321/dcn321_fpu.c:556
dcn321_update_bw_bounding_box_fpu() warn: inconsistent indenting.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=5304
Signed-off-by: Jiapeng Chong
---
No functional modification involved.
drivers/gpu/drm/amd/amdgpu/../display/dc/dml/dcn314/dcn314_fpu.c:269
dcn314_update_bw_bounding_box_fpu() warn: inconsistent indenting.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=5305
Signed-off-by: Jiapeng Chong
---
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #87 from Stuart Foster (smf-li...@virginmedia.com) ---
Is it worth the effort of bisecting this as it seems to be on a lot of kernel
versions ?
thanks
--
You may reply to this email to add a comment.
You are receiving this mail
Fixes compilation issues with older GCC versions and Clang after
changes introduced in commit 6810bb390282 ("drm/panel: Add Samsung
S6D7AA0 panel controller driver"). Tested with GCC 13.1.1, GCC 6.4.0
and Clang 16.0.3.
Fixes the following errors with Clang:
From: Phi-bang Nguyen
This is a new driver that supports the MIPI CSI CD-PHY version 0.5
The number of PHYs depend on the SoC.
Each PHY can support D-PHY only or CD-PHY configuration.
The driver supports only D-PHY mode, so CD-PHY
compatible PHY are configured in D-PHY mode.
Signed-off-by:
From: Florian Sylvestre
This adds the bindings, for the MIPI CD-PHY module v0.5 embedded in
some Mediatek soc, such as the mt8365
Signed-off-by: Florian Sylvestre
Signed-off-by: Julien Stephan
---
.../bindings/phy/mediatek,mt8365-csi-rx.yaml | 67 +++
MAINTAINERS
Add definition for CDPHY phy type that can be configured in either D-PHY
mode or C-PHY mode
Signed-off-by: Julien Stephan
---
include/dt-bindings/phy/phy.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/dt-bindings/phy/phy.h b/include/dt-bindings/phy/phy.h
index
Adding a new driver for the MIPI CSI CD-PHY module v 0.5 embedded in
some Mediatek soc, such as the MT8365
This driver was adapted from
https://patchwork.kernel.org/project/linux-mediatek/cover/20200708104023.3225-1-louis@mediatek.com/
v1 can be found here:
Hi
On Wed, May 24, 2023 at 10:55:08AM +0300, Oded Gabbay wrote:
> On Wed, May 24, 2023 at 10:49 AM Stanislaw Gruszka
> wrote:
> >
> > Add debugfs support for ivpu driver, most importantly firmware loging
> > and tracing.
> Hi,
> Without looking at the code I have 2 comments/questions:
>
> 1.
On Tue, 23 May 2023 21:14:50 -0100
Melissa Wen wrote:
> Hook up driver-specific atomic operations for managing AMD color
> properties and create AMD driver-specific color management properties
> and attach them according to HW capabilities defined by `struct
> dc_color_caps`. Add enumerated
On 24.05.2023 09:33, liao jaime wrote:
> Hi Miquel
>
>>
>> Hi Arseniy,
>>
>> avkras...@sberdevices.ru wrote on Mon, 15 May 2023 12:49:50 +0300:
>>
>>> Hello @Miquel!
>>>
>>> Sorry, but who could review this patch? :) IIUC this logic is very hw
>>> specific and we need
>>> someone who knows it
On 5/23/2023 9:14 AM, Jeffrey Hugo wrote:
Carl and Pranjal have been reviewing the QAIC patches. List them as
reviewers so that they are copied on all developments which will make
it easier for them to continue reviewing QAIC patches.
Signed-off-by: Jeffrey Hugo
---
MAINTAINERS | 2 ++
1
On 5/23/2023 9:44 PM, Jeffrey Hugo wrote:
Carl and Pranjal have been reviewing the QAIC patches. List them as
reviewers so that they are copied on all developments which will make
it easier for them to continue reviewing QAIC patches.
Signed-off-by: Jeffrey Hugo
---
MAINTAINERS | 2 ++
The call site of nouveau_dsm_pci_probe() uses single set of output
variables for all invocations. So, we must not write anything to them
unless it's an NVIDIA device. Otherwise, if we are called with another
device after the NVIDIA device, we'll clober the result of the NVIDIA
device.
For
Jeffrey Hugo writes:
> On 5/17/2023 8:52 AM, Alexandre Bailon wrote:
>> This adds a DRM driver that implements communication between the CPU and an
>> APU. The driver target embedded device that usually run inference using some
>> prebuilt models. The goal is to provide common infrastructure
Hi Miquel
>
> Hi Arseniy,
>
> avkras...@sberdevices.ru wrote on Mon, 15 May 2023 12:49:50 +0300:
>
> > Hello @Miquel!
> >
> > Sorry, but who could review this patch? :) IIUC this logic is very hw
> > specific and we need
> > someone who knows it well? I tested this patch on our devices (with
This adds support for OTP area access on MX30LFxG18AC chip series.
Signed-off-by: Arseniy Krasnov
---
v1 -> v2:
* Add slab.h include due to kernel test robot error.
v2 -> v3:
* Use 'uint64_t' as input argument for 'do_div()' instead
of 'unsigned long' due to kernel test robot error.
On 22.05.2023 17:14, Miquel Raynal wrote:
> Hi Arseniy,
>
> avkras...@sberdevices.ru wrote on Mon, 15 May 2023 12:49:50 +0300:
>
>> Hello @Miquel!
>>
>> Sorry, but who could review this patch? :) IIUC this logic is very hw
>> specific and we need
>> someone who knows it well? I tested this
This patch is part of the Linux Kernel Bug Fixing Summer screening
tasks. By removing the extra description, several documentation
compilation warnings such as the following have been fixed:
> ./drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:758: warning: Excess function
> parameter 'pcie_index'
On Wed, May 17, 2023 at 01:27:48PM +0200, Petr Tesařík wrote:
> On Wed, 17 May 2023 08:35:10 +0200
> Petr Tesařík wrote:
> > Anyway, my greatest objection to allocating additional swiotlb chunks is
> > that _all_ of them must be searched to determine that the physical
> > address does _not_
On 24/05/2023 09:59, Johan Hovold wrote:
On Tue, May 23, 2023 at 12:23:04PM -0700, Abhinav Kumar wrote:
On 5/23/2023 8:24 AM, Johan Hovold wrote:
On Fri, May 12, 2023 at 09:13:04PM +0300, Dmitry Baryshkov wrote:
On 28/04/2023 02:28, Abhinav Kumar wrote:
On sc7280 where eDP is the primary
On Wed, May 24, 2023 at 10:49 AM Stanislaw Gruszka
wrote:
>
> Add debugfs support for ivpu driver, most importantly firmware loging
> and tracing.
Hi,
Without looking at the code I have 2 comments/questions:
1. Please add an ABI documentation in Documentation/ABI/testing/ or
From: Krystian Pradzynski
Add information about currently used firmware, makes test
automation of different firmware images easier.
Signed-off-by: Krystian Pradzynski
Reviewed-by: Stanislaw Gruszka
Signed-off-by: Stanislaw Gruszka
---
drivers/accel/ivpu/ivpu_debugfs.c | 10 ++
1
From: Andrzej Kacprowski
Firmware file name and version are very important for debugging
customer issues - print them as INFO level message instead
of DEBUG message that is turned off by default.
Signed-off-by: Andrzej Kacprowski
Reviewed-by: Stanislaw Gruszka
Signed-off-by: Stanislaw Gruszka
Add new debugfs files to validate device recovery functionality.
Signed-off-by: Stanislaw Gruszka
---
drivers/accel/ivpu/ivpu_debugfs.c | 41 +++
drivers/accel/ivpu/ivpu_pm.c | 1 +
drivers/accel/ivpu/ivpu_pm.h | 1 +
3 files changed, 43 insertions(+)
Add support for firmware tracing and logging via debugfs.
Signed-off-by: Stanislaw Gruszka
---
drivers/accel/ivpu/Makefile | 3 +-
drivers/accel/ivpu/ivpu_debugfs.c | 169 ++
drivers/accel/ivpu/ivpu_fw.c | 52 -
drivers/accel/ivpu/ivpu_fw.h
Add initial debugfs support. Provide below functionality:
- print buffer objects
- print latest boot mode
- trigger vpu engine reset
Signed-off-by: Stanislaw Gruszka
---
drivers/accel/ivpu/Makefile | 1 +
drivers/accel/ivpu/ivpu_debugfs.c | 74 +++
Add debugfs support for ivpu driver, most importantly firmware loging
and tracing.
Andrzej Kacprowski (1):
accel/ivpu: Print firmware name and version
Krystian Pradzynski (1):
accel/ivpu: Add fw_name file to debugfs
Stanislaw Gruszka (3):
accel/ivpu: Initial debugfs support
accel/ivpu:
The STARRY ili9882t is a 10.51" WUXGA TFT LCD panel,
which fits in nicely with the existing panel-boe-tv101wum-nl6
driver. Hence, we add a new compatible with panel specific config.
Signed-off-by: Cong Yang
---
.../devicetree/bindings/display/panel/boe,tv101wum-nl6.yaml | 2 ++
1 file
The Starry-ili9882 is a 10.51" WUXGA TFT panel. which fits in nicely with
the existing panel-boe-tv101wum-nl6 driver. From the datasheet,MIPI need
to keep the LP11 state before the lcm_reset pin is pulled high. So add
lp11_before_reset flag.
Signed-off-by: Cong Yang
---
The STARRY himax83102-j02 is a 10.51" WUXGA TFT LCD panel,
which fits in nicely with the existing panel-boe-tv101wum-nl6
driver. Hence, we add a new compatible with panel specific config.
Signed-off-by: Cong Yang
---
.../devicetree/bindings/display/panel/boe,tv101wum-nl6.yaml | 2 ++
1 file
The Starry-himax83102-j02 is a 10.51" WUXGA TFT panel. which fits in nicely
with the existing panel-boe-tv101wum-nl6 driver. From the datasheet[1], MIPI
needs to keep the LP11 state before the lcm_reset pin is pulled high, so
increase lp11_before_reset flag.
[1]:
Compare V1:Add compatible for Starry himax83102-j02 and Starry-ili9882t
in dt-bindings.
Cong Yang (4):
drm/panel: Support for Starry-himax83102-j02 TDDI MIPI-DSI panel
dt-bindings: display: panel: Add compatible for Starry himax83102-j02
drm/panel: Support for Starry-ili9882t TDDI MIPI-DSI
On Wed, May 24, 2023 at 07:51:07AM +0100, Conor Dooley wrote:
> Hey Justin,
> On Tue, May 23, 2023 at 04:27:12PM -0700, Justin Chen wrote:
> > On Tue, May 23, 2023 at 3:55 PM Conor Dooley wrote:
> > > On Tue, May 23, 2023 at 02:53:43PM -0700, Justin Chen wrote:
> > >
> > > > + compatible:
> > >
Linux next-20230523 and next-20230524 the x86_64 and i386 builds failed
with clang.
Reported-by: Linux Kernel Functional Testing
make --silent --keep-going \
--jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=x86_64 \
SRCARCH=x86 CROSS_COMPILE=x86_64-linux-gnu- \
'HOSTCC=sccache
On Tue, May 23, 2023 at 12:23:04PM -0700, Abhinav Kumar wrote:
> On 5/23/2023 8:24 AM, Johan Hovold wrote:
> > On Fri, May 12, 2023 at 09:13:04PM +0300, Dmitry Baryshkov wrote:
> >> On 28/04/2023 02:28, Abhinav Kumar wrote:
> >>> On sc7280 where eDP is the primary display, PSR is causing
> >>> IGT
Hey Justin,
On Tue, May 23, 2023 at 04:27:12PM -0700, Justin Chen wrote:
> On Tue, May 23, 2023 at 3:55 PM Conor Dooley wrote:
> > On Tue, May 23, 2023 at 02:53:43PM -0700, Justin Chen wrote:
> >
> > > + compatible:
> > > +enum:
> > > + - brcm,asp-v2.0
> > > + - brcm,bcm72165-asp
>
201 - 253 of 253 matches
Mail list logo
