Thomas Zimmermann writes:
> Hi
>
> Am 01.11.21 um 09:54 schrieb Sven Schnelle:
>> Hi Thomas,
>> Thomas Zimmermann writes:
>> Thanks, i wasn't aware as i normally don't do any graphics related
>> development. I take a look at dri and port the driver, which is
>> hopefully not too hard.
>
> Sounds
Hi
Am 05.11.21 um 19:18 schrieb Daniel Vetter:
On Fri, Nov 05, 2021 at 10:35:57AM +0100, Thomas Zimmermann wrote:
Wrap GEM SHMEM functions for struct drm_gem_object_funcs and update
all callers. This will allow for an update of the public interfaces
of the GEM SHMEM helper library.
Signed-off-
Hi
Am 05.11.21 um 18:59 schrieb Daniel Vetter:
On Mon, Nov 01, 2021 at 11:59:15PM +0800, kernel test robot wrote:
Hi Thomas,
I love your patch! Yet something to improve:
[auto build test ERROR on next-20211029]
[cannot apply to drm/drm-next shawnguo/for-next pinchartl-media/drm/du/next
v5.15
The MIPI DBI helpers access struct drm_gem_cma_object.vaddr in a
few places. Replace all instances with the correct generic GEM
functions. Use drm_gem_fb_vmap() for mapping a framebuffer's GEM
objects and drm_gem_fb_vunmap() for unmapping them. This removes
the dependency on CMA helpers within MIPI
Link drm_fb_cma_helper.o into drm_cma_helper.ko if CONFIG_DRM_KMS_HELPER
has been set. Remove CONFIG_DRM_KMS_CMA_HELPER config option. Selecting
KMS helpers and CMA will now automatically enable CMA KMS helpers.
Some drivers' Kconfig files did not correctly select KMS or CMA helpers.
Fix this as p
(no changes; resending for kernel CI)
Remove CMA dependencies from MIPI-DBI and replace the config
symbol DRM_KMS_CMA_HELPER with DRM_KMS_HELPER. This allows to
link drm_fb_cma_helper.o into a helper library.
Thomas Zimmermann (2):
drm/mipi-dbi: Remove dependency on GEM CMA helper library
drm
Hi Michael,
On Thu, Nov 04, 2021 at 02:19:33PM +0100, Michael Nazzareno Trimarchi wrote:
> Hi Sam
>
> On Sat, Oct 16, 2021 at 2:27 PM Sam Ravnborg wrote:
> >
> > Hi Michael,
> >
> > On Sat, Oct 16, 2021 at 10:22:27AM +, Michael Trimarchi wrote:
> > > This patch series add support for W552946
Since '8ede2ecc3e5e ("drm/msm/dp: Add DP compliance tests on Snapdragon
Chipsets")' the hpd_high member of struct dp_usbpd has been write-only.
Let's clean up the code a little bit by removing the writes as well.
Signed-off-by: Bjorn Andersson
---
drivers/gpu/drm/msm/dp/dp_display.c | 6 --
Hi Markus,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on pza/reset/next linus/master v5.15 next-20211106]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use
On Fri 05 Nov 16:22 CDT 2021, Kuogee Hsieh wrote:
> Currently the msm_dp_*** functions implement the same sequence which would
> happen when drm_bridge is used. hence get rid of this intermediate layer
> and align with the drm_bridge usage to avoid customized implementation.
>
> Signed-off-by: Ku
On Wed 03 Nov 19:34 CDT 2021, Dmitry Baryshkov wrote:
> The "vdd" regulator was used by the mdp5 driver only on downstream
> kernels, where the GDSC is represented as a regulator. On all current
> kernels the MDSS_GDSC is implemented as the power domain, removing the
> need for this regulator. Rem
Acked-by: Simon Ser
From: Kuogee Hsieh
Combo phy supports both USB and DP simultaneously. There may has a
possible conflict during phy initialization phase between USB and
DP driver which may cause USB phy timeout when USB tries to power
up its phy. This patch has the DP driver not initialize its phy
during DP drive
On 11/5/2021 10:48 AM, Bjorn Andersson wrote:
On Fri 05 Nov 10:28 PDT 2021, Kuogee Hsieh wrote:
From: Kuogee Hsieh
Combo phy supports both USB and DP simultaneously. There may has a
possible conflict during phy initialization phase between USB and
DP driver which may cause USB phy timeout w
Currently the msm_dp_*** functions implement the same sequence which would
happen when drm_bridge is used. hence get rid of this intermediate layer
and align with the drm_bridge usage to avoid customized implementation.
Signed-off-by: Kuogee Hsieh
Changes in v2:
-- revise commit text
-- rename d
The Lenovo Yoga Book X91F/L uses a panel which has been mounted
90 degrees rotated. Add a quirk for this.
Cc: Yauhen Kharuzhy
Signed-off-by: Hans de Goede
---
drivers/gpu/drm/drm_panel_orientation_quirks.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/gpu/drm/drm_panel_orien
As per CEA-861 quantization range is always limited in case of YUV
output - indepentently which CEA mode it is or if it is an DMT mode.
This is already correctly setup in HDMI AVI inforame, but we always do
a RGB to YUV conversion which doesn't consider that RGB input can be
full range as well.
Th
tree: git://people.freedesktop.org/~airlied/linux.git
drm-intel-display-refactor
head: cb45bcc9cf97016e5d4edb7a4196f0847437460e
commit: 678661f2ff1ba755fc652011d3edb2977165f508 [12/19] drm/i915/display: move
display dump/verify code to a separate file
config: i386-randconfig-a011-20211018 (at
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Andreas (icedragon...@web.de) changed:
What|Removed |Added
Kernel Version|5.14.15 |5.15
--
You may reply to
19 matches
Mail list logo