On Mon, Jul 01, 2024 at 02:23:29PM GMT, Rob Clark wrote:
> From: Rob Clark
>
> The __build_asserts() function only exists to have a place to put
> build-time asserts.
>
> Reported-by: kernel test robot
> Closes:
> https://lore.kernel.org/oe-kbuild-all/202407010401.rfunrbsx-...@intel.com/
> Sig
Hi Conor,
On 01/07/24 3:33 pm, Conor Dooley wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the
> content is safe
>
>
> ForwardedMessage.eml
>
> Subject:
> Re: [PATCH v2 1/3] dt-bindings: display: himax-hx8394: Add Microchip
> AC40T08A MIPI Display panel
> From
Dumb buffers can be used in kms but also through prime with gallium's
resource_from_handle. In the second case the dumb buffers can be
rendered by the GPU where with the regular DRM kms interfaces they
are mapped and written to by the CPU. Because the same buffer can
be written to by the GPU and CP
Make vmwgfx go through the dma-buf interface to map/unmap imported
buffers. The driver used to try to directly manipulate external
buffers, assuming that everything that was coming to it had to live
in cpu accessible memory. While technically true because what's in the
vms is controlled by us, it's
Fix races issues in virtual crc generation by making sure the surface
the code uses for crc computation is properly ref counted.
Crc generation was trying to be too clever by allowing the surfaces
to go in and out of scope, with the hope of always having some kind
of screen present. That's not alw
Introduce a version of the fence ops that on release doesn't remove
the fence from the pending list, and thus doesn't require a lock to
fix poll->fence wait->fence unref deadlocks.
vmwgfx overwrites the wait callback to iterate over the list of all
fences and update their status, to do that it hol
This small series fixes all known prime/dumb_buffer/buffer dirty
tracking issues. Fixing of dumb-buffers turned out to be a lot more
complex than I wanted it to be. There's not much that can be done
there because the driver has to support old userspace (our Xorg driver
expects those to not be gem b
在 2024-07-01星期一的 13:40 +0200，Christian König写道：
> Am 29.06.24 um 22:51 schrieb Icenowy Zheng:
> >
> > 于 2024年6月30日 GMT+08:00 03:57:47，Jiaxun Yang
> > 写道：
> > >
> > > 在2024年6月29日六月 上午6:22，Icenowy Zheng写道：
> > > [...]
> > > > @@ -302,6 +302,10 @@ pgprot_t ttm_io_prot(struct
> > > > ttm_buffer_obje
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/
On 6/28/24 13:07, Zack Rusin wrote:
> This small series fixes all known prime/dumb_buffer/buffer dirty
> tracking issues. Fixing of dumb-buffers turned out to be a lot more
> complex than I wanted it to be. There's not much that can be done
> there because the driver has to support old userspace (o
Am Mo., 1. Juli 2024 um 21:02 Uhr schrieb Mario Limonciello
:
> Hmm I'm a bit surprised the IGT tests I did didn't catch this.
>
> Are you working on a system with two GPUs by chance (like a Framework
> 16)? If so; can you try the "other GPU"?
No, I tested on a Framework 13.
> As it seems your P
From: Rob Clark
Fixes a sparse "different address spaces" error.
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202406280050.syeewlte-...@intel.com/
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/msm_gem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Sun, Jun 30, 2024 at 05:19:31PM GMT, Adam Ford wrote:
> In the process of adding support for shared IRQ pins, a scenario
> was accidentally created where adv7511_irq_process returned
> prematurely causing the EDID to fail randomly.
>
> Since the interrupt handler is broken up into two main help
From: Rob Clark
The __build_asserts() function only exists to have a place to put
build-time asserts.
Reported-by: kernel test robot
Closes:
https://lore.kernel.org/oe-kbuild-all/202407010401.rfunrbsx-...@intel.com/
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/adreno/a6xx_catalog.c | 2 +
On Mon, Jul 01, 2024 at 05:22:37PM +0530, Ekansh Gupta wrote:
> For user PD initialization, initmem is allocated and sent to DSP for
> initial memory requirements like shell loading. This size is passed
> by user space and is checked against a max size.
Why does fastrpc_init_create_process() alloc
On 6/30/24 19:36, Stefan Wahren wrote:
> The commit c4a0f7a6ab54 ("usb: dwc2: Skip clock gating on Samsung
> SoCs") introduced a parameter to skip enabling clock gating mode
> even the hardware platform should supports it.
>
> In order to make this more visible also print this in show
> paramete
In the match() callback, the struct device_driver * should not be
changed, so change the function callback to be a const *. This is one
step of many towards making the driver core safe to have struct
device_driver in read-only memory.
Because the match() callback is in all busses, all busses are
On Fri, Jun 28, 2024 at 2:49 PM Abhinav Kumar wrote:
>
> Introduce a new API msm_iommu_disp_new() for display use-cases.
>
> Signed-off-by: Abhinav Kumar
> ---
> drivers/gpu/drm/msm/msm_iommu.c | 26 ++
> drivers/gpu/drm/msm/msm_mmu.h | 1 +
> 2 files changed, 27 inser
On Sun, Jun 30, 2024 at 08:36:29PM GMT, Caleb Connolly wrote:
> This is a 1080x2400 120hz panel used on the OnePlus 8T. It uses DSC but
> with many non-standard DCS commands.
>
> The only user of this panel (the OnePlus 8T) has a bug somewhere in the
> DSI stack whereby it isn't possible to proper
On Sun, Jun 30, 2024 at 08:36:27PM GMT, Caleb Connolly wrote:
> Some panels like the Samsung AMB655X use long write commands for all
> non-standard messages and do not work when trying to use the appropriate
> command type.
>
> Support these panels by introducing a new helper to send commands of a
On Sun, Jun 30, 2024 at 08:36:28PM GMT, Caleb Connolly wrote:
> Introduce mipi_dsi_dcs_set_column_address_multi() and
> mipi_dsi_dcs_set_page_address_multi() helpers.
>
> Signed-off-by: Caleb Connolly
> ---
> include/drm/drm_mipi_dsi.h | 16
> 1 file changed, 16 insertions(+)
>
The if condition !A || A && B can be simplified to !A || B.
Fixes the following Coccinelle/coccicheck warning reported by
excluded_middle.cocci:
WARNING !A || A && B is equivalent to !A || B
Compile-tested only.
Acked-by: Thomas Zimmermann
Signed-off-by: Thorsten Blum
---
drivers/gpu
On Fri, Jun 28, 2024 at 02:48:45PM GMT, Abhinav Kumar wrote:
> Introduce a new API msm_iommu_disp_new() for display use-cases.
>
> Signed-off-by: Abhinav Kumar
> ---
> drivers/gpu/drm/msm/msm_iommu.c | 26 ++
> drivers/gpu/drm/msm/msm_mmu.h | 1 +
> 2 files changed, 27
On Fri, Jun 28, 2024 at 04:39:27PM GMT, Abhinav Kumar wrote:
> On QCM2290 chipset DPU does not support UBWC.
>
> Add a dpu cap to indicate this and do not expose compressed formats
> in this case.
>
> changes since RFC:
> - use ubwc enc and dec version of mdss_data instead of catalog
>
On Fri, Jun 28, 2024 at 02:48:47PM GMT, Abhinav Kumar wrote:
> There is no recovery mechanism in place yet to recover from mmu
> faults for DPU. We can only prevent the faults by making sure there
> is no misconfiguration.
>
> Rate-limit the snapshot capture for mmu faults to once per
> msm_kms_in
On Fri, Jun 28, 2024 at 02:48:42PM GMT, Abhinav Kumar wrote:
> To debug display mmu faults, this series introduces a display fault
> handler similar to the gpu one.
>
> This series has been tested on sc7280 chromebook by using triggering
> a smmu fault by forcing an incorrect stride on the planes.
Applied the series. Thanks!
Alex
On Mon, Jul 1, 2024 at 3:15 AM Jiapeng Chong
wrote:
>
> Avoid pointer type value compared with 0 to make code clear.
>
> ./drivers/gpu/drm/amd/display/dc/dml2/dml21/src/dml2_core/dml2_core_factory.c:14:12-13:
> WARNING comparing pointer to 0.
>
> Reported-by: A
Applied. Thanks!
On Sun, Jun 30, 2024 at 11:10 PM Jiapeng Chong
wrote:
>
> The return value from the call to dml21_find_dc_pipes_for_plane() is int.
> However, the return value is being assigned to an unsigned int variable
> 'num_pipes', the condition if(num_pipes <= 0) is not rigorous enough,
>
On Fri, Jun 28, 2024 at 3:10 AM Donald Hunter wrote:
>
> Mina Almasry writes:
> > + -
> > +name: bind-dmabuf
> > +attributes:
> > + -
> > +name: ifindex
> > +doc: netdev ifindex to bind the dma-buf to.
>
> Minor nit:
>
> The series uses a mix of dmabuf and dma-buf bu
On 7/1/2024 13:47, Xaver Hugl wrote:
Am Do., 20. Juni 2024 um 22:22 Uhr schrieb Xaver Hugl :
Merging can only happen once a real world userspace application has
implemented support for it. I'll try to do that sometime next week in
KWin
Here's the promised implementation:
https://invent.kde.org
On Fri, Jun 28, 2024 at 3:10 AM Donald Hunter wrote:
>
> Mina Almasry writes:
> > +
> > +The user must bind a dmabuf to any number of RX queues on a given NIC using
> > +the netlink API::
> > +
> > + /* Bind dmabuf to NIC RX queue 15 */
> > + struct netdev_queue *queues;
> > + queues
Am Do., 20. Juni 2024 um 22:22 Uhr schrieb Xaver Hugl :
> Merging can only happen once a real world userspace application has
> implemented support for it. I'll try to do that sometime next week in
> KWin
Here's the promised implementation:
https://invent.kde.org/plasma/kwin/-/merge_requests/6028
If there is a next bridge in the OF graph don't let it be ignored.
Attach the next bridge to the chain.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/bridge/lontium-lt9611uxc.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bridge/lontium-lt9611
Having no in-kernel devices that use !DRM_BRIDGE_ATTACH_NO_CONNECTOR
mode for the Lontium LT9611UXC bridge, drop the in-bridge implementation
of the drm_connector.
Signed-off-by: Dmitry Baryshkov
---
drivers/gpu/drm/bridge/lontium-lt9611uxc.c | 104 +++--
1 file changed,
There are no in-kernel DTs that use Lontium LT9611UXC bridge and still
require creation of the drm_connector by the bridge on attachment.
Drop support for !DRM_BRIDGE_ATTACH_NO_CONNECTOR by the driver.
Signed-off-by: Dmitry Baryshkov
---
Dmitry Baryshkov (2):
drm/bridge: lt9611uxc: properly
Hi Louis,
On 7/1/24 10:06, Louis Chauvet wrote:
Hi everyone,
I sent this iteration over a month ago, and I haven't received any
feedback since then. The same goes for the two other series [1] and [2],
which I sent after discussing with Melissa.
As you may know, Melissa is stepping down on her
Am Freitag, dem 28.06.2024 um 13:07 +0200 schrieb Philipp Zabel:
> On Fr, 2024-06-28 at 12:47 +0200, Lucas Stach wrote:
> > The next changes will introduce another place where the debug registers
> > need to be en-/disabled. Split into separate functions, so we don't need
> > to replicate the code
Hi Conor,
On Sun, Jun 30, 2024 at 11:17 PM Conor Dooley wrote:
>
> On Sat, Jun 29, 2024 at 05:26:56PM +0900, Hironori KIKUCHI wrote:
> > Hello Conor,
> >
> > Thank you for your reply.
> >
> > On Sat, Jun 29, 2024 at 1:27 AM Conor Dooley wrote:
> > >
> > > On Fri, Jun 28, 2024 at 02:10:15PM +0900
On Mon, Jul 01, 2024 at 07:13:19PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the drm tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> In file included from arch/powerpc/include/asm/mmu.h:144,
> from arch/powerpc/include/asm/paca.h:18,
From: Christian König
Multiple drivers came up with the requirement to measure how
much runtime each entity accumulated on the HW.
A previous attempt of accounting this had to be reverted because
HW submissions can have a lifetime exceeding that of the entity
originally issuing them.
Amdgpu on
From: Christian König
Instead of implementing this ourself.
Signed-off-by: Christian König
Signed-off-by: Lucas Stach
---
v2:
- rebased to v6.10-rc1
- adapted to match new function names
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.c | 52 -
1 file changed, 8 insertions(+
This exposes a accumulated GPU active time per client via the
fdinfo infrastructure.
Signed-off-by: Lucas Stach
---
v2:
- new patch
---
drivers/gpu/drm/etnaviv/etnaviv_drv.c | 32 ++-
1 file changed, 31 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/etnaviv/et
From: Christian König
This reverts commit 8ee3a52e3f35e064a3bf82f21dc74ddaf9843648.
The new amdgpu_ctx_mgr_entity_fini() was never called, so it was pure
coincident that this patch didn't cause a crash. Since the workaround
shouldn't be needed any more just mostly revert the changes to amdgpu.
On Mon, Jul 01, 2024 at 10:50:38AM GMT, Ekansh Gupta wrote:
>
>
> On 6/28/2024 7:51 PM, Greg KH wrote:
> > On Fri, Jun 28, 2024 at 04:12:10PM +0530, Ekansh Gupta wrote:
> >>
> >> On 6/28/2024 3:59 PM, Ekansh Gupta wrote:
> >>> On 6/27/2024 4:43 PM, Dmitry Baryshkov wrote:
> On Thu, Jun 27, 2
+ Marek
On Sat, Jun 29, 2024 at 1:15 PM Simon Ser wrote:
>
> Hi all!
>
> In 7ceb94e87bff ("drm/amd: Add gfx12 swizzle mode defs"), some
> definitions were added for GFX12 modifiers. However I'm not quite sure
> I understand how these work.
>
> Tile values seem to not be in the same namespace as G
On 01/07/2024 10:25, Maarten Lankhorst wrote:
Den 2024-06-28 kl. 16:04, skrev Maxime Ripard:
Hi,
On Thu, Jun 27, 2024 at 09:22:56PM GMT, Maarten Lankhorst wrote:
Den 2024-06-27 kl. 19:16, skrev Maxime Ripard:
Hi,
Thanks for working on this!
On Thu, Jun 27, 2024 at 05:47:21PM GMT, Maarten
On Sun, Jun 30, 2024 at 8:40 AM Jeff Layton wrote:
>
> I've been testing some vfs patches (multigrain timestamps) on my
> personal desktop with a 6.10.0-rc5-ish kernel, and have hit a number of
> warnings in the amdgpu driver, including a UBSAN warning that looks
> like a potential array overrun:
On 01/07/2024 15:50, Maxime Ripard wrote:
> On Thu, Jun 27, 2024 at 01:13:03PM GMT, Marc Gonzalez wrote:
>
>> TDP158 is an AC-coupled DVI / HDMI to TMDS level shifting Redriver.
>> It supports DVI 1.0, HDMI 1.4b and 2.0b.
>> It supports 4 TMDS channels, HPD, and a DDC interface.
>> It supports dua
On LNL because of flat CCS, driver creates a migrate job to clear
CCS meta data. Extend that to also clear system pages using GPU.
Inform TTM to allocate pages without __GFP_ZERO to avoid double page
clearing by clearing out TTM_TT_FLAG_ZERO_ALLOC flag and set
TTM_TT_FLAG_CLEARED_ON_FREE while free
XE_FAST_COLOR_BLT will clear out CCS meta data when clearing bo with
uncompress PTE, so skip emit_copy_ccs() when XE_FAST_COLOR_BLT is used
to clear out a bo.
Cc: Himal Prasad Ghimiray
Cc: Matthew Auld
Cc: "Thomas Hellström"
Signed-off-by: Nirmoy Das
---
drivers/gpu/drm/xe/xe_migrate.c | 14 +
Parameterize clearing ccs and bo data in xe_migrate_clear() which higher
layers can utilize. This patch will be used later on when doing bo data
clear for igfx as well.
Cc: Himal Prasad Ghimiray
Cc: Matthew Auld
Cc: "Thomas Hellström"
Signed-off-by: Nirmoy Das
---
drivers/gpu/drm/xe/tests/xe
Add TTM_TT_FLAG_CLEARED_ON_FREE, which DRM drivers can set before
releasing backing stores if they want to skip clear-on-free.
Cc: Matthew Auld
Cc: Thomas Hellström
Suggested-by: Christian König
Signed-off-by: Nirmoy Das
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_pool.c | 18 ++
On 28/06/2024 09:49, Dmitry Baryshkov wrote:
> On Fri, Jun 28, 2024 at 09:36:57AM GMT, Krzysztof Kozlowski wrote:
>> On 27/06/2024 18:45, Marc Gonzalez wrote:
>>> On 27/06/2024 18:25, Conor Dooley wrote:
On Thu, Jun 27, 2024 at 01:13:03PM +0200, Marc Gonzalez wrote:
> TDP158 is an AC-
Hi,
On Thu, Jun 27, 2024 at 01:13:03PM GMT, Marc Gonzalez wrote:
> TDP158 is an AC-coupled DVI / HDMI to TMDS level shifting Redriver.
> It supports DVI 1.0, HDMI 1.4b and 2.0b.
> It supports 4 TMDS channels, HPD, and a DDC interface.
> It supports dual power supply rails (1.1V on VDD, 3.3V on VCC
Add compatible to panel-simple for Jiangsu Smartwin Electronics
SMMT043480272A-A19 4.3" 480x272 LCD-TFT panel.
Acked-by: Conor Dooley
Signed-off-by: Marco Felsch
---
Changelog:
v2:
- rebased ontop of drm-misc-next
- added Conor's acked-by
.../devicetree/bindings/display/panel/panel-simple.yaml
From: Rouven Czerwinski
Add support for the Jiangsu Smartwin SMMT043480272A-A19 4.3" 480x272
TFT-LCD panel. The timings are based on the ILI6485 controller IC
datasheet.
Signed-off-by: Rouven Czerwinski
Reviewed-by: Neil Armstrong
Signed-off-by: Marco Felsch
---
Changelog:
v2:
- rebased ontop
Hi everyone,
I sent this iteration over a month ago, and I haven't received any
feedback since then. The same goes for the two other series [1] and [2],
which I sent after discussing with Melissa.
I'm a bit surprised that nothing has been reviewed or merged, as Maíra
mentioned in [3] that she
On Tue, Jun 25, 2024 at 07:38:22PM GMT, Dmitry Baryshkov wrote:
> On Tue, Jun 25, 2024 at 05:49:54PM GMT, Maxime Ripard wrote:
> > On Tue, Jun 25, 2024 at 06:05:33PM GMT, Dmitry Baryshkov wrote:
> > > On Tue, 25 Jun 2024 at 18:02, Maxime Ripard wrote:
> > > >
> > > > Hi,
> > > >
> > > > On Sun, Ju
[adding more people to this thread based on the drivers using gpu_scheduler]
Hi,
Christian's comment on patch 1/5 will be addressed in v6, but before
pushing another version I'd like to know if there's a consensus among
the drivers maintainers regarding the changes proposed in this series.
T
On Mon, Jul 01, 2024 at 10:46:48AM +, Omer Shpigelman wrote:
> On 6/30/24 16:29, Leon Romanovsky wrote:
> > On Fri, Jun 28, 2024 at 10:24:32AM +, Omer Shpigelman wrote:
> >> On 6/19/24 13:52, Leon Romanovsky wrote:
> >>> On Wed, Jun 19, 2024 at 09:27:54AM +, Omer Shpigelman wrote:
> >>>
On Fri, Jun 28, 2024 at 11:07 PM Zack Rusin wrote:
>
> This small series fixes all known prime/dumb_buffer/buffer dirty
> tracking issues. Fixing of dumb-buffers turned out to be a lot more
> complex than I wanted it to be. There's not much that can be done
> there because the driver has to suppor
Am 01.07.24 um 13:52 schrieb Jiaxun Yang:
在2024年7月1日七月 下午12:40，Christian König写道：
[...]
Ah, wait a second.
Such a thing as non-coherent PCIe implementation doesn't exist. The PCIe
specification makes it mandatory for memory access to be cache coherent.
There are some non-PCIe TTM GPU being hit
On Thu, 20 Jun 2024 12:09:47 +0100, Dave Stevenson wrote:
> Adds test for the cmdline parser, connector property, and
> drm_analog_tv_mode to ensure the behaviour of the new value is
> correct.
>
>
Applied to misc/kernel.git (drm-misc-next).
Thanks!
Maxime
For user PD initialization, initmem is allocated and sent to DSP for
initial memory requirements like shell loading. This size is passed
by user space and is checked against a max size. For unsigned PD
offloading requirement, more than 2MB size could be passed by user
which would result in PD initi
在2024年7月1日七月 下午12:40，Christian König写道：
[...]
>
> Ah, wait a second.
>
> Such a thing as non-coherent PCIe implementation doesn't exist. The PCIe
> specification makes it mandatory for memory access to be cache coherent.
There are some non-PCIe TTM GPU being hit by this pitfall, we have non-co
Am 29.06.24 um 22:51 schrieb Icenowy Zheng:
于 2024年6月30日 GMT+08:00 03:57:47，Jiaxun Yang 写道：
在2024年6月29日六月 上午6:22，Icenowy Zheng写道：
[...]
@@ -302,6 +302,10 @@ pgprot_t ttm_io_prot(struct ttm_buffer_object *bo,
struct ttm_resource *res,
caching = res->bus.caching;
}
+
Am 29.06.24 um 07:22 schrieb Icenowy Zheng:
This patchset tries to make TTM support devices w/o full DMA coherency
capability (usually due to part of the link between the device and the
CPU, esp. PCIe controller, do not have full coherency).
The patchset itself looks quite straightforward, howev
On 6/28/24 16:58, Matthew Schwartz wrote:
This is a series of 2 patches.
The first patch is from Valve's public kernel
source tree. It adds a panel rotation quirk for Valve's Steam Deck Galileo
revision, which has an 800x1280 OLED panel. The previous Steam Deck panel
orientation quirk does not a
On Fri, 28 Jun 2024, Imre Deak wrote:
> This is v2 of [1], renaming the helpers from drm_x16 to fxp_q4 as
> suggested by Jani.
>
> [1] https://lore.kernel.org/all/20240614173911.3743172-1-imre.d...@intel.com
>
> Cc: Jani Nikula
No detailed review, but on the approach and naming,
Acked-by: Jani
On Mon, Jul 1, 2024 at 3:32 AM Kuninori Morimoto
wrote:
>
> We already have for_each_endpoint_of_node(), don't use
> of_graph_get_next_endpoint() directly. Replace it.
>
> Signed-off-by: Kuninori Morimoto
> Reviewed-by: Laurent Pinchart
> ---
> drivers/media/platform/ti/am437x/am437x-vpfe.c |
On Mon, Jun 24, 2024 at 05:19:55PM +0200, Thomas Zimmermann wrote:
> The backlight code currently uses fbdev's FB_BLANK_ constants to
> represent power states UNBLANK and POWERDOWN. Introduce dedicated
> backlight constants to remove this dependency on fbdev.
>
> Patch 1 introduces BACKLIGHT_POWER_
On 6/30/24 16:29, Leon Romanovsky wrote:
> On Fri, Jun 28, 2024 at 10:24:32AM +, Omer Shpigelman wrote:
>> On 6/19/24 13:52, Leon Romanovsky wrote:
>>> On Wed, Jun 19, 2024 at 09:27:54AM +, Omer Shpigelman wrote:
On 6/18/24 15:58, Leon Romanovsky wrote:
> On Tue, Jun 18, 2024 at 11
Am 28.06.24 um 20:13 schrieb Daniel Vetter:
On Fri, Jun 28, 2024 at 03:51:33PM +, Matthew Brost wrote:
On Fri, Jun 28, 2024 at 05:38:48PM +0200, Thomas Hellström wrote:
Bos can be put with multiple unrelated dma-resv locks held. But
imported bos attempt to grab the bo dma-resv during dma-bu
On 01/07/2024 03:32, Kuninori Morimoto wrote:
We already have for_each_endpoint_of_node(), don't use
of_graph_get_next_endpoint() directly. Replace it.
Signed-off-by: Kuninori Morimoto
Reviewed-by: Suzuki K Poulose
Reviewed-by: Laurent Pinchart
Reviewed-by: James Clark
---
drivers/hwtracin
On Mon, Jul 01, 2024 at 02:28:35PM +0530, Manikandan Muralidharan wrote:
> Add compatible string for the Microchip's AC40T08A MIPI Display
> panel.This panel uses a Himax HX8394 display controller.
> The reset line is not populated and leads to driver probe issues,
> thus add conditional block to n
Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
for once, to make this easily accessible to everyone.
Thomas, was there some progress wrt to fixing below regression? I might
have missed something, but from here it looks like this fall through the
cracks.
Makes me wonder if w
Hi Jonas,
On Monday, 1 July 2024 11:07:50 CEST Diederik de Haas wrote:
> On Saturday, 15 June 2024 19:03:51 CEST Jonas Karlman wrote:
> > This prepares and enable use of HDMI2.0 modes, e.g. 4K@60Hz, on RK3228,
> > RK3328, RK3399 and RK356x.
> > ...
> > This series may not fully depend on but was o
Den 2024-06-28 kl. 16:04, skrev Maxime Ripard:
> Hi,
>
> On Thu, Jun 27, 2024 at 09:22:56PM GMT, Maarten Lankhorst wrote:
>> Den 2024-06-27 kl. 19:16, skrev Maxime Ripard:
>>> Hi,
>>>
>>> Thanks for working on this!
>>>
>>> On Thu, Jun 27, 2024 at 05:47:21PM GMT, Maarten Lankhorst wrote:
T
Am 28.06.24 um 15:40 schrieb mrip...@kernel.org:
[SNIP]
So nobody can map that buffer, and the firmware driver is the one who
knows that this buffer cannot be accessed by anyone.
On most hw I know you can actually map that buffer, it's just that the
CPU sees only garbage in it because you don't
Hi Jonas,
On Saturday, 15 June 2024 19:03:51 CEST Jonas Karlman wrote:
> This prepares and enable use of HDMI2.0 modes, e.g. 4K@60Hz, on RK3228,
> RK3328, RK3399 and RK356x.
> ...
> This series may not fully depend on but was only tested together with
> the series "drm: bridge: dw_hdmi: Misc enabl
Hi all,
After merging the drm tree, today's linux-next build (powerpc
allyesconfig) failed like this:
In file included from arch/powerpc/include/asm/mmu.h:144,
from arch/powerpc/include/asm/paca.h:18,
from arch/powerpc/include/asm/current.h:13,
f
On Mon, 1 Jul 2024 at 09:26, zhaoxiong lv
wrote:
>
> On Fri, Jun 21, 2024 at 9:43 AM zhaoxiong lv
> wrote:
> >
> > On Fri, Jun 21, 2024 at 3:56 AM Dmitry Baryshkov
> > wrote:
> > >
> > > On Thu, Jun 20, 2024 at 07:52:45PM GMT, Zhaoxiong Lv wrote:
> > > > The bias IC of this starry-er88577 panel
On 28/06/2024 15:55, Boris Brezillon wrote:
> A sync-only job is meant to provide a synchronization point on a
> queue, so we can't return a NULL fence there, we have to add a signal
> operation to the command stream which executes after all other
> previously submitted jobs are done.
>
> Fixes: d
On 28/06/2024 15:55, Boris Brezillon wrote:
> The user is likely to leave all the drm_panthor_obj_array fields
> to zero when the array is empty, which will cause an EINVAL failure.
>
> Fixes: 4bdca1150792 ("drm/panthor: Add the driver frontend block")
> Signed-off-by: Boris Brezillon
Reviewed-b
Switch the driver to use devm_gpiod_get_optional() on reset_gpio to avoid
driver probe issues when reset line is not specified.
Signed-off-by: Manikandan Muralidharan
---
drivers/gpu/drm/panel/panel-himax-hx8394.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/dr
Add compatible string for the Microchip's AC40T08A MIPI Display
panel.This panel uses a Himax HX8394 display controller.
The reset line is not populated and leads to driver probe issues,
thus add conditional block to narrow reset-gpio property per variant.
Signed-off-by: Manikandan Muralidharan
-
This patch series adds panel himax display controller support for the
Microchip's AC40T08A MIPI display.
yaml file is validated using the following commands
make dt_binding_check DT_SCHEMA_FILES=
make CHECK_DTBS=y DT_SCHEMA_FILES=
Changelogs are available in respective patches.
Manikandan Mural
Add support for the Microchip AC40T08A MIPI Display panel. This panel uses
a Himax HX8394 display controller and requires a vendor provided init
sequence. The display resolution is 720x1280@60Hz with width and height
of 76mm and 132mm respectively.
Signed-off-by: Manikandan Muralidharan
---
driv
On Fri, 2024-06-28 at 20:06 +0200, Daniel Vetter wrote:
> On Thu, Jun 27, 2024 at 02:18:44PM +0200, Thomas Hellström wrote:
> > On Thu, 2024-06-27 at 10:04 +0200, Daniel Vetter wrote:
> > > On Wed, Jun 26, 2024 at 05:58:02PM +0200, Thomas Hellström wrote:
> > > > Hi!
> > > >
> > > > I'm seeing the
Hi Thomas,
On Mon, Jul 1, 2024 at 10:42 AM Thomas Huth wrote:
> On 28/06/2024 08.07, Thomas Zimmermann wrote:
> > Am 27.06.24 um 19:35 schrieb Thomas Huth:
> >> Starting with kernel 6.7, the framebuffer text console is not working
> >> anymore with the virtio-gpu device on s390x hosts. Such big e
On 28/06/2024 08.07, Thomas Zimmermann wrote:
Hi
Am 27.06.24 um 19:35 schrieb Thomas Huth:
Starting with kernel 6.7, the framebuffer text console is not working
anymore with the virtio-gpu device on s390x hosts. Such big endian fb
devices are usinga different pixel ordering than little endian d
Am 28.06.24 um 22:16 schrieb Nicolas Dufresne:
[SNIP]
Why can't you get this information from userspace?
Same reason amd and i915/xe also pass this around internally in the
kernel, it's just that for those gpus the render and kms node are the
same
driver so this is easy.
The reason I ask is t
Avoid pointer type value compared with 0 to make code clear.
./drivers/gpu/drm/amd/display/dc/dml2/dml21/src/dml2_pmo/dml2_pmo_factory.c:31:12-13:
WARNING comparing pointer to 0.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=9458
Signed-off-by: Jiapeng Chong
-
Avoid pointer type value compared with 0 to make code clear.
./drivers/gpu/drm/amd/display/dc/dml2/dml21/src/dml2_mcg/dml2_mcg_factory.c:19:12-13:
WARNING comparing pointer to 0.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=9458
Signed-off-by: Jiapeng Chong
-
Avoid pointer type value compared with 0 to make code clear.
./drivers/gpu/drm/amd/display/dc/dml2/dml21/src/dml2_dpmm/dml2_dpmm_factory.c:24:12-13:
WARNING comparing pointer to 0.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=9458
Signed-off-by: Jiapeng Chong
Avoid pointer type value compared with 0 to make code clear.
./drivers/gpu/drm/amd/display/dc/dml2/dml21/src/dml2_core/dml2_core_factory.c:14:12-13:
WARNING comparing pointer to 0.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=9458
Signed-off-by: Jiapeng Chong
On Sat, 29 Jun 2024 13:10:35 +0100
Liviu Dudau wrote:
> On Sat, Jun 29, 2024 at 10:52:56AM +0200, Boris Brezillon wrote:
> > On Fri, 28 Jun 2024 22:34:57 +0100
> > Liviu Dudau wrote:
> >
> > > On Fri, Jun 28, 2024 at 04:55:36PM +0200, Boris Brezillon wrote:
> > > > A sync-only job is meant
97 matches
Mail list logo
