On Mon, 11 Mar 2019 23:21:59 -0300
Helen Koike wrote:
> In the case of async update, modifications are done in place, i.e. in the
> current plane state, so the new_state is prepared and the new_state is
> cleanup up (instead of the old_state, diferrently on what happen in a
^ cleaned up
AH, enlightenment!
Yeah, the whole kernel driver won't work on no-mmu platforms. So
compiling the userspace parts doesn't make any sense either.
Thanks for clearing that up, it wasn't obvious to me why we had this
limitation here.
Regards,
Christian.
Am 11.03.19 um 23:25 schrieb Fabrice
On Mon, 11 Mar 2019, Robert Tarasov wrote:
> Yes, you're right. Will prepare another patch which will use
> drm_do_get_edid()
Oh, you might want to have this patch first with cc: stable and all
that, and do the cleanup afterwards.
BR,
Jani.
>
> On Mon, Mar 11, 2019 at 4:33 AM Jani Nikula
>
https://bugs.freedesktop.org/show_bug.cgi?id=105733
Allan changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109970
Michel Dänzer changed:
What|Removed |Added
Product|DRI |Spam
Version|DRI git
On Mon, 11 Mar 2019 23:22:03 -0300
Helen Koike wrote:
> In the case of a normal sync update, the preparation of framebuffers (be
> it calling drm_atomic_helper_prepare_planes() or doing setups with
> drm_framebuffer_get()) are performed in the new_state and the respective
> cleanups are
Hi,
Am Dienstag, 12. März 2019, 02:54:57 CET schrieb Qiang Yu:
> On Mon, Mar 11, 2019 at 11:37 PM Rob Herring wrote:
> >
> > On Sat, Mar 9, 2019 at 6:21 AM Qiang Yu wrote:
> > >
> > > - Mali 4xx GPUs have two kinds of processors GP and PP. GP is for
> > > OpenGL vertex shader processing and
On Tue, 12 Mar 2019, Al Viro wrote:
> On Mon, Mar 11, 2019 at 08:59:00PM -0700, syzbot wrote:
>> syzbot has bisected this bug to:
>>
>> commit 34e07e42c55aeaa78e93b057a6664e2ecde3fadb
>> Author: Chris Wilson
>> Date: Thu Feb 8 10:54:48 2018 +
>>
>> drm/i915: Add missing kerneldoc for
On Thu, 27 Dec 2018 at 20:28, Andrey Grodzovsky
wrote:
>
> Decauple sched threads stop and start and ring mirror
> list handling from the policy of what to do about the
> guilty jobs.
> When stoppping the sched thread and detaching sched fences
> from non signaled HW fenes wait for all signaled
Hi,
> - if (funcs->atomic_enable)
> - funcs->atomic_enable(crtc, old_crtc_state);
> - else
> - funcs->commit(crtc);
> + if (funcs) {
> + if
On Thu, Feb 21, 2019 at 12:39:24PM +0200, Laurent Pinchart wrote:
> Forgot to CC Rob, sorry about that.
Rob, could you take this in your tree ?
> On Thu, Feb 21, 2019 at 12:32:08PM +0200, Laurent Pinchart wrote:
> > The msm_atomic_state_clear() and msm_atomic_state_free() functions are
> >
Change the api in order to enable callers that can't supply a valid
intel_plane pointer, as would be the case prior to calling
drm_universal_plane_init.
v4:
- Rename variables and move a declaration (Ville)
v6:
- Rebase and fix merge conflict
Cc: Uma Shankar
Cc: Shashank Sharma
Cc: David
64 bpp half float formats are supported on hdr planes only and are subject
to the following restrictions:
* 90/270 rotation not supported
* Yf Tiling not supported
* Frame Buffer Compression not supported
* Color Keying not supported
v2:
- Drop handling pixel normalize register
- Don't
This series defines new formats and adds implementation to the i915 driver.
Since posting v1 I have removed the pixel normalize property, as it's not needed
for basic functionality. Also, I have been working on adding support to
userspace, but we can't land any patches until drm_fourcc.h has been
Hi,
On Tue, Mar 12, 2019 at 11:58:10AM +0100, Daniel Vetter wrote:
> On Mon, Mar 11, 2019 at 11:33:15PM +0100, Noralf Trønnes wrote:
> >
> >
> > Den 11.03.2019 20.23, skrev Daniel Vetter:
> > > On Mon, Mar 11, 2019 at 06:42:16PM +0100, Noralf Trønnes wrote:
[...]
> > >> +}
> > >> +
> > >> +static
Add 64 bpp 16:16:16:16 half float pixel formats. Each 16 bit component is
formatted in IEEE-754 half-precision float (binary16) 1:5:10
MSb-sign:exponent:fraction form.
This patch attempts to address the feedback provided when 2 of these
formats were previosly proposed:
Hi Liviu,
On Fri, Mar 08, 2019 at 03:02:39PM +, Liviu Dudau wrote:
> On Fri, Mar 08, 2019 at 02:46:08PM +0200, Laurent Pinchart wrote:
> > On Thu, Mar 07, 2019 at 04:31:40PM +, Liviu Dudau wrote:
> >> On Thu, Mar 07, 2019 at 03:48:23PM +0200, Laurent Pinchart wrote:
> >>> On Thu, Mar 07,
Current driver sets the tile property only for DP MST connectors.
However there are some tiled displays where each SST connector
carries a single tile. So we need to attach this property object
for every connector and set it for every connector (DP SST and MST).
Plus since the tile information is
Hi,
[[ CCing John for the trylock parts ]]
On Mon, Mar 11, 2019 at 11:33:15PM +0100, Noralf Trønnes wrote:
>
> Den 11.03.2019 20.23, skrev Daniel Vetter:
> > On Mon, Mar 11, 2019 at 06:42:16PM +0100, Noralf Trønnes wrote:
> >> This adds support for outputting kernel messages on panic().
> >> A
The mapping between DRM and V4L2 fourcc's is stored in two separate
tables in rcar_du_vsp.c. In order to make it reusable to implement
writeback support, move it to the rcar_du_format_info structure.
Signed-off-by: Laurent Pinchart
Reviewed-by: Kieran Bingham
---
Implement writeback support for R-Car Gen3 by exposing writeback
connectors. Behind the scene the calls are forwarded to the VSP
backend.
Using writeback connectors will allow implemented writeback support for
R-Car Gen2 with a consistent API if desired.
Signed-off-by: Laurent Pinchart
---
As writeback jobs contain a framebuffer, drivers may need to prepare and
cleanup them the same way they can prepare and cleanup framebuffers for
planes. Add two new optional connector helper operations,
.prepare_writeback_job() and .cleanup_writeback_job() to support this.
The job prepare
The rcar_du_vsp_plane_prepare_fb() and rcar_du_vsp_plane_cleanup_fb()
functions implement the DRM plane .prepare_fb() and .cleanup_fb()
operations. They map and unmap the framebuffer to/from the VSP
internally, which will be useful to implement writeback support. Split
the mapping and unmapping
The rcar_du_crtc structure index field contains the CRTC hardware index,
not the hardware and software index. Update the documentation
accordingly.
Fixes: 5361cc7f8e91 ("drm: rcar-du: Split CRTC handling to support hardware
indexing")
Signed-off-by: Laurent Pinchart
Reviewed-by: Kieran Bingham
From: Noralf Trønnes
This adds a library for shmem backed GEM objects.
v8:
- export drm_gem_shmem_create_with_handle
- call mapping_set_gfp_mask to set default zone to GFP_HIGHUSER
- Add helper drm_gem_shmem_get_pages_sgt()
v7:
- Use write-combine for mmap instead. This is the more common
The VSP-DL instances have two LIFs, and thus two copies of the
VI6_DISP_IRQ_ENB, VI6_DISP_IRQ_STA and VI6_WPF_WRBCK_CTRL registers. Fix
the corresponding macros accordingly.
Signed-off-by: Laurent Pinchart
Reviewed-by: Kieran Bingham
---
drivers/media/platform/vsp1/vsp1_drm.c | 4 ++--
Hello everybody,
This patch series implements display writeback support for the R-Car
Gen3 platforms in the VSP1 and DU drivers.
Patches 01/18 to 11/18 prepare the VSP1 driver for writeback support
with all the necessary plumbing, including extensions of the API between
the VSP1 and DU drivers.
The code that initializes the RPF format-related fields for display
pipelines will also be useful for the WPF to implement writeback
support. Split it from vsp1_du_atomic_update() to a new
vsp1_du_pipeline_set_rwpf_format() function.
Signed-off-by: Laurent Pinchart
---
Display list fragments have been renamed to bodies. Replace one last
occurrence of the word fragment in the documentation.
Signed-off-by: Laurent Pinchart
Reviewed-by: Kieran Bingham
---
drivers/media/platform/vsp1/vsp1_dl.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Add support for the writeback feature of the WPF, to enable capturing
frames at the WPF output for display pipelines. To enable writeback the
vsp1_rwpf structure mem field must be set to the address of the
writeback buffer and the writeback field set to true before the WPF
.configure_stream() and
The drm_writeback_queue_job() function takes ownership of the passed job
and requires the caller to manually set the connector state
writeback_job pointer to NULL. To simplify drivers and avoid errors
(such as the missing NULL set in the vc4 driver), pass the connector
state pointer to the
The WPF needs access to the current display list to configure writeback.
Add a display list pointer to the VSP1 entity .configure_stream()
operation.
Only display pipelines can make use of the display list there as
mem-to-mem pipelines don't have access to a display list at stream
configuration
To prepare for addition of more flags to the display list, replace the
'internal' flag field by a bitmask 'flags' field.
Signed-off-by: Laurent Pinchart
Reviewed-by: Kieran Bingham
---
Changes since v4:
- Fix check for the completed flag in vsp1_du_pipeline_frame_end()
---
The VSP1 driver will need to pass extra flags to the DU through the
frame completion API. Replace the completed bool flag by a bitmask to
support this.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 4 ++--
drivers/media/platform/vsp1/vsp1_drm.c | 4 ++--
When configuring partitions for memory-to-memory pipelines, the WPF
accesses data of the current partition through pipe->partition.
Writeback support will require full configuration of the WPF while not
providing a valid pipe->partition. Rework the configuration code to fall
back to the full image
Writeback jobs are allocated when the WRITEBACK_FB_ID is set, and
deleted when the jobs complete. This results in both a memory leak of
the job and a leak of the framebuffer if the atomic commit returns
before the job is queued for processing, for instance if the atomic
check fails or if the
From: Kieran Bingham
This reverts commit 3299ba5c0b21 ("[media] v4l: vsp1: Supply frames to
the DU continuously")
The DU output mode does not rely on frames being supplied on the WPF as
its pipeline is supplied from DRM. For the upcoming WPF writeback
functionality, we will choose to enable
Extend the vsp1_du_atomic_flush() API with writeback support by adding
format, pitch and memory addresses of the writeback framebuffer.
Writeback completion is reported through the existing frame completion
callback with a new VSP1_DU_STATUS_WRITEBACK status flag.
Signed-off-by: Laurent Pinchart
Refactor the display list header setup to allow chained display lists
with display pipelines. Chain the display lists as for mem-to-mem
pipelines, but enable the frame end interrupt for every list as display
pipelines have a single list per frame.
This feature will be used to disable writeback
https://bugs.freedesktop.org/show_bug.cgi?id=109924
Javier Fernandez changed:
What|Removed |Added
Hardware|Other |x86-64 (AMD64)
On Wed, Mar 13, 2019 at 12:52 AM Boris Brezillon
wrote:
>
> On Tue, 12 Mar 2019 12:34:45 -0300
> Helen Koike wrote:
>
> > On 3/12/19 3:34 AM, Boris Brezillon wrote:
> > > On Mon, 11 Mar 2019 23:21:59 -0300
> > > Helen Koike wrote:
> > >
> > >> In the case of async update, modifications are done
On Tue, Mar 12, 2019 at 10:53:20AM +0100, Daniel Vetter wrote:
> On Mon, Mar 11, 2019 at 11:40:36PM +0100, Noralf Trønnes wrote:
> >
> >
> > Den 11.03.2019 20.29, skrev Daniel Vetter:
> > > On Mon, Mar 11, 2019 at 08:23:38PM +0100, Daniel Vetter wrote:
> > >> On Mon, Mar 11, 2019 at 06:42:16PM
https://bugs.freedesktop.org/show_bug.cgi?id=109975
ramana changed:
What|Removed |Added
URL||http://192.168.1.97/ebank2/
https://bugzilla.kernel.org/show_bug.cgi?id=201957
Cameron (ker...@cameron.bz) changed:
What|Removed |Added
CC||ker...@cameron.bz
---
https://bugs.freedesktop.org/show_bug.cgi?id=109973
Bug ID: 109973
Summary: System hangs/freeze/hiccups
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: FreeBSD
Status: NEW
Severity: critical
https://bugs.freedesktop.org/show_bug.cgi?id=109974
Bug ID: 109974
Summary: libgl will not load radeonsi on X running using DRM
lease
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=109975
Bug ID: 109975
Summary: personal banking button is not working
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: NEW
On 2019-03-11 6:42 p.m., Noralf Trønnes wrote:
> This adds support for outputting kernel messages on panic().
> A kernel message dumper is used to dump the log. The dumper iterates
> over each DRM device and it's crtc's to find suitable framebuffers.
>
> All the other dumpers are run before this
On Tue, Mar 12, 2019 at 10:32:09AM +0100, Boris Brezillon wrote:
> On Mon, 11 Mar 2019 20:51:27 +0100
> Daniel Vetter wrote:
>
> > On Mon, Mar 11, 2019 at 03:20:09PM +0100, Boris Brezillon wrote:
> > > On Mon, 11 Mar 2019 13:15:23 +
> > > "Kazlauskas, Nicholas" wrote:
> > >
> > > > On
https://bugs.freedesktop.org/show_bug.cgi?id=109977
Bug ID: 109977
Summary: Segmentation fault in drmParsePlatformDeviceInfo
Product: DRI
Version: XOrg git
Hardware: All
OS: All
Status: NEW
Severity:
OK, thanks for your input, I'll disable amdgpu on platforms without MMU.
Fabrice
Le lun. 11 mars 2019 à 18:40, Koenig, Christian
a écrit :
>
> Am 11.03.19 um 18:17 schrieb Fabrice Fontaine:
> > OK, then will you accept a patch that disable amdgpu test if fork is
> > not available or a patch
On Mon, Mar 4, 2019 at 4:30 AM Laurent Pinchart
wrote:
>
> Hi Andrey,
>
> Thank you for the patch.
>
> On Tue, Feb 26, 2019 at 11:36:05AM -0800, Andrey Smirnov wrote:
> > Replace explicit polling in tc_link_training() with equivalent call to
> > regmap_read_poll_timeout() for simplicity. No
syzbot has bisected this bug to:
commit 09ef09b4ab95dc405ad4171ec2cd8a4ff5227108
Author: Shayenne Moura
Date: Wed Feb 6 20:08:13 2019 +
drm/vkms: WARN when hrtimer_forward_now fails
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=128448cf20
start commit: 09ef09b4
On Mon, Mar 4, 2019 at 4:20 AM Laurent Pinchart
wrote:
>
> Hello,
>
> On Mon, Mar 04, 2019 at 10:42:20AM +0100, Andrzej Hajda wrote:
> > On 26.02.2019 20:36, Andrey Smirnov wrote:
> > > Drop the use of tc_write() as well as "magicly" used "ret" and "err:"
> > > and replace it with a simple call
On Mon, Mar 11, 2019 at 02:49:41PM +0100, Daniel Vetter wrote:
> On Mon, Mar 11, 2019 at 11:04:19AM +0200, Jani Nikula wrote:
> > On Sun, 10 Mar 2019, "Ahmed S. Darwish" wrote:
> > > Hello DRM/UEFI maintainers,
> > >
> > > Several years ago, I wrote a set of patches to dump the kernel
> > > log
https://bugs.freedesktop.org/show_bug.cgi?id=109974
Michel Dänzer changed:
What|Removed |Added
Attachment #143631|text/x-log |text/plain
mime type|
On Mon, Mar 11, 2019 at 06:01:20PM -0300, Rodrigo Siqueira wrote:
> The function disable_outputs() and
> drm_atomic_helper_commit_modeset_enables() tries to retrieve
> helper_private from the target CRTC, for dereferencing some operations.
> However, the current implementation does not check
https://bugs.freedesktop.org/show_bug.cgi?id=109977
Eric Engestrom changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Mon, 11 Mar 2019 20:51:27 +0100
Daniel Vetter wrote:
> On Mon, Mar 11, 2019 at 03:20:09PM +0100, Boris Brezillon wrote:
> > On Mon, 11 Mar 2019 13:15:23 +
> > "Kazlauskas, Nicholas" wrote:
> >
> > > On 3/11/19 6:06 AM, Boris Brezillon wrote:
> > > > Hello Nicholas,
> > > >
> > > >
On Mon, Mar 4, 2019 at 4:26 AM Laurent Pinchart
wrote:
>
> Hi Andrey,
>
> Thank you for the patch.
>
> On Tue, Feb 26, 2019 at 11:36:03AM -0800, Andrey Smirnov wrote:
> > Simplify tc_set_video_mode() by replacing repreated calls to
> > tc_write()/regmap_write() with a single call
Hi,
Just found out that this was patched and reverted before.(lol)
The revert was 3 months ago for RK3399 boards, but other processors
like RK3066 are left without shutdown now.
What's the status for a fix?
Keep using the old patch for now?
drm/rockchip: shutdown drm subsystem on shutdown
This patch series aims at removing access to the DMC register range from
the meson DRM driver, and is the final step at fully migrating it to using
the meson canvas provider module.
Please see the commit notes of patch 1/2
"dt-bindings: display: amlogic, meson-vpu: exclusively use amlogic,canvas"
The Boe Himax8279d is a 8.0" panel with a 1200x1920 resolution and
connected to DSI using four lanes.
V6:
- Add the information of the reviewer
V5:
- Added changelog
V4:
- None
V3:
- None
V2:
- Add compatible device "boe,himax8279d10p" (Sam)
- Add the necessary property descriptions (Sam)
Yes, you're right. Will prepare another patch which will use
drm_do_get_edid()
On Mon, Mar 11, 2019 at 4:33 AM Jani Nikula
wrote:
> On Fri, 08 Mar 2019, Robert Tarasov wrote:
> > Fixed bug with reading of last EDID extra block in drm/udl driver.
> > Previouse approach read all the blocks
When the DRM driver for the meson platform was created, the bindings
required that the DMC register region was provided.
Through those DMC registers, the display driver could configure an IP
called "canvas", a video lookup table used by the display IP.
It was later discovered that "canvas" is
On Mon, Mar 11, 2019 at 1:28 PM syzbot
wrote:
>
> syzbot has bisected this bug to:
>
> commit 09ef09b4ab95dc405ad4171ec2cd8a4ff5227108
> Author: Shayenne Moura
> Date: Wed Feb 6 20:08:13 2019 +
>
> drm/vkms: WARN when hrtimer_forward_now fails
+Shayenne
This should have been
On Mon, Mar 11, 2019 at 08:59:00PM -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 34e07e42c55aeaa78e93b057a6664e2ecde3fadb
> Author: Chris Wilson
> Date: Thu Feb 8 10:54:48 2018 +
>
> drm/i915: Add missing kerneldoc for 'ent' in i915_driver_init_early
>
>
On Tue, Mar 12, 2019 at 12:24:00AM +, Wentland, Harry wrote:
> To all X.Org Foundation Members:
>
> The election for the X.Org Foundation Board of Directors will begin on
> 14 March 2019. We have 6 candidates who are running for 4 seats. They
> are (in alphabetical order):
> Attached below
Hi,
First of all, thanks for the feedback.
I will fix all the problems pointed out in the review.
I just have two inline questions.
On 03/12, Daniel Vetter wrote:
> On Mon, Mar 11, 2019 at 06:01:20PM -0300, Rodrigo Siqueira wrote:
> > The function disable_outputs() and
> >
On 3/12/19 2:44 AM, Boris Brezillon wrote:
> On Mon, 11 Mar 2019 23:22:03 -0300
> Helen Koike wrote:
>
>> In the case of a normal sync update, the preparation of framebuffers (be
>> it calling drm_atomic_helper_prepare_planes() or doing setups with
>> drm_framebuffer_get()) are performed in the
5.0-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e02f5c1bb2283cfcee68f2f0feddcc06150f13aa ]
The DRM driver stack is designed to work with cache coherent devices
only, but permits an optimization to be enabled in some cases, where
Den 12.03.2019 17.17, skrev Ville Syrjälä:
> On Tue, Mar 12, 2019 at 11:47:04AM +0100, Michel Dänzer wrote:
>> On 2019-03-11 6:42 p.m., Noralf Trønnes wrote:
>>> This adds support for outputting kernel messages on panic().
>>> A kernel message dumper is used to dump the log. The dumper iterates
4.9-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e02f5c1bb2283cfcee68f2f0feddcc06150f13aa ]
The DRM driver stack is designed to work with cache coherent devices
only, but permits an optimization to be enabled in some cases, where
Andrey Grodzovsky writes:
> Also stop calling drm_sched_increase_karma multiple times.
Each v3d->queue[q].sched was initialized with a separate
drm_sched_init(). I wouldn't have thought they were all the "same
sched".
signature.asc
Description: PGP signature
Rob Herring writes:
> On Fri, Mar 8, 2019 at 10:17 AM Eric Anholt wrote:
>>
>> Now that we have the reservation object in the GEM object, it's easy
>> to provide a helper for this common case. Noticed while reviewing
>> panfrost and lima drivers. This particular version came out of v3d,
>>
Den 12.03.2019 18.37, skrev Noralf Trønnes:
>
>
> Den 12.03.2019 18.25, skrev Ville Syrjälä:
>> On Tue, Mar 12, 2019 at 06:15:24PM +0100, Noralf Trønnes wrote:
>>>
>>>
>>> Den 12.03.2019 17.17, skrev Ville Syrjälä:
On Tue, Mar 12, 2019 at 11:47:04AM +0100, Michel Dänzer wrote:
> On
Maxime Ripard writes:
> Hi!
>
> On Mon, Mar 11, 2019 at 01:47:13PM +, Mans Rullgard wrote:
>> Sometimes it is desirabled to use a separate i2c controller for ddc
>> access. This adds support for the ddc-i2c-bus property of the
>> hdmi-connector node, using the specified controller if
Hi Ezequiel,
On Mon, Mar 11, 2019 at 1:02 AM, Ezequiel Garcia
wrote:
On Thu, 2019-02-28 at 19:07 -0300, Paul Cercueil wrote:
Hi,
This is a first attempt at a KMS driver for the JZ47xx MIPS SoCs by
Ingenic. It is aimed to replace the aging jz4740-fb driver.
The driver will later be
On Mon, Mar 4, 2019 at 4:33 AM Laurent Pinchart
wrote:
>
> Hi Andrey,
>
> Thank you for the patch.
>
> On Tue, Feb 26, 2019 at 11:36:06AM -0800, Andrey Smirnov wrote:
> > Tc_poll_timeout() can only return -ETIMEDOUT, so checking for other
> > errors is not necessary. Drop it. No functional change
syzbot has bisected this bug to:
commit 34e07e42c55aeaa78e93b057a6664e2ecde3fadb
Author: Chris Wilson
Date: Thu Feb 8 10:54:48 2018 +
drm/i915: Add missing kerneldoc for 'ent' in i915_driver_init_early
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1322028320
start
Hi Dan,
Thanks a lot for your feedback, this is my first patch for the linux kernel
so I'm learning a lot from your comments.
I'll try to make a more clear version of the patch following your
suggestions
to resubmit.
Best,
Dante Paz
El lun., 11 mar. 2019 a las 5:18, Dan Carpenter ()
escribió:
On Fri, Mar 08, 2019 at 06:35:36PM +0800, Tom Li wrote:
> On Fri, Mar 08, 2019 at 10:13:58AM +0100, Geert Uytterhoeven wrote:
> > On Thu, Mar 7, 2019 at 10:38 PM Tom Li wrote:
> > > Nevertheless, does it mean there's no way to prevent it from happening if
> > > the
> > > user issues a emergency
Support Boe Himax8279d 8.0" 1200x1920 TFT LCD panel, it is a MIPI DSI
panel.
V6:
- Add the information of the reviewer (Sam)
- Delete unnecessary header files #include (Sam)
- The config DRM_PANEL_BOE_HIMAX8279D appears twice. Drop one of them (Sam)
- ADD static, set_gpios function is not used
Hello Sam, thank you very much for your comments,
As I told Dan (my email did not reach the mailing list) this is my
first attempt to contribute,
So I'm learning a lot from your advice and corrections.
I will look for TODO lists to see if there are more useful
contributions to make, all
Sometimes it is desirabled to use a separate i2c controller for ddc
access. This adds support for the ddc-i2c-bus property of the
hdmi-connector node, using the specified controller if provided.
Signed-off-by: Mans Rullgard
---
drivers/gpu/drm/sun4i/sun4i_hdmi.h | 1 +
> You might want to re-use the exisiting modifier
> AFBC_FORMAT_MOD_BLOCK_SIZE_16x16.
>
> I would suggest you to have a look at the exisiting AFBC modifiers
> (denoted by AFBC_FORMAT_MOD_XXX ) and let us know if there is
> something you cannot reuse.
So, the "tiled" format in question (that
Now that the DMC register range is no longer in the bindings, remove any
mention towards it and exclusively use the meson-canvas module.
Signed-off-by: Maxime Jourdan
---
drivers/gpu/drm/meson/Makefile| 2 +-
drivers/gpu/drm/meson/meson_canvas.c | 73 ---
On Mon, 11 Mar 2019, "Ahmed S. Darwish" wrote:
> Hello Jani,
>
> On Mon, Mar 11, 2019 at 11:04:19AM +0200, Jani Nikula wrote:
>> On Sun, 10 Mar 2019, "Ahmed S. Darwish" wrote:
>> Please first better define what you want to achieve.
>>
>
> Oh I thought this was clear..
>
> What I want to achieve
On Mon, Mar 11, 2019 at 11:33:15PM +0100, Noralf Trønnes wrote:
>
>
> Den 11.03.2019 20.23, skrev Daniel Vetter:
> > On Mon, Mar 11, 2019 at 06:42:16PM +0100, Noralf Trønnes wrote:
> >> This adds support for outputting kernel messages on panic().
> >> A kernel message dumper is used to dump the
Also stop calling drm_sched_increase_karma multiple times.
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/v3d/v3d_sched.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/v3d/v3d_sched.c b/drivers/gpu/drm/v3d/v3d_sched.c
index
4.19-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e02f5c1bb2283cfcee68f2f0feddcc06150f13aa ]
The DRM driver stack is designed to work with cache coherent devices
only, but permits an optimization to be enabled in some cases, where
On Tue, Mar 12, 2019 at 06:15:24PM +0100, Noralf Trønnes wrote:
>
>
> Den 12.03.2019 17.17, skrev Ville Syrjälä:
> > On Tue, Mar 12, 2019 at 11:47:04AM +0100, Michel Dänzer wrote:
> >> On 2019-03-11 6:42 p.m., Noralf Trønnes wrote:
> >>> This adds support for outputting kernel messages on
Den 12.03.2019 18.25, skrev Ville Syrjälä:
> On Tue, Mar 12, 2019 at 06:15:24PM +0100, Noralf Trønnes wrote:
>>
>>
>> Den 12.03.2019 17.17, skrev Ville Syrjälä:
>>> On Tue, Mar 12, 2019 at 11:47:04AM +0100, Michel Dänzer wrote:
On 2019-03-11 6:42 p.m., Noralf Trønnes wrote:
> This adds
They are not the same, but the guilty job belongs to only one {entity,
scheduler} pair and so we mark as guilty only for that particular entity in the
context of that scheduler only once.
Andrey
From: Eric Anholt
Sent: 12 March 2019 13:33:16
To:
On Tue, Mar 12, 2019 at 06:37:57PM +0100, Noralf Trønnes wrote:
>
>
> Den 12.03.2019 18.25, skrev Ville Syrjälä:
> > On Tue, Mar 12, 2019 at 06:15:24PM +0100, Noralf Trønnes wrote:
> >>
> >>
> >> Den 12.03.2019 17.17, skrev Ville Syrjälä:
> >>> On Tue, Mar 12, 2019 at 11:47:04AM +0100, Michel
4.20-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e02f5c1bb2283cfcee68f2f0feddcc06150f13aa ]
The DRM driver stack is designed to work with cache coherent devices
only, but permits an optimization to be enabled in some cases, where
4.14-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit e02f5c1bb2283cfcee68f2f0feddcc06150f13aa ]
The DRM driver stack is designed to work with cache coherent devices
only, but permits an optimization to be enabled in some cases, where
syzbot has bisected this bug to:
commit 09ef09b4ab95dc405ad4171ec2cd8a4ff5227108
Author: Shayenne Moura
Date: Wed Feb 6 20:08:13 2019 +
drm/vkms: WARN when hrtimer_forward_now fails
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=128448cf20
start commit: 09ef09b4
Hi Neil,
On Mon, Feb 4, 2019 at 10:55 AM Neil Armstrong wrote:
>
> When meson_canvas is not yet probed, meson_canvas_get returns -EPROBE_DEFER.
>
> Handle this case but deferring the probe of the drm driver aswell.
>
> Fixes: 66cae477c380 ("drm/meson: Use optional canvas provider")
>
Hello Jani,
On Mon, Mar 11, 2019 at 11:04:19AM +0200, Jani Nikula wrote:
> On Sun, 10 Mar 2019, "Ahmed S. Darwish" wrote:
> > Hello DRM/UEFI maintainers,
> >
> > Several years ago, I wrote a set of patches to dump the kernel
> > log to disk upon panic -- through BIOS INT 0x13 services. [1]
> >
>
1 - 100 of 140 matches
Mail list logo
