Am 25.03.22 um 05:05 schrieb Ryan Lin:
Disable ABM feature when the system is running on AC mode to get
the more perfect contrast of the display.
Signed-off-by: Ryan Lin
---
drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | 4 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c| 1 +
drivers
On Thu, Mar 24, 2022 at 01:07:56PM +0100, Robert Foss wrote:
> > > > > The driver uses DRM_DEV_* for logs. Can we use this?
> > > > Hi Hsin-Yi, as comment in drm/drm_print.h:
> > > > "NOTE: this is deprecated in favor of drm_dbg". DRM bridge driver not
> > > > use DRM_DEV_* any more. I'll send a pa
Disable ABM feature when the system is running on AC mode to get
the more perfect contrast of the display.
Signed-off-by: Ryan Lin
---
drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | 4 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c| 1 +
drivers/gpu/drm/amd/display/dc/dce/dmub_abm.c | 58
On 17 3月 22 10:26:31, Cai Huoqing wrote:
> Using "size of" instead of "end of" to fix the description for 'size' tag.
>
> Signed-off-by: Cai Huoqing
> ---
> drivers/gpu/drm/drm_mm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/
> FYI, this breaks the DT bindings. The relevant patches didn't get
> reviewed nor run thru automated testing because their encoding was
> 'charset=y'[1]. (While email clients seem to just ignore that
> encoding, patchwork and b4 do not.) linux-next is still broken and has
> been since Mar 2[2]. v2
Please drop the UPSTREAM prefix. Might be needed in the ChromeOS patch, but
not for upstream.
On Fri, Mar 25, 2022, 2:29 AM Ryan Lin wrote:
> Disable ABM feature when the system is running on AC mode to get
> the more perfect contrast of the display.
>
> Signed-off-by: Ryan Lin
>
> ---
> drive
Hi Linus,
Some fixes were queued up in and in light of the fbdev regressions,
I've pulled those in as well,
I think the mediatek one is going to be a bit more painful, since now
you have a merge and I need to have the mediatek stuff get rebased and
retested onto that merge point, but I'll make sur
Disable ABM feature when the system is running on AC mode to get
the more perfect contrast of the display.
Signed-off-by: Ryan Lin
---
drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | 4 ++
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c| 1 +
drivers/gpu/drm/amd/display/dc/dce/dmub_abm.c | 58
From: Sean Paul
ATOMIC and DRIVER log categories do not typically contain per-frame log
messages. This patch re-classifies some messages in amd to chattier
categories to keep ATOMIC/DRIVER quiet.
Signed-off-by: Sean Paul
---
drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 5 +++--
drivers/
https://bugzilla.kernel.org/show_bug.cgi?id=215727
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
The pull request you sent on Thu, 24 Mar 2022 12:30:02 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2022-03-24
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b14ffae378aa1db993e62b01392e70d1e585fb23
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
On Fri, 25 Mar 2022 at 09:09, Chun-Kuang Hu wrote:
>
> Hi, Dave & Daniel:
>
> This includes:
>
> 1. Fix dt-binding issue.
>
This tree is based on a random drm-next tree, which I can't pull.
Please base it on the latest drm-next tree.
I tried cherry-pick these patches over and it failed badly on
On Wed, Mar 23, 2022 at 7:30 PM Dave Airlie wrote:
>
> This is the main drm pull request for 5.18.
>
> The summary changelog is below, lots of work all over,
> Intel improving DG2 support, amdkfd CRIU support, msm
> new hw support, and faster fbdev support.
Ok, so this was annoying.
I've merged
Hi, Corentin:
I've applied Jason's series [1] to my tree [2], does that series fix
your problem?
[1] https://patchwork.kernel.org/project/linux-mediatek/list/?series=621899
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/chunkuang.hu/linux.git/log/?h=mediatek-drm-fixes
Regards,
Chun-Kuang.
Hi, Dave & Daniel:
This includes:
1. Fix dt-binding issue.
Regards,
Chun-Kuang.
The following changes since commit 71941773e143369a73c9c4a3b62fbb60736a1182:
Add linux-next specific files for 20220310 (2022-03-10 20:04:36 +1100)
are available in the git repository at:
https://git.kernel.o
On Fri, Mar 4, 2022 at 1:03 AM Joel Stanley wrote:
> The example needs updating to match the to be added yaml bindings for
> the gfx node.
>
> Signed-off-by: Joel Stanley
Patch applied.
Yours,
Linus Walleij
On Thu, Mar 24, 2022 at 3:32 AM Dave Airlie wrote:
>
> Hi Linus,
>
> This is the main drm pull request for 5.18.
>
> The summary changelog is below, lots of work all over,
> Intel improving DG2 support, amdkfd CRIU support, msm
> new hw support, and faster fbdev support.
>
> Conflicts:
> I did a m
On 3/24/22 12:18, Thomas Zimmermann wrote:
Hi
Am 24.03.22 um 20:11 schrieb Guenter Roeck:
Hi,
On Wed, Feb 23, 2022 at 08:38:03PM +0100, Thomas Zimmermann wrote:
Improve the performance of cfb_imageblit() by manually unrolling
the inner blitting loop and moving some invariants out. The compile
On Sun, Mar 13, 2022 at 08:29:52PM +0100, Thomas Zimmermann wrote:
> Commit 0d03011894d2 ("fbdev: Improve performance of cfb_imageblit()")
> broke cfb_imageblit() for image widths that are not aligned to 8-bit
> boundaries. Fix this by handling the trailing pixels on each line
> separately. The per
Quoting Dmitry Baryshkov (2022-03-23 02:25:38)
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> index 38627ccf3068..ab8a35e09bc9 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> @@ -381,8 +3
Quoting Dmitry Baryshkov (2022-03-23 02:25:35)
> Currently the msm platform driver is a multiplex handling several cases:
> - headless GPU-only driver,
> - MDP4 with flat device nodes,
> - MDP5/DPU MDSS with all the nodes being children of MDSS node.
>
> This results in not-so-perfect code, checkin
Hi,
On Thu, Mar 24, 2022 at 11:14 AM Matthias Kaehlcke wrote:
>
> Add binding for the AUO B133UAN01 panel. It is 13.3" TFT LCD panel
> with WUXGA (1920x1200) resolution.
>
> Signed-off-by: Matthias Kaehlcke
> ---
>
> .../devicetree/bindings/display/panel/panel-simple.yaml | 2 ++
> 1 fi
Hi,
On Thu, Mar 24, 2022 at 1:48 PM Matthias Kaehlcke wrote:
>
> Add support for the AUO B133UAN01 13.3" WUXGA panel.
>
> Signed-off-by: Matthias Kaehlcke
> ---
>
> Changes in v2:
> - autodetect and configure the panel based on the EDID data instead of
> relying on a compatible string and hard
Add support for the AUO B133UAN01 13.3" WUXGA panel.
Signed-off-by: Matthias Kaehlcke
---
Changes in v2:
- autodetect and configure the panel based on the EDID data instead of
relying on a compatible string and hardcoded mode settings.
drivers/gpu/drm/panel/panel-edp.c | 1 +
1 file changed,
Quoting Dmitry Baryshkov (2022-03-24 04:55:36)
> Make dpu-qcm2290 example really follow the defined schema:
> - Drop qcom,mdss compatible. It's only used for MDP5 devices.
> - Change display controller name to display-controller as specified in
> the yaml
>
> Reported-by: Rob Herring
> Cc: Loic
Quoting Dmitry Baryshkov (2022-03-23 03:35:45)
> Since dp_panel_get_modes() handling for dp_mode was removed,
> dp_display_get_modes also doesn't change the passed dp_mode, drop the
> unused dp_mode variable being allocated unused and then freed.
>
> Signed-off-by: Dmitry Baryshkov
> ---
Reviewed
Quoting Dmitry Baryshkov (2022-03-23 03:35:46)
> Since the last commit, the max_pclk_khz became constant, it's set to
> DP_MAX_PIXEL_CLK_KHZ and never changed afterwards. Remove it completely
> and use DP_MAX_PIXEL_CLK_KHZ directly.
>
> Signed-off-by: Dmitry Baryshkov
> ---
Reviewed-by: Stephen B
Quoting Dmitry Baryshkov (2022-03-23 03:35:44)
> Since the commit ab205927592b ("drm/msm/dp: remove mode hard-coding in
> case of DP CTS") the function dp_panel_get_modes() doesn't use (or fill)
> the dp_mode argument. Drop it completely.
>
> Signed-off-by: Dmitry Baryshkov
> ---
Reviewed-by: Ste
m.
collie crash log and bisect log attached.
Guenter
---
8<--- cut here ---
Unable to handle kernel paging request at virtual address e090d000
[e090d000] *pgd=c0c0b811c0c0b811, *pte=c0c0b000, *ppte=
Internal error: Oops: 807 [#1] ARM
CPU: 0 PID: 1 Comm: swapper Not tainted 5.17.0-next-20220
On Wed, Mar 23, 2022 at 4:01 AM Liu Zixian wrote:
> diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c
> b/drivers/gpu/drm/virtio/virtgpu_display.c
> index 5b00310ac..f73352e7b 100644
> --- a/drivers/gpu/drm/virtio/virtgpu_display.c
> +++ b/drivers/gpu/drm/virtio/virtgpu_display.c
> @@ -179,6
Internal error: Oops: 807 [#1] ARM
CPU: 0 PID: 1 Comm: swapper Not tainted 5.17.0-next-20220324 #1
Hardware name: Sharp-Collie
PC is at cfb_imageblit+0x58c/0x6e0
Guenter
On 3/23/22 11:51, Maxime Ripard wrote:
> Hi,
>
> On Tue, Mar 22, 2022 at 10:05:56PM +0300, Dmitry Osipenko wrote:
>> On 2/25/22 17:35, Maxime Ripard wrote:
>>> When we change a clock minimum or maximum using clk_set_rate_range(),
>>> clk_set_min_rate() or clk_set_max_rate(), the current code will
Hi Doug,
On Thu, Mar 24, 2022 at 11:27:46AM -0700, Doug Anderson wrote:
> Hi,
>
> On Thu, Mar 24, 2022 at 11:14 AM Matthias Kaehlcke wrote:
> >
> > Add support for the AUO B133UAN01 13.3" WUXGA panel.
> >
> > Signed-off-by: Matthias Kaehlcke
> > ---
> > output of edid-decode:
> >
> > Block 0,
ror: Oops: 807 [#1] ARM
CPU: 0 PID: 1 Comm: swapper Not tainted 5.17.0-next-20220324 #1
Hardware name: Sharp-Collie
PC is at cfb_imageblit+0x58c/0x6e0
LR is at 0x5
pc : []lr : [<0005>]psr: a153
sp : e0809958 ip : e090d000 fp : e08099f4
r10: e08099c8 r9 : c0c70600 r8 : ff
Quoting Maxime Ripard (2022-03-23 01:51:40)
> Hi,
>
>
> The whole point of this patch is to give an opportunity to every driver
> to change the rate whenever the boundaries have changed, so we very much
> want to have the option to change it if clk_set_rate() has never been
> called.
>
> However
On Thu, 24 Mar 2022, Tvrtko Ursulin wrote:
> On 24/03/2022 11:57, Jani Nikula wrote:
>> On Thu, 24 Mar 2022, Tvrtko Ursulin wrote:
>>> On 24/03/2022 09:31, Jani Nikula wrote:
On Tue, 22 Mar 2022, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> ...
>
> Signed-off-by: Tv
Hi,
On Thu, Mar 24, 2022 at 11:14 AM Matthias Kaehlcke wrote:
>
> Add support for the AUO B133UAN01 13.3" WUXGA panel.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> output of edid-decode:
>
> Block 0, Base EDID:
> EDID Structure Version & Revision: 1.4
> Vendor & Product Identification:
Add support for the AUO B133UAN01 13.3" WUXGA panel.
Signed-off-by: Matthias Kaehlcke
---
output of edid-decode:
Block 0, Base EDID:
EDID Structure Version & Revision: 1.4
Vendor & Product Identification:
Manufacturer: AUO
Model: 34196
Made in: 2020
Basic Display
Add binding for the AUO B133UAN01 panel. It is 13.3" TFT LCD panel
with WUXGA (1920x1200) resolution.
Signed-off-by: Matthias Kaehlcke
---
.../devicetree/bindings/display/panel/panel-simple.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/disp
On 3/24/2022 1:36 AM, xkernel.w...@foxmail.com wrote:
From: Xiaoke Wang
kzalloc() is a memory allocation function which can return NULL when
some internal memory errors happen. So it is better to check it to
prevent potential wrong memory access.
Signed-off-by: Xiaoke Wang
Reviewed-by: Ab
On 3/24/2022 2:15 AM, xkernel.w...@foxmail.com wrote:
From: Xiaoke Wang
kzalloc() is a memory allocation function which can return NULL when
some internal memory errors happen. So it is better to check it to
prevent potential wrong memory access.
Signed-off-by: Xiaoke Wang
Reviewed-by: Ab
On Thu, Mar 24, 2022 at 03:25:08PM +0100, Christian König wrote:
> Am 23.03.22 um 11:35 schrieb Daniel Vetter:
> > On Mon, Mar 21, 2022 at 02:25:56PM +0100, Christian König wrote:
> > > [SNIP]
> > > EXPORT_SYMBOL(ttm_resource_init);
> > > @@ -66,15 +172,21 @@ EXPORT_SYMBOL(ttm_resource_init);
> >
On Wed, Mar 23, 2022 at 02:34:35PM -0400, Lyude Paul wrote:
> On Wed, 2022-03-23 at 11:25 +0100, Daniel Vetter wrote:
> > On Tue, Mar 22, 2022 at 05:37:40PM -0400, Lyude Paul wrote:
> > > OK so - this has become a bit of a larger rabbit hole. I've been putting
> > > quite
> > > a bit of work into t
Move the sanity check that both src and dst are never both system
memory, which should never happen on discrete, and likely means we have
a bug. The only exception is on integrated where we trigger this path in
the selftests.
Signed-off-by: Matthew Auld
Cc: Thomas Hellström
Cc: Nirmoy Das
---
We only need this when allocating device local-memory, where this
influences the drm_buddy. Currently there is some funny behaviour where
an "in limbo" system memory object is lacking the relevant placement
flags etc. before we first allocate the ttm_tt, leading to ttm
performing a move when not ne
On Thu, Mar 24, 2022 at 03:47:24PM +0100, Maxime Ripard wrote:
> The HVS state configuration is useful when debugging what's going on in
> the vc4 hardware pipeline. Add an implementation of .atomic_print_state.
>
> Signed-off-by: Maxime Ripard
On the two vc4 patches:
Acked-by: Daniel Vetter
>
On Thu, Mar 24, 2022 at 03:47:22PM +0100, Maxime Ripard wrote:
> A number of drivers (amdgpu, komeda, vc4, etc.) leverage the
> drm_private_state structure, but we don't have any infrastructure to
> provide debugging like we do for the other components state. Let's add
> an atomic_print_state hook
On Thu, Mar 24, 2022 at 03:47:21PM +0100, Maxime Ripard wrote:
> The DRM_UT_STATE controls whether we're calling
> drm_atomic_print_new_state() whenever a new state is committed. However,
> that call is made in the drm_mode_atomic_ioctl(), whereas we have
> multiple users of the drm_atomic_commit()
Hi Liviu
Thanks for the response.
On 3/24/2022 3:12 AM, Liviu Dudau wrote:
On Wed, Mar 23, 2022 at 11:28:56AM -0700, Abhinav Kumar wrote:
Hi Liviu
Hello,
Thanks for the review.
On 3/23/2022 9:46 AM, Liviu Dudau wrote:
On Mon, Mar 21, 2022 at 04:56:43PM -0700, Abhinav Kumar wrote:
For v
On 3/21/22 23:44, Ramalingam C wrote:
On Xe-HP and later devices, dedicated compression control state (CCS)
stored in local memory is used for each surface, to support the
3D and media compression formats.
The memory required for the CCS of the entire local memory is 1/256 of
the local memory
On 17-02-22, 23:20, Marijn Suijten wrote:
> On 2022-02-10 16:04:16, Vinod Koul wrote:
> > Later gens of hardware have DSC bits moved to hw_ctl, so configure these
> > bits so that DSC would work there as well
> >
> > Reviewed-by: Dmitry Baryshkov
> > Signed-off-by: Vinod Koul
> > ---
> > driver
On 3/21/22 23:44, Ramalingam C wrote:
Handle the src and dst chunk offsets for different instances of the copy
engines.
Signed-off-by: Ramalingam C
---
drivers/gpu/drm/i915/gt/intel_migrate.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_migrate.c
b/
On Tue, Feb 01, 2022 at 04:11:30PM +0530, Ramalingam C wrote:
> From: Anshuman Gupta
>
> DG2 onwards discrete gfx has support for new flat CCS mapping,
> which brings in display feature in to avoid Aux walk for compressed
> surface. This support build on top of Flat CCS support added in XEHPSDV.
Hi, Ram
On 3/21/22 23:44, Ramalingam C wrote:
Xe-HP and latest devices support Flat CCS which reserved a portion of
the device memory to store compression metadata, during the clearing of
device memory buffer object we also need to clear the associated
CCS buffer.
XY_CTRL_SURF_COPY_BLT is a BLT
On 21-02-22, 05:11, Dmitry Baryshkov wrote:
> On 10/02/2022 13:34, Vinod Koul wrote:
> > When DSC is enabled, we need to configure DSI registers accordingly and
> > configure the respective stream compression registers.
> >
> > Add support to calculate the register setting based on DSC params and
On 23-03-22, 20:10, Vinod Koul wrote:
> On 17-02-22, 23:32, Marijn Suijten wrote:
> > On 2022-02-10 16:04:17, Vinod Koul wrote:
> > > +
> > > + slice_count = dsc->drm->slice_count;
> > > + slice_per_intf = DIV_ROUND_UP(width, dsc->drm->slice_width);
> > > +
> > > + /*
> > > + * If slice_count is
On Mi, 2022-03-23 at 17:08 +0100, Lucas Stach wrote:
The flush sequence is a marker that the page tables have been changed
and any affected TLBs need to be flushed. Move the flush_seq increment
a little further down the call stack to place it next to the actual
page table manipulation. Not function
On Mi, 2022-03-23 at 17:08 +0100, Lucas Stach wrote:
> This makes it a little more clear that the mapping holds a reference
> to the context once the buffer has been successfully mapped into that
> context and simplifies the error handling a bit.
>
> Signed-off-by: Lucas Stach
Reviewed-by: Phili
On Mi, 2022-03-23 at 17:08 +0100, Lucas Stach wrote:
> When the mapping is already reaped the unmap must be a no-op, as we
> would otherwise try to remove the mapping twice, corrupting the
> involved
> data structures.
>
> Cc: sta...@vger.kernel.org # 5.4
> Signed-off-by: Lucas Stach
Reviewed-by
On 3/21/22 23:44, Ramalingam C wrote:
Move the static calculations out of the loops for copy and clear.
Signed-off-by: Ramalingam C
Reviewed-by: Thomas Hellström
---
drivers/gpu/drm/i915/gt/intel_migrate.c | 44 -
1 file changed, 21 insertions(+), 23 deletions
On Thu, Mar 24, 2022 at 02:21:09PM +0100, Gerd Hoffmann wrote:
> On Thu, Mar 24, 2022 at 06:34:02PM +0800, liuco...@kylinos.cn wrote:
> >ok, thanks, a lot of our customer use qxl on x86 before, so it still need
> >to supoort qxl on arm64.
>
> Well, qxl isn't the best choice even on x86. T
make dt_binding_check fail on lot of mediatek bindings due to missing
includes.
Signed-off-by: Corentin Labbe
---
2 files remains to be fixed, but their examples use some variable undefined, so
I cannot do anything:
- display/mediatek/mediatek,ethdr.yaml
- display/mediatek/mediatek,merge.yaml
On Thu, Mar 24, 2022 at 08:06:08AM +0100, Jakob Koschel wrote:
> To move the list iterator variable into the list_for_each_entry_*()
> macro in the future it should be avoided to use the list iterator
> variable after the loop body.
>
> To *never* use the list iterator variable after the loop it w
Hi Maxime,
On Thu, Mar 24, 2022 at 03:23:24PM +0100, Maxime Ripard wrote:
> On Thu, Mar 24, 2022 at 03:43:42PM +0200, Laurent Pinchart wrote:
> > On Thu, Mar 24, 2022 at 09:18:19AM +0100, Maxime Ripard wrote:
> > > On Wed, Mar 23, 2022 at 10:38:19PM +0200, Laurent Pinchart wrote:
> > > > Hi Maxime
The HVS state configuration is useful when debugging what's going on in
the vc4 hardware pipeline. Add an implementation of .atomic_print_state.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/vc4/vc4_kms.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/drivers/gpu/drm/v
A number of drivers (amdgpu, komeda, vc4, etc.) leverage the
drm_private_state structure, but we don't have any infrastructure to
provide debugging like we do for the other components state. Let's add
an atomic_print_state hook to be consistent.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/d
None of those helpers modify the pointed data, let's make them const.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/vc4/vc4_kms.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/vc4/vc4_kms.c b/drivers/gpu/drm/vc4/vc4_kms.c
index 24de29bc1cda..26b771
The DRM_UT_STATE controls whether we're calling
drm_atomic_print_new_state() whenever a new state is committed. However,
that call is made in the drm_mode_atomic_ioctl(), whereas we have
multiple users of the drm_atomic_commit() function in the kernel
(framebuffer emulation, drm_atomic_helper_dirty
Hi,
This series adds an atomic_print_state hook for drm_private_obj to ease the
debugging of driver-specific sub-classes, and adds one for vc4.
It also changes the call site of drm_atomic_print_new_state to make it more
consistent.
Let me know what you think,
Maxime
Maxime Ripard (4):
drm/ato
On Thu, Mar 24, 2022 at 01:42:33AM +0200, Chery, Nanley G wrote:
> > -Original Message-
> > From: Deak, Imre
> > Sent: Monday, March 21, 2022 6:20 AM
> > To: Chery, Nanley G ; Juha-Pekka Heikkila
> >
> > Cc: Nanley Chery ; C, Ramalingam
> > ; intel-gfx ;
> > Auld, Matthew ; dri-devel
>
Am 23.03.22 um 11:35 schrieb Daniel Vetter:
On Mon, Mar 21, 2022 at 02:25:56PM +0100, Christian König wrote:
[SNIP]
EXPORT_SYMBOL(ttm_resource_init);
@@ -66,15 +172,21 @@ EXPORT_SYMBOL(ttm_resource_init);
* @res: the resource to clean up
*
* Should be used by resource manager backends
On Thu, Mar 24, 2022 at 03:43:42PM +0200, Laurent Pinchart wrote:
> On Thu, Mar 24, 2022 at 09:18:19AM +0100, Maxime Ripard wrote:
> > On Wed, Mar 23, 2022 at 10:38:19PM +0200, Laurent Pinchart wrote:
> > > Hi Maxime,
> > >
> > > (CC'ing Sakari)
> > >
> > > Thank you for the patch.
> > >
> > > O
On Thu, Mar 24, 2022 at 01:40:37AM +0200, Chery, Nanley G wrote:
> > [...]
> > Capturing all the above would you be ok with the following?:
> >
> > Intel color control surfaces (CCS) for DG2 render compression.
> >
> > The main surface is Tile 4 and at plane index 0. The CCS data is stored
> > ou
On 24/03/2022 12:55, Dmitry Baryshkov wrote:
> Make dpu-qcm2290 example really follow the defined schema:
> - Drop qcom,mdss compatible. It's only used for MDP5 devices.
> - Change display controller name to display-controller as specified in
> the yaml
>
> Reported-by: Rob Herring
> Cc: Loic P
On Thu, Mar 24, 2022 at 03:32:01PM +0800, Sui Jingfeng wrote:
>
> On 2022/3/23 04:49, Rob Herring wrote:
> > > + }
> > > +
> > > + spin_lock_init(&li2c->reglock);
> > > +
> > > + snprintf(compat, sizeof(compat), "lsdc,i2c-gpio-%d", index);
> > compatible values shouldn't have an index and you shou
Hi Maxime,
On Thu, Mar 24, 2022 at 09:18:19AM +0100, Maxime Ripard wrote:
> On Wed, Mar 23, 2022 at 10:38:19PM +0200, Laurent Pinchart wrote:
> > Hi Maxime,
> >
> > (CC'ing Sakari)
> >
> > Thank you for the patch.
> >
> > On Wed, Mar 23, 2022 at 04:48:23PM +0100, Maxime Ripard wrote:
> > > MIPI
On Thu, Mar 24, 2022 at 09:39:49AM +0800, Sui Jingfeng wrote:
>
> On 2022/3/23 04:49, Rob Herring wrote:
> > On Tue, Mar 22, 2022 at 12:29:16AM +0800, Sui Jingfeng wrote:
> > > From: suijingfeng
> > >
> > > There is a display controller in loongson's LS2K1000 SoC and LS7A1000
> > > bridge chip,
On 24/03/2022 11:57, Jani Nikula wrote:
On Thu, 24 Mar 2022, Tvrtko Ursulin wrote:
On 24/03/2022 09:31, Jani Nikula wrote:
On Tue, 22 Mar 2022, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
...
Signed-off-by: Tvrtko Ursulin
Cc: Jani Nikula
Cc: Lucas De Marchi
---
Typed up how I see it -
On Thu, Mar 24, 2022 at 10:16 AM Haowen Bai wrote:
>
> WARNING: Statements should start on a tabstop
>
> WARNING: Missing a blank line after declarations
>
> Signed-off-by: Haowen Bai
Hi, thanks for the patch.
> ---
> drivers/gpu/drm/gma500/mid_bios.c | 5 +++--
> 1 file changed, 3 insertions(
On Thu, Mar 24, 2022 at 09:48:19AM +0800, Sui Jingfeng wrote:
>
> On 2022/3/23 21:03, Rob Herring wrote:
> > On Wed, Mar 23, 2022 at 11:38:55AM +0800, Sui Jingfeng wrote:
> > > On 2022/3/23 04:55, Rob Herring wrote:
> > > > On Tue, Mar 22, 2022 at 10:33:45AM +0800, Sui Jingfeng wrote:
> > > > > On
On Thu, Mar 24, 2022 at 06:34:02PM +0800, liuco...@kylinos.cn wrote:
>ok, thanks, a lot of our customer use qxl on x86 before, so it still need
>to supoort qxl on arm64.
Well, qxl isn't the best choice even on x86. The main advantage it
offers (2d acceleration) is basically useless today
The previous pull request tag was botched due to my key expiring, updated!
drm-misc-next-fixes-2022-03-24-1:
drm-misc-next-fixes for v5.18-rc1:
- Make audio and color plane support checking only happen
when a CEA extension block is found.
- Fix a small regression from ttm_resource_fini()
- Small
drm-misc-next-fixes-2022-03-24:
Short summary of fixes pull (less than what git shortlog provides):
- explain anything non-fixes (e.g. cleanups) and why it's appropriate
- highlight regressions
- summarize pull requests contained
This shouldn't be more than a few lines (or it indicates your fixes p
On Thu, Mar 24, 2022 at 03:25:42PM +0800, Zheng Bin wrote:
> If CONFIG_DRM_VC4=y, CONFIG_RASPBERRYPI_FIRMWARE=m, CONFIG_COMPILE_TEST=n,
> bulding fails:
>
> drivers/gpu/drm/vc4/vc4_drv.o: In function `vc4_drm_bind':
> vc4_drv.c:(.text+0x320): undefined reference to `rpi_firmware_get'
> vc4_drv.c:(
On Tue, 22 Feb 2022 17:40:35 +0100, Maxime Ripard wrote:
> This is another attempt at supporting the HDMI YUV output in the vc4 HDMI
> driver.
>
> This is a follow-up of
> https://lore.kernel.org/dri-devel/20210317154352.732095-1-max...@cerno.tech/
>
> And the discussions that occured recently on
> > > > The driver uses DRM_DEV_* for logs. Can we use this?
> > > Hi Hsin-Yi, as comment in drm/drm_print.h:
> > > "NOTE: this is deprecated in favor of drm_dbg". DRM bridge driver not
> > > use DRM_DEV_* any more. I'll send a patch to replace all of DRM_DEV_*
> > > later.
> >
> > drm_dbg is bette
On Thu, 24 Mar 2022, Tvrtko Ursulin wrote:
> On 24/03/2022 09:31, Jani Nikula wrote:
>> On Tue, 22 Mar 2022, Tvrtko Ursulin wrote:
>>> From: Tvrtko Ursulin
>>>
>>> ...
>>>
>>> Signed-off-by: Tvrtko Ursulin
>>> Cc: Jani Nikula
>>> Cc: Lucas De Marchi
>>> ---
>>> Typed up how I see it - bash aw
Make dpu-qcm2290 example really follow the defined schema:
- Drop qcom,mdss compatible. It's only used for MDP5 devices.
- Change display controller name to display-controller as specified in
the yaml
Reported-by: Rob Herring
Cc: Loic Poulain
Fixes: 164f69d9d45a ("dt-bindings: msm: disp: add y
Added r-b & applied to drm-misc-next.
On 24/03/2022 09:31, Jani Nikula wrote:
On Tue, 22 Mar 2022, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
...
Signed-off-by: Tvrtko Ursulin
Cc: Jani Nikula
Cc: Lucas De Marchi
---
Typed up how I see it - bash away.
So is intel_vtd_active() so performance critical that it needs to be
inl
From: Xiaoke Wang
kzalloc() is a memory allocation function which can return NULL when
some internal memory errors happen. So it is better to check it.
Besides, to properly handle the error, another check is added for the
return of omap_irq_wait_init().
Signed-off-by: Xiaoke Wang
---
drivers/g
From: Thierry Reding
Buffer mappings used in job submissions are usually small and not
rapidly reused as opposed to framebuffers (which are usually large and
rapidly reused, for example when page-flipping between double-buffered
framebuffers). Avoid going through the mapping cache for these buffe
On Wed, 23 Mar 2022 at 16:32, Christian König wrote:
>
> Am 23.03.22 um 16:24 schrieb Daniel Stone:
> > On Wed, 23 Mar 2022 at 15:14, Alex Deucher wrote:
> >> On Wed, Mar 23, 2022 at 11:04 AM Daniel Stone wrote:
> >>> That's not what anyone's saying here ...
> >>>
> >>> No-one's demanding AMD pu
On Tue, Feb 22, 2022 at 05:40:35PM +0100, Maxime Ripard wrote:
> Hi,
>
> This is another attempt at supporting the HDMI YUV output in the vc4 HDMI
> driver.
>
> This is a follow-up of
> https://lore.kernel.org/dri-devel/20210317154352.732095-1-max...@cerno.tech/
>
> And the discussions that occu
On Thu, Mar 24, 2022 at 10:20:40AM +0100, Christian König wrote:
> Hi Cong,
>
> when I understand Robin correctly all mapping (host, guest, kernel,
> userspace etc..) must have the same caching attributes unless you use the
> S2FWB feature introduced with Armv8.4.
>
> If you don't follow those ru
On Wed, Mar 23, 2022 at 11:28:56AM -0700, Abhinav Kumar wrote:
> Hi Liviu
Hello,
>
> Thanks for the review.
>
> On 3/23/2022 9:46 AM, Liviu Dudau wrote:
> > On Mon, Mar 21, 2022 at 04:56:43PM -0700, Abhinav Kumar wrote:
> > > For vendors drivers which pass an already allocated and
> > > initial
On Wed, 23 Mar 2022, Ville Syrjälä wrote:
> On Wed, Mar 23, 2022 at 12:04:38PM +0200, Jani Nikula wrote:
>> Only an EDID CEA extension has byte #3, while the CTA DisplayID Data
>> Block does not. Don't interpret bogus data for color formats.
>
> I think what we might want eventually is a cleaner s
On Thu, 24 Mar 2022, Lee Shawn C wrote:
> From: Cooper Chiou
>
> Tag code stored in bit7:5 for CTA block byte[3] is not the same as
> CEA extension block definition. Only check CEA block has
> basic audio support.
>
> v3: update commit message.
>
> Cc: sta...@vger.kernel.org
> Cc: Jani Nikula
>
Reviewed-by: Nirmoy Das
On 3/24/2022 1:04 AM, Daniele Ceraolo Spurio wrote:
On error the "new" allocation is not freed, so add the required kfree.
Fixes: 247f8071d5893 ("drm/i915/guc: Pre-allocate output nodes for extraction")
Signed-off-by: Daniele Ceraolo Spurio
Cc: Alan Previn
Cc: John Ha
On Thu, 24 Mar 2022, Jani Nikula wrote:
> On Tue, 22 Mar 2022, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin
>>
>> ...
>>
>> Signed-off-by: Tvrtko Ursulin
>> Cc: Jani Nikula
>> Cc: Lucas De Marchi
>> ---
>> Typed up how I see it - bash away.
>
> So is intel_vtd_active() so performance critica
1 - 100 of 113 matches
Mail list logo
