HI Nikolaus,
On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
Hi Ivaylo,
it took a while until I found time to test newer kernels (mainline + Letux
additions)
on the OMAP5 Pyra but unfortunately I did not get screen display for v6.1. Even
worse,
the console was flooded by
Could you elabo
On Sat, Oct 29, 2022 at 07:34:26PM +0200, Julia Lawall wrote:
>
>
> On Sat, 29 Oct 2022, Deepak R Varma wrote:
>
> > On Sat, Oct 29, 2022 at 09:32:50AM +0200, Greg Kroah-Hartman wrote:
> > > On Fri, Oct 28, 2022 at 07:00:05PM +0530, Deepak R Varma wrote:
> > > > The ARRAY_SIZE(foo) macro should be
Hi Ivaylo,
> Am 31.10.2022 um 08:05 schrieb Ivaylo Dimitrov :
>
> HI Nikolaus,
>
> On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
>> Hi Ivaylo,
>> it took a while until I found time to test newer kernels (mainline + Letux
>> additions)
>> on the OMAP5 Pyra but unfortunately I did not get s
> Am 31.10.2022 um 08:44 schrieb H. Nikolaus Schaller :
>
> Hi Ivaylo,
>
>> Am 31.10.2022 um 08:05 schrieb Ivaylo Dimitrov :
>>
>> HI Nikolaus,
>>
>> On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
>>> Hi Ivaylo,
>>> it took a while until I found time to test newer kernels (mainline + Le
Hi,
On 17/10/2022 14:04, Geraldo Nascimento wrote:
Hi Mark, resending this as it failed to apply in my last submission. Added
Neil Armstrong to Cc: as hopefully he will be able to better review this.
Thanks,
Geraldo Nascimento
---
Starting with version 2.10a of Synopsys DesignWare HDMI contr
On Fri, 28 Oct 2022, "Aurélien" wrote:
> Hi,
>
> I come back on my problem regarding the development of a specific driver
> which controls the brightness of my OLED device.
>
>> If it's eDP and uses some proprietary DPCD brightness control mechanism,
>> I think in practice it usually is somewhat
On Mon, Oct 31, 2022 at 12:41:40PM +0530, Deepak Varma wrote:
> On Sat, Oct 29, 2022 at 07:34:26PM +0200, Julia Lawall wrote:
> >
> >
> > On Sat, 29 Oct 2022, Deepak R Varma wrote:
> >
> > > On Sat, Oct 29, 2022 at 09:32:50AM +0200, Greg Kroah-Hartman wrote:
> > > > On Fri, Oct 28, 2022 at 07:00:05
On Mon, Oct 31, 2022 at 03:10:27PM +0530, Deepak Varma wrote:
> On Mon, Oct 31, 2022 at 12:41:40PM +0530, Deepak Varma wrote:
> > On Sat, Oct 29, 2022 at 07:34:26PM +0200, Julia Lawall wrote:
> > >
> > >
> > > On Sat, 29 Oct 2022, Deepak R Varma wrote:
> > >
> > > > On Sat, Oct 29, 2022 at 09:32:50
ping. Any comments?
Am 25.10.22 um 12:17 schrieb Thomas Zimmermann:
This patchset adds the callbacks begin_fb_access and end_fb_access
to struct drm_plane_helper_funcs. They provide hooks to acquire and
release resources that are only held during the commit. It adds
related simple-KMS helpers an
Merged into drm-misc-fixes
Am 27.10.22 um 15:57 schrieb Hector Martin:
drm_fb_build_fourcc_list() currently returns all emulated formats
unconditionally as long as the native format is among them, even though
not all combinations have conversion helpers. Although the list is
arguably provided to
On Sat, Oct 29, 2022 at 12:59:35AM +0530, Badal Nilawar wrote:
> This workaround is added for Media Tile of MTL A step. It is to help
> pcode workaround which handles the hardware bug seen on CXL splitter
> during package C2/C3 transitins due to MC6 entry/exit. As a part of
> workaround pcode expec
On 31.10.22 г. 9:57 ч., H. Nikolaus Schaller wrote:
Am 31.10.2022 um 08:44 schrieb H. Nikolaus Schaller :
Hi Ivaylo,
Am 31.10.2022 um 08:05 schrieb Ivaylo Dimitrov :
HI Nikolaus,
On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
Hi Ivaylo,
it took a while until I found time to test
Hi Ivaylo,
> Am 31.10.2022 um 10:58 schrieb Ivaylo Dimitrov :
>
>
>
> On 31.10.22 г. 9:57 ч., H. Nikolaus Schaller wrote:
>>> Am 31.10.2022 um 08:44 schrieb H. Nikolaus Schaller :
>>>
>>> Hi Ivaylo,
>>>
Am 31.10.2022 um 08:05 schrieb Ivaylo Dimitrov
:
HI Nikolaus,
On 28/10/2022 20:46, john.c.harri...@intel.com wrote:
From: John Harrison
The engine busyness stats has a worker function to do things like
64bit extend the 32bit hardware counters. The GuC's reset prepare
function flushes out this worker function to ensure no corruption
happens during the re
* Ivaylo Dimitrov [221031 06:55]:
> On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
> > [ 39.419846] WARNING: CPU: 0 PID: 3673 at drivers/bus/omap_l3_noc.c:139
> > l3_interrupt_handler+0x23c/0x330
> > [ 39.429914] 4400.l3-noc:L3 Custom Error: MASTER MPU TARGET GPMC
> > (Idle): Data A
On 31.10.22 г. 12:13 ч., Tony Lindgren wrote:
* Ivaylo Dimitrov [221031 06:55]:
On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
[ 39.419846] WARNING: CPU: 0 PID: 3673 at drivers/bus/omap_l3_noc.c:139
l3_interrupt_handler+0x23c/0x330
[ 39.429914] 4400.l3-noc:L3 Custom Error: MAS
On Thu, Oct 27, 2022 at 10:05 AM Viresh Kumar wrote:
> Acked-by: Viresh Kumar
Thanks.
Could someone take a final look and apply this? I don't have drm-misc
commit rights.
Erico
Hi Jason,
On 2022/10/26 02:17, Jason Gunthorpe wrote:
This series provides an alternative container layer for VFIO implemented
using iommufd. This is optional, if CONFIG_IOMMUFD is not set then it will
not be compiled in.
At this point iommufd can be injected by passing in a iommfd FD to
VFIO_G
Hi Dave & Daniel,
Here goes first drm-intel-gt-next pull req towards 6.2.
We have a fix for #6222 (kernel memory corruption issue) and fix for
display regression after resume. A missing W/A for Gen12 iGPUs and
extension of compute pre-emption timeout to 7.5 seconds to account for
compute corner c
On 31.10.22 г. 12:13 ч., Tony Lindgren wrote:
* Ivaylo Dimitrov [221031 06:55]:
On 31.10.22 г. 0:08 ч., H. Nikolaus Schaller wrote:
[ 39.419846] WARNING: CPU: 0 PID: 3673 at drivers/bus/omap_l3_noc.c:139
l3_interrupt_handler+0x23c/0x330
[ 39.429914] 4400.l3-noc:L3 Custom Error: MAS
Shifting signed 32-bit value by 31 bits is undefined, so changing
significant bit to unsigned. The UBSAN warning calltrace like below:
UBSAN: shift-out-of-bounds in ./include/drm/ttm/ttm_tt.h:122:26
left shift of 1 by 31 places cannot be represented in type 'int'
Call Trace:
dump_stack_lvl+0x7d
gcc-13 warns about mismatching types for enums. That revealed switched
arguments of nv50_wndw_new_():
drivers/gpu/drm/nouveau/dispnv50/wndw.c:696:1: error: conflicting types for
'nv50_wndw_new_' due to enum/integer mismatch; have 'int(const struct
nv50_wndw_func *, struct drm_device *, enum drm
rn_vbios_smu_set_dcn_low_power_state() produces a valid warning with
gcc-13:
drivers/gpu/drm/amd/display/dc/clk_mgr/dcn21/rn_clk_mgr_vbios_smu.c:237:6:
error: conflicting types for 'rn_vbios_smu_set_dcn_low_power_state' due to
enum/integer mismatch; have 'void(struct clk_mgr_internal *, enum
d
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.lastclose. It's used to restore the
> fbdev console. But as komeda uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See
> the call to drm_client_dev_restore() in drm_lastclose()
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.lastclose. It's used to restore the
> fbdev console. But as mcde uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See
> the call to drm_client_dev_restore() in drm_lastclose().
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.lastclose. It's used to restore the
> fbdev console. But as vboxvideo uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See
> the call to drm_client_dev_restore() in drm_lastclos
On Mon, 31 Oct 2022, Deepak R Varma wrote:
> On Mon, Oct 31, 2022 at 12:41:40PM +0530, Deepak Varma wrote:
> > On Sat, Oct 29, 2022 at 07:34:26PM +0200, Julia Lawall wrote:
> > >
> > >
> > > On Sat, 29 Oct 2022, Deepak R Varma wrote:
> > >
> > > > On Sat, Oct 29, 2022 at 09:32:50AM +0200, Greg
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.output_poll_changed. It's used to restore
> the fbdev console. But as amdgpu uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See the
> functions drm_kms_helper_hotplug_event()
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.output_poll_changed. It's used to restore
> the fbdev console. But as amdgpu uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See the
> functions drm_kms_helper_hotplug_event()
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.output_poll_changed. It's used to restore
> the fbdev console. But as DCSS uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See the
> functions drm_kms_helper_hotplug_event() an
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.output_poll_changed. It's used to restore
> the fbdev console. But as ingenic uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See the
> functions drm_kms_helper_hotplug_event()
On Mon, Oct 31, 2022 at 06:38:45PM +0800, Yi Liu wrote:
> Hi Jason,
>
> On 2022/10/26 02:17, Jason Gunthorpe wrote:
> > This series provides an alternative container layer for VFIO implemented
> > using iommufd. This is optional, if CONFIG_IOMMUFD is not set then it will
> > not be compiled in.
>
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.output_poll_changed. It's used to restore
> the fbdev console. But as logicvc uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See the
> functions drm_kms_helper_hotplug_event()
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Don't set struct drm_driver.output_poll_changed. It's used to restore
> the fbdev console. But as rockchip uses generic fbdev emulation, the
> console is being restored by the DRM client helpers already. See the
> functions drm_kms_helper_hotplug_event(
Convert cdns,dsi.txt binding to yaml format
Signed-off-by: Rahul T R
Reviewed-by: Rob Herring
---
.../bindings/display/bridge/cdns,dsi.txt | 112 -
.../bindings/display/bridge/cdns,dsi.yaml | 157 ++
2 files changed, 157 insertions(+), 112 deletions(-)
dele
Following series of patches adds supports for CDNS DSI
bridge on j721e.
v9:
- Fixed below based on review comments in v8
- Added more info on wrapper in the commit message
- Fixed the description in Kconfig
- Fixed the formatting of of_match table
- exit -> deinit in platform ops
- Remove du
Create a header file for cdns dsi and move
register offsets and structure to header,
to prepare for adding j721e wrapper support
Signed-off-by: Rahul T R
Reviewed-by: Tomi Valkeinen
---
.../gpu/drm/bridge/cadence/cdns-dsi-core.c| 446 +
.../gpu/drm/bridge/cadence/cdns-dsi-co
Add compatible to support dsi bridge on j721e
Signed-off-by: Rahul T R
Reviewed-by: Rob Herring
---
.../bindings/display/bridge/cdns,dsi.yaml | 25 ++-
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/display/bridge/cdns,dsi.yam
Add support for wrapper settings for DSI bridge on
j721e. Also enable DPI0
--- ---
| ---| |--- |
| DSS | DPI2 |->| DPI0 | DSI Wrapper |
| ---| |--- |
--- --
Move the cadence dsi bridge under drm/bridge/cadence
directory, to prepare for adding j721e wrapper
support
Signed-off-by: Rahul T R
Reviewed-by: Tomi Valkeinen
---
drivers/gpu/drm/bridge/Kconfig| 11 ---
drivers/gpu/drm/bridge/Makefile | 1
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Include for devm_of_find_backlight().
>
> Signed-off-by: Thomas Zimmermann
> ---
Reviewed-by: Javier Martinez Canillas
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Include for of_match_ptr().
>
> Signed-off-by: Thomas Zimmermann
> ---
Reviewed-by: Javier Martinez Canillas
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Only include what we have to.
>
> Signed-off-by: Thomas Zimmermann
> ---
Nice cleanup.
Reviewed-by: Javier Martinez Canillas
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
Hi Tomi,
On 09:12-20221026, Tomi Valkeinen wrote:
> Hi,
>
> On 21/10/2022 20:18, Rahul T R wrote:
> > Add support for wrapper settings for DSI bridge on
> > j721e. Also set the DPI input to DPI0
>
> I think a few more words on the HW layout would be nice. What does the
> wrapper do and how is it
On XE_LPM+ platforms the media engines are carved out into a separate
GT but have a common GGTMMADR address range which essentially makes
the GGTT address space to be shared between media and render GT.
BSPEC: 63834
Cc: Matt Roper
Signed-off-by: Aravind Iddamsetty
---
drivers/gpu/drm/i915/gt/i
On 2022/10/31 20:18, Jason Gunthorpe wrote:
On Mon, Oct 31, 2022 at 06:38:45PM +0800, Yi Liu wrote:
Hi Jason,
On 2022/10/26 02:17, Jason Gunthorpe wrote:
This series provides an alternative container layer for VFIO implemented
using iommufd. This is optional, if CONFIG_IOMMUFD is not set then
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Rename struct drm_fb_helper.fbdev to info. The current name is
> misleading as it overlaps with generic fbdev naming conventions.
> Adapt to the usual naming in fbdev drivers by calling the field
> 'info'. No functional changes.
>
> Signed-off-by: Thom
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Rename drm_fb_helper_alloc_fbi() to drm_fb_helper_alloc_info() as
> part of unifying the naming within fbdev helpers. Adapt drivers. No
> functional changes.
>
> Signed-off-by: Thomas Zimmermann
> ---
Reviewed-by: Javier Martinez Canillas
--
Best
On 31/10/2022 10:09, Tvrtko Ursulin wrote:
On 28/10/2022 20:46, john.c.harri...@intel.com wrote:
From: John Harrison
The engine busyness stats has a worker function to do things like
64bit extend the 32bit hardware counters. The GuC's reset prepare
function flushes out this worker function
On 28/10/2022 18:00, Ceraolo Spurio, Daniele wrote:
On 10/28/2022 1:38 AM, Tvrtko Ursulin wrote:
On 27/10/2022 23:15, Daniele Ceraolo Spurio wrote:
The GSC CS re-uses the same interrupt bits that the GSC used in older
platforms. This means that we can now have an engine interrupt coming
out
On Sun, Oct 30, 2022 at 08:42:52AM -0600, jim.cro...@gmail.com wrote:
> On Thu, Oct 27, 2022 at 2:10 PM Ville Syrjälä
> wrote:
> >
> > On Thu, Oct 27, 2022 at 01:55:39PM -0600, jim.cro...@gmail.com wrote:
> > > On Thu, Oct 27, 2022 at 9:59 AM Ville Syrjälä
> > > wrote:
> > > >
> > > > On Thu, Oct
WA 18017747507 applies to all DG2 skus.
BSpec: 56035, 46121, 68173
Signed-off-by: Wayne Boyer
---
drivers/gpu/drm/i915/gt/intel_gt_regs.h | 3 +++
drivers/gpu/drm/i915/gt/intel_workarounds.c | 3 +++
2 files changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_gt_regs.h
b/d
https://bugzilla.kernel.org/show_bug.cgi?id=216645
Bug ID: 216645
Summary: Fence fallback timer expired on ring gfx
Product: Drivers
Version: 2.5
Kernel Version: 5.15.0-43-generic
Hardware: All
OS: Linux
Tree:
https://bugzilla.kernel.org/show_bug.cgi?id=216645
Martin Šušla (ask4supp...@email.cz) changed:
What|Removed |Added
Attachment #303109|Kernel log created by the |Kernel log created b
On 10/24/22 13:19, Thomas Zimmermann wrote:
> Rename drm_fb_helper_unregister_fbi() to drm_fb_helper_unregister_info()
> as part of unifying the naming within fbdev helpers. Adapt drivers. No
> functional changes.
>
> Signed-off-by: Thomas Zimmermann
> ---
Reviewed-by: Javier Martinez Canillas
Il 28/10/22 08:55, Mark-PK Tsai ha scritto:
Remove duplicated 'by' from comment in cma_heap_allocate().
Signed-off-by: Mark-PK Tsai
Reviewed-By: Mukesh Ojha
Acked-by: John Stultz
Reviewed-by: AngeloGioacchino Del Regno
Hi Rodrigo,
On 31-10-2022 15:19, Rodrigo Vivi wrote:
On Sat, Oct 29, 2022 at 12:59:35AM +0530, Badal Nilawar wrote:
This workaround is added for Media Tile of MTL A step. It is to help
pcode workaround which handles the hardware bug seen on CXL splitter
during package C2/C3 transitins due to MC
On 2022-10-31 07:42, Jiri Slaby (SUSE) wrote:
> rn_vbios_smu_set_dcn_low_power_state() produces a valid warning with
> gcc-13:
> drivers/gpu/drm/amd/display/dc/clk_mgr/dcn21/rn_clk_mgr_vbios_smu.c:237:6:
> error: conflicting types for 'rn_vbios_smu_set_dcn_low_power_state' due to
> enum/integer
On Fri, Oct 28, 2022 at 11:22 PM Alex Hung wrote:
>
> This is a copy-and-paste error. Fix the comment to match the macro
> definition.
>
> Signed-off-by: Alex Hung
Reviewed-by: Alex Deucher
> ---
> drivers/gpu/drm/amd/display/dc/dml/dcn10/dcn10_fpu.h | 2 +-
> 1 file changed, 1 insertion(+),
On 2022-10-29 15:13, Filip Moc wrote:
> There are some devices on which amdgpu won't allow user to set brightness
> to sufficiently low values even though the hardware would support it just
> fine.
>
> This usually happens in two cases when either configuration of brightness
> levels via ACPI/ATIF
On 2022-10-28 16:44, Hamza Mahfooz wrote:
> As of commit 09a5df6c444c ("drm/amd/display: Fix multi-display support
> for idle opt workqueue"), vblank_lock is no longer being used. So, don't
> init it in amdgpu_dm_init() and remove it from struct
> amdgpu_display_manager.
>
> Signed-off-by: Hamza M
Racing conflict could be:
task A task B
list_for_each_entry
strcmp(h->name))
list_for_each_entry
strcmp(h->name)
kzallockzalloc
.. .
device_create device_create
list_add
On 10/31/2022 5:55 AM, Tvrtko Ursulin wrote:
On 28/10/2022 18:00, Ceraolo Spurio, Daniele wrote:
On 10/28/2022 1:38 AM, Tvrtko Ursulin wrote:
On 27/10/2022 23:15, Daniele Ceraolo Spurio wrote:
The GSC CS re-uses the same interrupt bits that the GSC used in older
platforms. This means that
On Fri, 21 Oct 2022, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> The Cerf, H3100, Badge4, Hackkit, LART, NanoEngine, PLEB, Shannon and
> Simpad machines were all marked as unused as there are no known users
> left. Remove all of these, along with references to them in defconfig
> files and dr
On Sun, Oct 30, 2022 at 5:26 AM Filip Moc wrote:
>
> There are some devices on which amdgpu won't allow user to set brightness
> to sufficiently low values even though the hardware would support it just
> fine.
>
> This usually happens in two cases when either configuration of brightness
> levels
https://bugzilla.kernel.org/show_bug.cgi?id=216645
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=216645
--- Comment #2 from Alex Deucher (alexdeuc...@gmail.com) ---
Are you getting interrupts on the GPU? Check /proc/interrupts to see if you
are getting interrupts for the GPU.
--
You may reply to this email to add a comment.
You are receiving thi
On Thu, Oct 27, 2022 at 8:57 AM Hector Martin wrote:
>
> drm_fb_build_fourcc_list() currently returns all emulated formats
> unconditionally as long as the native format is among them, even though
> not all combinations have conversion helpers. Although the list is
> arguably provided to userspace
On Thu, Oct 27, 2022 at 03:15:50PM -0700, Daniele Ceraolo Spurio wrote:
> Starting on MTL, the GSC is no longer managed with direct MMIO access,
> but we instead have a dedicated command streamer for it. As a first step
> for adding support for this CS, add the required definitions.
> Note that, al
Summary:
* Add support to turn on/off backlight when changing values in bl_power
file. This is achieved by using function backlight_get_brightness()
in nva3_set_intensity to get current brightness.
Test plan:
* Turn off:
echo 1 > /sys/class/backlight/nv_backlight/bl_power
* Turn on:
echo 0
On 10/31/2022 9:26 AM, Matt Roper wrote:
On Thu, Oct 27, 2022 at 03:15:50PM -0700, Daniele Ceraolo Spurio wrote:
Starting on MTL, the GSC is no longer managed with direct MMIO access,
but we instead have a dedicated command streamer for it. As a first step
for adding support for this CS, add
On 01/11/2022 01.15, Justin Forbes wrote:
> On Thu, Oct 27, 2022 at 8:57 AM Hector Martin wrote:
>>
>> drm_fb_build_fourcc_list() currently returns all emulated formats
>> unconditionally as long as the native format is among them, even though
>> not all combinations have conversion helpers. Altho
Hi!
I used to be able to do:
pavel@duo:~$ xrandr --output HDMI1 --mode 1920x1080 --primary
warning: output HDMI1 not found; ignoring
pavel@duo:~$ xrandr --output VGA1 --mode 1280x1024 --below HDMI1
warning: output VGA1 not found; ignoring
...but now I have to do:
pavel@duo:~$ xrandr
Did you change which xorg DDX you are using? E.g., between
xf86-video-modesetting and a xf86-video-[i915/radeon/amdgpu/etc.]?
They may have different naming conventions.
Alex
On Mon, Oct 31, 2022 at 1:04 PM Pavel Machek wrote:
>
> Hi!
>
> I used to be able to do:
>
> pavel@duo:~$ xrandr --o
On Mon, Oct 31, 2022 at 05:58:34PM +0100, Pavel Machek wrote:
> Hi!
>
> I used to be able to do:
>
> pavel@duo:~$ xrandr --output HDMI1 --mode 1920x1080 --primary
> warning: output HDMI1 not found; ignoring
> pavel@duo:~$ xrandr --output VGA1 --mode 1280x1024 --below HDMI1
> warning: outp
The downstream code from which this was derived didn't ever run through
this 'switch' block with non-AFBC formats, but the upstream code does --
we use this function to probe whether a given format is supported.
Demote the warning to eliminate this sort of warning seen on every
boot:
[drm] unsu
Hi!
> > I used to be able to do:
> >
> > pavel@duo:~$ xrandr --output HDMI1 --mode 1920x1080 --primary
> > warning: output HDMI1 not found; ignoring
> > pavel@duo:~$ xrandr --output VGA1 --mode 1280x1024 --below HDMI1
> > warning: output VGA1 not found; ignoring
> >
> > ...but now I have
FIELD_PREP and REG_FIELD_PREP have checks requiring a compile time constant
mask. When the mask comes in as the argument of a function these checks can
can fail depending on the compiler (gcc vs clang), optimization level,
etc. Use a simpler version of FIELD_PREP which skips these checks. The
check
On Mon, Oct 31, 2022 at 1:19 PM Pavel Machek wrote:
>
> Hi!
>
> > > I used to be able to do:
> > >
> > > pavel@duo:~$ xrandr --output HDMI1 --mode 1920x1080 --primary
> > > warning: output HDMI1 not found; ignoring
> > > pavel@duo:~$ xrandr --output VGA1 --mode 1280x1024 --below HDMI1
> >
An HBR3-capable device shall also support TPS4. Since TPS4 feature
had been implemented already, it is not necessary to limit link
rate at HBR2 (5.4G). This patch remove this limitation to support
HBR3 (8.1G) link rate.
Signed-off-by: Kuogee Hsieh
---
drivers/gpu/drm/msm/dp/dp_panel.c | 4
On Mon, Oct 31, 2022 at 06:19:52PM +0100, Pavel Machek wrote:
> Hi!
>
> > > I used to be able to do:
> > >
> > > pavel@duo:~$ xrandr --output HDMI1 --mode 1920x1080 --primary
> > > warning: output HDMI1 not found; ignoring
> > > pavel@duo:~$ xrandr --output VGA1 --mode 1280x1024 --below H
On Mon, Oct 31, 2022 at 06:01:11PM +0530, Aravind Iddamsetty wrote:
> On XE_LPM+ platforms the media engines are carved out into a separate
> GT but have a common GGTMMADR address range which essentially makes
> the GGTT address space to be shared between media and render GT.
While this is all tru
https://bugzilla.kernel.org/show_bug.cgi?id=216645
--- Comment #3 from Martin Šušla (ask4supp...@email.cz) ---
After the message mention in title appears, not even a single interrupt is
registered.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are wat
https://bugzilla.kernel.org/show_bug.cgi?id=216645
--- Comment #4 from Martin Šušla (ask4supp...@email.cz) ---
Created attachment 303110
--> https://bugzilla.kernel.org/attachment.cgi?id=303110&action=edit
Kernel log interlaced with contents of /proc/interrupts polled every second
#! /bin/sh
p
https://bugzilla.kernel.org/show_bug.cgi?id=216645
--- Comment #5 from Martin Šušla (ask4supp...@email.cz) ---
(In reply to Martin Šušla from comment #3)
> After the message mention in title appears, not even a single interrupt is
> registered.
(Valid for both interrupts of the amdgpu driver.)
-
On Mon, Oct 31, 2022 at 11:52 AM Hector Martin wrote:
>
> On 01/11/2022 01.15, Justin Forbes wrote:
> > On Thu, Oct 27, 2022 at 8:57 AM Hector Martin wrote:
> >>
> >> drm_fb_build_fourcc_list() currently returns all emulated formats
> >> unconditionally as long as the native format is among them,
On 10/31/2022 05:51, Tvrtko Ursulin wrote:
On 31/10/2022 10:09, Tvrtko Ursulin wrote:
On 28/10/2022 20:46, john.c.harri...@intel.com wrote:
From: John Harrison
The engine busyness stats has a worker function to do things like
64bit extend the 32bit hardware counters. The GuC's reset prepare
f
On Mon, Oct 31, 2022 at 09:43:33AM -0700, Ceraolo Spurio, Daniele wrote:
>
>
> On 10/31/2022 9:26 AM, Matt Roper wrote:
> > On Thu, Oct 27, 2022 at 03:15:50PM -0700, Daniele Ceraolo Spurio wrote:
> > > Starting on MTL, the GSC is no longer managed with direct MMIO access,
> > > but we instead hav
On 31/10/2022 20:27, Kuogee Hsieh wrote:
An HBR3-capable device shall also support TPS4. Since TPS4 feature
had been implemented already, it is not necessary to limit link
rate at HBR2 (5.4G). This patch remove this limitation to support
HBR3 (8.1G) link rate.
The DP driver supports several pla
On Fri, Oct 21, 2022 at 5:55 PM Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> The Cerf, H3100, Badge4, Hackkit, LART, NanoEngine, PLEB, Shannon and
> Simpad machines were all marked as unused as there are no known users
> left. Remove all of these, along with references to them in defconfig
> f
On 10/29/2022 4:38 AM, Dmitry Baryshkov wrote:
On 29/10/2022 01:59, Jessica Zhang wrote:
Loosen the requirements for atomic and legacy commit so that, in cases
where solid fill planes is enabled (and FB_ID is NULL), the commit can
still go through.
In addition, add framebuffer NULL checks in
Hi Dmitry,
Link rate is advertised by sink, but adjusted (reduced the link rate)
by host during link training.
Therefore should be fine if host did not support HBR3 rate.
It will reduce to lower link rate during link training procedures.
kuogee
On 10/31/2022 11:46 AM, Dmitry Baryshkov wro
On Tue, Sep 13, 2022 at 01:55:44PM -0700, Nathan Huckleberry wrote:
> The mode_valid field in drm_connector_helper_funcs is expected to be of
> type:
> enum drm_mode_status (* mode_valid) (struct drm_connector *connector,
> struct drm_display_mode *mode);
>
> T
https://bugzilla.kernel.org/show_bug.cgi?id=216645
--- Comment #6 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to Martin Šušla from comment #5)
> (In reply to Martin Šušla from comment #3)
> > After the message mention in title appears, not even a single interrupt is
> > registered.
>
From: John Harrison
Some of the GuC state dump messages were adding extra line feeds. When
printing via a DRM printer to dmesg, for example, that messes up the
log formatting as it loses any prefixing from the printer. Given that
the extra line feeds are just in the middle of random bits of GuC
s
On 10/29/2022 4:23 AM, Dmitry Baryshkov wrote:
On 29/10/2022 01:59, Jessica Zhang wrote:
Add support for COLOR_FILL and COLOR_FILL_FORMAT properties for
drm_plane. In addition, add support for setting and getting the values
of these properties.
COLOR_FILL represents the color fill of a plane
Hi all,
On Tue, Sep 13, 2022 at 01:55:48PM -0700, Nathan Huckleberry wrote:
> The mode_valid field in drm_connector_helper_funcs is expected to be of
> type:
> enum drm_mode_status (* mode_valid) (struct drm_connector *connector,
> struct drm_display_mode *mode
On Mon, Oct 31, 2022 at 7:07 AM Ville Syrjälä
wrote:
>
> On Sun, Oct 30, 2022 at 08:42:52AM -0600, jim.cro...@gmail.com wrote:
> > On Thu, Oct 27, 2022 at 2:10 PM Ville Syrjälä
> > wrote:
> > >
> > > On Thu, Oct 27, 2022 at 01:55:39PM -0600, jim.cro...@gmail.com wrote:
> > > > On Thu, Oct 27, 202
On 10/29/2022 4:40 AM, Dmitry Baryshkov wrote:
On 29/10/2022 01:59, Jessica Zhang wrote:
Initialize and use the color_fill properties for planes in DPU driver. In
addition, relax framebuffer requirements within atomic commit path and
add checks for NULL framebuffers.
Signed-off-by: Jessica Z
Hi all,
On Tue, Sep 13, 2022 at 01:56:00PM -0700, Nathan Huckleberry wrote:
> The mode_valid field in drm_connector_helper_funcs is expected to be of
> type
> enum drm_mode_status (* mode_valid) (struct drm_connector *connector,
> struct drm_display_mode *mode)
1 - 100 of 125 matches
Mail list logo
