Hi Sam,
On 20/08/2019 13:37, Sam Ravnborg wrote:
@@ -123,6 +123,18 @@ static void panel_bridge_post_disable(struct drm_bridge
*bridge)
drm_panel_unprepare(panel_bridge->panel);
}
+static int panel_bridge_get_modes(struct drm_bridge *bridge,
+
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.0
head: e971bfc1faa0fa4df97ecca7a867a194455f26fd
commit: 13a2da823a67d53982d85b4d28a9a2532fede843 [3808/3821] drm/amd/autoconf:
check drm_mode_is_420_xxx() is available
config: i386-randconfig-b004-201939 (attached as
Hi,
On Tue, Oct 1, 2019 at 1:34 PM Icenowy Zheng wrote:
>
> According to the BSP source code, when calculating the magic DRQ value
> outside burst mode, a formula of "lcd_ht - lcd_x - lcd_hbp", which is
> interpreted as right margin (HFP value). However, currently the
> sun6i_mipi_dsi driver
Hi Wens,
On Tue, Oct 1, 2019 at 1:34 PM Icenowy Zheng wrote:
>
> This reverts commit 62e7511a4f4dcf07f753893d3424decd9466c98b.
>
> This commit, although claimed as a refactor, in fact changed the
> formula.
>
> By expanding the original formula, we can find that the const 10 is not
>
From: Daniel Kurtz
When setting a new display mode, dw_hdmi_setup() calls
dw_hdmi_enable_video_path(), which disables all hdmi clocks, including
the audio clock.
We should only (re-)enable the audio clock if audio was already enabled
when setting the new mode.
Without this patch, on RK3288,
https://bugs.freedesktop.org/show_bug.cgi?id=111415
Tom Seewald changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
From: Daniel Kurtz
When setting a new display mode, dw_hdmi_setup() calls
dw_hdmi_enable_video_path(), which disables all hdmi clocks, including
the audio clock.
We should only (re-)enable the audio clock if audio was already enabled
when setting the new mode.
Without this patch, on RK3288,
在 2019-10-02三的 12:36 +0200，Maxime Ripard写道：
> Hi,
>
> On Tue, Oct 01, 2019 at 04:02:50PM +0800, Icenowy Zheng wrote:
> > This patchset fixes some portion of timing calculation in
> > sun6i_mipi_dsi
> > driver according to the BSP driver.
> >
> > Two of the patches are reverting, one is fixing
On 2019/10/03 5:59, Willem de Bruijn wrote:
On Wed, Oct 2, 2019 at 3:56 PM syzbot
wrote:
Hello,
syzbot found the following crash on:
HEAD commit:a32db7e1 Add linux-next specific files for 20191002
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x
From: "Paul E. McKenney"
This commit replaces the use of rcu_swap_protected() with the more
intuitively appealing rcu_replace() as a step towards removing
rcu_swap_protected().
Link:
https://lore.kernel.org/lkml/CAHk-=wiAsJLw1egFEE=z7-ggtm6wcvtyytxza1+bhqta4gg...@mail.gmail.com/
Reported-by:
On Wed, Oct 2, 2019 at 1:49 AM Gerd Hoffmann wrote:
>
> On Tue, Oct 01, 2019 at 06:49:35PM -0700, Gurchetan Singh wrote:
> > This doesn't really break userspace, since it always passes down
> > 0 for stride/layer_stride currently. We could:
> >
> > (1) modify UAPI now and add a
Quoting Joonas Lahtinen (2019-10-03 00:28:43)
> + Chris and Tvrtko
It's a trivial warning, that's already fixed. In this case by separating
out the poweroff into process context.
c7302f204490 ("drm/i915: Defer final intel_wakeref_put to process context")
-Chris
+ Chris and Tvrtko
Quoting Andrew Morton (2019-10-03 00:57:21)
>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 01 Oct 2019 17:06:35 + bugzilla-dae...@bugzilla.kernel.org wrote:
>
> >
https://bugzilla.kernel.org/show_bug.cgi?id=205069
freddyrei...@comcast.net changed:
What|Removed |Added
Status|NEW |RESOLVED
On Wed, Oct 2, 2019 at 3:10 PM kbuild test robot wrote:
>
> Hi John,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on linus/master]
> [cannot apply to v5.4-rc1 next-20191002]
> [if your patch is applied to the wrong git tree, please drop us
Hi John,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.4-rc1 next-20191002]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify
Hi John,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.4-rc1 next-20191002]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 01 Oct 2019 17:06:35 + bugzilla-dae...@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=205065
>
> Bug ID: 205065
>Summary: workqueue:
tree: git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
head: cf82d9ddd3b5203dea5561dfabd1216b8159af37
commit: cf82d9ddd3b5203dea5561dfabd1216b8159af37 [4/4] drm/i915/tgl: Introduce
gen12 forcewake ranges
reproduce:
# apt-get install sparse
# sparse version:
On Wed, Oct 2, 2019 at 5:19 PM Nick Desaulniers wrote:
>
> On Wed, Oct 2, 2019 at 5:03 AM Arnd Bergmann wrote:
> >
> > Just like all the other variants, this one passes invalid
> > compile-time options with clang after the new code got
> > merged:
> >
> > clang: error: unknown argument:
On Wed, Oct 2, 2019 at 3:56 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:a32db7e1 Add linux-next specific files for 20191002
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=175ab7cd60
Hi Dave, Daniel,
Fixes for 5.4. Nothing too major. Enabling bulk moves is not exactly
a bug fix, but it's been working well for a while and it improves
performance and reduces latency in command submission. If you have
concerns, I can respin without it.
The following changes since commit
Hi Dave, Daniel,
I hope that you enjoy XDC if you could make it this year :)
Here's the first round of fixes for drm-misc
Maxime
drm-misc-fixes-2019-10-02:
- One include fix for tilcdc
- A memory leak fix for Komeda
- Some fixes for resources cleanups with writeback
The following changes
Hello,
syzbot found the following crash on:
HEAD commit:a32db7e1 Add linux-next specific files for 20191002
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=175ab7cd60
kernel config: https://syzkaller.appspot.com/x/.config?x=599cf05035799eef
On Wed, Oct 2, 2019 at 9:45 AM Ville Syrjälä
wrote:
>
> On Tue, Oct 01, 2019 at 02:20:55PM -0700, Jeykumar Sankaran wrote:
> > On 2019-09-30 03:39, Ville Syrjälä wrote:
> > > On Fri, Sep 27, 2019 at 06:28:51PM -0700, Jeykumar Sankaran wrote:
> > >> The mode_config max width/height values
Hi Jean,
On 10/2/19 3:58 PM, Jean-Jacques Hiblot wrote:
> Hi Jacek,
>
> On 24/09/2019 23:03, Jacek Anaszewski wrote:
>> Hi Jean,
>>
>> Thank you for rebasing the set
>>
>> On 9/18/19 4:57 PM, Jean-Jacques Hiblot wrote:
>>> If initialization data is available and its fwnode is actually a
>>>
The DDC/CI protocol involves sending a multi-byte request to the
display via I2C, which is typically followed by a multi-byte
response. The internal I2C controller only allows single byte
reads/writes or reads of 8 sequential bytes, hence DDC/CI is not
supported when the internal I2C controller is
On Wed, Oct 2, 2019 at 8:47 PM Alex Deucher wrote:
>
> On Wed, Oct 2, 2019 at 8:02 AM Arnd Bergmann wrote:
> >
> > Here are a couple of build fixes from my backlog in the randconfig
> > tree. It would be good to get them all into linux-5.4.
> >
> > Arnd
> >
> > Arnd Bergmann (6):
> >
On Wed, Oct 2, 2019 at 8:02 AM Arnd Bergmann wrote:
>
> Here are a couple of build fixes from my backlog in the randconfig
> tree. It would be good to get them all into linux-5.4.
>
> Arnd
>
> Arnd Bergmann (6):
> drm/amdgpu: make pmu support optional, again
> drm/amdgpu: hide another
https://bugs.freedesktop.org/show_bug.cgi?id=110963
Jeremy Newton changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |jeremy.new...@amd.com
Hi Oleg,
Thanks for your patch, I'll apply it soon.
Tested-by: Rodrigo Siqueira
Reviewed-by: Rodrigo Siqueira
On 09/30, Oleg Vasilev wrote:
> Bring dmabuf sharing through implementing prime_import_sg_table callback.
> This will help to validate userspace conformance in prime configurations
>
Hi Andrzej
Always good to have clear documentation.
On Wed, Oct 02, 2019 at 05:43:49PM +0200, Andrzej Pietrasiewicz wrote:
> To human readers
>
> "array of struct drm_format modifiers" is almost indistinguishable from
> "array of struct drm_format_modifiers", especially given that
> struct
On 9/26/2019 4:20 AM, Robin Murphy wrote:
> On 2019-09-26 11:44 am, Nicolas Saenz Julienne wrote:
>> Robin, have you looked into supporting multiple dma-ranges? It's the
>> next thing
>> we need for BCM STB's PCIe. I'll have a go at it myself if nothing
>> is in
>> the
This adds a CMA heap, which allows userspace to allocate
a dma-buf of contiguous memory out of a CMA region.
This code is an evolution of the Android ION implementation, so
thanks to its original author and maintainters:
Benjamin Gaignard, Laura Abbott, and others!
Cc: Laura Abbott
Cc:
Add very trivial allocation and import test for dma-heaps,
utilizing the vgem driver as a test importer.
A good chunk of this code taken from:
tools/testing/selftests/android/ion/ionmap_test.c
Originally by Laura Abbott
Cc: Benjamin Gaignard
Cc: Sumit Semwal
Cc: Liam Mark
Cc: Pratik
Add generic helper dmabuf ops for dma heaps, so we can reduce
the amount of duplicative code for the exported dmabufs.
This code is an evolution of the Android ION implementation, so
thanks to its original authors and maintainters:
Rebecca Schultz Zavin, Colin Cross, Laura Abbott, and others!
This patch adds system heap to the dma-buf heaps framework.
This allows applications to get a page-allocator backed dma-buf
for non-contiguous memory.
This code is an evolution of the Android ION implementation, so
thanks to its original authors and maintainters:
Rebecca Schultz Zavin, Colin
From: "Andrew F. Davis"
This framework allows a unified userspace interface for dma-buf
exporters, allowing userland to allocate specific types of memory
for use in dma-buf sharing.
Each heap is given its own device node, which a user can allocate
a dma-buf fd from using the DMA_HEAP_IOC_ALLOC.
Here is yet another pass at the dma-buf heaps patchset Andrew
and I have been working on which tries to destage a fair chunk
of ION functionality.
The patchset implements per-heap devices which can be opened
directly and then an ioctl is used to allocate a dmabuf from the
heap.
The interface is
Reviewed-by: Huang Rui
-Original Message-
From: amd-gfx On Behalf Of Christian
König
Sent: Friday, September 27, 2019 8:34 AM
To: amd-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org
Subject: [PATCH 2/2] drm/radeon: finally fix the racy VMA setup
Finally clean up the VMA
Ahh.
Reviewed-by: Huang Rui
-Original Message-
From: amd-gfx On Behalf Of Christian
König
Sent: Wednesday, October 2, 2019 4:38 AM
To: amd-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/ttm: also export ttm_bo_vm_fault
Just a gentle ping on
https://bugs.freedesktop.org/show_bug.cgi?id=110968
Jeremy Newton changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |jeremy.new...@amd.com
https://bugs.freedesktop.org/show_bug.cgi?id=109440
Jeremy Newton changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.freedesktop.org/show_bug.cgi?id=111402
Jeremy Newton changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |jeremy.new...@amd.com
https://bugs.freedesktop.org/show_bug.cgi?id=111402
Jeremy Newton changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #1 from Jeremy
On Wed, Oct 2, 2019 at 9:46 AM Jonathan Corbet wrote:
>
> On Tue, 1 Oct 2019 10:09:46 -0600
> Mat King wrote:
>
> > I have been looking into adding Linux support for electronic privacy
> > screens which is a feature on some new laptops which is built into the
> > display and allows users to turn
https://bugs.freedesktop.org/show_bug.cgi?id=110188
Jeremy Newton changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110926
Jeremy Newton changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110968
Jeremy Newton changed:
What|Removed |Added
Status|REOPENED|ASSIGNED
--- Comment #4 from Jeremy
https://bugs.freedesktop.org/show_bug.cgi?id=91749
Alex Deucher changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
pwm_backlight_probe() re-assigns pb->levels for every brightness
level. This is not needed and was likely not intended, since
neither side of the assignment changes during the loop. Assign
the field only once.
Signed-off-by: Matthias Kaehlcke
---
Changes in v2:
- removed curly braces from for
On 9/30/19 5:17 AM, Neil Armstrong wrote:
> Hi Andrey,
>
> On 27/09/2019 22:55, Grodzovsky, Andrey wrote:
>> Can you please use addr2line or gdb to pinpoint where in
>> drm_sched_increase_karma you hit the NULL ptr ? It looks like the guilty
>> job, but to be sure.
> Did a new run from 5.3:
>
> [
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #64 from Marko Popovic ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #33)
> Created attachment 145323 [details] [review]
> wip patch
>
> You can give a try to the attached kernel patch which hopefully could
> prevent
Convert Samsung PWM (S3C, S5P and Exynos SoCs) bindings to DT schema
format using json-schema.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v2:
1. Add additionalProperties: false.
Changes since v1:
1. Indent example with four spaces (more readable),
2. Fix samsung,pwm-outputs after
Convert generic PWM bindings to DT schema format using json-schema. The
consumer bindings are split to separate file.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v2:
1. Change also pwm-sprd.txt
Changes since v1:
1. Indent example with four spaces (more readable),
2. Change pattern
On Wed, Oct 2, 2019 at 11:39 AM Arnd Bergmann wrote:
>
> On Wed, Oct 2, 2019 at 5:12 PM Alex Deucher wrote:
> > On Wed, Oct 2, 2019 at 10:51 AM Arnd Bergmann wrote:
>
> > >
> > > Nothing should really change with regards to the -msse flag here, only
> > > the stack alignment flag changed. Maybe
On Wed, Oct 02, 2019 at 11:07:37AM +0100, Daniel Thompson wrote:
> On Tue, Oct 01, 2019 at 04:29:24PM -0700, Matthias Kaehlcke wrote:
> > pwm_backlight_probe() re-assigns pb->levels for every brightness
> > level. This is not needed and was likely not intended, since
> > neither side of the
tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-dkms-5.0
head: e971bfc1faa0fa4df97ecca7a867a194455f26fd
commit: ad1afcdf30608bd5148c54893257cc2ef1655c4b [2128/3821] drm/amd/autoconf:
generate config.h for in-tree build
config: x86_64-randconfig-d002-201939 (attached as
On Wed, Oct 02, 2019 at 06:22:23PM +0200, Andrzej Pietrasiewicz wrote:
> Hi Ville,
>
> W dniu 02.10.2019 o 18:18, Ville Syrjälä pisze:
> > On Wed, Oct 02, 2019 at 05:43:49PM +0200, Andrzej Pietrasiewicz wrote:
> >> To human readers
> >>
> >> "array of struct drm_format modifiers" is almost
Hi Ville,
W dniu 02.10.2019 o 18:18, Ville Syrjälä pisze:
On Wed, Oct 02, 2019 at 05:43:49PM +0200, Andrzej Pietrasiewicz wrote:
To human readers
"array of struct drm_format modifiers" is almost indistinguishable from
"array of struct drm_format_modifiers",
Unless I'm blind those two *are*
On Wed, Oct 02, 2019 at 05:43:49PM +0200, Andrzej Pietrasiewicz wrote:
> To human readers
>
> "array of struct drm_format modifiers" is almost indistinguishable from
> "array of struct drm_format_modifiers",
Unless I'm blind those two *are* indistinguishable :P
> especially given that
> struct
On Mon, Sep 30, 2019 at 1:14 AM Hillf Danton wrote:
> On Fri, 6 Sep 2019 18:47:09 + John Stultz wrote:
> >
> > + cma_pages = cma_alloc(cma_heap->cma, nr_pages, align, false);
> > + if (!cma_pages)
> > + goto free_buf;
> > +
> > + if (PageHighMem(cma_pages)) {
> > +
On Sun, Sep 29, 2019 at 8:27 PM Hillf Danton wrote:
> On Fri, 6 Sep 2019 18:47:08 + John Stultz wrote:
> > +/**
> > + * dma_heap_get_data() - get per-heap driver data
> > + * @heap: DMA-Heap to retrieve private data for
> > + *
> > + * Returns:
> > + * The per-heap data for the heap.
> > +
On Mon, Sep 23, 2019 at 04:52:02PM +0200, Thierry Reding wrote:
> On Mon, Sep 23, 2019 at 04:52:50PM +0300, Jani Nikula wrote:
> > On Fri, 20 Sep 2019, Thierry Reding wrote:
> > > On Mon, Sep 02, 2019 at 01:31:00PM +0200, Thierry Reding wrote:
> > >> From: Thierry Reding
> > >>
> > >> Hi,
> >
Convert Samsung Exynos Soc Power Domain bindings to DT schema format using
json-schema.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. Indent example with four spaces (more readable),
2. Remove unneeded types,
3. Add missing address in example and fix the name.
---
Convert Generic Power Domain bindings to DT schema format using
json-schema. The consumer bindings are split to separate file.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. Select all nodes for consumers,
2. Remove from consumers duplicated properties with dt-schema,
3. Fix
The device node name should reflect generic class of a device so rename
power domain nodes to "power-domain". No functional change.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos4.dtsi| 14 +++---
arch/arm/boot/dts/exynos4210.dtsi | 2 +-
On Tue, 1 Oct 2019 10:09:46 -0600
Mat King wrote:
> I have been looking into adding Linux support for electronic privacy
> screens which is a feature on some new laptops which is built into the
> display and allows users to turn it on instead of needing to use a
> physical privacy filter. In
Hi Dave, Daniel,
we had some problems this cycle sending out TTM fixes because of lack of
time to rebase amd-staging-drm-next.
Because of this Alex and I decided that I'm going to send out TTM pull
requests separately now. So this is the first small bunch of fixes for 5.4.
The following
To human readers
"array of struct drm_format modifiers" is almost indistinguishable from
"array of struct drm_format_modifiers", especially given that
struct drm_format_modifier does exist.
And indeed the parameter passes an array of uint64_t rather than an array
of structs, but the first words
On Wed, Oct 2, 2019 at 5:12 PM Alex Deucher wrote:
> On Wed, Oct 2, 2019 at 10:51 AM Arnd Bergmann wrote:
> >
> > Nothing should really change with regards to the -msse flag here, only
> > the stack alignment flag changed. Maybe there was some other change
> > in your Makefile that conflicts
The :doc: reference did not match the DOC comment's name.
Fixes: 5fc537bfd000 ("drm/mcde: Add new driver for ST-Ericsson MCDE")
Signed-off-by: Jonathan Neuschäfer
---
Documentation/gpu/mcde.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gpu/mcde.rst
- Format the pipe diagram as a monospace block.
- Fix formatting of the list. Without the empty line, the first dash is
not parsed as a bullet point.
Signed-off-by: Jonathan Neuschäfer
---
drivers/gpu/drm/mcde/mcde_drv.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff
On Wed, Oct 2, 2019 at 4:46 AM Jani Nikula wrote:
>
> On Wed, 02 Oct 2019, Daniel Thompson wrote:
> > On Wed, Oct 02, 2019 at 12:30:05PM +0300, Jani Nikula wrote:
> >> On Tue, 01 Oct 2019, Mat King wrote:
> >> > Resending in plain text mode
> >> >
> >> > I have been looking into adding Linux
On Wed, Oct 2, 2019 at 10:51 AM Arnd Bergmann wrote:
>
> On Wed, Oct 2, 2019 at 4:17 PM Alex Deucher wrote:
> >
> > I'm getting an error with gcc with this patch:
> > CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_resource.o
> >
On Wed, Oct 2, 2019 at 4:17 PM Alex Deucher wrote:
>
> I'm getting an error with gcc with this patch:
> CC [M] drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_resource.o
> drivers/gpu/drm/amd/amdgpu/../display/dc/dcn21/dcn21_resource.c: In
> function ‘calculate_wm_set_for_vlevel’:
>
Hi Andrey,
On 02/10/2019 16:40, Grodzovsky, Andrey wrote:
>
> On 9/30/19 10:52 AM, Hillf Danton wrote:
>> On Mon, 30 Sep 2019 11:17:45 +0200 Neil Armstrong wrote:
>>> Did a new run from 5.3:
>>>
>>> [ 35.971972] Call trace:
>>> [ 35.974391] drm_sched_increase_karma+0x5c/0xf0
>>>
On Wed, Oct 02, 2019 at 01:46:17PM +0200, Bartosz Golaszewski wrote:
> śr., 2 paź 2019 o 12:33 Daniel Thompson
> napisał(a):
> >
> > On Tue, Oct 01, 2019 at 02:58:37PM +0200, Bartosz Golaszewski wrote:
> > > From: Bartosz Golaszewski
> > >
> > > The probe function in the gpio-backlight driver
On 9/30/19 10:52 AM, Hillf Danton wrote:
> On Mon, 30 Sep 2019 11:17:45 +0200 Neil Armstrong wrote:
>> Did a new run from 5.3:
>>
>> [ 35.971972] Call trace:
>> [ 35.974391] drm_sched_increase_karma+0x5c/0xf0
>> 10667f3810667F94
>>
On Wed, Oct 2, 2019 at 8:03 AM Arnd Bergmann wrote:
>
> Just like all the other variants, this one passes invalid
> compile-time options with clang after the new code got
> merged:
>
> clang: error: unknown argument: '-mpreferred-stack-boundary=4'
> scripts/Makefile.build:265: recipe for target
On Tue, 24 Sep 2019, Jani Nikula wrote:
> drm/print: move drm_debug variable to drm_print.[ch]
> drm/print: add drm_debug_enabled()
> drm/etnaviv: use drm_debug_enabled() to check for debug categories
> drm/i2c/sil164: use drm_debug_enabled() to check for debug categories
> drm/msm: use
This adds initial support for iMX8MQ's Display Controller Subsystem (DCSS).
Some of its capabilities include:
* 4K@60fps;
* HDR10;
* one graphics and 2 video pipelines;
* on-the-fly decompression of compressed video and graphics;
The reference manual can be found here:
Add bindings for iMX8MQ Display Controller Subsystem.
Signed-off-by: Laurentiu Palcu
---
.../bindings/display/imx/nxp,imx8mq-dcss.yaml | 86 ++
1 file changed, 86 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/imx/nxp,imx8mq-dcss.yaml
diff
Currently the drm/imx/ directory is compiled only if DRM_IMX is set. Adding a
new IMX related IP in the same directory would need DRM_IMX to be set, which
would
bring in also IPUv3 core driver...
The current patch would allow adding new IPs in the imx/ directory without
needing
to set DRM_IMX.
Hi,
This patchset adds initial DCSS support for iMX8MQ chip. Initial support
includes only graphics plane support (no video planes), no HDR10 capabilities,
no graphics decompression (only linear, tiled and super-tiled buffers allowed).
Support for the rest of the features will be added
For historical reasons, the function drm_wait_vblank_ioctl always return
-EINVAL if something gets wrong. This scenario limits the flexibility
for the userspace to make detailed verification of any problem and take
some action. In particular, the validation of “if (!dev->irq_enabled)”
in the
Hi Jacek,
On 24/09/2019 23:03, Jacek Anaszewski wrote:
Hi Jean,
Thank you for rebasing the set
On 9/18/19 4:57 PM, Jean-Jacques Hiblot wrote:
If initialization data is available and its fwnode is actually a of_node,
store this information in the led device's structure. This will allow the
On 10/1/19 17:21, Liu, Leo wrote:
OK. So, maybe we can add a comment pointing that out?
>>> That could be better.
>>>
>> Great. I'm glad it's not a bug. I'll write a patch for that so other
>> people don't waste time taking a look.
>
> Thanks, just sent two patches to add comment, and
On Tue, Oct 1, 2019 at 5:00 PM Navid Emamdoost
wrote:
>
> Would you please review this patch?
>
Applied. thanks!
Alex
>
> Thanks,
> Navid.
>
> On Mon, Sep 16, 2019 at 10:21 PM Navid Emamdoost
> wrote:
> >
> > In dcn*_clock_source_create when dcn20_clk_src_construct fails allocated
> >
On Tue, Oct 01, 2019 at 02:20:55PM -0700, Jeykumar Sankaran wrote:
> On 2019-09-30 03:39, Ville Syrjälä wrote:
> > On Fri, Sep 27, 2019 at 06:28:51PM -0700, Jeykumar Sankaran wrote:
> >> The mode_config max width/height values determine the maximum
> >> resolution the pixel reader can handle.
> >
On Mon, Sep 30, 2019 at 3:03 AM yu kuai wrote:
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> rivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c: In function
> ‘amdgpu_gfx_graphics_queue_acquire’:
> drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c:234:16: warning:
> variable ‘pipe’ set but not used
On Mon, Sep 30, 2019 at 4:09 PM Siqueira, Rodrigo
wrote:
>
> The 'debug_data' variable gets printed in debug statements without a
> prior initialization in the function
> hubbub1_verify_allow_pstate_change_high, as reported when building with
> gcc 9.1.0:
>
> warning: ‘debug_data’ may be used
On Wed, Oct 2, 2019 at 3:19 AM Austin Kim wrote:
>
> Even though 'smu8_smu' is declared, it is not used after below statement.
>
>smu8_smu = hwmgr->smu_backend;
>
> So 'unused variable' could be safely removed
> to stop warning message as below:
>
>
On 10/2/19 3:18 PM, Kirill A. Shutemov wrote:
On Wed, Oct 02, 2019 at 11:21:01AM +0200, Thomas Hellström (VMware) wrote:
On 9/26/19 10:16 PM, Linus Torvalds wrote:
On Thu, Sep 26, 2019 at 1:09 PM Thomas Hellström (VMware)
wrote:
That said, if people are OK with me modifying the assert in
https://bugs.freedesktop.org/show_bug.cgi?id=111881
erhar...@mailbox.org changed:
What|Removed |Added
OS|All |Linux (All)
See Also|
https://bugs.freedesktop.org/show_bug.cgi?id=111021
erhar...@mailbox.org changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=111021
erhar...@mailbox.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Wed, Oct 02, 2019 at 11:21:01AM +0200, Thomas Hellström (VMware) wrote:
> On 9/26/19 10:16 PM, Linus Torvalds wrote:
> > On Thu, Sep 26, 2019 at 1:09 PM Thomas Hellström (VMware)
> > wrote:
> > > That said, if people are OK with me modifying the assert in
> > > pud_trans_huge_lock() and make
When logging the AVI InfoFrame, clearly indicate whether or not the
extended colorimetry attribute is active. This is only the case when
the AVI InfoFrame colorimetry attribute is set to extended. [0]
[0] CTA-861-G section 6.4 page 57
Signed-off-by: Johan Korsnes
---
drivers/video/hdmi.c | 8
On Wed, Oct 2, 2019 at 7:25 AM Tomi Valkeinen wrote:
>
> The OMAP36xx and AM/DM37x TRMs say that the maximum divider for DSS fclk
> (in CM_CLKSEL_DSS) is 32. Experimentation shows that this is not
> correct, and using divider of 32 breaks DSS with a flood or underflows
> and sync losts. Dividers
1 - 100 of 150 matches
Mail list logo
