On Fri, 31 Dec 2021 at 07:48, Dmitry Baryshkov
wrote:
>
> HI,
>
> On Wed, 29 Dec 2021 at 07:12, Bjorn Andersson
> wrote:
> >
> > On Thu 25 Nov 20:35 CST 2021, Dmitry Baryshkov wrote:
> >
> > > In order to simplify DP code, drop hand-coded loops over clock arrays,
> > > replacing them with
HI,
On Wed, 29 Dec 2021 at 07:12, Bjorn Andersson
wrote:
>
> On Thu 25 Nov 20:35 CST 2021, Dmitry Baryshkov wrote:
>
> > In order to simplify DP code, drop hand-coded loops over clock arrays,
> > replacing them with clk_bulk_* functions.
> >
>
> I've yet to debug this, but applying the two
The pull request you sent on Fri, 31 Dec 2021 12:20:04 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2021-12-31
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4f3d93c6eaff6b84e43b63e0d7a119c5920e1020
Thank you!
--
Deet-doot-dot, I am a bot.
Hi Linus (and misc maintainers),
This is a bit bigger than I'd like, however it has two weeks of amdgpu
fixes in it, since they missed last week, which was very small.
The nouveau regression is probably the biggest fix in here, and it
needs to go into 5.15 as well, two i915 fixes, and then a
Implement the .atomic_get_input_bus_fmts callback to let the bridge
indicate the pixel format it requires on the parallel bus to the LCDIF.
Based on Marek's commit db8b7ca5b232 ("drm/bridge: ti-sn65dsi83: Replace
connector format patching with atomic_get_input_bus_fmts").
Tested on a
Use the atomic version of the enable/disable operations to continue the
transition to the atomic API, started with the introduction of
.atomic_get_input_bus_fmts(). This will be needed to access the mode
from the atomic state.
Based on Laurent's commit a6ea7d268a63("drm: bridge: ti-sn65dsi83:
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #7 from spassw...@web.de ---
The
[drm] Register(0) [mmUVD_POWER_STATUS] failed to reach value 0x0001 !=
0x0002
are still there, but they don't seem to be harmful, in fact they were there
even
in linux.5.15.11 where suspend
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #6 from spassw...@web.de ---
After sorting out some .config troubles I've reverted commit
2a50edbf10c8c56e930bfb53d8f9f00a33fd837e in linux-5.16-rc7 and this seems to
cure both the not properly suspending issue (fan and keyboard
When afbcd.ops->init fails we need to free the struct drm_device. Also
all errors which come after afbcd.ops->init was successful need to exit
the AFBCD, just like meson_drv_unbind() does.
Fixes: d1b5e41e13a7e9 ("drm/meson: Add AFBCD module driver")
Signed-off-by: Martin Blumenstingl
---
Use this to simplify the driver shutdown. It will also come handy when
fixing the error handling in meson_drv_bind_master().
Signed-off-by: Martin Blumenstingl
---
drivers/gpu/drm/meson/meson_drv.c | 6 ++--
drivers/gpu/drm/meson/meson_osd_afbcd.c | 41 -
Hi Neil,
this series consists of a small cleanup patch and a fix for the error
handling in meson_drv_bind_master() when AFBCD is used.
The patches are based on drm-misc to not conflict with your previous
driver rework. Since the problem has not been observed in the wild I
decided not to Cc
> https://github.com/0day-ci/linux/commits/Claudio-Suarez/drm-get-rid-of-DRM_DEBUG_-log-calls-in-drm-core-files-drm_-b-c-c/20211230-185446
> base: git://anongit.freedesktop.org/drm/drm drm-next
> config: hexagon-randconfig-r041-20211230
> (https://download.01.org/0day-ci/archive/202
Sure, I guess i can drop this patch then.
Andrey
On 2021-12-24 4:57 a.m., JingWen Chen wrote:
I do agree with shaoyun, if the host find the gpu engine hangs first, and do
the flr, guest side thread may not know this and still try to access HW(e.g.
kfd is using a lot of amdgpu_in_reset and
Thanks a lot, please let me know.
Andrey
On 2021-12-24 3:58 a.m., Deng, Emily wrote:
These patches look good to me. JingWen will pull these patches and do some
basic TDR test on sriov environment, and give feedback.
Best wishes
Emily Deng
-Original Message-
From: Liu, Monk
Sent:
If this approach is not appropriate, then perhaps need to fix it in
files for all SoCs, to make it possible for extension board dtsi to be
compatible with all of them.
I'm writing a patch to drop those right now :-) I'll CC you.
Ok.
But, are you sure that empty nodes like these are that bad?
I'd prefer to make each DT fragment to use only either entities defined in that
fragment itself, or
defined "interface entities" between this and "neighbor" DT fragment.
Such as:
- SoC's DT fragment defines a named port/endpoint to export video stream at
- board's DT fragment defines a named
clang reports a unused-but-set variable warning:
drivers/gpu/drm/mediatek/mtk_cec.c:85:6: warning: variable 'tmp' set but not
used [-Wunused-but-set-variable]
In current implementation, mtk_cec_mask() writes val into target register
and ignores the mask. After talking to our hdmi experts,
Variable Ftarget is being initialized with a value that is never read,
it is being re-assigned a different value a little later on. The
assignment is redundant and can be removed.
Signed-off-by: Colin Ian King
---
drivers/video/fbdev/asiliantfb.c | 2 +-
1 file changed, 1 insertion(+), 1
Hi.
Thank you for looking at this.
+ port@1 {
+ reg = <1>;
+ lvds0_out: endpoint {
};
Endpoints must have a remote-endpoint property. Let's drop
This series is to add DSI PHY tuning support in Qualcomm Snapdragon
SoCs with 10nm DSI PHY e.g. SC7180
In most cases the default values of DSI PHY tuning registers
should be sufficient as they are fully optimized. However, in
some cases (for example, where extreme board parasitics cause
the eye
On Wed, 2021-12-29 at 10:03 -0600, Bjorn Helgaas wrote:
> On Wed, Dec 29, 2021 at 01:12:07PM +0100, Mauro Carvalho Chehab wrote:
> > Em Wed, 29 Dec 2021 12:45:38 +0100
> > Niklas Schnelle escreveu:
> > > ...
> > > I do think we agree that once done correctly there is value in
> > > such an option
Endpoints are meant to model a link between two ports, so an endpoint
shouldn't exist in isolation. The issue with creating named endpoints in
SoC files is that you can't tell there what remote devices may exist, so
the endpoint may or may not match the actual hardware design of a board.
I
In a future patch HAS_IOPORT=n will result in inb()/outb() and friends
not being declared. We thus need to add HAS_IOPORT as dependency for
those drivers using them and guard inline code in headers.
Co-developed-by: Arnd Bergmann
Signed-off-by: Arnd Bergmann
Signed-off-by: Niklas Schnelle
---
Le lundi 27 décembre 2021 17:40:28 Rafael J. Wysocki a écrit :
> CC Daniel, Thomas and dri-devel.
>
> On Mon, Dec 27, 2021 at 5:32 PM wrote:
> > Hello
> >
> > I've noticed my laptop totally freeze when going to hibernation.
> > The git bisect log is appended below.
> > Please note however that
Fix cma_heap_buffer mutex lock area to protect vmap_cnt and vaddr. And
move struct dma_heap_attachment to dma-heap.h so that vendor dma heaps
can use it, the same behaviour as struct dma_buf_attachment.
Fixes: a5d2d29e24be ("dma-buf: heaps: Move heap-helper logic into the cma_heap
Pointer bufs is being initialized with a value that is never read, it
is being re-assigned with a different value later on. The assignment
is redundant and can be removed. Cleans up clang-scan warning:
drivers/video/fbdev/s3c-fb.c:492:16: warning: Value stored to 'buf'
during its initialization
Fix cma_heap_buffer mutex lock area to protect vmap_cnt and vaddr. And
move struct dma_heap_attachment to dma-heap.h so that vendor dma heaps
can use it, the same behaviour as struct dma_buf_attachment.
Fixes: a5d2d29e24be ("dma-buf: heaps: Move heap-helper logic into the cma_heap
In most cases the default values of DSI PHY tuning registers
should be sufficient as they are fully optimized. However, in
some cases (for example, where extreme board parasitics cause
the eye shape to degrade), the override bits can be used to
improve the signal quality.
As per the MSM DSI PHY
Hi,
On 28/12/2021 10:25, Miles Chen wrote:
> Fix unused-but-set variable warning:
>> drivers/gpu/drm/mediatek/mtk_cec.c:85:6: warning: variable 'tmp' set but not
>> used [-Wunused-but-set-variable]
>>
>
>Actually we ignore the value passed to mtk_cec_mask. In case of
>mtk_cec_mask(cec,
On Tue, 2021-12-28 at 10:15 +0100, Mauro Carvalho Chehab wrote:
> Em Tue, 28 Dec 2021 09:21:23 +0100
> Greg Kroah-Hartman escreveu:
>
> > On Mon, Dec 27, 2021 at 05:42:46PM +0100, Niklas Schnelle wrote:
> > > --- a/drivers/pci/Kconfig
> > > +++ b/drivers/pci/Kconfig
> > > @@ -23,6 +23,17 @@
Fix unused-but-set variable warning:
drivers/gpu/drm/mediatek/mtk_cec.c:85:6: warning: variable 'tmp' set but not
used [-Wunused-but-set-variable]
Cc: CK Hu
Cc: Matthias Brugger
Fixes: 8f83f26891e1 ("drm/mediatek: Add HDMI support")
Signed-off-by: Miles Chen
---
Change since v1:
add Fixes
>You are right, in both cases the bit is set, but the funciton does not do what
>it is supposed to do.
>Will just clear all bits of the mask.
>
>Without your patch, we will just write the val to the register and don't care
>what the register value was before that.
>
>We should somehow mention
In a future patch HAS_IOPORT=n will result in inb()/outb() and friends
not being declared. We thus need to add HAS_IOPORT as dependency for
those drivers using them. There is also a direct and hard coded use in
cirrus.c which according to the comment is only necessary during resume.
Let's just
If the null pointer is not judged in advance,
there is a risk that the pointer will cross
the boundary
Signed-off-by: Wen Zhiwei
---
drivers/gpu/drm/radeon/radeon_vm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/radeon/radeon_vm.c
Add 10nm dsi phy tuning properties for phy drive strength and
phy drive level adjustemnt.
Signed-off-by: Rajeev Nandan
---
.../devicetree/bindings/display/msm/dsi-phy-10nm.yaml | 19 +++
1 file changed, 19 insertions(+)
diff --git
Fix unused-but-set variable warning:
drivers/gpu/drm/mediatek/mtk_cec.c:85:6: warning: variable 'tmp' set but not
used [-Wunused-but-set-variable]
Signed-off-by: Miles Chen
---
drivers/gpu/drm/mediatek/mtk_cec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, 2021-12-28 at 18:12 +0100, Mauro Carvalho Chehab wrote:
> Em Tue, 28 Dec 2021 16:06:44 +0100
> Niklas Schnelle escreveu:
>
> (on a side note: the c/c list of this patch is too long. I would try to
> avoid using a too long list, as otherwise this e-mail may end being rejected
> by mail
Hi All, I am working on a platform based on the Renesas RZ/G2 SoC family.
This chip uses the rcar-du driver for the display. I would like to submit a
patch to address the fact that the driver does not check/honor the flag
DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE. My issue is that I would like to
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any
issue:
Reported-and-tested-by: syzbot+2c56b725ec547fa9c...@syzkaller.appspotmail.com
Tested on:
commit: eec4df26 Merge tag 's390-5.16-6' of git://git.kernel.o..
git tree: upstream
kernel config:
Introduce a new LEGACY_PCI Kconfig option which gates support for legacy
PCI devices including those attached to a PCI-to-PCI Express bridge and
PCI Express devices using legacy I/O spaces. Note that this is different
from non PCI uses of I/O ports such as by ACPI.
Add dependencies on LEGACY_PCI
On Tue, 2021-12-28 at 13:54 +0100, Mauro Carvalho Chehab wrote:
>
---8<---
>
> > > > All you really care about is the "legacy" I/O spaces here, this isn't
> > > > tied to PCI specifically at all, right?
> > > >
> > > > So why not just have a OLD_STYLE_IO config option or something like
> > > >
Hi Nikita,
On Thu, Dec 30, 2021 at 08:30:43AM +0300, Nikita Yushchenko wrote:
> >> I'd prefer to make each DT fragment to use only either entities defined in
> >> that fragment itself, or
> >> defined "interface entities" between this and "neighbor" DT fragment.
> >>
> >> Such as:
> >> - SoC's
Am 28.12.21 um 08:31 schrieb Wen Zhiwei:
If the null pointer is not judged in advance,
there is a risk that the pointer will cross
the boundary
As far as I can see that case is impossible, why do you want to add a
check for it?
Regards,
Christian.
Signed-off-by: Wen Zhiwei
---
Hi, Miaoqian:
Miaoqian Lin 於 2021年12月24日 週五 下午4:21寫道：
>
> The of_device_get_match_data() function may return NULL.
> Add check to prevent potential null dereference.
>
> Signed-off-by: Miaoqian Lin
> ---
> drivers/phy/mediatek/phy-mtk-mipi-dsi.c | 2 ++
> 1 file changed, 2 insertions(+)
>
>
patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Claudio-Suarez/drm-get-rid-of-DRM_DEBUG_-log-calls-in-drm-core-files-drm_-b-c-c/20211230-185446
base: git://anongit.freedesktop.org/drm/drm drm-next
On Thu, 30 Dec 2021 at 12:25, Rajeev Nandan wrote:
>
> In most cases the default values of DSI PHY tuning registers
> should be sufficient as they are fully optimized. However, in
> some cases (for example, where extreme board parasitics cause
> the eye shape to degrade), the override bits can be
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #5 from spassw...@web.de ---
There might also be different suspend errors we're dealing with:
linux-5.16-rc7 e.g. seems to hang when going into suspend with the last log
message before reboot being:
Dec 30 14:53:19 lisa kernel: [
Syzbot has reported GPF in sg_alloc_append_table_from_pages(). The
problem was in ubuf->pages == ZERO_PTR.
ubuf->pagecount is calculated from arguments passed from user-space. If
user creates udmabuf with list.size == 0 then ubuf->pagecount will be
also equal to zero; it causes kmalloc_array() to
On Thu, 30 Dec 2021 at 12:25, Rajeev Nandan wrote:
>
> Add 10nm dsi phy tuning properties for phy drive strength and
> phy drive level adjustemnt.
>
> Signed-off-by: Rajeev Nandan
> ---
> .../devicetree/bindings/display/msm/dsi-phy-10nm.yaml | 19
> +++
> 1 file changed, 19
Hi Dave, Daniel,
Fixes for 5.17. Now with more S-o-b.
The following changes since commit a342655865b2f14d1fbf346356d3b3360e63e872:
drm/radeon: Fix syntax errors in comments (2021-12-14 16:11:02 -0500)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git
On Thu, 30 Dec 2021 at 12:25, Rajeev Nandan wrote:
>
> Add 10nm dsi phy tuning properties for phy drive strength and
> phy drive level adjustemnt.
>
> Signed-off-by: Rajeev Nandan
> ---
> .../devicetree/bindings/display/msm/dsi-phy-10nm.yaml | 19
> +++
> 1 file changed, 19
On Thu, Dec 30, 2021 at 12:29 AM Dave Airlie wrote:
>
> On Thu, 30 Dec 2021 at 01:51, Alex Deucher wrote:
> >
> > Hi Dave, Daniel,
>
> Just FYI on merging this into tip I got a conflict I'm not sure what
> answer is right.
>
> fixes has:
> ee2698cf79cc759a397c61086c758d4cc85938bf
> Author: Angus
On 10/13/21 19:51, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:717478d89fe2 Merge tag 'riscv-for-linus-5.15-rc5' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12489abf30
kernel config:
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #4 from spassw...@web.de ---
Unfortunately I optimized my .config to make bisections faster, but now I
cannot reproduce the Hang with commit 2a50edbf10c8c56e930bfb53d8f9f00a33fd837e.
So now I will start over with the bisection ...
--
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #3 from spassw...@web.de ---
I added printk at the beginnig and exit(s) of rn_clocks_update:
This is the result when resuming from suspend on commit
d020970959169627d59a711769f8c4b87bf5f90c
Dec 30 13:55:42 lisa kernel: [ 140.198849]
On 30/12/2021 10:36, Miles Chen wrote:
clang reports a unused-but-set variable warning:
drivers/gpu/drm/mediatek/mtk_cec.c:85:6: warning: variable 'tmp' set but not
used [-Wunused-but-set-variable]
In current implementation, mtk_cec_mask() writes val into target register
and ignores the
On Mon, Dec 13, 2021 at 3:34 PM Hsin-Yi Wang wrote:
>
> On Mon, Nov 8, 2021 at 10:06 AM xiazhengqiao
> wrote:
> >
> > Add STARRY 2081101QFH032011-53G 10.1" WUXGA TFT LCD panel
> >
> > Signed-off-by: xiazhengqiao
Can you also create this panel's binding document? thanks
Hi Vinod,
Quoting Vinod Koul (2021-12-29 07:00:34)
>
> On 17-12-21, 16:08, Guillaume Ranquet wrote:
> > From: Markus Schneider-Pargmann
>
> Pls cc relevant folks on cover so that they know what is going on in the
> series... Is this dependent on rest? It should not and can be sent and
> reviewed
DRM_DEBUG_* and DRM_* log calls are deprecated.
Change them to drm_dbg_* / drm_{err,info,...} calls in drm core
files.
To avoid making a very big patch, this change is split in
smaller patches. This one includes drm_{b,c}*.c
Signed-off-by: Claudio Suarez
---
drivers/gpu/drm/drm_blend.c
59 matches
Mail list logo
