Hi Linus,
Thank you for the comment.
Linus Walleij 於 2022年6月24日 週五 下午2:25寫道：
>
> On Fri, Jun 24, 2022 at 8:23 AM Linus Walleij
> wrote:
> > Thanks for your patch!
> >
> > On Thu, Jun 23, 2022 at 1:58 PM ChiaEn Wu wrote:
> >
> > > From: ChiYuan Huang
> > >
> > > Add Mediatek MT6370 current si
Hi
Am 22.06.22 um 14:48 schrieb Jocelyn Falempe:
With an AST2600, the screen is garbage when going out of suspend.
This is because color settings are lost, and not restored on resume.
Force the color settings on DPMS_ON, to make sure the settings are correct.
I didn't write this code, it comes
Am Freitag, 24. Juni 2022, 01:44:52 CEST schrieb Doug Anderson:
> Hi,
>
> On Fri, Jun 17, 2022 at 5:27 PM Brian Norris wrote:
> >
> > It's possible for users to try to duplicate the CRTC state even when the
> > state doesn't exist. drm_atomic_helper_crtc_duplicate_state() (and other
> > users of
Hello everyone,
To summarize the issue I'm trying to address here: Processes can allocate
resources through a file descriptor without being held responsible for it.
I'm not explaining all the details again. See here for a more deeply
description of the problem:
https://lwn.net/ml/linux-kernel/20
From: Andrey Grodzovsky
Some files allocate large amounts of memory on behalf of userspace without
any on disk backing store. This memory isn't necessarily mapped into the
address space, but should still accounts towards the RSS of a process just
like mapped shared pages do.
That information can
From: Andrey Grodzovsky
Try to make better decisions which process to kill based on
per file RSS.
Signed-off-by: Andrey Grodzovsky
---
mm/oom_kill.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index 3c6cf9e3cd66..76a5ea73eb6a
Add the per file RSS to the memory management accounting.
This allows to see the per file RSS in tools like top as well.
Signed-off-by: Christian König
---
fs/proc/array.c | 7 +--
fs/proc/internal.h | 3 ++-
fs/proc/task_mmu.c | 6 --
fs/proc/task_nommu.c | 3 ++-
4 files chan
From: Andrey Grodzovsky
Large amounts of VRAM are usually not CPU accessible, so they are not mapped
into the processes address space. But since the device drivers usually support
swapping buffers from VRAM to system memory we can still run into an out of
memory situation when userspace starts to
This gives the OOM killer an additional hint which processes are
referencing shmem files with potentially no other accounting for them.
Signed-off-by: Christian König
---
mm/shmem.c | 16
1 file changed, 16 insertions(+)
diff --git a/mm/shmem.c b/mm/shmem.c
index a6f565308133..
This allows the OOM killer to make a better decision which process to reap.
Signed-off-by: Christian König
---
drivers/gpu/drm/gma500/psb_drv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/gma500/psb_drv.c b/drivers/gpu/drm/gma500/psb_drv.c
index 1d8744f3e702..92c005aa6e9e
Just return the size of the DMA-buf in pages since pages allocated or
mapped through DMA-bufs are usually not accounted elsewhere.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-buf.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dm
From: Andrey Grodzovsky
This allows the OOM killer to make a better decision which process to reap.
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/driv
This allows the OOM killer to make a better decision which process to reap.
Signed-off-by: Christian König
---
drivers/gpu/drm/radeon/radeon_drv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/radeon/radeon_drv.c
b/drivers/gpu/drm/radeon/radeon_drv.c
index 956c72b5aa33..11
This allows the OOM killer to make a better decision which process to reap.
Signed-off-by: Christian König
---
drivers/gpu/drm/i915/i915_driver.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/i915/i915_driver.c
b/drivers/gpu/drm/i915/i915_driver.c
index 90b0ce5051af..fc269
This allows the OOM killer to make a better decision which process to reap.
Signed-off-by: Christian König
---
drivers/gpu/drm/nouveau/nouveau_drm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/nouveau/nouveau_drm.c
b/drivers/gpu/drm/nouveau/nouveau_drm.c
index 561309d447
This allows the OOM killer to make a better decision which process to reap.
Signed-off-by: Christian König
---
drivers/gpu/drm/omapdrm/omap_drv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/omapdrm/omap_drv.c
b/drivers/gpu/drm/omapdrm/omap_drv.c
index eaf67b9e5f12..dff63
This allows the OOM killer to make a better decision which process to reap.
Signed-off-by: Christian König
---
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
b/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c
index 01a5b47e95f9..99
This allows the OOM killer to make a better decision which process to reap.
Signed-off-by: Christian König
---
drivers/gpu/drm/tegra/drm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/tegra/drm.c b/drivers/gpu/drm/tegra/drm.c
index 4cdc8faf798f..cc0c2fc57250 100644
--- a/d
On 17/06/2022 12:32, Thomas Zimmermann wrote:
Provide drm_atomic_helper_check_crtc_state() for validating a CRTC
state against common constraints. As many CRTC need a primary plane
to work correctly, add this as the first test.
The simple-KMS helpers already contain related code. Convert it
to t
Am Freitag, dem 24.06.2022 um 08:54 +0200 schrieb Christian König:
> Am 23.06.22 um 17:26 schrieb Lucas Stach:
> > Am Donnerstag, dem 23.06.2022 um 14:52 +0200 schrieb Christian König:
> > > Am 23.06.22 um 14:14 schrieb Lucas Stach:
> > > > Am Donnerstag, dem 23.06.2022 um 13:54 +0200 schrieb Chris
On 24/06/2022 06:32, Niranjana Vishwanathapura wrote:
VM_BIND and related uapi definitions
v2: Reduce the scope to simple Mesa use case.
v3: Expand VM_UNBIND documentation and add
I915_GEM_VM_BIND/UNBIND_FENCE_VALID
and I915_GEM_VM_BIND_TLB_FLUSH flags.
v4: Remove I915_GEM_VM_BIND_TL
22. 6. 16. 16:22에 hongao 이(가) 쓴 글:
> Once EDID is parsed, the monitor HDMI support information is available
> through drm_display_info.is_hdmi.
>
> This driver calls drm_detect_hdmi_monitor() to receive the same
> information, which is less efficient.
>
> Avoid calling drm_detect_hdmi_monitor(
> Wiadomość napisana przez Piotr Oniszczuk w dniu
> 14.05.2022, o godz. 15:58:
>
>
>
>> Wiadomość napisana przez Peter Geis w dniu 09.05.2022,
>> o godz. 18:00:
>>
>> If you want to confirm the hardware is configured correctly you can
>> remove the cec pin from the hdmi node and set up a
On 23/06/2022 22:05, Zeng, Oak wrote:
-Original Message-
From: Intel-gfx On Behalf Of Tvrtko
Ursulin
Sent: June 23, 2022 7:06 AM
To: Landwerlin, Lionel G ; Vishwanathapura,
Niranjana
Cc: Zanoni, Paulo R ; intel-...@lists.freedesktop.org;
dri-devel@lists.freedesktop.org; Hellstrom, Tho
On 23/06/2022 12:17, Andi Shyti wrote:
Hi Mauro,
On Wed, Jun 15, 2022 at 04:27:39PM +0100, Mauro Carvalho Chehab wrote:
From: Chris Wilson
Don't allow two engines to be reset in parallel, as they would both
try to select a reset bit (and send requests to common registers)
and wait on that r
Hi Christian,
Am Dienstag, dem 21.06.2022 um 09:20 +0200 schrieb Christian Gmeiner:
> This adds a SMA algorithm inspired by Exponentially weighted moving
> average (EWMA) algorithm found in the kernel.
>
Still not sure about this one. I _feel_ that a simple moving average
over a period of one sec
Hi Joe,
Joe Simmons-Talbott 於 2022年6月23日 週四 晚上9:17寫道：
>
> On Thu, Jun 23, 2022 at 07:56:22PM +0800, ChiaEn Wu wrote:
> > From: ChiYuan Huang
> >
> > Add mt6370 backlight binding documentation.
> >
> > Signed-off-by: ChiYuan Huang
> > ---
> >
> > v3
> > - Rename "mediatek,bled-pwm-hys-input-thre
Am Dienstag, dem 21.06.2022 um 09:20 +0200 schrieb Christian Gmeiner:
> The GPU has an idle state register where each bit represents the idle
> state of a sub-GPU component like FE or TX. Sample this register
> every 10ms and calculate a simple moving average over the sub-GPU
> component idle state
Am Dienstag, dem 21.06.2022 um 09:20 +0200 schrieb Christian Gmeiner:
> Make it possible to access the sub-GPU component load value from
> user space with the perfmon infrastructure.
>
You need to explain a bit more how you intend to use those.
Contrary to all other perfmon values, where we go to
Hi Daniel,
Thanks for your comments!
Daniel Thompson 於 2022年6月23日 週四 晚上9:43寫道：
>
> On Thu, Jun 23, 2022 at 07:56:31PM +0800, ChiaEn Wu wrote:
> > From: ChiaEn Wu
> >
> > Add Mediatek MT6370 Backlight support.
> >
> > Signed-off-by: ChiaEn Wu
>
> > diff --git a/drivers/video/backlight/Kconfig
Hi Andy,
Thanks for your helpful comments! We have some questions below.
Andy Shevchenko 於 2022年6月24日 週五 凌晨2:01寫道：
>
> On Thu, Jun 23, 2022 at 1:59 PM ChiaEn Wu wrote:
> >
> > From: ChiYuan Huang
> >
> > Add Mediatek MT6370 MFD support.
>
> ...
>
> > +config MFD_MT6370
> > + tristate "Me
On 23/06/2022 13:56, ChiaEn Wu wrote:
> From: ChiaEn Wu
>
> Add Mediatek MT6370 Charger binding documentation.
>
> Signed-off-by: ChiaEn Wu
> ---
>
> v3
> - Add items and remove maxItems of io-channels
> - Add io-channel-names and describe each item
> - Add "unevaluatedProperties: false" in "u
Hi Andy,
Thanks for your helpful comments!
Andy Shevchenko 於 2022年6月24日 週五 凌晨2:19寫道：
>
> On Thu, Jun 23, 2022 at 2:00 PM ChiaEn Wu wrote:
> >
> > From: ChiYuan Huang
> >
> > Add mt6370 DisplayBias and VibLDO support.
>
> ...
>
> > +#include
> > +#include
> > +#include
> > +#include
> > +#i
On 23/06/2022 13:56, ChiaEn Wu wrote:
> From: ChiYuan Huang
>
> Add Mediatek mt6370 current sink type LED indicator binding documentation.
>
> Signed-off-by: ChiYuan Huang
> ---
>
> v3
> - Use leds-class-multicolor.yaml instead of common.yaml.
> - Split multi-led and led node.
> - Add subdevic
On 24/06/2022 12:35, Krzysztof Kozlowski wrote:
> On 23/06/2022 13:56, ChiaEn Wu wrote:
>> From: ChiYuan Huang
>>
>> Add Mediatek mt6370 current sink type LED indicator binding documentation.
>>
>> Signed-off-by: ChiYuan Huang
>> ---
>>
>> v3
>> - Use leds-class-multicolor.yaml instead of common.
On 23/06/2022 13:56, ChiaEn Wu wrote:
> From: Alice Chen
>
> Add Mediatek MT6370 flashlight binding documentation.
>
> Signed-off-by: Alice Chen
> ---
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
On 23/06/2022 13:56, ChiaEn Wu wrote:
> From: ChiYuan Huang
>
> Add Mediatek MT6370 binding documentation.
>
> Signed-off-by: ChiYuan Huang
> ---
>
> v3
> - Use " in entire patchset
> - Refine ADC description
> - Rename "enable-gpio" to "enable-gpios" in "regualtor"
> - Change "/schemas/" to "
On Thu, Jun 23, 2022 at 07:56:25PM +0800, ChiaEn Wu wrote:
> --- /dev/null
> +++ b/drivers/usb/typec/tcpm/tcpci_mt6370.c
> @@ -0,0 +1,212 @@
> +// SPDX-License-Identifier: GPL-2.0+
Are you sure you mean "+" here?
I have to ask, sorry.
And no copyright line? Your company is ok with that, nice!
On Thu, Jun 23, 2022 at 04:43:47PM +0800, Jiapeng Chong wrote:
> This was found by coccicheck:
>
> ./drivers/usb/gadget/udc/aspeed_udc.c:496:8-13: WARNING: Unsigned expression
> compared with zero: chunk >= 0.
What does this mean? Where is the error?
Please explain the reason for changes, not
The various Freescale i.MX8 display bridges are only present on
Freescale i.MX8 SoCs. Hence add a dependency on ARCH_MXC, to prevent
asking the user about these drivers when configuring a kernel without
i.MX SoC support.
Fixes: e60c4354840b2fe8 ("drm/bridge: imx: Add LDB support for i.MX8qm")
Fix
On Fri, Jun 24, 2022 at 4:30 AM Piotr Oniszczuk
wrote:
>
>
>
> > Wiadomość napisana przez Piotr Oniszczuk w dniu
> > 14.05.2022, o godz. 15:58:
> >
> >
> >
> >> Wiadomość napisana przez Peter Geis w dniu
> >> 09.05.2022, o godz. 18:00:
> >>
> >> If you want to confirm the hardware is configure
Am Montag, dem 13.06.2022 um 23:31 +0200 schrieb Marek Vasut:
> Add support for i.MX8MP LCDIF variant. This is called LCDIFv3 and is
> completely different from the LCDIFv3 found in i.MX23 in that it has
> a completely scrambled register layout compared to all previous LCDIF
> variants. The new LCD
On Tue, Jun 21, 2022 at 02:21:22PM -0700, Nicolin Chen wrote:
> On Sun, Jun 19, 2022 at 11:32:07PM -0700, Christoph Hellwig wrote:
> > On Sun, Jun 19, 2022 at 11:57:26PM -0300, Jason Gunthorpe wrote:
> > > The remark about io memory is because on s390 memcpy() will crash even
> > > on ioremapped me
Hi,
On Fri, Jun 24, 2022 at 04:35:25PM +0200, Paul Kocialkowski wrote:
> On Tue 14 Jun 22, 15:08, Dan Carpenter wrote:
> > The "regmap" is supposed to be initialized to NULL but it's used
> > without being initialized.
> >
> > Fixes: efeeaefe9be5 ("drm: Add support for the LogiCVC display control
Hello Dan,
On Tue 14 Jun 22, 15:07, Dan Carpenter wrote:
> Hello Paul Kocialkowski,
>
> The patch efeeaefe9be5: "drm: Add support for the LogiCVC display
> controller" from May 20, 2022, leads to the following Smatch static
> checker warning:
>
> drivers/gpu/drm/logicvc/logicvc_layer.c:320
On Fri, Jun 24, 2022 at 09:11:35AM +0100, Tvrtko Ursulin wrote:
On 24/06/2022 06:32, Niranjana Vishwanathapura wrote:
VM_BIND and related uapi definitions
v2: Reduce the scope to simple Mesa use case.
v3: Expand VM_UNBIND documentation and add
I915_GEM_VM_BIND/UNBIND_FENCE_VALID
and I9
On 6/23/2022 5:09 PM, Stephen Boyd wrote:
Quoting Kuogee Hsieh (2022-06-23 16:34:16)
eDP implementation does not reuried to support hpd signal. Therefore
s/reuried/require/
it only has either ST_DISPLAY_OFF or ST_CONNECTED state during normal
operation. This patch remove unnecessary dp_hpd_
On Fri, Jun 24, 2022 at 04:46:36PM +0200, Paul Kocialkowski wrote:
> Hi,
>
> On Fri 24 Jun 22, 16:37, Maxime Ripard wrote:
> > Hi,
> >
> > On Fri, Jun 24, 2022 at 04:35:25PM +0200, Paul Kocialkowski wrote:
> > > On Tue 14 Jun 22, 15:08, Dan Carpenter wrote:
> > > > The "regmap" is supposed to be
> > +
> > +static int lcdif_rpm_resume(struct device *dev)
> > +{
> > + struct drm_device *drm = dev_get_drvdata(dev);
> > + struct lcdif_drm_private *lcdif = drm->dev_private;
> > +
> > + /* These clock supply the Control Bus, APB, APBH Ctrl Registers */
> > + clk_prepare_enable(lcdif->clk
On 20/06/2022 22:54, Rahul T R wrote:
> Convert cdns,dsi.txt binding to yaml format
>
> Signed-off-by: Rahul T R
> ---
> .../bindings/display/bridge/cdns,dsi.txt | 112 --
> .../bindings/display/bridge/cdns,dsi.yaml | 193 ++
> 2 files changed, 193 insertions(+),
On 6/23/2022 1:21 PM, David Hildenbrand wrote:
On 23.06.22 20:20, Sierra Guiza, Alejandro (Alex) wrote:
On 6/23/2022 2:57 AM, David Hildenbrand wrote:
On 23.06.22 01:16, Sierra Guiza, Alejandro (Alex) wrote:
On 6/21/2022 11:16 AM, David Hildenbrand wrote:
On 21.06.22 18:08, Sierra Guiza, Al
On Thu, Jun 23, 2022 at 11:54:52AM +0200, Lukas Bulwahn wrote:
> Commit fd27de58b0ad ("dt-bindings: display: tegra: Convert to json-schema")
> converts nvidia,tegra20-host1x.txt to yaml, but missed to adjust its
> references in MAINTAINERS.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patter
This is already on by default.
Suggested-by: Al Viro
Cc: Sumit Semwal
Cc: Christian König
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Jason A. Donenfeld
---
drivers/dma-buf/dma-buf.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/dma-buf/dma-buf.c b/drivers/dma-buf/dma-buf.
fix primary corruption :
1) move struc of msm_display_info to msm_drv.h
2) decoupling dp->id out of dp controller_id at sc_dp_cfg table
3) place edp at head of drm bridge chain to fix screen corruption
Kuogee Hsieh (3):
drm/msm/dp: move struc of msm_display_info to msm_drv.h
drm/msm/dp: d
The msm_dp_modeset_init() is used to attach DP driver to drm bridge chain.
msm_dp_modeset_init() is executed in the order of index (dp->id) of DP
descriptor table.
Currently, DP is placed at first entry (dp->id = 0) of descriptor table
and eDP is placed at secondary entry (dp->id = 1 ) of descript
With current implementation, communication between interface driver and
upper mdss encoder layer are implemented through function calls. This
increase code complexity. Since struct msm_display_info contains msm
generic display information, it can be expended to contains more useful
information, suc
Current the index (dp->id) of DP descriptor table (sc_dp_cfg[]) are tightly
coupled with DP controller_id. This means DP use controller id 0 must be placed
at first entry of DP descriptor table (sc_dp_cfg[]). Otherwise the internal
INTF will mismatch controller_id. This will cause controlle
Hi Jiapeng,
On Fri, Jun 24, 2022 at 09:31:59AM +0800, Jiapeng Chong wrote:
> This was found by coccicheck:
>
> ./drivers/gpu/drm/ingenic/ingenic-drm-drv.c:1149:35-38: WARNING: Suspicious
> code. resource_size is maybe missing with res.
>
Nice one, now I have to go back and fix my code as well.
Hi Philip,
On Thu, Jun 23, 2022 at 01:22:56PM +0200, Philip Oberfichtner wrote:
> Add DataImage FG1001L0DSSWMG01 10.1" 1280x800 TFT LCD panel compatible
> string.
>
> Signed-off-by: Philip Oberfichtner
> Acked-by: Krzysztof Kozlowski
Both patches applied to drm-misc (drm-misc-next)
Sa
On Tue, 21 Jun 2022 18:10:14 +0300, Mikko Perttunen wrote:
> From: Thierry Reding
>
> Convert the Tegra host1x controller bindings from the free-form text
> format to json-schema.
>
> This also adds the missing display-hub DT bindings that were not
> previously documented.
>
> Reviewed-by: Rob
VM_BIND design document with description of intended use cases.
v2: Reduce the scope to simple Mesa use case.
v3: Expand documentation on dma-resv usage, TLB flushing and
execbuf3.
v4: Remove vm_bind tlb flush request support.
v5: Update TLB flushing documentation.
Signed-off-by: Niranjana Vi
Add some missing i915 upai documentation which the new
i915 VM_BIND feature documentation will be refer to.
Signed-off-by: Niranjana Vishwanathapura
Reviewed-by: Matthew Auld
---
include/uapi/drm/i915_drm.h | 205
1 file changed, 160 insertions(+), 45 deleti
VM_BIND and related uapi definitions
v2: Reduce the scope to simple Mesa use case.
v3: Expand VM_UNBIND documentation and add
I915_GEM_VM_BIND/UNBIND_FENCE_VALID
and I915_GEM_VM_BIND_TLB_FLUSH flags.
v4: Remove I915_GEM_VM_BIND_TLB_FLUSH flag and add additional
documentation for vm_bin
This is the i915 driver VM_BIND feature design RFC patch series along
with the required uapi definition and description of intended use cases.
v2: Reduce the scope to simple Mesa use case.
Remove all compute related uapi, vm_bind/unbind queue support and
only support a timeline out fence i
On Fri, Jun 24, 2022 at 12:23 AM Heiko Stuebner wrote:
> The interesting question would be, do we want some fixes tag for it?
I'm not aware of any currently-upstream code that will hit this [1].
I've hit it in out-of-tree code (or, code that I submitted to
dri-devel, but wasn't accepted as-is), a
Add compatible string for i.MX8MP LCDIF variant. This is called LCDIFv3
and is completely different from the LCDIFv3 found in i.MX23 in that it
has a completely scrambled register layout compared to all previous LCDIF
variants. The new LCDIFv3 also supports 36bit address space. However,
except for
Add support for i.MX8MP LCDIF variant. This is called LCDIFv3 and is
completely different from the LCDIFv3 found in i.MX23 in that it has
a completely scrambled register layout compared to all previous LCDIF
variants. The new LCDIFv3 also supports 36bit address space.
Add a separate driver which i
Yiqing raised a problem of negative fence refcount for resubmitted jobs
in amdgpu and suggested a workaround in [1]. I took a look myself and
discovered
some deeper problems both in amdgpu and scheduler code.
Yiqing helped with testing the new code and also drew a detailed refcount and
flow
tra
This function should drop the fence refcount when it extracts the
fence from the fence array, just as it's done in amdgpu_fence_process.
Signed-off-by: Andrey Grodzovsky
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c | 4 +++-
1 file changed, 3 insertions(+), 1 delet
Problem:
This patch caused negative refcount as described in [1] because
for that case parent fence did not signal by the time of drm_sched_stop and
hence
kept in pending list the assumption was they will not signal and
so fence was put to account for the s_fence->parent refcount but for
amdgpu wh
Problem:
After we start handling timed out jobs we assume there fences won't be
signaled but we cannot be sure and sometimes they fire late. We need
to prevent concurrent accesses to fence array from
amdgpu_fence_driver_clear_job_fences during GPU reset and amdgpu_fence_process
from a late EOP inte
Align refcount behaviour for amdgpu_job embedded HW fence with
classic pointer style HW fences by increasing refcount each
time emit is called so amdgpu code doesn't need to make workarounds
using amdgpu_job.job_run_counter to keep the HW fence refcount balanced.
Also since in the previous patch w
Hi allen.
On Thu, Jun 23, 2022 at 05:31:54PM +0800, allen wrote:
> From: allen chen
>
> add read max-lane and max-pixel-clock from dt property
>
> Signed-off-by: Allen-kh Cheng
>
Can you fix so your s-o-b mail and author mail matches?
As it is now an error is flagged as they do not match.
The DSI lane count can be accessed via the dsi device pointer,
make use of that. No functional change.
Signed-off-by: Marek Vasut
Cc: Andrzej Hajda
Cc: Laurent Pinchart
Cc: Lucas Stach
Cc: Maxime Ripard
Cc: Robert Foss
Cc: Sam Ravnborg
---
drivers/gpu/drm/bridge/tc358767.c | 6 ++
1 fi
From: Rob Clark
This was a typo, we didn't actually want to return zero.
Fixes: a61acbbe9cf8 ("drm/msm: Track "seqno" fences by idr")
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/msm_gem_submit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/msm_ge
The pull request you sent on Fri, 24 Jun 2022 15:55:38 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2022-06-24
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/38bc4ac431684498126f9baa3a530e5a132f0173
Thank you!
--
Deet-doot-dot, I am a bot.
https://k
> Wiadomość napisana przez Peter Geis w dniu 24.06.2022,
> o godz. 14:40:
>
>>
>> Sascha, Peter
>>
>> I returned to trying to find why hdmi-cec is not working on rock3-a v1.31 hw.
>>
>> I'm on vop2 v11 on 5.18 mainline.
>>
>> Current findings:
>>
>> (1) the same sw. stack/binaries works
Hi,
Le ven., juin 24 2022 at 09:31:59 +0800, Jiapeng Chong
a écrit :
This was found by coccicheck:
./drivers/gpu/drm/ingenic/ingenic-drm-drv.c:1149:35-38: WARNING:
Suspicious code. resource_size is maybe missing with res.
Signed-off-by: Jiapeng Chong
---
drivers/gpu/drm/ingenic/ingenic-d
On Wed, Jun 22, 2022 at 04:31:05PM +0200, Maxime Ripard wrote:
> Unlike most of the other files in DRM, and Linux in general, the headers in
> drm_connector.c aren't sorted alphabetically. Let's fix that.
>
> Signed-off-by: Maxime Ripard
Acked-by: Sam Ravnborg
> ---
> drivers/gpu/drm/drm_connec
On Fri, Jun 24, 2022 at 10:56:15AM -0300, Jason Gunthorpe wrote:
> > How about the updated commit log below? Thanks.
> >
> > The pinned PFN list returned from vfio_pin_pages() is converted using
> > page_to_pfn(), so direct access via memcpy() will crash on S390 if the
> > PFN is an IO PFN, as we
On Wed, Jun 22, 2022 at 04:31:06PM +0200, Maxime Ripard wrote:
> Unlike encoders and CRTCs, the drm_connector_init() and
> drm_connector_init_with_ddc() don't mention how the cleanup is supposed to
> be done. Let's add it.
>
> Signed-off-by: Maxime Ripard
Looks sensible,
Acked-by: Sam Ravnborg
>
On Wed, Jun 22, 2022 at 04:31:07PM +0200, Maxime Ripard wrote:
> The current documentation for drm_connector_unregister() mentions that
> it's needed for connectors that have been registered through
> drm_dev_register().
>
> However, this was a typo and was meant to be drm_connector_register(),
>
On Wed, Jun 22, 2022 at 04:31:08PM +0200, Maxime Ripard wrote:
> Unlike other DRM entities, there's no helper to create a DRM-managed
> initialisation of a connector.
>
> Let's create an helper to initialise a connector that would be passed as an
> argument, and handle the cleanup through a DRM-ma
On Wed, Jun 22, 2022 at 04:31:09PM +0200, Maxime Ripard wrote:
> Let's create a DRM-managed variant of drm_connector_init_with_ddc that will
> take care of an action of the connector cleanup.
>
> Signed-off-by: Maxime Ripard
Acked-by: Sam Ravnborg
On Wed, Jun 22, 2022 at 04:31:10PM +0200, Maxime Ripard wrote:
> Unlike what can be found for other entities, there's no DRM-managed
> function to create a panel_bridge instance from a panel.
>
> Let's introduce one.
>
> Signed-off-by: Maxime Ripard
Acked-by: Sam Ravnborg
On Fri, Jun 24, 2022 at 12:22:36PM -0700, Nicolin Chen wrote:
> On Fri, Jun 24, 2022 at 10:56:15AM -0300, Jason Gunthorpe wrote:
>
> > > How about the updated commit log below? Thanks.
> > >
> > > The pinned PFN list returned from vfio_pin_pages() is converted using
> > > page_to_pfn(), so direct
On Wed, Jun 22, 2022 at 04:31:11PM +0200, Maxime Ripard wrote:
> Unlike what can be found for other DRM entities, we don't have a
> DRM-managed function equivalent to devm_drm_of_get_bridge().
>
> Let's create it.
>
> Signed-off-by: Maxime Ripard
> ---
> drivers/gpu/drm/bridge/panel.c | 35
On Fri, Jun 24, 2022 at 10:49:34AM -0700, Niranjana Vishwanathapura wrote:
> VM_BIND design document with description of intended use cases.
>
> v2: Reduce the scope to simple Mesa use case.
> v3: Expand documentation on dma-resv usage, TLB flushing and
> execbuf3.
> v4: Remove vm_bind tlb flu
On Tue, Jun 21, 2022 at 09:31:07PM +0800, Jiang Jian wrote:
> there is an unexpected word "the" in the comments that need to be dropped
>
> file: drivers/gpu/drm/pl111/pl111_display.c
> line: 251
> * Note that the the ARM hardware's format reader takes 'r' from
> changed to
> * Note that the the A
On Tue, Jun 21, 2022 at 10:01:51PM +0800, Jiang Jian wrote:
> file: ./drivers/gpu/drm/panel/panel-novatek-nt35510.c
> line: 193,214,253
> * amplification for the the step-up circuit:
> changed to
> * amplification for the step-up circuit:
>
> Signed-off-by: Jiang Jian
Thanks, applied to drm-misc
On Tue, Jun 21, 2022 at 09:21:18AM +0200, Alexander Stein wrote:
> If the backlight node is not enabled, this (silently) returns with
> -EPROBE_DEFER. /sys/kernel/debug/devices_deferred also shows nothing
> helpful:
> $ cat /sys/kernel/debug/devices_deferred
> display
>
> With this patch, there is
Hi Javier,
On Sat, Jun 18, 2022 at 07:43:38PM +0200, Javier Martinez Canillas wrote:
> Data writes for the ssd130x 4-wire SPI protocol need special handling, due
> the Data/Command control (D/C) pin having to be toggled prior to the write.
>
> The regmap API only allowed drivers to provide .reg_{
On Fri, Jun 24, 2022 at 10:49:35AM -0700, Niranjana Vishwanathapura wrote:
> Add some missing i915 upai documentation which the new
> i915 VM_BIND feature documentation will be refer to.
>
> Signed-off-by: Niranjana Vishwanathapura
> Reviewed-by: Matthew Auld
> ---
> include/uapi/drm/i915_drm.h
On Thu, Jun 16, 2022 at 07:23:15PM +0200, Stephen Kitt wrote:
> Instead of retrieving the backlight brightness in struct
> backlight_properties manually, and then checking whether the backlight
> should be on at all, use backlight_get_brightness() which does all
> this and insulates this from futur
On Thu, Jun 16, 2022 at 07:23:14PM +0200, Stephen Kitt wrote:
> Instead of retrieving the backlight brightness in struct
> backlight_properties manually, and then checking whether the backlight
> should be on at all, use backlight_get_brightness() which does all
> this and insulates this from futur
On Thu, Jun 16, 2022 at 07:23:13PM +0200, Stephen Kitt wrote:
> backlight_properties.fb_blank is deprecated. The states it represents
> are handled by other properties; but instead of accessing those
> properties directly, drivers should use the helpers provided by
> backlight.h.
>
> Instead of re
On Thu, Jun 16, 2022 at 07:08:21PM +0200, Stephen Kitt wrote:
> This started with work on the removal of backlight_properties'
> deprecated fb_blank field, much of which can be taken care of by using
> helper functions provided by backlight.h instead of directly accessing
> fields in backlight_prop
Quoting Prashant Malani (2022-06-23 19:48:04)
> On Thu, Jun 23, 2022 at 7:13 PM Stephen Boyd wrote:
> >
> > Quoting Prashant Malani (2022-06-23 17:35:38)
> > > On Thu, Jun 23, 2022 at 4:14 PM Stephen Boyd wrote:
> > > >
> > > > I'm not aware of any documentation for the dos and don'ts here. Are
>
https://bugzilla.kernel.org/show_bug.cgi?id=216119
--- Comment #20 from Harald Judt (h.j...@gmx.at) ---
One thing that I have noticed: Since these changes, the kernel seems to switch
to text mode when hibernating. Before that I think it remained (frozen) on the
X screen.
Here are the results:
- 1
Hi Bastian,
On Fri, Jun 10, 2022 at 01:15:11PM +0200, Bastian Krause wrote:
> Add support for the Ampire AM-800600P5TMQW-TB8H 800x600 panel. Data
> sheet is currently not publicly available, unfortunately.
>
> Signed-off-by: Bastian Krause
Applied to drm-misc (drm-misc-next).
When applying I fi
1 - 100 of 217 matches
Mail list logo
