Hi Matt,
Always use the dim tooling when applying patches, it will do the right
thing with regards to adding the S-o-b.
Regards, Joonas
Quoting Stephen Rothwell (2021-07-15 07:18:54)
> Hi all,
>
> Commit
>
> db47fe727e1f ("drm/i915/step: s/_revid_tbl/_revids")
>
> is missing a Signed-off-by
Hi Linus,
Regular weekly fixes pull, live from a Brisbane lockdown with kids at home.
A big bunch of scattered amdgpu fixes, but they are all pretty small,
minor i915 fixes, kmb, and one vmwgfx regression fixes, all pretty
quiet for this time.
Dave.
drm-fixes-2021-08-06:
drm fixes for 5.14-rc5
VM_BIND design document with description of intended use cases.
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/gpu/rfc/i915_vm_bind.rst | 126 +
Documentation/gpu/rfc/index.rst| 4 +
2 files changed, 130 insertions(+)
create mode 100644 Documentatio
This is the i915 driver VM_BIND feature design RFC patch series along
with the required uapi definition and description of intended use cases.
Signed-off-by: Niranjana Vishwanathapura
Niranjana Vishwanathapura (2):
drm/doc/rfc: VM_BIND feature design document
drm/doc/rfc: VM_BIND uapi defini
VM_BIND and GEM_WAIT_USER_FENCE uapi document
Signed-off-by: Niranjana Vishwanathapura
---
Documentation/gpu/rfc/i915_vm_bind.h | 113 +
Documentation/gpu/rfc/i915_vm_bind.rst | 6 ++
2 files changed, 119 insertions(+)
create mode 100644 Documentation/gpu/rfc/i915_vm
The user can open multiple device FDs if it likes, however these open()
functions call vfio_register_notifier() on some device global
state. Calling vfio_register_notifier() twice in will trigger a WARN_ON
from notifier_chain_register() and the first close will wrongly delete the
notifier and more.
This symbol is not used outside of dw-mipi-dsi-rockchip.c, so marks
it static.
Fix the following sparse warning:
drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c:646:13: warning: symbol
'hstt_table' was not declared. Should it be static?
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
Address the following checkpatch errors:
ERROR: do not initialise statics to false
FILE: :drivers/gpu/drm/msm/msm_drv.c:21:
-static bool reglog = false;
FILE: :drivers/gpu/drm/msm/msm_drv.c:31:
-bool dumpstate = false;
Signed-off-by: zhaoxiao
---
v2: change the patch description
drivers/gpu/d
The user can open multiple device FDs if it likes, however the open
function calls vfio_register_notifier() on device global state. Calling
vfio_register_notifier() twice will trigger a WARN_ON from
notifier_chain_register() and the first close will wrongly delete the
notifier and more.
Since thes
The patch to move the get/put to core and the patch to convert the samples
to use vfio_device crossed in a way that this was missed. When both
patches are together the samples do not need their own get/put.
Fixes: 437e41368c01 ("vfio/mdpy: Convert to use vfio_register_group_dev()")
Fixes: 681c1615
Platform simply wants to run some code when the device is first
opened/last closed. Use the core framework and locking for this. Aside
from removing a bit of code this narrows the locking scope from a global
lock.
Reviewed-by: Cornelia Huck
Reviewed-by: Eric Auger
Reviewed-by: Christoph Hellwig
The core code no longer requires these ops to be defined, so delete these
empty functions and leave the op as NULL. mtty's functions only log a
pointless message, delete that entirely.
Signed-off-by: Yishai Hadas
Reviewed-by: Cornelia Huck
Reviewed-by: Christoph Hellwig
Signed-off-by: Jason Gun
FSL uses the internal reflck to implement the open_device() functionality,
conversion to the core code is straightforward.
The decision on which set to be part of is trivially based on the
is_fsl_mc_bus_dprc() and we use a 'struct device *' pointer as the set_id.
The dev_set lock is protecting th
Nothing uses this anymore, delete it.
Signed-off-by: Yishai Hadas
Reviewed-by: Christoph Hellwig
Signed-off-by: Jason Gunthorpe
---
drivers/vfio/mdev/vfio_mdev.c | 22 --
drivers/vfio/vfio.c | 14 +-
include/linux/mdev.h | 7 ---
include/
From: Max Gurtovoy
This pairs with vfio_init_group_dev() and allows undoing any state that is
stored in the vfio_device unrelated to registration. Add appropriately
placed calls to all the drivers.
The following patch will use this to add pre-registration state for the
device set.
Signed-off-by
Like vfio_pci_dev_set_try_reset() this code wants to reset all of the
devices in the "reset group" which is the same membership as the device
set.
Instead of trying to reconstruct the device set from the PCI list go
directly from the device set's device list to execute the reset.
The same basic s
From: Yishai Hadas
PCI wants to have the usual open/close_device() logic with the slight
twist that the open/close_device() must be done under a singelton lock
shared by all of the vfio_devices that are in the PCI "reset group".
The reset group, and thus the device set, is determined by what dev
Currently the driver ops have an open/release pair that is called once
each time a device FD is opened or closed. Add an additional set of
open/close_device() ops which are called when the device FD is opened for
the first time and closed for the last time.
An analysis shows that all of the driver
Convert mbochs to use an atomic scheme for this like mtty was changed
into. The atomic fixes various race conditions with probing. Add the
missing error unwind. Also add the missing kfree of mdev_state->pages.
Fixes: 681c1615f891 ("vfio/mbochs: Convert to use vfio_register_group_dev()")
Reported-b
vfio_pci_try_bus_reset() is triggering a reset of the entire_dev set if
any device within it has accumulated a needs_reset. This reset can only be
done once all of the drivers operating the PCI devices to be reset are in
a known safe state.
Make this clearer by directly operating on the dev_set in
mbochs_close() iterates over global device state and frees it. Currently
this is done every time a device FD is closed, but if multiple device FDs
are open this could corrupt other still active FDs.
Change this to use close_device() so it only runs on the last close.
Reviewed-by: Cornelia Huck
R
This is in support of Max's series to split vfio-pci. For that to work the
reflck concept embedded in vfio-pci needs to be sharable across all of the
new VFIO PCI drivers which motivated re-examining how this is
implemented.
Another significant issue is how the VFIO PCI core includes code like:
Hi Dave, Daniel,
Same pull, more S-o-b.
The following changes since commit d28e2568ac26fff351c846bf74ba6ca5dded733e:
Merge tag 'amd-drm-fixes-5.14-2021-07-28' of
https://gitlab.freedesktop.org/agd5f/linux into drm-fixes (2021-07-29 17:20:29
+1000)
are available in the Git repository at:
https://bugzilla.kernel.org/show_bug.cgi?id=213201
Erhard F. (erhar...@mailbox.org) changed:
What|Removed |Added
Attachment #297921|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=213201
--- Comment #12 from Erhard F. (erhar...@mailbox.org) ---
Created attachment 298217
--> https://bugzilla.kernel.org/attachment.cgi?id=298217&action=edit
kernel dmesg (5.14-rc4, AMD A10-7860K)
--
You may reply to this email to add a comment.
Y
https://bugzilla.kernel.org/show_bug.cgi?id=213201
Erhard F. (erhar...@mailbox.org) changed:
What|Removed |Added
Attachment #296969|0 |1
is obsolete|
Hi Thomas,
> -Original Message-
> From: Thomas Zimmermann
> Sent: Wednesday, August 4, 2021 12:11 AM
> To: Chrisanthus, Anitha ; Sam Ravnborg
>
> Cc: dan...@ffwll.ch; airl...@linux.ie; alexander.deuc...@amd.com;
> christian.koe...@amd.com; liviu.du...@arm.com; brian.star...@arm.com;
> bb
Thanks Thomas, I'll keep this in mind for the next patch.
> -Original Message-
> From: dri-devel On Behalf Of
> Thomas Zimmermann
> Sent: Wednesday, August 4, 2021 11:13 AM
> To: Chrisanthus, Anitha ; dri-
> de...@lists.freedesktop.org; Dea, Edmund J
> Subject: Re: [PATCH 02/14] drm/kmb:
On Thu, Aug 05, 2021 at 11:33:11AM -0600, Alex Williamson wrote:
> > +static int vfio_pci_is_device_in_set(struct pci_dev *pdev, void *data)
> > +{
> > + struct vfio_device_set *dev_set = data;
> > + struct vfio_device *cur;
> > +
> > + lockdep_assert_held(&dev_set->lock);
> > +
> > + list_
On Thu, Aug 5, 2021 at 3:47 AM Daniel Vetter wrote:
>
> Originally drm_sched_job_init was the point of no return, after which
> drivers must submit a job. I've split that up, which allows us to fix
> this issue pretty easily.
>
> Only thing we have to take care of is to not skip to error paths aft
From: Zi Yan
This prepares for the upcoming changes to make MAX_ORDER a boot time
parameter instead of compilation time constant. All static arrays with
MAX_ORDER size are converted to pointers and their memory is allocated
at runtime.
free_area array in struct zone is allocated using memblock_a
Hi Markuss,
sorry for reacting so late!
On Thu, Aug 5, 2021 at 3:36 PM Markuss Broks wrote:
> +#define s6d27a1_command(ctx, cmd, seq...) \
> +({ \
> + struct mipi_dbi *dbi = &ctx->dbi; \
> + int ret; \
> + ret = mipi_dbi_command(dbi, cmd, seq); \
> + if (ret) { \
> +
Hi CK,
On Sun, 2021-08-01 at 08:33 +0800, Chun-Kuang Hu wrote:
> Hi, Jason:
>
> jason-jh.lin 於 2021年7月30日 週五 上午1:07寫道：
> >
> > Add MERGE module file:
> >
> > MERGE module is used to merge two slice-per-line inputs
> > into one side-by-side output.
> >
> > Signed-off-by: jason-jh.lin
> > ---
Hi CK,
On Sat, 2021-07-31 at 07:11 +0800, Chun-Kuang Hu wrote:
> Hi, Jason:
>
> jason-jh.lin 於 2021年7月30日 週五 上午1:07寫道：
> >
> > Add DSC into mtk_drm_ddp_comp to support for mt8195.
> >
> > DSC is designed for real-time systems with real-time compression,
> > transmission, decompression and disp
Add mtk-mutex support for mt8195 vdosys0.
Signed-off-by: jason-jh.lin
---
This patch is base on [1]
[1] dt-bindings: mediatek: display: add mt8195 SoC binding
https://patchwork.kernel.org/project/linux-mediatek/patch/20210805171346.24249-5-jason-jh@mediatek.com/
---
drivers/soc/mediatek/mtk
Add MERGE engine file:
MERGE module is used to merge two slice-per-line inputs
into one side-by-side output.
Signed-off-by: jason-jh.lin
---
This patch is base on [1]
[1] dt-bindings: mediatek: display: add mt8195 SoC binding
https://patchwork.kernel.org/project/linux-mediatek/patch/202108051713
Add display node for vdosys0.
Signed-off-by: jason-jh.lin
---
This patch is based on [1][2][3][4]
[1]arm64: dts: Add Mediatek SoC MT8195 and evaluation board dts and Makefile
-
https://patchwork.kernel.org/project/linux-mediatek/patch/20210601075350.31515-2-seiya.w...@mediatek.com/
[2]arm64: dt
DSC is designed for real-time systems with real-time compression,
transmission, decompression and display.
The DSC standard is a specification of the algorithms used for
compressing and decompressing image display streams, including
the specification of the syntax and semantics of the compressed
vi
Add driver data of mt8195 vdosys0 to mediatek-drm and the sub driver.
Signed-off-by: jason-jh.lin
---
This patch is base on [1]
[1] dt-bindings: mediatek: display: add mt8195 SoC binding
https://patchwork.kernel.org/project/linux-mediatek/patch/20210805171346.24249-5-jason-jh@mediatek.com/
-
Add mt8195 vdosys0 clock driver name and routing table to
the driver data of mtk-mmsys.
Signed-off-by: jason-jh.lin
---
This patch is base on [1]
[1] dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding
https://patchwork.kernel.org/project/linux-mediatek/patch/20210805171346.24249-2-jason-j
1. Adjust to the alphabetic order for the define, function, struct
and array in mediatek-drm driver
2. Remove the unsed define in mtk_drm_ddp_comp.c
Signed-off-by: jason-jh.lin
---
drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 180 +---
drivers/gpu/drm/mediatek/mtk_drm_ddp_com
The hardware path of vdosys0 with eDP panel output need to go through
by several modules, such as, OVL, RDMA, COLOR, CCORR, AAL, GAMMA,
DITHER, DSC and MERGE.
Change in v6:
- adjust alphabetic order for mediatek-drm
- move the patch that add mt8195 support for mediatek-drm as the lastest patch
- a
Response with correct edid checksum saved at connector after corrupted edid
checksum read. This fixes Link Layer CTS cases 4.2.2.3, 4.2.2.6.
Signed-off-by: Kuogee Hsieh
---
drivers/gpu/drm/msm/dp/dp_panel.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/
Aux hardware calibration sequence requires resetting the aux controller
in order for the new setting to take effect. However resetting the AUX
controller will also clear HPD interrupt status which may accidentally
cause pending unplug interrupt to get lost. Therefore reset aux
controller only when
Initialize both pre-emphasis and voltage swing level to 0 before
start link training and do not end link training until video is
ready to reduce the period between end of link training and video
start to meet Link Layer CTS requirement. Some dongle main link
symbol may become unlocked again if hos
Remove special handling of replug interrupt and instead treat replug event
as a sequential unplug followed by a plugin event. This is needed to meet
the requirements of DP Link Layer CTS test case 4.2.1.3.
Changes in V2:
-- add fixes statement
Changes in V3:
-- delete EV_HPD_REPLUG_INT
Fixes: f2
Reduce link rate and re start link training if link training 1
failed due to loss of clock recovery done to fix Link Layer
CTS case 4.3.1.7. Also only update voltage and pre-emphasis
swing level after link training started to fix Link Layer CTS
case 4.3.1.6.
Changes in V2:
-- replaced cr_status w
DP cable should always connect to DPU during the entire PHY compliance
testing run. Since DP PHY compliance test is executed at irq_hpd event
context, dp_ctrl_off_link_stream() should be used instead of dp_ctrl_off().
dp_ctrl_off() is used for unplug event which is triggered when DP cable is
dis co
add fixes to pass DP Link Layer compliance test cases
Kuogee Hsieh (6):
drm/msm/dp: use dp_ctrl_off_link_stream during PHY compliance test run
drm/msm/dp: reduce link rate if failed at link training 1
drm/msm/dp: reset aux controller after dp_aux_cmd_fifo_tx() failed.
drm/msm/dp: replug ev
Hi!
Dne četrtek, 05. avgust 2021 ob 20:50:39 CEST je Robert Foss napisal(a):
> The return value of drm_bridge_attach() is ignored during
> the it66121_bridge_attach() call, which is incorrect.
>
> Fixes: 988156dc2fc9 ("drm: bridge: add it66121 driver")
> Signed-off-by: Robert Foss
> ---
> drive
On 29/06/2021 16:58, Thomas Zimmermann wrote:
Print the name of the DRM driver when taking over fbdev devices. Makes
the output to dmesg more consistent. Note that the driver name is only
used for printing a string to the kernel log. No UAPI is affected by this
change.
Signed-off-by: Thomas Zimm
Hi everyone! I got some questions from someone that made me realize that
there's a couple of things that I forgot to mention here that might be
useful for folks to know regarding being a mentor:
* "Who decides what project and what student?"
It's up to the student to come up with ideas for what
Hi Greg,
Le jeu., août 5 2021 at 21:35:34 +0200, Greg Kroah-Hartman
a écrit :
On Thu, Aug 05, 2021 at 09:21:09PM +0200, Paul Cercueil wrote:
When the drivers of remote devices (e.g. HDMI chip) are disabled in
the
config, we want the ingenic-drm driver to be able to probe
nonetheless
with
On 5 Aug 2021, at 15:16, Christian König wrote:
> Am 05.08.21 um 21:02 schrieb Zi Yan:
>> From: Zi Yan
>>
>> This prepares for the upcoming changes to make MAX_ORDER a boot time
>> parameter instead of compilation time constant. All static arrays with
>> MAX_ORDER size are converted to pointers a
Applied. Thanks!
Alex
On Thu, Aug 5, 2021 at 2:44 PM Christophe JAILLET
wrote:
>
> 'watermarks_table' must be freed instead 'clocks_table', because
> 'clocks_table' is known to be NULL at this point and 'watermarks_table' is
> never freed if the last kzalloc fails.
>
> Fixes: c98ee89736b8 ("drm
On Thu, Aug 5, 2021 at 6:46 AM Zhenneng Li wrote:
>
>
> When primary bo is updated, crtc's pitch may
> have not been updated, this will lead to show
> disorder content when user changes display mode,
> we update crtc's pitch in page flip to avoid
> this bug.
> This refers to amdgpu's pageflip.
>
>
On Thu, Aug 05, 2021 at 09:21:09PM +0200, Paul Cercueil wrote:
> When the drivers of remote devices (e.g. HDMI chip) are disabled in the
> config, we want the ingenic-drm driver to be able to probe nonetheless
> with the other devices (e.g. internal LCD panel) that are enabled.
>
> Signed-off-by:
On Thu, Aug 05, 2021 at 09:21:08PM +0200, Paul Cercueil wrote:
> Export this function as a GPL symbol, so that it can be used from
> modules.
>
> Signed-off-by: Paul Cercueil
> ---
> drivers/base/dd.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/base/dd.c b/drivers/base/dd.c
On Thu, Aug 05, 2021 at 03:30:55PM +0800, Xin Ji wrote:
> IVO panel require less input video clock variation than video clock
> variation in DP CTS spec.
>
> This patch decreases the K value of ANX7625 which will shrink eDP Tx
> video clock variation to meet IVO panel's requirement.
>
> Signed-of
Hi Markuss,
On Thu, Aug 05, 2021 at 04:33:42PM +0300, Markuss Broks wrote:
> This adds a driver for Samsung S6D27A1 display controller and panel.
> This panel is found in the Samsung GT-I8160 mobile phone,
> and possibly some other mobile phones.
>
> This display needs manufacturer commands to co
When the drivers of remote devices (e.g. HDMI chip) are disabled in the
config, we want the ingenic-drm driver to be able to probe nonetheless
with the other devices (e.g. internal LCD panel) that are enabled.
Signed-off-by: Paul Cercueil
---
drivers/gpu/drm/ingenic/ingenic-drm-drv.c | 12 ++
Export this function as a GPL symbol, so that it can be used from
modules.
Signed-off-by: Paul Cercueil
---
drivers/base/dd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/base/dd.c b/drivers/base/dd.c
index daeb9b5763ae..658f1527a58b 100644
--- a/drivers/base/dd.c
+++ b/drivers/ba
Hi,
A small patchset to make sure that the ingenic-drm driver won't fail to
probe if an optional device (e.g. HDMI chip) has its driver disabled in
the kernel config.
Since most of the boards using the ingenic-drm driver have a LCD panel
attached, the drivers for external devices (be it a HDMI tr
Hi Markuss,
On Thu, Aug 05, 2021 at 04:33:41PM +0300, Markuss Broks wrote:
> This adds device-tree bindings for the Samsung S6D27A1 RGB
> DPI display panel.
>
> Signed-off-by: Markuss Broks
> ---
> .../display/panel/samsung,s6d27a1.yaml| 97 +++
> 1 file changed, 97 inse
Am 05.08.21 um 21:02 schrieb Zi Yan:
From: Zi Yan
This prepares for the upcoming changes to make MAX_ORDER a boot time
parameter instead of compilation time constant. All static arrays with
MAX_ORDER size are converted to pointers and their memory is allocated
at runtime.
Well in general I st
Hey Xin,
Thanks for submitting this.
On Thu, 5 Aug 2021 at 09:31, Xin Ji wrote:
>
> IVO panel require less input video clock variation than video clock
> variation in DP CTS spec.
>
> This patch decreases the K value of ANX7625 which will shrink eDP Tx
> video clock variation to meet IVO panel's
Hi Oleksij,
On Thu, Aug 05, 2021 at 01:19:42PM +0200, Oleksij Rempel wrote:
> changes v2:
> - set connector_type to DRM_MODE_CONNECTOR_DPI for the
> logictechno_lttd800480070_l6wh_rt panel
>
> Sam Ravnborg (1):
> drm/panel: simple: add Multi-Innotechnology MI1010AIT-1CP1
>
> Søren Andersen (
The return value of drm_bridge_attach() is ignored during
the it66121_bridge_attach() call, which is incorrect.
Fixes: 988156dc2fc9 ("drm: bridge: add it66121 driver")
Signed-off-by: Robert Foss
---
drivers/gpu/drm/bridge/ite-it66121.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/driver
'watermarks_table' must be freed instead 'clocks_table', because
'clocks_table' is known to be NULL at this point and 'watermarks_table' is
never freed if the last kzalloc fails.
Fixes: c98ee89736b8 ("drm/amd/pm: add the fine grain tuning function for
vangogh")
Signed-off-by: Christophe JAILLET
Hi
Am 23.07.21 um 09:36 schrieb Daniel Vetter:
The real fix is to get at the architecture-specific wc allocator, which is
currently not something that's exposed, but hidden within the dma api. I
think having this stick out like this is better than hiding it behind fake
generic code (like we do
On Thu, Aug 5, 2021 at 2:14 PM Linus Torvalds
wrote:
>
> This might possibly have been fixed already by the previous drm pull,
> but I wanted to report it anyway, just in case.
>
> It happened after an uptime of over a week, so it might not be trivial
> to reproduce.
>
> It's a NULL pointer derefe
This might possibly have been fixed already by the previous drm pull,
but I wanted to report it anyway, just in case.
It happened after an uptime of over a week, so it might not be trivial
to reproduce.
It's a NULL pointer dereference in dc_stream_retain() with the code being
lock xadd %
On Thu, 5 Aug 2021 08:47:01 -0300
Jason Gunthorpe wrote:
> On Tue, Aug 03, 2021 at 10:52:25AM -0600, Alex Williamson wrote:
> > On Tue, 3 Aug 2021 13:41:52 -0300
> > Jason Gunthorpe wrote:
> > > On Tue, Aug 03, 2021 at 10:34:06AM -0600, Alex Williamson wrote:
> > > > I think the vfio_pci_fin
1. There are 2 mmsys, namely vdosys0 and vdosys1 in mt8195.
Each of them is bound to a display pipeline, so add their
definition in mtk-mmsys documentation with 2 compatibles.
2. Add description for power-domain property.
Signed-off-by: jason-jh.lin
---
this patch is base on [1][2]
[1] dt
1. Add mediatek,dsc.yaml to describe DSC module in details.
2. Add mt8195 SoC binding to mediatek,dsc.yaml.
Signed-off-by: jason-jh.lin
---
.../display/mediatek/mediatek,dsc.yaml| 69 +++
1 file changed, 69 insertions(+)
create mode 100644
Documentation/devicetree/bindi
1. Remove mediatek,dislpay.txt
2. Split each display function block to individual yaml file.
Signed-off-by: jason-jh.lin
---
.../display/mediatek/mediatek,aal.yaml| 75 ++
.../display/mediatek/mediatek,ccorr.yaml | 69 ++
.../display/mediatek/mediatek,color.yaml | 84
1. Add mt8195 SoC binding to AAL, CCORR, COLOR, DITHER, GAMMA, MERGE,
MUTEX, OVL and RDMA yaml schema.
2. Add MERGE additional property description for mt8195
- async clock
- fifo setting enable
- reset controller
Signed-off-by: jason-jh.lin
---
.../display/mediatek/mediatek,aal.yaml
Change in v3:
- slpit each display function block to individual taml file.
Change in v2:
- add power-domain property into mediatek,mmsys.yaml
and modify commit message.
jason-jh.lin (4):
dt-bindings: arm: mediatek: mmsys: add mt8195 SoC binding
dt-bindings: mediatek: display: split each blo
Unlike previous generations, 7nm PHYs are required to collaborate with
the host for conitnuos clock mode. Add changes neccessary to enable
continuous clock mode in the 7nm DSI PHYs.
Signed-off-by: Dmitry Baryshkov
---
Changes since v4:
- Fix the comment regarding msm_dsi_phy_set_continuous_clock
On Thu, Aug 05, 2021 at 01:05:09PM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> When a non-persistent context exits we currently mark it as banned in
> order to trigger fast termination of any outstanding GPU jobs it may have
> left running.
>
> In doing so we apply a very strict 1ms
Hi Paul,
> Am 05.08.2021 um 18:17 schrieb Paul Cercueil :
>
> Hi Nikolaus and Laurent,
>
> Le jeu., août 5 2021 at 18:07:20 +0200, H. Nikolaus Schaller
> a écrit :
>> Hi Laurent,
>>> Am 05.08.2021 um 17:04 schrieb Laurent Pinchart
>>> :
>>> Hi Nikolaus,
>>> Thank you for the patch.
>>> On Thu
Hi Nikolaus and Laurent,
Le jeu., août 5 2021 at 18:07:20 +0200, H. Nikolaus Schaller
a écrit :
Hi Laurent,
Am 05.08.2021 um 17:04 schrieb Laurent Pinchart
:
Hi Nikolaus,
Thank you for the patch.
On Thu, Aug 05, 2021 at 04:07:57PM +0200, H. Nikolaus Schaller
wrote:
This patch atte
Hi Laurent,
> Am 05.08.2021 um 17:04 schrieb Laurent Pinchart
> :
>
> Hi Nikolaus,
>
> Thank you for the patch.
>
> On Thu, Aug 05, 2021 at 04:07:57PM +0200, H. Nikolaus Schaller wrote:
>> This patch attempts to convert the ingenic-dw-hdmi driver
>> into a version that uses the component frame
Hi Paul,
> Am 05.08.2021 um 17:22 schrieb Paul Cercueil :
>
> Hi Nikolaus & Paul,
>
> Le jeu., août 5 2021 at 16:07:52 +0200, H. Nikolaus Schaller
> a écrit :
>> From: Paul Boddie
>> Add support for the LCD controller present on JZ4780 SoCs.
>> This SoC uses 8-byte descriptors which extend th
On Thu, Aug 05, 2021 at 09:49:52AM +0200, Paul Cercueil wrote:
> Hi Sam,
>
> Le mer., août 4 2021 at 20:25:23 +0200, Sam Ravnborg a
> écrit :
> > On Wed, Aug 04, 2021 at 03:23:52AM +0300, Artjom Vejsel wrote:
> > > Add DT bindings for QiShenglong Gopher 2b 4.3" 480(RGB)x272 TFT LCD
> > > panel.
Hi Nikolaus & Paul,
Le jeu., août 5 2021 at 16:07:52 +0200, H. Nikolaus Schaller
a écrit :
From: Paul Boddie
Add support for the LCD controller present on JZ4780 SoCs.
This SoC uses 8-byte descriptors which extend the current
4-byte descriptors used for other Ingenic SoCs.
Also, add special
Acked-by: Alyssa Rosenzweig
On Thu, Aug 05, 2021 at 12:46:52PM +0200, Daniel Vetter wrote:
> Just deletes some code that's now more shared.
>
> Note that thanks to the split into drm_sched_job_init/arm we can now
> easily pull the _init() part from under the submission lock way ahead
> where we'
On Thu, Aug 5, 2021 at 5:07 PM Peter Stuge wrote:
> Laurent Pinchart wrote:
> > +++ b/drivers/gpu/drm/omapdrm/Kconfig
> > @@ -1,7 +1,7 @@
> > # SPDX-License-Identifier: GPL-2.0-only
> > config DRM_OMAP
> > tristate "OMAP DRM"
> > - depends on DRM
> > + depends on DRM && OF
> >
On Thu, Aug 5, 2021 at 4:47 PM Christian König wrote:
>
> Am 05.08.21 um 16:07 schrieb Daniel Vetter:
> > On Thu, Aug 5, 2021 at 3:44 PM Christian König
> > wrote:
> >> Am 05.08.21 um 12:46 schrieb Daniel Vetter:
> >>> This is a very confusingly named function, because not just does it
> >>> ini
Laurent Pinchart wrote:
> +++ b/drivers/gpu/drm/omapdrm/Kconfig
> @@ -1,7 +1,7 @@
> # SPDX-License-Identifier: GPL-2.0-only
> config DRM_OMAP
> tristate "OMAP DRM"
> - depends on DRM
> + depends on DRM && OF
> depends on ARCH_OMAP2PLUS || ARCH_MULTIPLATFORM
> select OMAP
On Thu, Aug 5, 2021 at 3:57 PM Christian König wrote:
> Am 05.08.21 um 15:25 schrieb Daniel Vetter:
> > On Thu, Aug 5, 2021 at 3:18 PM Christian König
> > wrote:
> >>
> >>
> >> Am 05.08.21 um 12:46 schrieb Daniel Vetter:
> >>> This is essentially part of drm_sched_dependency_optimized(), which
>
Hi Nikolaus,
Thank you for the patch.
On Thu, Aug 05, 2021 at 04:07:57PM +0200, H. Nikolaus Schaller wrote:
> This patch attempts to convert the ingenic-dw-hdmi driver
> into a version that uses the component framework.
Why ? What problem would this solve ?
> Unfortunately the new version does
Am 05.08.21 um 16:07 schrieb Daniel Vetter:
On Thu, Aug 5, 2021 at 3:44 PM Christian König wrote:
Am 05.08.21 um 12:46 schrieb Daniel Vetter:
This is a very confusingly named function, because not just does it
init an object, it arms it and provides a point of no return for
pushing a job into
Hi Robert,
> Am 05.08.2021 um 16:32 schrieb Robert Foss :
>
> Hey Nikolaus,
>
> Thanks for submitting this series.
>
> On Thu, 5 Aug 2021 at 16:08, H. Nikolaus Schaller wrote:
>>
>> From: Paul Boddie
>>
>> + .mode_fixup = dw_hdmi_bridge_mode_fixup,
>
> mode_fixup() has been deprecate
Hey Nikolaus,
Thanks for submitting this series.
On Thu, 5 Aug 2021 at 16:08, H. Nikolaus Schaller wrote:
>
> From: Paul Boddie
>
> The platform-specific configuration structure is augmented with
> mode_fixup and timings members so that specialisations of the
> Synopsys driver can introduce mod
This series adds HDMI support for JZ4780 and CI20 board
V2:
- code and commit messages revisited for checkpatch warnings
- rebased on v5.14-rc4
- include (failed, hence RFC 8/8) attempt to convert to component framework
(was suggested by Paul Cercueil a while ago)
H. Nikolaus Schaller (2):
From: Paul Boddie
We need to hook up
* HDMI power regulator
* HDMI connector
* DDC pinmux
* HDMI and LCD endpoint connections
Signed-off-by: Paul Boddie
Signed-off-by: H. Nikolaus Schaller
---
arch/mips/boot/dts/ingenic/ci20.dts | 64 +
1 file changed, 64 insertion
From: Sam Ravnborg
Add DT bindings for the hdmi driver for the Ingenic JZ4780 SoC.
Based on .txt binding from Zubair Lutfullah Kakakhel
Signed-off-by: Sam Ravnborg
Signed-off-by: H. Nikolaus Schaller
Cc: Rob Herring
Cc: devicet...@vger.kernel.org
---
.../bindings/display/ingenic-jz4780-hdmi.
From: Paul Boddie
The platform-specific configuration structure is augmented with
mode_fixup and timings members so that specialisations of the
Synopsys driver can introduce mode flags and bus flags.
Signed-off-by: Paul Boddie
Signed-off-by: Ezequiel Garcia
Signed-off-by: H. Nikolaus Schaller
This patch attempts to convert the ingenic-dw-hdmi driver
into a version that uses the component framework.
Unfortunately the new version does not work.
Debugging shows that ingenic_dw_hdmi_bind() is never called.
Suggestions for reasons and fixes are welcome.
Signed-off-by: Paul Boddie
Co-aut
1 - 100 of 185 matches
Mail list logo
