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=sc
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:
> > > >
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 p
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]: https://github.com/HimaxSoftware/D
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-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
---
.../gpu/drm/panel/panel-b
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 change
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: A
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 +++
drivers/acc
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 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(+)
dif
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
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 file
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
Documentation/ABI/sta
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 disp
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_ belong
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' desc
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 pa
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.
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 alre
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 that
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 example,
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 ++
1
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 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 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 trans
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. Ple
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:
https://lore.kernel.org/all/20230
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 6b901b342348..a19d85
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
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: Loui
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:
drivers/gpu/drm/panel/panel-samsung-s
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 bec
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
---
dri
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
---
...
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 (!intel_gt_
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
Review
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 usi
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 Zimme
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 entirel
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. 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 entirel
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 no
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 entirel
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 entire
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 thems
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 entirel
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.
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. 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 enti
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 fbdev callbacks. i915 was the only
caller of the DRM helpers, so remove them from the helper module.
i915's fbdev emulation is still incomplete as it do
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 entirely
On Tue, May 23, 2023 at 02:53:47PM -0700, Justin Chen wrote:
> Add maintainers entry for ASP 2.0 Ethernet driver.
>
> Signed-off-by: Florian Fainelli
> Signed-off-by: Justin Chen
Reviewed-by: Simon Horman
On Tue, May 23, 2023 at 02:53:42PM -0700, Justin Chen wrote:
> The ASP 2.0 Ethernet controller uses a brcm unimac.
>
> Acked-by: Conor Dooley
> Signed-off-by: Florian Fainelli
> Signed-off-by: Justin Chen
Reviewed-by: Simon Horman
On Tue, May 23, 2023 at 02:53:45PM -0700, Justin Chen wrote:
> Add mdio compat string for ASP 2.0 ethernet driver.
>
> Signed-off-by: Florian Fainelli
> Signed-off-by: Justin Chen
> Reviewed-by: Andrew Lunn
Reviewed-by: Simon Horman
On Tue, May 23, 2023 at 02:53:46PM -0700, Justin Chen wrote:
> From: Florian Fainelli
>
> 74165 is a 16nm process SoC with a 10/100 integrated Ethernet PHY,
> utilize the recently defined 16nm EPHY macro to configure that PHY.
>
> Signed-off-by: Florian Fainelli
> Signed-off-by: Justin Chen
>
Change magic numerical masks with usage of the GENMASK() macro
to improve readability.
This commit brings no functional changes.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 46 --
1 file changed, 24 insertions(+), 22 deletions(
In mtk_dsi_phy_timconfig(), we're dividing the `data_rate` variable,
expressed in Hz to retrieve a value in MHz: instead of open-coding,
use the HZ_PER_MHZ definition, available in linux/units.h.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 3 ++-
1 file ch
This series performs some cleanups for mtk_dsi, enhancing human
readability, using kernel provided macros where possible and
also reducing code size.
Tested on MT8173 and MT8192 Chromebooks (using a DSI<->DP bridge)
and on MT6795 Sony Xperia M5 (DSI video mode panel).
Please note:
This series dep
Instead of open coding bitshifting for various register fields,
use the bitfield macro FIELD_PREP(): this allows to enhance the
human readability, decrease likeliness of mistakes (and register
field overflowing) and also to simplify the code.
The latter is especially seen in mtk_dsi_rxtx_control(),
Function mtk_dsi_ps_control() is a subset of mtk_dsi_ps_control_vact():
merge the two in one mtk_dsi_ps_control() function by adding one
function parameter `config_vact` which, when true, writes the VACT
related registers.
Signed-off-by: AngeloGioacchino Del Regno
---
drivers/gpu/drm/mediatek/m
On 24/05/2023 10:43, Artur Weber wrote:
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
Il 24/05/23 10:30, Julien Stephan ha scritto:
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 |
Il 24/05/23 10:30, Julien Stephan ha scritto:
Add definition for CDPHY phy type that can be configured in either D-PHY
mode or C-PHY mode
Signed-off-by: Julien Stephan
Reviewed-by: AngeloGioacchino Del Regno
---
include/dt-bindings/phy/phy.h | 1 +
1 file changed, 1 insertion(+)
diff
Hi,
On Wed, 24 May 2023 10:43:24 +0200, Artur Weber wrote:
> 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 t
On 2023-05-23 13:01:13, Abhinav Kumar wrote:
>
>
> On 5/21/2023 10:21 AM, Dmitry Baryshkov wrote:
> > Drop SSPP-specifig debugfs register dumps in favour of using
> > debugfs/dri/0/kms or devcoredump.
> >
>
> I did see another series which removes src_blk from the catalog (I am
> yet to review
On Mon, May 22, 2023 at 02:53:48PM -0700, Bjorn Andersson wrote:
> On Mon, May 22, 2023 at 03:51:01PM -0500, Bjorn Andersson wrote:
> > On Fri, Oct 08, 2021 at 03:38:21PM +0300, Heikki Krogerus wrote:
> > > Hi,
> > >
> > > On Thu, Oct 07, 2021 at 09:15:12AM -0700, Bjorn Andersson wrote:
> > > > Th
Hi,
On 23/05/2023 21:27, Douglas Anderson wrote:
In a whole pile of panel drivers, we have code to make the
prepare/unprepare/enable/disable callbacks behave as no-ops if they've
already been called. It's silly to have this code duplicated
everywhere. Add it to the core instead so that we can ev
On Wed, May 24, 2023 at 11:29 AM Stanislaw Gruszka
wrote:
>
> 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.
On Wed, 24 May 2023 at 12:48, Marijn Suijten
wrote:
>
> On 2023-05-23 13:01:13, Abhinav Kumar wrote:
> >
> >
> > On 5/21/2023 10:21 AM, Dmitry Baryshkov wrote:
> > > Drop SSPP-specifig debugfs register dumps in favour of using
> > > debugfs/dri/0/kms or devcoredump.
> > >
> >
> > I did see another
On Wed, May 24, 2023 at 2:34 AM Kevin Hilman wrote:
>
> 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
The test robot reports some make warnings.
Fix those warnings:
drivers/gpu/drm/i915/i915_gpu_error.c:2174: warning: Function parameter or
member 'dump_flags' not described in 'i915_capture_error_state'
drivers/gpu/drm/i915/i915_perf.c:5307: warning: Function parameter or
member 'i915' no
The test robot reports some make warnings.
Fix those warnings:
drivers/gpu/drm/i915/gt/intel_gtt.h:499: warning: Function parameter or
member 'vm' not described in 'i915_vm_resv_put'
drivers/gpu/drm/i915/gt/intel_context.h:108: warning: Function parameter or
member 'ce' not described in
The test robot reports some make warnings.
Fix those warnings:
drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:491: warning: Function
parameter or member 'marker' not described in 'guc_log_buffer_state'
drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h:491: warning: Function
parameter or member 'r
Hello Azeem,
On Tue, 23 May 2023 at 22:52, Kees Cook wrote:
>
> On Tue, May 23, 2023 at 02:19:43AM +, Azeem Shaikh wrote:
> > strlcpy() reads the entire source buffer first.
> > This read may exceed the destination size limit.
> > This is both inefficient and can lead to linear read
> > over
On Wed, May 24, 2023 at 01:27:00PM +0300, Oded Gabbay wrote:
> On Wed, May 24, 2023 at 2:34 AM Kevin Hilman wrote:
> >
> > 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
> > >>
The test robot reports some make warnings.
Fix those warnings:
drivers/gpu/drm/i915/pxp/intel_pxp_types.h:96: warning: Function parameter
or member 'dev_link' not described in 'intel_pxp'
Reported-by: k2ci
Signed-off-by: pengfuyuan
---
drivers/gpu/drm/i915/pxp/intel_pxp_types.h | 2 +-
1
Hi,
sorry that this took so long.
Am 24.05.23 um 04:34 schrieb Jammy Huang:
Hi Thomas,
Could you help review this patch?
This is an issue leading to kernel panic found by Intel. Wendy has
confirmed issue resolved by this patch.
On 2023/4/14 下午 03:42, Jammy Huang wrote:
In resume, DP's lau
Hi,
this patch also fell through the cracks. Apologies.
Am 24.05.23 um 04:29 schrieb Jammy Huang:
Hi Thomas,
Do you have other suggestion for this patch??
The main issue was that struct ast_private is now called struct
ast_device. So the current patch cannot be applied.
Please kindly a
On Wed, 24 May 2023, pengfuyuan wrote:
> The test robot reports some make warnings.
>
> Fix those warnings:
> drivers/gpu/drm/i915/i915_gpu_error.c:2174: warning: Function parameter
> or member 'dump_flags' not described in 'i915_capture_error_state'
> drivers/gpu/drm/i915/i915_perf.c:530
On 23/05/2023 16: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
---
Thanks a lot. Pushed to drm-misc-fixes.
Am 23.05.23 um 17:06 schrieb Geert Uytterhoeven:
Fbtest contains some very simple validation of the fbdev userspace API
contract. When used with shmob-drm, it reports the following warnings
and errors:
height changed from 68 to 0
height was rou
Hi
Am 23.05.23 um 17:31 schrieb Geert Uytterhoeven:
Hi all,
Currently, there are two drivers for the LCD controller on Renesas
SuperH-based and ARM-based SH-Mobile and R-Mobile SoCs:
1. sh_mobile_lcdcfb, using the fbdev framework,
2. shmob_drm, using the DRM framework.
However, on
Kuogee Hsieh writes:
> The internal_hpd flag is set to true by dp_bridge_hpd_enable() and set to
> false by dp_bridge_hpd_disable() to handle GPIO pinmuxed into DP controller
> case. HDP related interrupts can not be enabled until internal_hpd is set
> to true. At current implementation dp_display
Hi Thomas,
On Wed, May 24, 2023 at 1:42 PM Thomas Zimmermann wrote:
> Am 23.05.23 um 17:31 schrieb Geert Uytterhoeven:
> > Currently, there are two drivers for the LCD controller on Renesas
> > SuperH-based and ARM-based SH-Mobile and R-Mobile SoCs:
> >1. sh_mobile_lcdcfb, using the fbdev fra
On 23/05/2023 09:37, Andi Shyti wrote:
Hi Fei,
finally... pushed in drm-intel-gt-next! :)
I had to revert this (uapi commit only) by force pushing, luckily it was
the top commit.
1)
IGT is not merged yet.
2)
The tools/include/uapi/drm/i915_drm.h part of the patch was not removed.
Please
Am 24.05.23 um 13:54 schrieb Geert Uytterhoeven:
Hi Thomas,
On Wed, May 24, 2023 at 1:42 PM Thomas Zimmermann wrote:
Am 23.05.23 um 17:31 schrieb Geert Uytterhoeven:
Currently, there are two drivers for the LCD controller on Renesas
SuperH-based and ARM-based SH-Mobile and R-Mobile SoCs:
On 24/05/2023 12:56, Tvrtko Ursulin wrote:
On 23/05/2023 09:37, Andi Shyti wrote:
Hi Fei,
finally... pushed in drm-intel-gt-next! :)
I had to revert this (uapi commit only) by force pushing, luckily it was
the top commit.
1)
IGT is not merged yet.
2)
The tools/include/uapi/drm/i915_drm
Hi Tvrtko,
> > finally... pushed in drm-intel-gt-next! :)
>
> I had to revert this (uapi commit only) by force pushing, luckily it was the
> top commit.
OK, sorry!
> 1)
> IGT is not merged yet.
if igt is merged without the kernel it would fail, though.
> 2)
> The tools/include/uapi/drm/i915_d
Hi again,
> > > finally... pushed in drm-intel-gt-next! :)
> >
> > I had to revert this (uapi commit only) by force pushing, luckily it was the
> > top commit.
>
> OK, sorry!
>
> > 1)
> > IGT is not merged yet.
>
> if igt is merged without the kernel it would fail, though.
can we at least agr
Hi all,
This patch series adds support for the Ampire AM-800480L1TMQW-T00H 5"
WVGA TFT LCD panel, which can be found on e.g. the Atmark Techno
Armadillo-800-EVA development board.
It has been tested with a WIP DT-enhanced version of the shmob-drm
driver.
Thanks for your comments!
Geert
Document support for the Ampire AM-800480L1TMQW-T00H 5" WVGA TFT LCD
panel.
Signed-off-by: Geert Uytterhoeven
---
.../devicetree/bindings/display/panel/panel-simple.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/panel/panel-simple.yam
Add support for the Ampire AM-800480L1TMQW-T00H 5" WVGA TFT LCD panel.
Signed-off-by: Geert Uytterhoeven
---
drivers/gpu/drm/panel/panel-simple.c | 33
1 file changed, 33 insertions(+)
diff --git a/drivers/gpu/drm/panel/panel-simple.c
b/drivers/gpu/drm/panel/panel-
On 24/05/2023 13:19, Andi Shyti wrote:
Hi Tvrtko,
finally... pushed in drm-intel-gt-next! :)
I had to revert this (uapi commit only) by force pushing, luckily it was the
top commit.
OK, sorry!
1)
IGT is not merged yet.
if igt is merged without the kernel it would fail, though.
Ideal
Both the patform_driver and mipi_dsi_driver structures contain pointers
to the match table used, so the custom code to obtain match and match
data can be replaced by calls to of_device_get_match_data().
Signed-off-by: Geert Uytterhoeven
---
drivers/gpu/drm/panel/panel-simple.c | 15 ++---
On Tue, May 23, 2023 at 12:01:34PM +0300, Lisovskiy, Stanislav wrote:
> On Tue, May 16, 2023 at 02:40:27PM +0300, Ville Syrjälä wrote:
> > On Tue, May 16, 2023 at 01:43:44PM +0300, Lisovskiy, Stanislav wrote:
> > > On Fri, May 12, 2023 at 11:54:16AM +0530, Ankit Nautiyal wrote:
> > > > Currently, w
Hi Dave and Daniel,
here is this week's PR for drm-misc-next. I'm taking over while Maxime
is away. There's support for a few more panels and bridges. In fbdev,
I/O helpers are now implemented within the architecture code. DRM's
shmobile driver received some updates.
Best regards
Thomas
drm-misc
Hi Adam,
On Tue, May 23, 2023 at 8:49 PM Adam Ford wrote:
> Inki,
>
> I haven't heard back from you on whether or not you want the bindings
> patch to be included with me resending the series as V7 or if you're
> OK with a single, stand-alone patch.
> Will you let me know? I have the patch stan
On Wed, May 24, 2023 at 7:45 AM Fabio Estevam wrote:
>
> Hi Adam,
>
> On Tue, May 23, 2023 at 8:49 PM Adam Ford wrote:
>
> > Inki,
> >
> > I haven't heard back from you on whether or not you want the bindings
> > patch to be included with me resending the series as V7 or if you're
> > OK with a s
On 24/05/2023 13:30, Andi Shyti wrote:
Hi again,
finally... pushed in drm-intel-gt-next! :)
I had to revert this (uapi commit only) by force pushing, luckily it was the
top commit.
OK, sorry!
1)
IGT is not merged yet.
if igt is merged without the kernel it would fail, though.
can we
1 - 100 of 253 matches
Mail list logo
