Hi Linus,
Am Mittwoch, 4. September 2024, 08:36:46 CEST schrieb Linus Walleij:
> On Wed, Sep 4, 2024 at 8:09 AM Alexander Stein
> wrote:
>
> > Can you please check in which memory zone this VRAM is located. In my case
> > it's important CMA is located in Normal zone to trigger this problem.
>
>
On Tue, Sep 03, 2024 at 01:27:29PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam
>
> i.MX28 has an RX DMA channel associated with the LCDIF controller.
>
> Document the 'dmas' and 'dma-names' properties to fix the following
> dt-schema warnings:
>
> lcdif@8003: 'dma-names', 'dmas' do no
On Wed, Sep 4, 2024 at 8:09 AM Alexander Stein
wrote:
> Can you please check in which memory zone this VRAM is located. In my case
> it's important CMA is located in Normal zone to trigger this problem.
dmesg says this:
Reserved memory: created DMA memory pool at 0x1800, size 8 MiB
OF: rese
Hi all,
After merging the drm-misc-fixes tree, today's linux-next build (htmldocs)
produced this warning:
Error: Cannot open file drivers/gpu/drm/drm_bridge_connector.c
Introduced by commit
9da7ec9b19d8 ("drm/bridge-connector: move to DRM_DISPLAY_HELPER module")
--
Cheers,
Stephen Rothwell
On Wed, Sep 04, 2024 at 05:43:15AM +0300, Paul Pu wrote:
> This changes the judgement of if needing to round up the width or not,
> from using the `dp_flow` to the plane's type.
>
> The `dp_flow` can be -22(-EINVAL) even the plane is a PRIMARY one.
> See `client_reg[]` in `ipu-common.c`.
>
> [
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Reviewed-by: Tomi Valkeinen
---
drivers/media/platform/xilinx/xilinx-tpg.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git a/drivers/media/platform/xilinx/xilinx
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
---
drivers/video/fbdev/omap2/omapfb/dss/dpi.c| 3 +-
drivers/video/fbdev/omap2/omapfb/dss/dss-of.c | 66 ---
drivers/video/fbdev/omap2/omapfb/dss/dss.c| 15 ++---
driver
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Reviewed-by: Tomi Valkeinen
---
drivers/gpu/drm/omapdrm/dss/dpi.c | 3 ++-
drivers/gpu/drm/omapdrm/dss/sdi.c | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/d
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Acked-by: Mark Brown
---
sound/soc/generic/audio-graph-card2.c | 113 +++---
1 file changed, 48 insertions(+), 65 deletions(-)
diff --git a/sound/soc/generic/audio-graph-car
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Acked-by: Mark Brown
---
sound/soc/generic/audio-graph-card.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/sound/soc/generic/audio-graph-card.c
b/sound/soc/ge
Current test-component.c is using for_each_endpoint_of_node()
for parsing "port", because there was no "port" base loop before.
It has been assuming 1 port has 1 endpoint here.
But now we can use "port" base loop (= for_each_of_graph_port()).
Let's replace for_each function from "endpoint" base to
Now we can use new port related functions for port parsing. Use it.
Signed-off-by: Kuninori Morimoto
Acked-by: Mark Brown
---
sound/soc/sh/rcar/core.c | 21 +++--
1 file changed, 7 insertions(+), 14 deletions(-)
diff --git a/sound/soc/sh/rcar/core.c b/sound/soc/sh/rcar/core.c
i
We already have of_graph_get_next_endpoint(), but it is not
intuitive to use in some case.
(X) node {
(Y) ports {
(P0)port@0 { endpoint { remote-endpoint = ...; };};
(P10) port@1 { endpoint { remote-endpoint = ...; };
(P11)
We have endpoint base functions
- of_graph_get_next_device_endpoint()
- of_graph_get_device_endpoint_count()
- for_each_of_graph_device_endpoint()
Here, for_each_of_graph_device_endpoint() loop finds each endpoints
ports {
port@0 {
(1)
Hi Rob, Saravana, Tomi, Laurent, Sakari, Mark
This is v5 patch-set
Current Of-graph has "endpoint base" for loop, but doesn't have
"port base" loop. "endpoint base" loop only is not enough.
This patch-set add new "port base" for loop, and use it.
Unfortunately, new helper function need to call
Hi Linus,
Am Mittwoch, 4. September 2024, 00:53:42 CEST schrieb Linus Walleij:
> On Fri, Apr 19, 2024 at 10:35 AM Thomas Zimmermann
> wrote:
>
> > Add support for damage handling and deferred I/O to fbdev-dma. This
> > enables fbdev-dma to support all DMA-memory-based DRM drivers, even
> > such
This changes the judgement of if needing to round up the width or not,
from using the `dp_flow` to the plane's type.
The `dp_flow` can be -22(-EINVAL) even the plane is a PRIMARY one.
See `client_reg[]` in `ipu-common.c`.
[0.605141] [drm:ipu_plane_init] channel 28, dp flow -22, possible_crtcs
Hi Paul,
Thanks for your patch.
On 09/04/2024, Paul Pu wrote:
> This changes the judgement of if needing to round up the width or not,
> from using the `dp_flow` to the plane's type.
>
> The `dp_flow` can be -22(-EINVAL) even the plane is a PRIMARY one.
s/even/even if/
> See `client_reg[]` in
> > > +static int
> > > +intel_atomic_replace_property_blob_from_id(struct drm_device *dev,
> > > +struct drm_property_blob **blob,
> > > +u64 blob_id,
> > > +ssize_t expected_size,
> > > +
^
drivers/gpu/drm/bridge/ti-tdp158.c:80:65: note: each undeclared identifier is
reported only once for each function it appears in
Caused by commit
a15710027afb ("drm/bridge: add support for TI TDP158")
I have used the drm-misc t
Hi Jani,
Sorry for being late.
> -Original Message-
> From: Jani Nikula
> Sent: Thursday, August 29, 2024 8:45 PM
> To: dri-devel@lists.freedesktop.org
> Cc: Daniel Vetter ; inki@samsung.com
> Subject: Re: [PATCH 0/6] drm: conversions to struct drm_edid
>
> On Thu, 22 Aug 2024, Jan
As per the previous dt-binding commit, update the WL-355608-A8 panel
compatible to reflect the the integrating device vendor and name as the
panel OEM is unknown.
Signed-off-by: Ryan Walklin
--
Changelog v2..v3:
- Use integrating device name with vendor prefix instead of OEM serial.
---
driver
The WL-355608-A8 is a 3.5" 640x480@60Hz RGB LCD display from an unknown
OEM used in a number of handheld gaming devices made by Anbernic.
Previously committed using the OEM serial without a vendor prefix,
however following subsequent discussion the preference is to use the
integrating device vendor
Hi,
V3 of this patch updated to reflect discussion and agreement to use the
integrating vendor prefix and device names for this display panel.
The previous patch adding support for this panel [1] referred to previously by
its serial number only. As discussed after the patch was committed, the
On 8/30/2024 3:16 PM, Dmitry Baryshkov wrote:
On Fri, 30 Aug 2024 at 22:28, Jessica Zhang wrote:
On 8/30/2024 10:18 AM, Dmitry Baryshkov wrote:
On Thu, Aug 29, 2024 at 01:48:32PM GMT, Jessica Zhang wrote:
Add support for allocating the concurrent writeback mux as part of the
WB allocati
When the FW state is too large to fit in initial seq_file buffer,
seq_write returns -1, which is subsequently returned from
dmub_fw_state_show. This causes the read operation to fail.
Return instead always 0 and let the seq_file handling retry the read
with a larger buffer if the initial buffer ov
On Tue, 03 Sep 2024 11:22:30 -0400, Detlev Casanova wrote:
> Add the rk3576-armsom-sige5 device tree as well as its rk3576.dtsi base
> and pinctrl information in rk3576-pinctrl.dtsi.
>
> The other commits add DT bindings documentation for the devices that
> already work with the current correspond
On 2024-09-03 02:35, Mikhail Gavrilov wrote:
On Sun, Aug 25, 2024 at 2:12 AM Mikhail Gavrilov
wrote:
Hi,
Is anyone trying to look into it?
I continue to reproduce this issue on fresh kernel builds 6.11-rc4+.
In addition to the RenPy engine, the problem also reproduces on games
from Ubisoft
Hi,
On Fri, Aug 23, 2024 at 9:49 AM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Aug 23, 2024 at 9:35 AM Charles Han wrote:
> >
> > In hx83102_get_modes(), the return value of drm_mode_duplicate()
> > is assigned to mode, which will lead to a possible NULL pointer
> > dereference on failure of drm_m
Hi,
On Mon, Sep 2, 2024 at 12:10 AM Tejas Vipin wrote:
>
> Changes the samsung-s6e3fa7 panel to use multi style functions for
> improved error handling.
>
> Signed-off-by: Tejas Vipin
> ---
> drivers/gpu/drm/panel/panel-samsung-s6e3fa7.c | 71 ++-
> 1 file changed, 21 insertions
On Fri, Apr 19, 2024 at 10:35 AM Thomas Zimmermann wrote:
> Add support for damage handling and deferred I/O to fbdev-dma. This
> enables fbdev-dma to support all DMA-memory-based DRM drivers, even
> such with a dirty callback in their framebuffers.
>
> The patch adds the code for deferred I/O an
Quoting Andy Shevchenko (2024-09-02 04:12:49)
> On Sat, Aug 31, 2024 at 09:06:49PM -0700, Stephen Boyd wrote:
>
> Is it possible to move these Cc:s after --- line below?
Ok.
>
> > /**
> > * devcon_match_fn_t - device connection match function
> > * @fwnode: Remote connection's device node
>
Quoting Andy Shevchenko (2024-09-02 04:17:12)
> On Sat, Aug 31, 2024 at 09:06:48PM -0700, Stephen Boyd wrote:
> > The usage of this match function is hard to understand at a glance.
> > Document the arguments and the return value so it is clear how to
> > implement the function.
>
> Thank you for t
On 8/30/2024 10:41 AM, Dmitry Baryshkov wrote:
On Thu, Aug 29, 2024 at 01:48:31PM GMT, Jessica Zhang wrote:
From: Esha Bharadwaj
Add function ops to allow hw_wb to configure CWB registers and adjust
the WB_MUX configuration to account for using dedicated CWB pingpong
blocks.
Signed-off-by:
Hi Heiko,
On Tue, Sep 03, 2024 at 11:59:12PM GMT, Heiko Stübner wrote:
> Am Dienstag, 3. September 2024, 18:47:17 CEST schrieb Andi Shyti:
> > On Tue, Sep 03, 2024 at 11:59:34AM GMT, Detlev Casanova wrote:
> > > On Tuesday, 3 September 2024 11:46:00 EDT Andi Shyti wrote:
> > > > Hi,
> > > >
> > >
On 8/30/2024 10:13 AM, Dmitry Baryshkov wrote:
On Thu, Aug 29, 2024 at 01:48:29PM GMT, Jessica Zhang wrote:
From: Esha Bharadwaj
Add new block for concurrent writeback mux to HW catalog and change
pingpong index names to distinguish between general use pingpong blocks
and pingpong blocks de
Hi,
On Tue, Sep 03, 2024 at 11:22:33AM GMT, Detlev Casanova wrote:
> Just like RK356x and RK3588, RK3576 is compatible to the existing
> rk3399 binding.
>
> Signed-off-by: Detlev Casanova
> Acked-by: Krzysztof Kozlowski
> Acked-by: Heiko Stuebner
merged to i2c/i2c-host.
Thanks,
Andi
Quoting Andy Shevchenko (2024-09-02 04:35:46)
> On Sat, Aug 31, 2024 at 09:06:44PM -0700, Stephen Boyd wrote:
> > Extend the aux-hpd bridge driver to support assigning DP lanes to USB
> > type-c pins based on typec mux state entry. Existing users of this
> > driver only need the HPD signaling suppo
On 8/30/2024 10:00 AM, Dmitry Baryshkov wrote:
On Thu, Aug 29, 2024 at 01:48:28PM GMT, Jessica Zhang wrote:
Check that each encoder in the CRTC state's encoder_mask is marked as a
possible clone for all other encoders in the encoder_mask and that only
one CRTC is in clone mode at a time
Sign
On Tue, 3 Sep 2024 11:22:30 -0400, Detlev Casanova wrote:
> Add the rk3576-armsom-sige5 device tree as well as its rk3576.dtsi base
> and pinctrl information in rk3576-pinctrl.dtsi.
>
> The other commits add DT bindings documentation for the devices that
> already work with the current correspondi
Hi Andi,
Am Dienstag, 3. September 2024, 17:46:00 CEST schrieb Andi Shyti:
> On Tue, Sep 03, 2024 at 11:22:33AM GMT, Detlev Casanova wrote:
> > Just like RK356x and RK3588, RK3576 is compatible to the existing
> > rk3399 binding.
> >
> > Signed-off-by: Detlev Casanova
> > Acked-by: Krzysztof Koz
On Tue, 3 Sep 2024 11:22:30 -0400, Detlev Casanova wrote:
> Add the rk3576-armsom-sige5 device tree as well as its rk3576.dtsi base
> and pinctrl information in rk3576-pinctrl.dtsi.
>
> The other commits add DT bindings documentation for the devices that
> already work with the current correspondi
Am Dienstag, 3. September 2024, 18:47:17 CEST schrieb Andi Shyti:
> On Tue, Sep 03, 2024 at 11:59:34AM GMT, Detlev Casanova wrote:
> > On Tuesday, 3 September 2024 11:46:00 EDT Andi Shyti wrote:
> > > Hi,
> > >
> > > On Tue, Sep 03, 2024 at 11:22:33AM GMT, Detlev Casanova wrote:
> > > > Just like
On Sat, 31 Aug 2024 00:43:11 + Mina Almasry wrote:
> +The socket must be flow steered to the dmabuf bound RX queue::
> +
> + ethtool -N eth1 flow-type tcp4 ... queue 15,
nit: tailing comma here
> +Devmem payloads are inaccessible to the kernel processing the packets. This
> +results in a
On Sat, 31 Aug 2024 00:43:08 + Mina Almasry wrote:
> static inline bool tcp_skb_can_collapse_to(const struct sk_buff *skb)
> {
> - return likely(!TCP_SKB_CB(skb)->eor);
> + return likely(!TCP_SKB_CB(skb)->eor && skb_frags_readable(skb));
Do you remember why this is here? Both for Rx
On Sat, 31 Aug 2024 00:43:07 + Mina Almasry wrote:
> Make skb_frag_page() fail in the case where the frag is not backed
> by a page, and fix its relevant callers to handle this case.
>
> Signed-off-by: Mina Almasry
> Reviewed-by: Eric Dumazet
Reviewed-by: Jakub Kicinski
On 2024-09-02 05:40, tjak...@math.uni-bielefeld.de wrote:
> From: Tobias Jakobi
>
> dc_state_destruct() nulls the resource context of the DC state. The pipe
> context passed to dcn35_set_drr() is a member of this resource context.
>
> If dc_state_destruct() is called parallel to the IRQ proce
On 2024-09-02 05:40, tjak...@math.uni-bielefeld.de wrote:
> From: Tobias Jakobi
>
> dc_state_destruct() nulls the resource context of the DC state. The pipe
> context passed to dcn10_set_drr() is a member of this resource context.
>
> If dc_state_destruct() is called parallel to the IRQ proce
On Sat, 31 Aug 2024 00:43:06 + Mina Almasry wrote:
> diff --git a/include/net/mp_dmabuf_devmem.h b/include/net/mp_dmabuf_devmem.h
> new file mode 100644
> index ..6d1cf2a77f6b
> --- /dev/null
> +++ b/include/net/mp_dmabuf_devmem.h
this header can live under net/core/ like netmem_pr
On Tue, Sep 03, 2024 at 03:46:43PM +0200, Christian König wrote:
> Hi Steven,
>
> Am 29.08.24 um 15:37 schrieb Steven Price:
> > Hi Christian,
> >
> > Mihail should be able to give more definitive answers, but I think I can
> > answer your questions.
> >
> > On 29/08/2024 10:40, Christian König
On Sat, 31 Aug 2024 00:43:03 + Mina Almasry wrote:
> Add a netdev_dmabuf_binding struct which represents the
> dma-buf-to-netdevice binding. The netlink API will bind the dma-buf to
> rx queues on the netdevice. On the binding, the dma_buf_attach
> & dma_buf_map_attachment will occur. The entri
This commit introduces a DRM device sysfs attribute that lets UM control
the job accounting status in the device. The knob variable had been brought
in as part of a previous commit, but now we're able to fix it manually.
As sysfs files are part of a driver's uAPI, describe its legitimate input
val
Implement drm object's status callback.
Also, we consider a PRIME imported BO to be resident if its matching
dma_buf has an open attachment, which means its backing storage had already
been allocated.
Signed-off-by: Adrián Larumbe
Reviewed-by: Liviu Dudau
---
drivers/gpu/drm/panthor/panthor_ge
Drawing from the FW-calculated values in the previous commit, we can
increase the numbers for an open file by collecting them from finished jobs
when updating their group synchronisation objects.
Display of fdinfo key-value pairs is governed by a flag that is by default
disabled in the present com
Enable calculations of job submission times in clock cycles and wall
time. This is done by expanding the boilerplate command stream when running
a job to include instructions that compute said times right before an after
a user CS.
A separate kernel BO is created per queue to store those values. J
This patch series enables userspace utilities like gputop and nvtop to
query a render context's fdinfo file and figure out rates of engine
and memory utilisation.
Previous discussion can be found at
https://lore.kernel.org/dri-devel/20240716201302.2939894-1-adrian.laru...@collabora.com/
Changelog
It is enabled by W=1 and amdgpu has a clean build with it enabled. So,
to make sure we block future instances of it from showing up on
our driver, enable it by default for the module.
Signed-off-by: Hamza Mahfooz
---
drivers/gpu/drm/amd/amdgpu/Makefile | 1 +
1 file changed, 1 insertion(+)
diff
On 5/23/24 09:37, Jani Nikula wrote:
Since commit a61ddb4393ad ("drm: enable (most) W=1 warnings by default
across the subsystem"), most of the extra warnings in the driver
Makefile are redundant. Remove them.
Note that -Wmissing-declarations and -Wmissing-prototypes are always
enabled by defaul
On Thu, Feb 29, 2024 at 05:22:24PM +0100, Boris Brezillon wrote:
> - Add our job fence as DMA_RESV_USAGE_WRITE to all external objects
> (was previously DMA_RESV_USAGE_BOOKKEEP). I don't get why, given
> we're supposed to be fully-explicit, but other drivers do that, so
> there must be a good
On Wed, Jul 31, 2024 at 2:13 PM Rob Herring (Arm) wrote:
>
> Use of_property_present() to test for property presence rather than
> of_find_property(). This is part of a larger effort to remove callers
> of of_find_property() and similar functions. of_find_property() leaks
> the DT struct property
On Wed, Aug 28, 2024 at 06:26:02PM +0100, Mihail Atanassov wrote:
> +int panthor_xgs_queue_create(struct panthor_file *pfile, u32 vm_id,
> + int eventfd_sync_update, u32 *handle)
> +{
> + struct panthor_device *ptdev = pfile->ptdev;
> + struct panthor_xgs_queue_pool
On Tue, Sep 03, 2024 at 08:34:37PM +0300, Jani Nikula wrote:
> Clang build with CONFIG_DRM_DEBUG_MM=n, CONFIG_WERROR=y, and W=1 leads
> to:
>
> CC [M] drivers/gpu/drm/drm_mm.o
> ../drivers/gpu/drm/drm_mm.c:614:20: error: function
> 'drm_mm_node_scanned_block' is not needed and will not be emit
BTW, just as a self reminder,
Reviewed-by: Andi Shyti
Thanks,
Andi
On Tue, Sep 03, 2024 at 11:22:33AM GMT, Detlev Casanova wrote:
> Just like RK356x and RK3588, RK3576 is compatible to the existing
> rk3399 binding.
>
> Signed-off-by: Detlev Casanova
> Acked-by: Krzysztof Kozlowski
> Acked-b
On Fri, Aug 30, 2024 at 12:04 AM Jens Wiklander
wrote:
>
> Add a Linaro restricted heap using the linaro,restricted-heap bindings
> implemented based on the generic restricted heap.
>
> The bindings defines a range of physical restricted memory. The heap
> manages this address range using genalloc
Hi Jeffrey,
I have completed the code changes based on your comments. And we are
still working on the documentation.
Should I send out another patch set with only the code changes for your
to review? Or you would wait for the documentation to review together?
Thanks,
Lizhi
On 8/14/24 13
On Fri, Aug 30, 2024 at 12:04 AM Jens Wiklander
wrote:
>
> From: Etienne Carriere
>
> Enable userspace to create a tee_shm object that refers to a dmabuf
> reference.
>
> Userspace registers the dmabuf file descriptor as in a tee_shm object.
> The registration is completed with a tee_shm file des
On Tue, Sep 03, 2024 at 04:05:06PM +0300, Tomi Valkeinen wrote:
> Hi,
>
> On 03/09/2024 14:56, Maxime Ripard wrote:
> > On Mon, Sep 02, 2024 at 03:31:28PM GMT, Tomi Valkeinen wrote:
> > > Hi,
> > >
> > > On 02/09/2024 13:50, Daniel Vetter wrote:
> > > > On Mon, Sep 02, 2024 at 11:26:11AM +0200, M
Clang build with CONFIG_DRM_DEBUG_MM=n, CONFIG_WERROR=y, and W=1 leads
to:
CC [M] drivers/gpu/drm/drm_mm.o
../drivers/gpu/drm/drm_mm.c:614:20: error: function 'drm_mm_node_scanned_block'
is not needed and will not be emitted [-Werror,-Wunneeded-internal-declaration]
static inline bool drm_mm_n
Transition to mipi_dsi_dcs_write_seq_multi() macros for initialization
sequences. The previous mipi_dsi_dcs_write_seq() macros were
non-intuitive and use other wrapped MIPI DSI functions in the
driver code to simplify the code pattern.
Reported-by: kernel test robot
Closes:
https://lore.kernel.o
On Tue, Sep 03, 2024 at 11:17:37AM +0200, Javier Martinez Canillas wrote:
> Abhishek Tamboli writes:
>
Hi Javier,
>
> > Use the new mipi_dsi_*_multi wrapped function in hx83112a_on
> > and hx83112a_disable function.
> IMO commit messages should explain why the change is needed and
> not just wh
On Mon, Jul 22, 2024 at 08:53:41AM +0200, amerg...@baylibre.com wrote:
> From: Nicolas Belin
>
> Add the support of MT6357 PMIC audio codec.
This breaks the build:
/build/stage/linux/sound/soc/codecs/mt6357.c: In function
‘mt6357_platform_driver_probe’:
/build/stage/linux/sound/soc/codecs/mt63
Hi Marek,
On Tue, Sep 3, 2024 at 1:51 PM Marek Vasut wrote:
> This also applies to MX23 , that one also has the support for
> command-mode LCDs which are then driven by pumping commands via DMA. I
> don't think Linux actually supports this mode of operation, but I do
> recall using it some long
On 9/3/24 6:27 PM, Fabio Estevam wrote:
From: Fabio Estevam
i.MX28 has an RX DMA channel associated with the LCDIF controller.
Document the 'dmas' and 'dma-names' properties to fix the following
dt-schema warnings:
lcdif@8003: 'dma-names', 'dmas' do not match any of the regexes:
'pinctrl
Hi Abhishek,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on linus/master v6.11-rc6 next-20240903]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to
Hi,
On Tue, Sep 03, 2024 at 11:59:34AM GMT, Detlev Casanova wrote:
> On Tuesday, 3 September 2024 11:46:00 EDT Andi Shyti wrote:
> > Hi,
> >
> > On Tue, Sep 03, 2024 at 11:22:33AM GMT, Detlev Casanova wrote:
> > > Just like RK356x and RK3588, RK3576 is compatible to the existing
> > > rk3399 bind
From: Fabio Estevam
i.MX28 has an RX DMA channel associated with the LCDIF controller.
Document the 'dmas' and 'dma-names' properties to fix the following
dt-schema warnings:
lcdif@8003: 'dma-names', 'dmas' do not match any of the regexes:
'pinctrl-[0-9]+'
Signed-off-by: Fabio Estevam
--
On Tue, 03 Sep 2024, Thierry Reding wrote:
> On Mon, Sep 02, 2024 at 07:13:17PM GMT, Jani Nikula wrote:
>> It's likely either output->drm_edid or output->ddc is non-NULL, but
>> avoid the uninitialized variable usage anyway.
>>
>> Reported-by: kernel test robot
>> Closes: https://lore.kernel.org
Marijn Suijten 于2024年9月3日周二 18:12写道：
>
> On 2024-08-29 18:17:32, Jun Nie wrote:
> > Data width for dsc engine is aligned with pipe, not with whole screen
> > width. Because the width may be halved in DSI bonded case.
> >
> > The dsc width is not related to the timing with back front porch in
> > l
On Tue, Aug 20, 2024 at 12:16:28PM +, Liao Chen wrote:
> Add MODULE_DEVICE_TABLE(), so modules could be properly autoloaded
> based on the alias from of_device_id table.
>
> Signed-off-by: Liao Chen
Reviewed-by: Daniel Thompson
Daniel.
Hello,
On Tuesday, 3 September 2024 11:46:00 EDT Andi Shyti wrote:
> Hi,
>
> On Tue, Sep 03, 2024 at 11:22:33AM GMT, Detlev Casanova wrote:
> > Just like RK356x and RK3588, RK3576 is compatible to the existing
> > rk3399 binding.
> >
> > Signed-off-by: Detlev Casanova
> > Acked-by: Krzysztof Ko
Hi Alex,
kernel test robot noticed the following build errors:
[auto build test ERROR on robh/for-next]
[also build test ERROR on drm-misc/drm-misc-next linus/master v6.11-rc6
next-20240903]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
Hi,
On Tue, Sep 03, 2024 at 11:22:33AM GMT, Detlev Casanova wrote:
> Just like RK356x and RK3588, RK3576 is compatible to the existing
> rk3399 binding.
>
> Signed-off-by: Detlev Casanova
> Acked-by: Krzysztof Kozlowski
> Acked-by: Heiko Stuebner
I will apply this after 1 and 2 have been merg
On Sat, 31 Aug 2024, Stephen Boyd wrote:
> Add a DT graph binding to google,cros-ec-typec so that it can combine
> DisplayPort (DP) and USB SuperSpeed (SS) data into a USB type-c endpoint
> that is connected to the usb-c-connector node's SS endpoint. This also
> allows us to connect the DP and USB
On Tue, 03 Sep 2024, Robert Foss wrote:
> On Mon, 12 Aug 2024 16:51:00 +0200, Marc Gonzalez wrote:
>> TDP158 is an AC-coupled DVI / HDMI to TMDS level shifting Redriver.
>>
>> Like the TFP410, the TDP158 can be set up in 2 different ways:
>> 1) hard-coding its configuration settings using pin-str
Just like RK356x and RK3588, RK3576 is compatible to the existing
rk3399 binding.
Signed-off-by: Detlev Casanova
Acked-by: Krzysztof Kozlowski
Acked-by: Heiko Stuebner
---
Documentation/devicetree/bindings/i2c/i2c-rk3x.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devi
Add board file for the rk3576 based ArmSoM Sige5 board. While the hardware
offers plenty of peripherals and connectivity this basic implementation
just handles things required to successfully boot Linux from SD card and
connect via UART or Ethernet.
Signed-off-by: Detlev Casanova
---
arch/arm64/
It is compatible with the rockchip,rk3066-spi SPI core.
Signed-off-by: Detlev Casanova
Acked-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/spi/spi-rockchip.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-rockchip.yaml
b/Documen
Add devicetree binding for the ArmSoM Sige 5 board.
Signed-off-by: Detlev Casanova
Acked-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml
b/Documentation/
Add the compatible for the pmu mfd on rk3576.
Signed-off-by: Detlev Casanova
Reviewed-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/arm/rockchip/pmu.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip/pmu.yaml
b/Documentatio
Add a Rockchip RK3576 compatible.
Signed-off-by: Detlev Casanova
Acked-by: Krzysztof Kozlowski
Acked-by: Heiko Stuebner
---
Documentation/devicetree/bindings/serial/snps-dw-apb-uart.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/serial/snps-dw-apb-ua
It is compatible with the other rockchip SoCs.
Signed-off-by: Detlev Casanova
Acked-by: Krzysztof Kozlowski
Acked-by: Guenter Roeck
---
Documentation/devicetree/bindings/watchdog/snps,dw-wdt.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/watchdog/snp
Add the rk3576-armsom-sige5 device tree as well as its rk3576.dtsi base
and pinctrl information in rk3576-pinctrl.dtsi.
The other commits add DT bindings documentation for the devices that
already work with the current corresponding drivers.
Note that as is, the rockchip gpio driver needs the gpi
The rk3576 SoC has an ARM Mali G52 MC3 GPU, that is compatible with
arm,mali-bifrost.
Signed-off-by: Detlev Casanova
Acked-by: Krzysztof Kozlowski
---
Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/binding
Hi Dave and Sima,
We'd like to include this extra display clean-up
towards the 6.12. Hence this extra pull-request on top
of what I declared as our last one last week.
It only delayed because it touches both Xe and i915 and
it depended on xe changes that propagated through drm-xe-next
last week +
Am 03.09.24 um 17:22 schrieb Thomas Hellström:
On Tue, 2024-09-03 at 17:14 +0200, Christian König wrote:
Am 03.09.24 um 15:38 schrieb Thomas Hellström:
Some user-space APIs distinguison between graphics memory OOMs and
system (host) memory OOMs. To aid UMDs in determining the type of
OOM, allow
On Tue, 2024-09-03 at 17:14 +0200, Christian König wrote:
> Am 03.09.24 um 15:38 schrieb Thomas Hellström:
> > Some user-space APIs distinguison between graphics memory OOMs and
> > system (host) memory OOMs. To aid UMDs in determining the type of
> > OOM, allow forwarding the ENOSPC from resource
Am 03.09.24 um 15:38 schrieb Thomas Hellström:
Some user-space APIs distinguison between graphics memory OOMs and
system (host) memory OOMs. To aid UMDs in determining the type of
OOM, allow forwarding the ENOSPC from resource managers to drivers
on calls to ttm_bo_validate().
Cc: Christian Köni
On Thu, Aug 22, 2024 at 02:25:46PM +0800, Jinjie Ruan wrote:
> Use scoped for_each_child_of_node_scoped() when iterating over device
> nodes to make code a bit simpler.
>
> Signed-off-by: Jinjie Ruan
Reviewed-by: Daniel Thompson
Daniel.
On Tue, Aug 20, 2024 at 11:22:38AM +0200, Thomas Zimmermann wrote:
> This series removes most dependencies on fbdev from the lcd subsystem
> and its drivers.
>
> Patches 1 to 3 rework the fbdev notifier, the fbdev's fb_info can
> now refer to a dedicated lcd device, and lcd defines constants for
>
On Tue, Aug 20, 2024 at 11:23:04AM +0200, Thomas Zimmermann wrote:
> Rename check_fb in struct lcd_ops with controls_device. The callback
> is not independent from fbdev's struct fb_info and tests is an lcd
> device controls a hardware display device. The new naming and semantics
> follow similar f
1 - 100 of 234 matches
Mail list logo
