Add hwmon support for fan1_input attribute, which will expose fan speed
in RPM. With this in place we can monitor fan speed using lm-sensors tool.
$ sensors
i915-pci-0300
Adapter: PCI adapter
in0: 653.00 mV
fan1:3833 RPM
power1: N/A (max = 43.00 W)
energy1: 32.02 k
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Reviewed-by: Tomi Valkeinen
---
drivers/media/platform/xilinx/xilinx-tpg.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/xilinx/xilinx-tpg.c
b/dri
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
---
drivers/video/fbdev/omap2/omapfb/dss/dpi.c| 3 +-
drivers/video/fbdev/omap2/omapfb/dss/dss-of.c | 66 ---
drivers/video/fbdev/omap2/omapfb/dss/dss.c| 9 +--
drivers/
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Reviewed-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/dpi.c | 3 ++-
drivers/gpu/drm/omapdrm/dss/sdi.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/d
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Acked-by: Mark Brown
---
sound/soc/generic/audio-graph-card2.c | 111 --
1 file changed, 49 insertions(+), 62 deletions(-)
diff --git a/sound/soc/generic/audio-graph-car
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Acked-by: Mark Brown
---
sound/soc/generic/audio-graph-card.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/sound/soc/generic/audio-graph-card.c
b/sound/soc/generic/au
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Acked-by: Mark Brown
---
sound/soc/sh/rcar/core.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/sound/soc/sh/rcar/core.c b/sound/soc/sh/rcar/core.c
index 63b3c
Current test-component.c is using for_each_endpoint_of_node()
for parsing "port", because there was no "port" base loop before.
It has been assuming 1 port has 1 endpoint here.
But now we can use "port" base loop (= for_each_of_graph_port()).
Let's replace for_each function from "endpoint" base to
We already have of_graph_get_next_endpoint(), but it is not
intuitive to use.
(X) node {
(Y) ports {
port@0 { endpoint { remote-endpoint = ...; };};
(A1)port@1 { endpoint { remote-endpoint = ...; };
(A2) endpoi
We have endpoint base functions
- of_graph_get_next_device_endpoint()
- of_graph_get_device_endpoint_count()
- for_each_of_graph_device_endpoint()
Here, for_each_of_graph_device_endpoint() loop finds each endpoints
ports {
port@0 {
(1)
Hi Rob, Saravana, Tomi
This is v2 patch-set
I have been posting to add new port base for loop function
as below steps.
[o] done
[*] posting (A)
[@] this patch set
[o] tidyup of_graph_get_endpoint_count()
[o] replace endpoint func - use endpoint_by_regs()
[*] replace en
Fix the unexpected indentation errors.
drm_connector.c has some kerneldoc comments that were missing newlines.
This results in the following warnings when running make htmldocs:
./Documentation/gpu/drm-kms:538: ./drivers/gpu/drm/drm_connector.c:2344:
WARNING: Definition list ends without a blank
Hi Tomi
> > +/**
> > + * of_graph_get_next_port_endpoint() - get next endpoint node in port.
> > + * If it reached to end of the port, it will return NULL.
> > + * @port: pointer to the target port node
> > + * @endpoint: current endpoint node, or NULL to get first
> > + *
> > + * Return: An 'en
On Thu, 8 Aug 2024 16:36:24 -0400 Mina Almasry wrote:
> > How do you know that the driver:
> > - supports net_iov at all (let's not make implicit assumptions based
> >on presence of queue API);
> > - supports net_iov in current configuration (eg header-data split is
> >enabled)
> > - sup
Hi Tomi
Thank you for your review
> > +/**
> > + * of_graph_get_next_ports() - get next ports node.
> > + * @parent: pointer to the parent device node
> > + * @ports: current ports node, or NULL to get first
> > + *
> > + * Return: A 'ports' node pointer with refcount incremented. Refcount
> >
From: John Harrison
The previous update to enable the workaround on ARL only changed two
out of three places where the w/a needs to be enabled. That meant the
GuC side was operational but not the KMD side. And as the KMD side is
the trigger, it meant the w/a was not actually active. So fix that.
sc7180 programs the ubwc settings as 0x1e as that would mean a
highest bank bit of 14 which matches what the GPU sets as well.
However, the highest_bank_bit field of the msm_mdss_data which is
being used to program the SSPP's fetch configuration is programmed
to a highest bank bit of 16 as 0x3 tra
On 8/7/2024 3:04 AM, Zhaoxiong Lv wrote:
Move the "exit sleep mode" and "set display on" command from
enable() to init() function.
As mentioned in the patch:
https://lore.kernel.org/all/20240624141926.5250-2-lvzhaoxi...@huaqin.corp-partner.google.com/
The Mediatek Soc DSI host has different
On 8/8/24 14:34, Alex Deucher wrote:
On Mon, Aug 5, 2024 at 1:50 PM Lizhi Hou wrote:
The hardware can be shared among multiple user applications. The
hardware resources are allocated/freed based on the request from
user application via driver IOCTLs.
DRM_IOCTL_AMDXDNA_CREATE_HWCTX
Allocate t
On Mon, Aug 5, 2024 at 1:50 PM Lizhi Hou wrote:
>
> The hardware can be shared among multiple user applications. The
> hardware resources are allocated/freed based on the request from
> user application via driver IOCTLs.
>
> DRM_IOCTL_AMDXDNA_CREATE_HWCTX
> Allocate tile columns and create a hard
On 8/6/2024 6:59 AM, Tejas Vipin wrote:
Add more functions that can benefit from being multi style and mark
older variants as deprecated to eventually convert all mipi_dsi functions
to multi style.
Acked-by: Maxime Ripard
Signed-off-by: Tejas Vipin
Acked-by: Jessica Zhang
---
drivers
On 8/6/2024 6:59 AM, Tejas Vipin wrote:
Use multi style wrapped functions for mipi_dsi in the
startek-kd070fhfid015 panel.
Signed-off-by: Tejas Vipin
Reviewed-by: Jessica Zhang
---
.../drm/panel/panel-startek-kd070fhfid015.c | 115 ++
1 file changed, 35 insertions(+
On Tue, Aug 6, 2024 at 4:59 PM Jakub Kicinski wrote:
>
...
> On Mon, 5 Aug 2024 21:25:20 + Mina Almasry wrote:
> > + if (pool->p.queue) {
> > + /* We rely on rtnl_lock()ing to make sure netdev_rx_queue
> > + * configuration doesn't change while we're initializing
Currently the array size is only limited by the largest kmalloc size which
is incorrect. This change will also return a more specific error message
than ENOMEM to userspace.
Signed-off-by: Ian Forbes
---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h | 4 ++--
drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 4 +++-
Hi,
On Thu, Aug 8, 2024 at 11:47 AM Rob Clark wrote:
>
> On Thu, Aug 8, 2024 at 11:44 AM Douglas Anderson
> wrote:
> >
> > The yaml had indentation errors:
> >
> > ./Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml:21:9:
> > [warning] wrong indentation: expected 10 b
On Thu, Aug 01, 2024 at 02:14:06PM +0200, Thomas Zimmermann wrote:
> Hi Dave, Sima,
>
> here's the first PR for drm-misc-next for what will become Linux v6.12.
> It's the ususal mix of new features and bug fixes. Nouveau got a larger
> refactoring, there are some improvements within TTM, work on t
On Thu, Aug 8, 2024 at 11:44 AM Douglas Anderson wrote:
>
> The yaml had indentation errors:
>
> ./Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml:21:9:
> [warning] wrong indentation: expected 10 but found 8 (indentation)
>
> ./Documentation/devicetree/bindings/disp
Hi,
On Thu, Aug 8, 2024 at 11:14 AM Rob Herring wrote:
>
> > > > From: Rob Clark
> > > >
> > > > The Samsung ATNA45DC02 panel is an AMOLED eDP panel, similar to the
> > > > existing ATNA45AF01 and ATNA33XC20 panel but with a higher resolution.
> > > >
> > > > Signed-off-by: Rob Clark
> > > > Ac
On 08/08/2024 20:35, Krzysztof Kozlowski wrote:
> On 08/08/2024 10:45, Tvrtko Ursulin wrote:
>>
>> Hi Dave, Sima,
>>
>> A small bunch of fixes for the weekly cycle:
>
> ...
>
>>
>>
>> Andi Shyti (2):
>> drm/i915/gem: Adjust vm
The yaml had indentation errors:
./Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml:21:9:
[warning] wrong indentation: expected 10 but found 8 (indentation)
./Documentation/devicetree/bindings/display/panel/samsung,atna33xc20.yaml:23:11:
[warning] wrong indentation:
On 08/08/2024 10:45, Tvrtko Ursulin wrote:
>
> Hi Dave, Sima,
>
> A small bunch of fixes for the weekly cycle:
...
>
>
> Andi Shyti (2):
> drm/i915/gem: Adjust vma offset for framebuffer mmap offset
> drm/i915/gem: Fi
On Tue, Aug 6, 2024 at 11:52 AM Doug Anderson wrote:
>
> Hi,
>
> On Wed, Jul 31, 2024 at 4:39 PM Doug Anderson wrote:
> >
> > Hi,
> >
> > On Mon, Jul 29, 2024 at 1:57 PM Rob Clark wrote:
> > >
> > > From: Rob Clark
> > >
> > > The Samsung ATNA45DC02 panel is an AMOLED eDP panel, similar to the
Hi Dave and Sima,
Here goes our first round of 6.11 fixes as I was out last week.
Dim failed to cherry-pick some cases that I'm going to take a
deeper look today/tomorrow, so probably some more fixes coming next
week towards -rc4...
Thanks,
Rodrigo.
drm-xe-fixes-2024-08-08:
- Fix off-by-one whe
drm_connector.c has two kerneldoc comments that were missing newlines.
This results in the following warnings when running make htmldocs:
./Documentation/gpu/drm-kms:538: ./drivers/gpu/drm/drm_connector.c:2344:
WARNING: Definition list ends without a blank line; unexpected unindent.
[docutils] ./D
On Thu, Aug 8, 2024 at 12:43 PM Alex Deucher wrote:
>
> On Thu, Aug 8, 2024 at 2:35 AM Lu Yao wrote:
> >
> > On 2024/8/5 17:25, Jocelyn Falempe wrote:
> > >
> > >
> > > On 02/08/2024 11:39, Christian König wrote:
> > >> Am 02.08.24 um 09:17 schrieb Lu Yao:
> > >>> Add support for the drm_panic mo
Hi Dave, Sima,
Fixes for 6.11. The drm buddy fix is needed to handle weird alignment
requirements for DCN 4.0 when DCC is enabled.
The following changes since commit 27ce65f65258cf2f2855162cbeef59659a81fac4:
Revert "nouveau: rip out busy fence waits" (2024-08-02 14:38:28 +1000)
are available
On Thu, Aug 8, 2024 at 2:35 AM Lu Yao wrote:
>
> On 2024/8/5 17:25, Jocelyn Falempe wrote:
> >
> >
> > On 02/08/2024 11:39, Christian König wrote:
> >> Am 02.08.24 um 09:17 schrieb Lu Yao:
> >>> Add support for the drm_panic module, which displays a pretty user
> >>> friendly message on the screen
On 8/7/2024 12:05 PM, Andi Shyti wrote:
In preparation for the upcoming partial memory mapping feature,
we want to make sure that when looking for a node we consider
also the offset and not just the starting address of the virtual
memory node.
Signed-off-by: Andi Shyti
Reviewed-by: Nirmoy Da
On 8/7/2024 12:05 PM, Andi Shyti wrote:
To enable partial memory mapping of GPU virtual memory, it's
necessary to introduce an offset to the object's memory
(obj->mm.pages) scatterlist. This adjustment compensates for
instances when userspace mappings do not start from the beginning
of the obje
On 8/8/24 02:40, Daniel Yang wrote:
drm_connector.c has two kerneldoc comments that were missing newlines.
This results in the following warnings when running make htmldocs:
./Documentation/gpu/drm-kms:538: ./drivers/gpu/drm/drm_connector.c:2344:
WARNING: Definition list ends without a blank lin
The keyboard driver encountered a bug due to changes in v2, so fixed them in v3
here:
https://lore.kernel.org/linux-input/1368fee8-58bb-41c9-b9ad-7f2f68ff1...@live.com/T/#t
From: Kerem Karabay
The Touch Bars found on x86 Macs support two USB configurations: one
where the device presents itself as a HID keyboard and can display
predefined sets of keys, and one where the operating system has full
control over what is displayed. This commit adds support for the display
From: Kerem Karabay
Add XRGB emulation helper for devices that only support BGR888.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/gpu/drm/drm_format_helper.c | 54 +
.../gpu/drm/tests/drm_format_helper_test.c| 81 +++
include
From: Kerem Karabay
Note that this is device ID is for T2 Macs. Testing on T1 Macs would be
appreciated.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/Kconfig | 1 +
drivers/hid/hid-multitouch.c | 26 ++
2 files changed, 23 insertion
From: Kerem Karabay
Currently the driver determines the device type based on the
application, but this value is not reliable on Apple Touch Bars, where
the application is HID_DG_TOUCHPAD even though the devices are direct,
so allow setting it in classes.
Signed-off-by: Kerem Karabay
Signed-off-
From: Kerem Karabay
This is needed for Apple Touch Bars, where no HID_DG_CONTACTMAX field is
present and the maximum contact count is greater than the default.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/hid-multitouch.c | 7 ---
1 file changed, 4 insertions(+)
From: Kerem Karabay
This is necessary on Apple Touch Bars, where the tip state is contained
in fields with the HID_DG_TOUCH usage. This feature is gated by a quirk
in order to prevent breaking other devices, see commit c2ef8f21ea8f
("HID: multitouch: add support for trackpads").
Signed-off-by: K
From: Kerem Karabay
This is needed to support Apple Touch Bars, where the contact ID is
contained in fields with the HID_DG_TRANSDUCER_INDEX usage.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/hid-multitouch.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-
From: Kerem Karabay
The Touch Bars found on x86 Macs support two USB configurations: one
where the device presents itself as a HID keyboard and can display
predefined sets of keys, and one where the operating system has full
control over what is displayed. This commit adds a driver for the
displa
From: Kerem Karabay
This commit adds a driver for the backlight of Apple Touch Bars on x86
Macs. Note that currently only T2 Macs are supported.
This driver is based on previous work done by Ronald Tschalär
.
Signed-off-by: Kerem Karabay
Co-developed-by: Aditya Garg
Signed-off-by: Aditya Garg
Hi Maintainers
The Touch Bars found on x86 Macs support two USB configurations: one
where the device presents itself as a HID keyboard and can display
predefined sets of keys, and one where the operating system has full
control over what is displayed.
This patch series adds support for both the c
On Thu, Aug 8, 2024 at 1:19 AM Thomas Zimmermann wrote:
>
> Hi
>
> Am 07.08.24 um 21:47 schrieb Alex Deucher:
> > On Tue, Aug 6, 2024 at 3:06 AM Thomas Zimmermann
> > wrote:
> >> Hi
> >>
> >> Am 05.08.24 um 21:00 schrieb Deucher, Alexander:
> >>> [Public]
> >>>
> -Original Message-
Hi Christophe,
On Thu, Aug 08, 2024 at 02:14:22PM +0200, Christophe JAILLET wrote:
> This file already uses sysfs_emit(). So be consistent and also use
> sysfs_emit_at().
>
> Moreover, size is always < PAGE_SIZE because scnprintf() (and now
> sysfs_emit_at()) returns the number of characters writ
Hi Mary,
kernel test robot noticed the following build errors:
[auto build test ERROR on f7f3ddb6e5c8dc7b621fd8c0903ea42190d67452]
url:
https://github.com/intel-lab-lkp/linux/commits/Mary-Guillemard/drm-panfrost-Add-SYSTEM_TIMESTAMP-and-SYSTEM_TIMESTAMP_FREQUENCY-parameters/20240808-032938
Hi Rob,
On 21/03/2024 07:52, Tomi Valkeinen wrote:
On 20/03/2024 17:37, Rob Herring wrote:
On Tue, Mar 19, 2024 at 10:22:37AM +0200, Tomi Valkeinen wrote:
The DP subsystem for ZynqMP support audio via two channels, and the DP
DMA has dma-engines for those channels. For some reason the DT bindi
Hi Sean,
On 17/06/2024 17:48, Sean Anderson wrote:
On 6/17/24 03:47, Tomi Valkeinen wrote:
Hi Sean,
On 03/05/2024 22:29, Sean Anderson wrote:
This series cleans up the zyqnmp_dp IRQ and locking situation. Once
that's done, it adds debugfs support. The intent is to enable compliance
testing or
v2 of the patches sent here:
https://lore.kernel.org/all/752d8eea-ee3b-4854-9b5e-f412afa20...@live.com/
This file already uses sysfs_emit(). So be consistent and also use
sysfs_emit_at().
Moreover, size is always < PAGE_SIZE because scnprintf() (and now
sysfs_emit_at()) returns the number of characters written not including the
trailing '\0'. So some tests can be removed.
This slightly simplifies t
From: Kerem Karabay
The Touch Bars found on x86 Macs support two USB configurations: one
where the device presents itself as a HID keyboard and can display
predefined sets of keys, and one where the operating system has full
control over what is displayed. This commit adds support for the display
From: Kerem Karabay
Add XRGB emulation helper for devices that only support BGR888.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/gpu/drm/drm_format_helper.c | 54 +
.../gpu/drm/tests/drm_format_helper_test.c| 81 +++
include
From: Kerem Karabay
Note that this is device ID is for T2 Macs. Testing on T1 Macs would be
appreciated.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/Kconfig | 1 +
drivers/hid/hid-multitouch.c | 26 ++
2 files changed, 23 insertion
From: Kerem Karabay
Currently the driver determines the device type based on the
application, but this value is not reliable on Apple Touch Bars, where
the application is HID_DG_TOUCHPAD even though the devices are direct,
so allow setting it in classes.
Signed-off-by: Kerem Karabay
Signed-off-
From: Kerem Karabay
This is needed for Apple Touch Bars, where no HID_DG_CONTACTMAX field is
present and the maximum contact count is greater than the default.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/hid-multitouch.c | 7 ---
1 file changed, 4 insertions(+)
From: Kerem Karabay
This is necessary on Apple Touch Bars, where the tip state is contained
in fields with the HID_DG_TOUCH usage. This feature is gated by a quirk
in order to prevent breaking other devices, see commit c2ef8f21ea8f
("HID: multitouch: add support for trackpads").
Signed-off-by: K
From: Kerem Karabay
This is needed to support Apple Touch Bars, where the contact ID is
contained in fields with the HID_DG_TRANSDUCER_INDEX usage.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/hid-multitouch.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-
From: Kerem Karabay
The Touch Bars found on x86 Macs support two USB configurations: one
where the device presents itself as a HID keyboard and can display
predefined sets of keys, and one where the operating system has full
control over what is displayed. This commit adds a driver for the
displa
From: Kerem Karabay
This commit adds a driver for the backlight of Apple Touch Bars on x86
Macs. Note that currently only T2 Macs are supported.
This driver is based on previous work done by Ronald Tschalär
.
Signed-off-by: Kerem Karabay
Co-developed-by: Aditya Garg
Signed-off-by: Aditya Garg
Hi Maintainers
The Touch Bars found on x86 Macs support two USB configurations: one
where the device presents itself as a HID keyboard and can display
predefined sets of keys, and one where the operating system has full
control over what is displayed.
This patch series adds support for both the c
Looks like I messed up the email series, Resending.
Sorry for the trouble
> On 8 Aug 2024, at 5:23 PM, Aditya Garg wrote:
>
> Hi Maintainers
>
> The Touch Bars found on x86 Macs support two USB configurations: one
> where the device presents itself as a HID keyboard and can display
> predefine
From: Kerem Karabay
Add XRGB emulation helper for devices that only support BGR888.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/gpu/drm/drm_format_helper.c | 54 +
.../gpu/drm/tests/drm_format_helper_test.c| 81 +++
include
From: Kerem Karabay
Note that this is device ID is for T2 Macs. Testing on T1 Macs would be
appreciated.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/Kconfig | 1 +
drivers/hid/hid-multitouch.c | 26 ++
2 files changed, 23 insertion
From: Kerem Karabay
Currently the driver determines the device type based on the
application, but this value is not reliable on Apple Touch Bars, where
the application is HID_DG_TOUCHPAD even though the devices are direct,
so allow setting it in classes.
Signed-off-by: Kerem Karabay
Signed-off-
From: Kerem Karabay
This is needed for Apple Touch Bars, where no HID_DG_CONTACTMAX field is
present and the maximum contact count is greater than the default.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/hid-multitouch.c | 7 ---
1 file changed, 4 insertions(+)
Move rockchip_drm_platform_driver unregistration after its sub-drivers,
which ensures all drivers are unregistered in the reverse order used
when they were registered.
Fixes: 8820b68bd378 ("drm/rockchip: Refactor the component match logic.")
Signed-off-by: Cristian Ciocaltea
---
drivers/gpu/drm/
From: Kerem Karabay
This is necessary on Apple Touch Bars, where the tip state is contained
in fields with the HID_DG_TOUCH usage. This feature is gated by a quirk
in order to prevent breaking other devices, see commit c2ef8f21ea8f
("HID: multitouch: add support for trackpads").
Signed-off-by: K
From: Kerem Karabay
This is needed to support Apple Touch Bars, where the contact ID is
contained in fields with the HID_DG_TRANSDUCER_INDEX usage.
Signed-off-by: Kerem Karabay
Signed-off-by: Aditya Garg
---
drivers/hid/hid-multitouch.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-
From: Kerem Karabay
The Touch Bars found on x86 Macs support two USB configurations: one
where the device presents itself as a HID keyboard and can display
predefined sets of keys, and one where the operating system has full
control over what is displayed. This commit adds a driver for the
displa
From: Kerem Karabay
This commit adds a driver for the backlight of Apple Touch Bars on x86
Macs. Note that currently only T2 Macs are supported.
This driver is based on previous work done by Ronald Tschalär
.
Signed-off-by: Kerem Karabay
Co-developed-by: Aditya Garg
Signed-off-by: Aditya Garg
Hi Maintainers
The Touch Bars found on x86 Macs support two USB configurations: one
where the device presents itself as a HID keyboard and can display
predefined sets of keys, and one where the operating system has full
control over what is displayed.
This patch series adds support for both the c
Hi Vignesh,
On 8/7/24 05:20, Vignesh Raman wrote:
Uprev mesa to adapt to the latest changes in mesa ci.
Project 'anholt/deqp-runner' was moved to 'mesa/deqp-runner'.
So update the link.
Signed-off-by: Vignesh Raman
---
v1:
- Working pipeline link,
https://gitlab.freedesktop.org/vignes
Am Wed, Aug 07, 2024 at 09:41:00PM + schrieb Daniel Gomez:
> Date: Wed, 7 Aug 2024 21:41:00 +
> From: Daniel Gomez
> To: Nicolas Schier
> CC: Masahiro Yamada , Nathan Chancellor
> , Lucas De Marchi , Thomas
> Hellström , Rodrigo Vivi
> , Maarten Lankhorst
> , Maxime Ripard ,
> Thomas
On 8/5/24 19:24, Rob Clark wrote:
> On Wed, Jul 24, 2024 at 12:00 PM Dmitry Osipenko
> wrote:
>>
>> On 7/23/24 14:49, Sergio Lopez wrote:
>>> There's an incresing number of machines supporting multiple page sizes
>>> and on these machines the host and a guest can be running, each one,
>>> with a d
On 08/08/2024 09:13, Ma Ke wrote:
As it may return NULL pointer and cause NULL pointer dereference. Add check
for the return value of alloc_ordered_workqueue.
Cc: sta...@vger.kernel.org
Fixes: 2f95bc6d324a ("drm: omapdrm: Perform initialization/cleanup at probe/remove
time")
Signed-off-by: Ma K
Hello Steve,
> VK_KHR_calibrated_timestamps says it should query 'quasi simultaneously
> from two time domains' - but this is purely providing an interface to
> read a single counter at a time.
>
> It _may_ be useful to report the GPU's view of time and at the same time
> (or as near as possible)
On 08/08/2024 13:24, Mary Guillemard wrote:
As it stands, this query has nothing to do with the actual GPU so
doesn't really belong here.
It'd be more valuable, and can maybe give better calibration results
than querying the system timestamp separately in userspace, if you
reported all of:
Memory intensive applications(which requires more tha 4GB) that wants
to offload tasks to DSP might have to split the tasks to multiple
user PD to make the resources available.
For every call to DSP, fastrpc driver passes the process tgid which
works as an identifier for the DSP to enqueue the tas
Gurchetan Singh writes:
> On Tue, Aug 6, 2024 at 1:15 PM Rob Clark wrote:
>
>> On Tue, Aug 6, 2024 at 9:15 AM Gurchetan Singh
>> wrote:
>> >
>> >
>> >
>> > On Mon, Aug 5, 2024 at 2:14 AM Sergio Lopez Pascual
>> wrote:
>> >>
>> >> Dmitry Osipenko writes:
>> >>
>> >> > On 7/23/24 14:49, Sergio
Hi Luca,
On Thu, Aug 08, 2024 at 12:26:14PM +0200, Luca Ceresoli wrote:
> When devm_drm_of_get_bridge() fails, the probe fails silently. Use
> dev_err_probe() instead to log an error or report the deferral reason,
> whichever is applicable.
>
> Signed-off-by: Luca Ceresoli
> ---
> drivers/gpu/d
>panel_bridge = panel_bridge;
---
base-commit: 8400291e289ee6b2bf9779ff1c83a291501f017b
change-id: 20240808-ti-sn65dsi83-dev_err_probe-98daf0ddafb1
Best regards,
--
Luca Ceresoli
Hi,
On Wed, Aug 07, 2024 at 11:45:53AM +0100, Andi Shyti wrote:
> By moving the pfn calculation to the set_address_limits()
> function we improve code readability. This way,
> set_address_limits() is responsible for calculating all memory
> mapping paramenters: "start", "end" and "pfn".
>
> This
Hi Christophe,
On Thu, Aug 08, 2024 at 11:46:11AM +0200, Christophe JAILLET wrote:
> Use sysfs_emit_at() instead of snprintf() + custom logic.
> Using sysfs_emit_at() is much more simple.
>
> Also, sysfs_emit() is already used in this function, so using
> sysfs_emit_at() is more consistent.
>
>
> As it stands, this query has nothing to do with the actual GPU so
> doesn't really belong here.
>
> It'd be more valuable, and can maybe give better calibration results
> than querying the system timestamp separately in userspace, if you
> reported all of:
> * the system timer value
> * the sy
On 07/08/2024 17:08, Mary Guillemard wrote:
> If a job requires cycle counters or system timestamps propagation, we
> must enable cycle counting before issuing a job and disable it right
> after the job completes.
>
> Since this extends the uAPI and because userland needs a way to advertise
> feat
On 07/08/2024 17:08, Mary Guillemard wrote:
> Extend the uAPI with a new job requirement flag for cycle
> counters. This requirement is used by userland to indicate that a job
> requires cycle counters or system timestamp to be propagated. (for use
> with write value timestamp jobs)
>
> We cannot
On 07/08/2024 17:08, Mary Guillemard wrote:
> Expose system timestamp and frequency supported by the GPU.
>
> Mali uses the generic arch timer as GPU system time so we currently
> wire cntvct_el0 and cntfrq_el0 respectively to those parameters.
> We could have directly read those values from userl
On 06/08/2024 07:58, Kuninori Morimoto wrote:
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
---
drivers/media/platform/xilinx/xilinx-tpg.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/xilin
On 06/08/2024 07:58, Kuninori Morimoto wrote:
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
---
drivers/gpu/drm/omapdrm/dss/dpi.c | 3 ++-
drivers/gpu/drm/omapdrm/dss/sdi.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff
Sorry about the accidental re-wrap, I got fat fingers...
On 08/08/2024 10:41, Mihail Atanassov wrote:
Hi Mary,
Thanks for your patch.
On 07/08/2024 16:35, Mary Guillemard wrote:
Expose system timestamp and frequency supported by the GPU with a
new device query.
[... snip ...]
base-commit:
Use sysfs_emit_at() instead of snprintf() + custom logic.
Using sysfs_emit_at() is much more simple.
Also, sysfs_emit() is already used in this function, so using
sysfs_emit_at() is more consistent.
Also simplify the logic:
- always add a space after an entry
- change the last space into a '\
Hi Mary,
Thanks for your patch.
On 07/08/2024 16:35, Mary Guillemard wrote:
Expose system timestamp and frequency supported by the GPU with a
new device query.
Mali uses the generic arch timer as GPU system time so we currently
wire cntvct_el0 and cntfrq_el0 respectively to a new device query
1 - 100 of 111 matches
Mail list logo
