On Thu, Apr 11, 2019 at 06:36:15PM -0700, Gurchetan Singh wrote:
> On Wed, Apr 10, 2019 at 10:03 PM Gerd Hoffmann wrote:
> >
> > > > +/* VIRTIO_GPU_CMD_RESOURCE_CREATE_V2 */
> > > > +struct virtio_gpu_cmd_resource_create_v2 {
> > > > + struct virtio_gpu_ctrl_hdr hdr;
> > > > + __le32
Hi Linus,
Fixes across the driver spectrum this week, the mediatek fbdev support
isn't very large and might be a bit late for this round, but I looked
over it and it's not very large and seems like a useful feature for
them.
Otherwise the main thing is a regression fix for i915 5.0 bug that
https://bugs.freedesktop.org/show_bug.cgi?id=110360
--- Comment #6 from jian-h...@endlessm.com ---
Created attachment 143946
--> https://bugs.freedesktop.org/attachment.cgi?id=143946=edit
lspci -nnv
--
You are receiving this mail because:
You are the assignee for the
On Tue, Apr 2, 2019 at 4:38 AM Heiko Stuebner wrote:
>
> From: Vicente Bergas
>
> As explained by Robin Murphy:
> > the IOMMU shutdown disables paging, so if the VOP is still
> > scanning out then that will result in whatever IOVAs it was using now going
> > straight out onto the bus as physical
On Wed, Apr 10, 2019 at 10:03 PM Gerd Hoffmann wrote:
>
> > > +/* VIRTIO_GPU_CMD_RESOURCE_CREATE_V2 */
> > > +struct virtio_gpu_cmd_resource_create_v2 {
> > > + struct virtio_gpu_ctrl_hdr hdr;
> > > + __le32 resource_id;
> > > + __le32 format;
> > > + __le32 width;
> > > +
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #78 from Garrett ---
(In reply to IvvanVG from comment #76)
> problem because of this commit
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/
> ?h=linux-4.18.y=d9ef158adf04b81772a7e9d682a054614ebac2fd
>
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #77 from Garrett ---
small change to a comment above:
sudo -i
echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo "2" > /sys/class/drm/card0/device/pp_dpm_sclk (notice NOT pp_dpm_mclk)
allows my
https://bugs.freedesktop.org/show_bug.cgi?id=110293
djip.per...@free.fr changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Correction on the link for the mock election. That should be
https://members.x.org/ballot/3/vote, not /admin.
It will also be linked from the members homepage and shown as the current
ballot.
Harry
On 2019-04-11 8:03 p.m., Harry Wentland wrote:
> To all X.Org Foundation Members:
>
> The 2019
To all X.Org Foundation Members:
The 2019 X.Org ballot closed yesterday. There is some good and some bad news.
The Good News:
The vote on the bylaw changes passed with 53 for, 1 against, and 2 abstaining.
The Bad News:
Due to some issues with our new members website all votes for new board
Hi Dave and Daniel,
Here goes drm-intel-fixes-2019-04-11:
- Revert back to max link rate and lane count on eDP.
- DSI related fixes for all platforms including Ice Lake.
- GVT Fixes including one vGPU display plane size regression fix,
one for preventing use-after-free in ppgtt shadow free
On Fri, 12 Apr 2019 at 03:37, Lyude Paul wrote:
>
> On Thu, 2019-04-11 at 08:48 +1000, Ben Skeggs wrote:
> > On Wed, 10 Apr 2019 at 06:23, Lyude Paul wrote:
> > > For a while, we've had the problem of i2c bus access not grabbing
> > > a runtime PM ref when it's being used in userspace by
Add support for 2MB sized pages. This will improve our map and unmap
times and save a bit of memory by avoiding 3rd level page tables for
contiguous allocations.
As we use shmem for buffers and huge page allocations for shmem are off
by default, there isn't an improvement out of the box and
On Thu, Apr 11, 2019 at 08:41:30AM +0300, Leon Romanovsky wrote:
> On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote:
> > On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote:
> > > From: Jérôme Glisse
> > >
[snip]
> > > diff --git a/include/linux/mmu_notifier.h
Den 11.04.2019 20.18, skrev Lukas Wunner:
> On Thu, Apr 11, 2019 at 06:42:33PM +0200, Noralf Trønnes wrote:
>> @@ -1299,6 +1299,11 @@ static void __spi_pump_messages(struct spi_controller
>> *ctlr, bool in_kthread)
>>
>> trace_spi_message_start(ctlr->cur_msg);
>>
>> +ret =
Den 11.04.2019 18.42, skrev Noralf Trønnes:
> From: Meghana Madhyastha
>
> Some drivers like spi_bcm2835 have a max size on DMA transfers. Work
> around this by splitting up the transfer if necessary.
>
> ->max_transfer_size is MAX_INT if the driver doesn't set it, so this change
> will only
https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #41 from quirin.blae...@freenet.de ---
Bug is still alive. v5.0.7
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
On Thu, Apr 11, 2019 at 06:42:33PM +0200, Noralf Trønnes wrote:
> @@ -1299,6 +1299,11 @@ static void __spi_pump_messages(struct spi_controller
> *ctlr, bool in_kthread)
>
> trace_spi_message_start(ctlr->cur_msg);
>
> + ret = spi_split_transfers_maxsize(ctlr, ctlr->cur_msg,
>
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #33 from Laurent ---
(In reply to Andre Klapper from comment #32)
> Closing as invalid as nothing was fixed in Mesa code and as this issue
> tracker is not a support desk to go through hundreds of lines of external
> random code.
On Thu, 2019-04-11 at 08:48 +1000, Ben Skeggs wrote:
> On Wed, 10 Apr 2019 at 06:23, Lyude Paul wrote:
> > For a while, we've had the problem of i2c bus access not grabbing
> > a runtime PM ref when it's being used in userspace by i2c-dev, resulting
> > in nouveau spamming the kernel log with
On 04/03/2019 10:20 AM, nicolas.fe...@microchip.com wrote:
> On 03/04/2019 at 09:24, YueHaibing wrote:
>> External E-Mail
>>
>>
>> Fixes gcc '-Wunused-but-set-variable' warning:
>>
>> drivers/video/fbdev/atmel_lcdfb.c: In function 'atmel_lcdfb_remove':
>>
On 04/03/2019 09:24 AM, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/video/fbdev/mxsfb.c: In function 'mxsfb_restore_mode':
> drivers/video/fbdev/mxsfb.c:633:11: warning:
> variable 'line_count' set but not used [-Wunused-but-set-variable]
>
> It's never used
On Thu, Apr 11, 2019 at 03:21:08PM +, Weiny, Ira wrote:
> > On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote:
> > > On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote:
> > > > From: Jérôme Glisse
> > > >
> > > > CPU page table update can happens for many reasons, not only
On 4/11/19 12:41 PM, Kazlauskas, Nicholas wrote:
> On 4/11/19 12:03 PM, Andrey Grodzovsky wrote:
>> Patch '5edb0c9b Fix deadlock with display during hanged ring recovery'
>> was accidentaly removed during one of DALs code merges.
>>
>> Signed-off-by: Andrey Grodzovsky
> Reviewed-by: Nicholas
From: Meghana Madhyastha
Remove chunk splitting in tinydrm_spi_transfer in tinydrm-helpers as the
spi core will split a buffer into max_dma_len chunks for the spi
controller driver to handle, automatic byte swapping in
tinydrm_spi_transfer as it doesn't have users.
Remove the spi_max module
From: Meghana Madhyastha
The spi core splits up transfers larger than ->max_dma_len now so we can
remove the upper bound on DMA transfers. Limit max_dma_len to 65532,
because the scatter gather segment is required to be a multiple of 4.
Signed-off-by: Meghana Madhyastha
Signed-off-by: Noralf
Don't warn about splitting transfers, the info is available in the
statistics if needed.
Signed-off-by: Noralf Trønnes
---
drivers/spi/spi.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
index 9a7def7c3237..05875e63be43 100644
---
From: Meghana Madhyastha
Some drivers like spi_bcm2835 have a max size on DMA transfers. Work
around this by splitting up the transfer if necessary.
->max_transfer_size is MAX_INT if the driver doesn't set it, so this change
will only affect drivers that set the value.
Signed-off-by: Meghana
spi-bcm2835 has a ~64kB upper limit on DMA transfers. Drivers in
drivers/gpu/drm/tinydrm work around this limitation by splitting the
buffer into multiple transfers. This patchset lifts this limitation by
splitting affected transfers in the SPI core using
spi_split_transfers_maxsize().
This
https://bugs.freedesktop.org/show_bug.cgi?id=109692
--- Comment #41 from Michel Dänzer ---
(In reply to Andrey Grodzovsky from comment #40)
> Actually since in non reset case this is an actual error maybe i just print
> it this happens NOT during reset.
Buggy / malicious userspace can probably
On 4/11/19 12:03 PM, Andrey Grodzovsky wrote:
> Patch '5edb0c9b Fix deadlock with display during hanged ring recovery'
> was accidentaly removed during one of DALs code merges.
>
> Signed-off-by: Andrey Grodzovsky
Reviewed-by: Nicholas Kazlauskas
Probably got lost in a refactor.
Also, didn't
https://bugs.freedesktop.org/show_bug.cgi?id=109692
--- Comment #40 from Andrey Grodzovsky ---
(In reply to Michel Dänzer from comment #38)
> (In reply to Andrey Grodzovsky from comment #37)
> > Those messages are actually expected for this particular use case, i might
> > consider switching
https://bugs.freedesktop.org/show_bug.cgi?id=110405
Michel Dänzer changed:
What|Removed |Added
Component|DRM/AMDgpu |DRM/AMDgpu-pro
--
You are receiving
On Thu, Apr 11, 2019 at 10:27 AM Maxime Ripard
wrote:
>
> On Thu, Apr 11, 2019 at 05:23:25PM +0200, Jernej Škrabec wrote:
> > Dne četrtek, 11. april 2019 ob 17:20:04 CEST je Clément Péron napisal(a):
> > > Hi,
> > >
> > > On Thu, 11 Apr 2019 at 17:05, Jernej Škrabec
> > wrote:
> > > > Dne
https://bugs.freedesktop.org/show_bug.cgi?id=110405
Bug ID: 110405
Summary: No successful install of amdgpu 18.30 on Ubuntu
18.04.02 LTS
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux
Patch '5edb0c9b Fix deadlock with display during hanged ring recovery'
was accidentaly removed during one of DALs code merges.
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff
From: Christian König
We now destroy finished jobs from the worker thread to make sure that
we never destroy a job currently in timeout processing.
By this we avoid holding lock around ring mirror list in drm_sched_stop
which should solve a deadlock reported by a user.
v2: Remove unused
Also reject TDRs if another one already running.
v2:
Stop all schedulers across device and entire XGMI hive before
force signaling HW fences.
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 125 -
1 file changed, 88 insertions(+),
For later driver's reference to see if the fence is signaled.
v2: Move parent fence put to resubmit jobs.
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/scheduler/sched_main.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git
On Thu, 2019-04-11 at 17:36 +0300, Gwan-gyeong Mun wrote:
> The hotplug detection routine of drm_helper_hpd_irq_event() can
> detect
> changing of status of connector, but it can not detect changing of
> edid.
>
> Following scenario requires detection of changing of edid.
>
> 1) plug display
Hi,
On Thu, Apr 11, 2019 at 09:38:06AM +0200, Hans Verkuil wrote:
> >> @@ -149,6 +155,7 @@ static const struct image_format_info formats[] = {
> >>.has_alpha = true,
> >>}, {
> >>.drm_fmt = DRM_FORMAT_RGB565,
> >> + .v4l2_fmt = V4L2_PIX_FMT_RGB565,
> >
> > ->
On Thu, Apr 11, 2019 at 05:42:56PM +0200, Jernej Škrabec wrote:
> Dne četrtek, 11. april 2019 ob 17:27:52 CEST je Maxime Ripard napisal(a):
> > On Thu, Apr 11, 2019 at 05:23:25PM +0200, Jernej Škrabec wrote:
> > > Dne četrtek, 11. april 2019 ob 17:20:04 CEST je Clément Péron napisal(a):
> > > >
On 03/30/2019 03:26 AM, YueHaibing wrote:
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/video/fbdev/pvr2fb.c: In function 'pvr2fb_init':
> drivers/video/fbdev/pvr2fb.c:1074:6: warning:
> variable 'size' set but not used [-Wunused-but-set-variable]
>
> It's not used since commit
https://bugs.freedesktop.org/show_bug.cgi?id=110229
Andre Klapper changed:
What|Removed |Added
Resolution|FIXED |INVALID
--- Comment #32 from Andre
On Thu, Apr 11, 2019 at 02:31:48PM +0300, Dmitry Osipenko wrote:
> 11.04.2019 13:06, Mikko Perttunen пишет:
> > On 11.4.2019 11.30, Thierry Reding wrote:
> >> On Thu, Apr 11, 2019 at 09:23:13AM +0100, Ben Dooks wrote:
> >>>
> >>>
> >>> On 2019-04-10 23:47, Stefan Agner wrote:
> In case the
https://bugs.freedesktop.org/show_bug.cgi?id=110229
Laurent changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
On Thu, Apr 11, 2019 at 05:23:25PM +0200, Jernej Škrabec wrote:
> Dne četrtek, 11. april 2019 ob 17:20:04 CEST je Clément Péron napisal(a):
> > Hi,
> >
> > On Thu, 11 Apr 2019 at 17:05, Jernej Škrabec
> wrote:
> > > Dne četrtek, 11. april 2019 ob 12:57:16 CEST je Clément Péron napisal(a):
> > > >
https://bugs.freedesktop.org/show_bug.cgi?id=110360
--- Comment #5 from Alex Deucher ---
Please attach the output of lspci -vnn
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
> On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote:
> > On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote:
> > > From: Jérôme Glisse
> > >
> > > CPU page table update can happens for many reasons, not only as a
> > > result of a syscall (munmap(), mprotect(), mremap(),
Hi Dave, Daniel,
Here is a new drm-misc-fixes PR.
thanks!
maxime
drm-misc-fixes-2019-04-11:
- core: Make atomic_enable and disable optional for CRTC
- dw-hdmi: Lower max frequency for the Allwinner H6, SCDC configuration
improvements for older controller versions
- omap: a fix
On 03/20/2019 10:33 AM, Linus Walleij wrote:
> These board families are now handled in the DRM subsystem
> where we can have reusable panel drivers and some other
> stuff. The PL111 there is now the driver used in the
> defconfig for Versatile and Nomadik so no need to keep
> this code around.
>
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #31 from Laurent ---
Okey, I've found a temporary solution : putting instructions in the second
fragment shader to slow down the shader execution code and it works...
const std::string fragmentShader2 =
R"(
https://bugs.freedesktop.org/show_bug.cgi?id=109692
--- Comment #39 from mikhail.v.gavri...@gmail.com ---
(In reply to Michel Dänzer from comment #38)
>
> I'd argue they should be debug, so they don't spam dmesg by default.
Let this messages stay in kernel log (dmesg), but I don't want see they
https://bugs.freedesktop.org/show_bug.cgi?id=109692
--- Comment #38 from Michel Dänzer ---
(In reply to Andrey Grodzovsky from comment #37)
> Those messages are actually expected for this particular use case, i might
> consider switching them to info.
I'd argue they should be debug, so they
On Wed, Apr 10, 2019 at 04:41:57PM -0700, Ira Weiny wrote:
> On Tue, Mar 26, 2019 at 12:47:46PM -0400, Jerome Glisse wrote:
> > From: Jérôme Glisse
> >
> > CPU page table update can happens for many reasons, not only as a result
> > of a syscall (munmap(), mprotect(), mremap(), madvise(), ...)
After suspend/resume process, hotplug detection is handled by
i915_hpd_poll_init_work() workqueue. While intel_hdmi_detect() or
intel_dp_detect() are called, intel_hdmi_set_edid() or intel_dp_set_edid()
only update an internal detect_edid variable of intel_connector.
A missed update of edid
The hotplug detection routine of drm_helper_hpd_irq_event() can detect
changing of status of connector, but it can not detect changing of edid.
Following scenario requires detection of changing of edid.
1) plug display device to a connector
2) system suspend
3) unplug 1)'s display device and
This patch series fix missed detection of changing of edid on between
suspend and resume.
First patch fixes drm_helper_hdp_irq_event() in order to fix a below use
case.
Following scenario requires detection of changing of edid.
1) plug display device to a connector
2) system suspend
Den 10.04.2019 15.03, skrev Neil Armstrong:
> On 10/04/2019 14:43, Noralf Trønnes wrote:
>> Due to copy/paste error, the fbdev format was changed to 32bpp = XRGB
>> which is an emulated format for the RGB565 drivers. Revert to to using the
>> fallback which is
Den 07.04.2019 18.52, skrev Noralf Trønnes:
> It is generic code and having it in the helper will let other drivers
> benefit from it.
>
> One change was necessary assuming this to be true:
> INTEL_INFO(dev_priv)->num_pipes == dev->mode_config.num_crtc
>
> Suggested-by: Daniel Vetter
> Cc:
https://bugs.freedesktop.org/show_bug.cgi?id=109692
--- Comment #37 from Andrey Grodzovsky ---
(In reply to mikhail.v.gavrilov from comment #36)
> Created attachment 143928 [details]
> Demonstration how message "drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to
> initialize parser -125!" get a
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #30 from Laurent ---
What do you mean by a test case ?
To make the source code easier to read, I put the source code into c++ class.
But if you want to have a source code to produce an executable file, just ask.
;)
But it'll take
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #29 from Laurent ---
Created attachment 143939
--> https://bugs.freedesktop.org/attachment.cgi?id=143939=edit
The main function.
--
You are receiving this mail because:
You are the assignee for the
Den 11.04.2019 06.49, skrev Gerd Hoffmann:
> Oops, the __iomem annotation was added to the header file only.
> Add it to the implementation (and documentation) too.
>
> Fixes: 5c5373b51bec ("drm: switch drm_fb_xrgb_to_rgb888_dstclip to accept
> __iomem dst")
> Signed-off-by: Gerd Hoffmann
https://bugs.freedesktop.org/show_bug.cgi?id=110229
Laurent changed:
What|Removed |Added
CC||laurentduroi...@gmail.com
--- Comment #28
On Mon, Apr 01, 2019 at 08:11:00PM +0100, Robin Murphy wrote:
> With the diff below squashed in to address my outstanding style nits,
>
> Acked-by: Robin Murphy
>
> I don't foresee any conflicting io-pgtable changes to prevent this going via
> DRM, but I'll leave the final say up to Joerg.
No
The command line parser is pretty tough to get right and very error prone,
so let's add a selftest to try to catch any regression.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/selftests/Makefile | 2 +-
drivers/gpu/drm/selftests/drm_cmdline_selftests.h | 49 +-
From: Maxime Ripard
Rewrite the command line parser in order to get away from the state machine
parsing the video mode lines.
Hopefully, this will allow to extend it more easily to support named modes
and / or properties set directly on the command line.
Signed-off-by: Maxime Ripard
---
Properly configuring the overscan properties might be needed for the
initial setup of the framebuffer for display that still have overscan.
Let's allow for more properties on the kernel command line to setup each
margin.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/drm_fb_helper.c | 47
Rotations and reflections setup are needed in some scenarios to initialise
properly the initial framebuffer. Some drivers already had a bunch of
quirks to deal with this, such as either a private kernel command line
parameter (omapdss) or on the device tree (various panels).
In order to
Hi,
The proprietary stack for the RaspberryPi allows for a number of video
parameters widely used by their users, but yet don't have any equivalents
in the mainline kernel.
Those options are detailed here:
https://www.raspberrypi.org/documentation/configuration/config-txt/video.md
While not all
From: Maxime Ripard
The drm subsystem also uses the video= kernel parameter, and in the
documentation refers to the fbdev documentation for that parameter.
However, that documentation also says that instead of giving the mode using
its resolution we can also give a name. However, DRM doesn't
On Thu, Apr 11, 2019 at 12:57:12PM +0200, Clément Péron wrote:
> Hi,
>
> The Allwinner H6 has a Mali-T720 MP2. The drivers are
> out-of-tree so this series only introduce the dt-bindings.
>
> The first patch is from Neil Amstrong and has been already
> merged in linux-amlogic. It is required for
On Thu, Apr 11, 2019 at 12:57:14PM +0200, Clément Péron wrote:
> Some SoCs adds a bus clock gate to the Mali Midgard GPU.
>
> Add the binding for the bus clock.
>
> Signed-off-by: Icenowy Zheng
> Signed-off-by: Clément Péron
I'm not quite sure what you did there. If Icenowy is the author and
On Thu, Apr 11, 2019 at 12:19:47PM +0200, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> Orange Pi 3 board requires enabling DDC I2C bus via some GPIO connected
> transistors, before the bus can be used.
>
> Model this as a power supply for DDC bus on the HDMI connector connected
> to the
Hi,
On Thu, Apr 11, 2019 at 12:19:44PM +0200, meg...@megous.com wrote:
> From: Ondrej Jirman
>
> H6 SoC has a "pio group withstand voltage mode" register (datasheet
> description), that needs to be used to select either 1.8V or 3.3V I/O mode,
> based on what voltage is powering the respective
https://bugs.freedesktop.org/show_bug.cgi?id=108990
--- Comment #2 from CI Bug Log ---
The CI Bug Log issue associated to this bug has been archived.
New failures matching the above filters will not be associated to this bug
anymore.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=108990
Martin Peres changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=110229
Andre Klapper changed:
What|Removed |Added
Status|REOPENED|NEEDINFO
--- Comment #27 from Andre
https://bugs.freedesktop.org/show_bug.cgi?id=102670
Arek Hiler changed:
What|Removed |Added
i915 platform|BXT, GLK, HSW, I915G, KBL, |ALL
|SKL, SNB
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:19 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> This patch add ddp write register common api
> this is preparation patch for ovl/ovl_2l direct link
> usecase.
> in that case, we need this funtion to set one bit of ovl_2l
> register
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:19 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> This patch add function to background color input select for ovl/ovl_2l
> direct link
> for ovl/ovl_2l direct link usecase, we need set background color
> input select for these
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:19 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> This patch add layer_nr for ovl private data
> ovl_2l almost same with with ovl hardware, except the
> layer number for ovl_2l is 2 and ovl is 4.
> this patch is a preparation for
On 11.04.2019 10:23, Ben Dooks wrote:
> On 2019-04-10 23:47, Stefan Agner wrote:
>> In case the IOMMU API is not available compiling host1x fails with
>> the following error:
>> In file included from drivers/gpu/host1x/hw/host1x06.c:27:
>> drivers/gpu/host1x/hw/channel_hw.c: In function
>>
https://bugs.freedesktop.org/show_bug.cgi?id=110229
Laurent changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|NOTOURBUG
https://bugs.freedesktop.org/show_bug.cgi?id=110229
Laurent changed:
What|Removed |Added
Summary|Textures binded to |glMemoryBarrier doesn't
On 11.4.2019 11.30, Thierry Reding wrote:
On Thu, Apr 11, 2019 at 09:23:13AM +0100, Ben Dooks wrote:
On 2019-04-10 23:47, Stefan Agner wrote:
In case the IOMMU API is not available compiling host1x fails with
the following error:
In file included from drivers/gpu/host1x/hw/host1x06.c:27:
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #26 from Laurent ---
Hi! Is still someone here ?
I've found the function which doesn't work, it's glMemoryBarrier.
glCheck(glMemoryBarrier( GL_SHADER_STORAGE_BARRIER_BIT ));
It doesn't wait after the first shader have written all
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:19 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> This patch add mmsys private data for ddp path config
> all these register offset and value will be different in future SOC
> add these define into mmsys private data
> u32
Hi, Yongqiang:
On Wed, 2019-03-27 at 14:19 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> This patch add support for mediatek SOC MT8183
> 1.ovl_2l share driver with ovl
> 2.rdma1 share drive with rdma0, but fifo size is different
> 3.add mt8183 mutex private data, and mmsys
On Thu, Apr 11, 2019 at 09:56:15AM +0200, Clément Péron wrote:
> Hi,
>
> On Thu, 11 Apr 2019 at 09:28, Maxime Ripard wrote:
> >
> > On Thu, Apr 11, 2019 at 01:25:39AM +0200, Clément Péron wrote:
> > > Add the mali gpu node to the H6 device-tree.
> > >
> > > Signed-off-by: Clément Péron
> > > ---
Hi Dave,
The following changes since commit 509869a2fec36ecb2b841180915995f41d5a0219:
drm/tegra: vic: Fix implicit function declaration warning (2019-03-22
14:08:55 +0100)
are available in the Git repository at:
git://anongit.freedesktop.org/tegra/linux tags/drm/tegra/for-5.1-rc5
for you
Creates plane alpha and blend mode properties attached to plane.
This patch depends on:
- https://patchwork.freedesktop.org/series/54448/
- https://patchwork.freedesktop.org/series/54449/
- https://patchwork.freedesktop.org/series/54450/
Changes since v1:
- Adds patch denpendency in the comment
Fixing the DMA mapping sg segment warning, which shows "DMA-API: mapping
sg segment longer than device claims to support [len=921600] [max=65536]".
Fixed by setting the max segment size at Komeda driver.
This patch depends on:
- https://patchwork.freedesktop.org/series/54448/
-
On Thu, Apr 11, 2019 at 09:23:13AM +0100, Ben Dooks wrote:
>
>
> On 2019-04-10 23:47, Stefan Agner wrote:
> > In case the IOMMU API is not available compiling host1x fails with
> > the following error:
> > In file included from drivers/gpu/host1x/hw/host1x06.c:27:
> >
Hi,
On Thu, 11 Apr 2019 at 09:28, Maxime Ripard wrote:
>
> On Thu, Apr 11, 2019 at 01:25:39AM +0200, Clément Péron wrote:
> > Add the mali gpu node to the H6 device-tree.
> >
> > Signed-off-by: Clément Péron
> > ---
> > arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 80
> >
Enable and add supply to the Mali GPU node on the
Pine H64 board.
Signed-off-by: Clément Péron
---
arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6-pine-h64.dts
The locks (timeline->lock and rq->lock) need to be taken with disabled
interrupts. This is done in __retire_engine_request() by disabling the
interrupts independently of the locks itself.
While local_irq_disable()+spin_lock() equals spin_lock_irq() on vanilla
it does not on RT. Also, it is not
Enable and add supply to the Mali GPU node on the
Orange Pi 3 board.
Signed-off-by: Clément Péron
---
arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi-3.dts | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6-orangepi-3.dts
Replace the indirection through struct stack_trace by using the storage
array based interfaces.
The original code in all printing functions is really wrong. It allocates a
storage array on stack which is unused because depot_fetch_stack() does not
store anything in it. It overwrites the entries
1 - 100 of 141 matches
Mail list logo
