https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #23 from quirin.blae...@freenet.de ---
Created attachment 280009
--> https://bugzilla.kernel.org/attachment.cgi?id=280009&action=edit
dmesg amd_gpu_firmware_info
(In reply to Alex Deucher from comment #22)
> You'll also need this up
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #7 from chris ---
Yes, same here. The system boots until GDM wants to start, then it freezes with
the mentioned amdgpu error. Disabling amdgpu let the system start up completely
including gdm.
--
You are receiving this mail because
Fix a broken build because of a typo in
"drm/scheduler: Add drm_sched_suspend/resume_timeout()".
Signed-off-by: Christian König
---
drivers/gpu/drm/etnaviv/etnaviv_dump.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/etnaviv/etnaviv_dump.c
b/drivers
Hi Laurent,
On 29/11/2018 12:43, Laurent Pinchart wrote:
> Hi Geert,
>
> Thank you for the patch.
>
> On Thursday, 29 November 2018 12:58:50 EET Geert Uytterhoeven wrote:
>> Using overlay sugar syntax makes the DTS files easier to read (and
>> write).
>>
>> Overlay syntactic sugar for generating
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #6 from Brian Schott ---
To clarify, the system can boot with the amdgpu module, but it will lock up
when LightDM/X starts. Booting with the amdgpu module blacklisted works.
--
You are receiving this mail because:
You are the assig
Hi Dave,
Just adding configurable plane alpha and pixel blend mode support
for FIMD device I missed.
Please kindly let me know if there is any problem.
Thanks,
Inki Dae
The following changes since commit 2a3c83f5fe0770d13bbb71b23674886ff4111f44:
Merge tag 'vmwgfx-next-2018-12-13' of
On 12/13/18 5:48 PM, Daniel Vetter wrote:
On Thu, Dec 13, 2018 at 12:17:54PM +0200, Oleksandr Andrushchenko wrote:
Daniel, could you please comment?
Cross-revieweing someone else's stuff would scale better,
fair enough
I don't think
I'll get around to anything before next year.
I put you
GF117 appears to use the same register as GK104 (but still with the
general Fermi readout mechanism).
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108980
Signed-off-by: Ilia Mirkin
---
drivers/gpu/drm/nouveau/nvkm/subdev/volt/gf100.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108980
Signed-off-by: Ilia Mirkin
---
drivers/gpu/drm/nouveau/nvkm/engine/falcon.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/falcon.c
b/drivers/gpu/drm/nouveau/nvkm/engine/
Hi Johan,
On Fri, Dec 14, 2018 at 2:32 AM Johan Jonker wrote:
>
> Bug fix? (PART 7)
>
> A little bit of success here.
> Penguins and other colors are on the screen.
> DRM and FB old style seems to work with DVI-D.
> Pure HDMI and sound not tested.
> I think 'someone' forgot to add HCLK_HDMI to th
Hi Linus,
While I hoped things would calm down, the world hasn't joined with me,
but it's a few things scattered over a wide area. The i915 workarounds
regression fix is probably the largest, the rest are more usual sized.
We also get some new AMD PCI IDs.
There is also a patch in here to MAINTAI
Hi all,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/vmwgfx/vmwgfx_ttm_glue.c
between commit:
fd567467753f ("drm/vmwgfx: Protect from excessive execbuf kernel memory
allocations v3")
from the drm-fixes tree and commit:
a64f784bb14a ("drm/ttm: initialize g
There has been a TODO waiting for quite a long time in
drm_dp_mst_topology.c:
/* We cannot rely on port->vcpi.num_slots to update
* topology_state->avail_slots as the port may not exist if the parent
* branch device was unplugged. This should be fixed by tracking
It occurred to me that we never actually check this! So let's start
doing that.
Signed-off-by: Lyude Paul
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/drm_dp_mst_topology.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
b/dri
Now that we finally have a sane way to keep port allocations around, use
it to fix the potential unchecked ->port accesses that nouveau makes by
making sure we keep the mst port allocated for as long as it's
drm_connector is accessible.
Additionally, now that we've guaranteed that mstc->port is al
Changes since v6:
- Move EXPORT_SYMBOL() for drm_dp_mst_topology_state_funcs to this
commit
- Document __drm_dp_mst_state_iter_get() and note that it shouldn't be
called directly
Signed-off-by: Lyude Paul
Reviewed-by: Daniel Vetter
---
drivers/gpu/drm/drm_dp_mst_topology.c | 5 +-
incl
Up until now, freeing payloads on remote MST hubs that just had ports
removed has almost never worked because we've been relying on port
validation in order to stop us from accessing ports that have already
been freed from memory, but ports which need their payloads released due
to being removed wi
Currently, nouveau uses the yolo method of setting up MST displays: it
uses the old VCPI helpers (drm_dp_find_vcpi_slots()) for computing the
display configuration. These helpers don't take care to make sure they
take a reference to the mstb port that they're checking, and
additionally don't actual
Going through the currently programmed payloads isn't safe without
holding mgr->payload_lock, so actually do that and warn if anyone tries
calling nv50_msto_payload() in the future without grabbing the right
locks.
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/nouveau/dispnv50/disp.c | 6 ++
This has never actually worked, and isn't needed anyway: the driver's
always going to try to deallocate VCPI when it tears down the display
that the VCPI belongs to.
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/drm_dp_mst_topology.c | 8
1 file changed, 8 deletions(-)
diff --git a/dri
Same as we did for i915, but for nouveau this time. Additionally, we
grab a malloc reference to the port that lasts for the entire lifetime
of nv50_mstc, which gives us the guarantee that mstc->port will always
point to valid memory for as long as the mstc stays around.
Signed-off-by: Lyude Paul
Trying to destroy the connector using mstc->connector.funcs->destroy()
if connector initialization fails is wrong: there is no possible
codepath in nv50_mstc_new where nv50_mstm_add_connector() would return
<0 and mstc would be non-NULL.
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/nouveau/disp
This is a WIP version of the series I've been working on for a while now
to get all of the atomic DRM drivers in the tree to use the atomic MST
helpers, and to make the atomic MST helpers actually idempotent. Turns
out it's a lot more difficult to do that without also fixing how port
and branch dev
There should be no functional changes here
Signed-off-by: Lyude Paul
Cc: Juston Li
---
drivers/gpu/drm/drm_dp_mst_topology.c | 71 ---
1 file changed, 42 insertions(+), 29 deletions(-)
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
b/drivers/gpu/drm/drm_dp_mst_topo
There is no need to look at the port's VCPI allocation before calling
drm_dp_mst_deallocate_vcpi(), as we already have msto->disabled to let
us avoid cleaning up an msto more then once. The DP MST core will never
call drm_dp_mst_deallocate_vcpi() on it's own, which is presumably what
these checks a
So that the ports stay around until we've destroyed the connectors, in
order to ensure that we don't pass an invalid pointer to any MST helpers
once we introduce the new MST VCPI helpers.
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/i915/intel_connector.c | 4
drivers/gpu/drm/i915/intel_dp
There's no reason we need this, it's just confusing looking.
Signed-off-by: Lyude Paul
Cc: Juston Li
---
drivers/gpu/drm/drm_dp_mst_topology.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
b/drivers/gpu/drm/drm_dp_mst_topology.c
in
The current way of handling refcounting in the DP MST helpers is really
confusing and probably just plain wrong because it's been hacked up many
times over the years without anyone actually going over the code and
seeing if things could be simplified.
To the best of my understanding, the current s
https://bugs.freedesktop.org/show_bug.cgi?id=109060
Bug ID: 109060
Summary: android-x86 64bit builds crashes due to
android/gralloc_handle.h
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: other
On Thu, 2018-12-13 at 07:18 +0200, Ville Syrjälä wrote:
> On Wed, Dec 12, 2018 at 04:32:02PM -0800, Dhinakaran Pandiyan wrote:
> > On Tue, 2018-11-20 at 18:13 +0200, Ville Syrjala wrote:
> > > From: Ville Syrjälä
> > >
> > > Fill out the AVI infoframe quantization range bits using
> > > drm_hdmi_
This patch remove the follow complete task from TODO documentation:
drm_mode_config.crtc_idr is misnamed, since it contains all KMS object.
Should be renamed to drm_mode_config.object_idr.
Signed-off-by: Shayenne da Luz Moura
---
Documentation/gpu/todo.rst | 3 ---
1 file changed, 3 deletio
Previous version of this series was here:
https://lists.freedesktop.org/archives/dri-devel/2018-December/200178.html
Gamma and degamma LUT's uploaded by userspace need to be checked to
ensure they're valid tables and that they meet any additional
constraints of a given platform's hardware. Let'
Some hardware may place additional restrictions on the gamma/degamma
curves described by our LUT properties. E.g., that a gamma curve never
decreases or that the red/green/blue channels of a LUT's entries must be
equal. Let's add a helper function that drivers can use to test that a
userspace-pro
We currently program userspace-provided gamma and degamma LUT's into our
hardware without really checking to see whether they satisfy our
hardware's rules. We should try to catch tables that are invalid for
our hardware early and reject the atomic transaction.
All of our platforms that accept a d
On Thu, Dec 13, 2018 at 07:29:57PM -0200, Shayenne da Luz Moura wrote:
> This patch solves this TODO task:
> drm_mode_config.crtc_idr is misnamed, since it contains all KMS object.
> Should be renamed to drm_mode_config.object_idr.
>
> Signed-off-by: Shayenne da Luz Moura
>
> ---
> Changes in
Hi Fabrizio,
Thank you for the patch.
On Thursday, 13 December 2018 22:23:27 EET Fabrizio Castro wrote:
> Add support for the RZ/G2E (R8A774C0) SoC to the R-Car DU driver.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Laurent Pinchart
and applied to my tree.
> ---
> drivers/gpu/drm/rcar-
Hi Fabrizio,
Thank you for the patch.
On Thursday, 13 December 2018 22:20:54 EET Fabrizio Castro wrote:
> The RZ/G2E (r8a774c0) supports two LVDS channels. Extend the binding to
> support them.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Laurent Pinchart
and applied to my tree.
> ---
>
Hi Fabrizio,
Thank you for the patch.
On Thursday, 13 December 2018 22:23:36 EET Fabrizio Castro wrote:
> The LVDS implementation on the RZ/G2E (a.k.a. R8A774C0) is very similar
> to the one found on R-Car E3 (a.k.a. R8A77990), therefore add RZ/G2E
> LVDS support to the LVDS encoder driver in a s
Hi Fabrizio,
Thank you for the patch.
On Thursday, 13 December 2018 22:20:45 EET Fabrizio Castro wrote:
> Document the RZ/G2E (a.k.a. r8a774c0) SoC in the R-Car DU bindings.
>
> Signed-off-by: Fabrizio Castro
Reviewed-by: Laurent Pinchart
and applied to my tree.
> ---
> Documentation/devic
This patch solves this TODO task:
drm_mode_config.crtc_idr is misnamed, since it contains all KMS object.
Should be renamed to drm_mode_config.object_idr.
Signed-off-by: Shayenne da Luz Moura
---
Changes in v2:
- Make commit message more clear and change header file
drivers/gpu/drm/drm_leas
Hi Maxime,
One more small note.
On Fri, Dec 07, 2018 at 02:55:30PM +0100, Maxime Ripard wrote:
...
> + /**
> + * @wakeup:
> + *
> + * Time, in picoseconds, that a transmitter drives a Mark-1
> + * state prior to a Stop state in order to initiate an exit
> + * from U
On Thu, Dec 13, 2018 at 10:54:28PM +0200, sakari.ai...@iki.fi wrote:
> Hi Maxime,
>
> One more small note.
>
> On Fri, Dec 07, 2018 at 02:55:30PM +0100, Maxime Ripard wrote:
>
> ...
>
> > + /**
> > +* @wakeup:
> > +*
> > +* Time, in picoseconds, that a transmitter drives a Mark-1
Hi Maxime,
On Fri, Dec 07, 2018 at 02:55:30PM +0100, Maxime Ripard wrote:
> Now that we have some infrastructure for it, allow the MIPI D-PHY phy's to
> be configured through the generic functions through a custom structure
> added to the generic union.
>
> The parameters added here are the ones
Hi Maxime,
On Fri, Dec 07, 2018 at 02:55:29PM +0100, Maxime Ripard wrote:
> The phy framework is only allowing to configure the power state of the PHY
> using the init and power_on hooks, and their power_off and exit
> counterparts.
>
> While it works for most, simple, PHYs supported so far, some
On Fri, Dec 14, 2018 at 12:56:03AM +0530, Jagan Teki wrote:
> On Thu, Dec 13, 2018 at 8:37 PM Sean Paul wrote:
> >
> > On Fri, Nov 16, 2018 at 10:09:15PM +0530, Jagan Teki wrote:
> > > Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
> > >
> > > Add panel driver for it.
> > >
> > >
On Thu, 13 Dec 2018 at 23:49, Gerd Hoffmann wrote:
>
> Signed-off-by: Gerd Hoffmann
Seems correct to me,
Reviewed-by: Dave Airlie
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=107826
--- Comment #2 from Jeremy Newton ---
Sorry, I thought I responded to this already. PX is not supported on the PRO
driver anymore. It seems we forgot to put in a deprecated message in the docs.
I'll try make note of it for future releases.
We r
Am 13.12.18 um 18:26 schrieb Daniel Vetter:
>>> Code sharing just because the code looks similar is imo a really
>>> bad idea, when the semantics are entirely different (that was also the
>>> reason behind not reusing all the cpu event stuff for dma_fence, they're
>>> not normal cpu events).
>> Ok,
Add display port support in DPU by creating hooks
for DP encoder enumeration and encoder mode
initialization.
This change is based on the SDM845 Display port
driver changes[1].
changes in v2:
- rebase on [2] (Sean Paul)
- remove unwanted error checks and
switch cases (Jo
Bail out KMS hw init on display initialization failures with
proper error logging.
changes in v3:
- introduced in the series
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 39 +++--
1 file changed, 27 insertions(+), 12 deletion
Fix intf_type description in msm_disp_info to show that
it represents drm encoder mode of the display.
changes in v3:
- introduced in the series
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/msm_drv.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers
Hi,
On Wed, Dec 12, 2018 at 1:18 PM Jordan Crouse wrote:
>
> Add the nodes to describe the Adreno GPU and GMU devices.
>
> Signed-off-by: Jordan Crouse
> ---
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 123 +++
> 1 file changed, 123 insertions(+)
>
> diff --git a/arch/arm64
Hi,
On Wed, Dec 12, 2018 at 1:18 PM Jordan Crouse wrote:
> diff --git a/Documentation/devicetree/bindings/display/msm/gpu.txt
> b/Documentation/devicetree/bindings/display/msm/gpu.txt
> index 43fac0fe09bb..8d9415180c22 100644
> --- a/Documentation/devicetree/bindings/display/msm/gpu.txt
> +++ b/
Hi,
On Thu, Dec 13, 2018 at 9:32 AM Jordan Crouse wrote:
>
> Define an interconnect port for the GPU to set bus
> capabilities.
>
> Signed-off-by: Jordan Crouse
> ---
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm8
https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #22 from Alex Deucher (alexdeuc...@gmail.com) ---
You'll also need this updated firmware:
https://people.freedesktop.org/~agd5f/radeon_ucode/polaris11_k_mc.bin
--
You are receiving this mail because:
You are watching the assignee of
On Thu, Dec 13, 2018 at 5:25 PM Daniel Vetter wrote:
>
> On Thu, Dec 13, 2018 at 5:18 PM Rafael J. Wysocki wrote:
> >
> > On Thu, Dec 13, 2018 at 1:36 PM Daniel Vetter
> > wrote:
[cut]
> > > I can do the old code exactly, but afaict the non-NULL parent just
> > > takes care of the parent bus
On Thu, Dec 13, 2018 at 5:27 PM Winkler, Tomas wrote:
>
> > On Thu, Dec 13, 2018 at 1:36 PM C, Ramalingam
> > wrote:
> > >
> > > Tomas and Daniel,
> > >
> > > We got an issue here.
> > >
> > > The relationship that we try to build between I915 and mei_hdcp is as
> > > follows:
> > >
> > > We are
Define an interconnect port for the GPU to set bus
capabilities.
Signed-off-by: Jordan Crouse
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
b/arch/arm64/boot/dts/qcom/sdm845.dtsi
index 0a5ddfc4c59b..9323f211c
Two quick patches to document and add an interconnect port definition
for the sdm845 GPU.
This is based on the base GPU DT changes:
https://patchwork.freedesktop.org/series/39308/
As well as the DT nodes from Georgi:
https://patchwork.kernel.org/patch/10719483/
Jordan Crouse (2):
dt-bindings:
Add documentation for the interconnect and interconnect-names bindings
for the GPU node as detailed by bindings/interconnect/interconnect.txt.
Signed-off-by: Jordan Crouse
---
Documentation/devicetree/bindings/display/msm/gpu.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Document
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #5 from chris ---
Can you boot the system without amdgpu loaded (e.g., append
modprobe.blacklist=amdgpu)
-> Doing this, i am able to boot my system.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=201985
--- Comment #3 from nancy (nancy...@gmx.com) ---
Thank you for the quick hint:
Now the system starts without problems.
$ uname -a
Linux tux 4.20.0-rc6 # 1 SMP Thu Dec 13 18:15:31 CET 2018 x86_64 AMD Ryzen 5
1600 Six-Core Processor AuthenticAMD GN
On Thu, Dec 13, 2018 at 5:47 PM Koenig, Christian
wrote:
>
> Am 13.12.18 um 17:01 schrieb Daniel Vetter:
> > On Thu, Dec 13, 2018 at 12:24:57PM +, Koenig, Christian wrote:
> >> Am 13.12.18 um 13:21 schrieb Chris Wilson:
> >>> Quoting Koenig, Christian (2018-12-13 12:11:10)
> Am 13.12.18 u
https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #21 from quirin.blae...@freenet.de ---
(In reply to Alex Deucher from comment #20)
> Can you try one of these branches?
> https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
> https://cgit.freedesktop.org/~agd5f/linux
On Thu, Dec 13, 2018 at 9:14 AM 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(), ...) but also
> as a result of kernel activities (memory compression, reclaim, migration,
> ...).
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(), ...) but also
as a result of kernel activities (memory compression, reclaim, migration,
...).
Users of mmu notifier API track changes to the CPU p
From: Jérôme Glisse
To avoid having to change many call sites everytime we want to add a
parameter use a structure to group all parameters for the mmu_notifier
invalidate_range_start/end cakks. No functional changes with this
patch.
Changes since v2:
- fix build warning in migrate.c when CON
From: Jérôme Glisse
To avoid having to change many callback definition everytime we want
to add a parameter use a structure to group all parameters for the
mmu_notifier invalidate_range_start/end callback. No functional changes
with this patch.
Changed since v1:
- fix make htmldocs warning i
From: Jérôme Glisse
Changes since v2:
- fix build warning with CONFIG_MMU_NOTIFIER=n
- fix make htmldocs warning
Changes since v1:
- fix build with CONFIG_MMU_NOTIFIER=n
- kernel docs
Original cover letter:
This patchset add contextual information, why an invalidation is
happening, to mmu
Am 13.12.18 um 17:01 schrieb Daniel Vetter:
> On Thu, Dec 13, 2018 at 12:24:57PM +, Koenig, Christian wrote:
>> Am 13.12.18 um 13:21 schrieb Chris Wilson:
>>> Quoting Koenig, Christian (2018-12-13 12:11:10)
Am 13.12.18 um 12:37 schrieb Chris Wilson:
> Quoting Chunming Zhou (2018-12-11
https://bugzilla.kernel.org/show_bug.cgi?id=201985
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC||alexdeuc...@gmail.c
https://bugzilla.kernel.org/show_bug.cgi?id=201985
--- Comment #1 from nancy (nancy...@gmx.com) ---
Created attachment 27
--> https://bugzilla.kernel.org/attachment.cgi?id=27&action=edit
dmesg-4.20.0-rc6
--
You are receiving this mail because:
You are watching the assignee of the bug.
> On Thu, Dec 13, 2018 at 1:36 PM C, Ramalingam
> wrote:
> >
> > Tomas and Daniel,
> >
> > We got an issue here.
> >
> > The relationship that we try to build between I915 and mei_hdcp is as
> > follows:
> >
> > We are using the components to establish the relationship.
> > I915 is component mast
On Thu, Dec 13, 2018 at 5:18 PM Rafael J. Wysocki wrote:
>
> On Thu, Dec 13, 2018 at 1:36 PM Daniel Vetter wrote:
> >
> > On Thu, Dec 13, 2018 at 11:23 AM Rafael J. Wysocki
> > wrote:
> > >
> > > On Thu, Dec 13, 2018 at 10:58 AM Daniel Vetter wrote:
> > > >
> > > > On Thu, Dec 13, 2018 at 10:3
https://bugzilla.kernel.org/show_bug.cgi?id=201985
Bug ID: 201985
Summary: mc: Failed to load firmware
"amdgpu/polaris11_k_mc.bin"
Product: Drivers
Version: 2.5
Kernel Version: 4.20.0-rc6
Hardware: x86-64
On Thu, Dec 13, 2018 at 1:36 PM Daniel Vetter wrote:
>
> On Thu, Dec 13, 2018 at 11:23 AM Rafael J. Wysocki wrote:
> >
> > On Thu, Dec 13, 2018 at 10:58 AM Daniel Vetter wrote:
> > >
> > > On Thu, Dec 13, 2018 at 10:38:14AM +0100, Rafael J. Wysocki wrote:
> > > > On Mon, Dec 10, 2018 at 9:47 AM
On Thu, Dec 13, 2018 at 1:36 PM C, Ramalingam wrote:
>
> Tomas and Daniel,
>
> We got an issue here.
>
> The relationship that we try to build between I915 and mei_hdcp is as follows:
>
> We are using the components to establish the relationship.
> I915 is component master where as mei_hdcp is com
On Thu, Dec 13, 2018 at 12:24:57PM +, Koenig, Christian wrote:
> Am 13.12.18 um 13:21 schrieb Chris Wilson:
> > Quoting Koenig, Christian (2018-12-13 12:11:10)
> >> Am 13.12.18 um 12:37 schrieb Chris Wilson:
> >>> Quoting Chunming Zhou (2018-12-11 10:34:45)
> From: Christian König
>
On Thu, Dec 13, 2018 at 12:17:54PM +0200, Oleksandr Andrushchenko wrote:
> Daniel, could you please comment?
Cross-revieweing someone else's stuff would scale better, I don't think
I'll get around to anything before next year.
-Daniel
>
> Thank you
>
> On 11/27/18 12:32 PM, Oleksandr Andrushche
Implement the exec_mipi_pmic_seq_element callback for the CHT Whiskey Cove
PMIC.
On some CHT devices this fixes the LCD panel not lighting up when it was
not initialized by the GOP, because an external monitor was plugged in and
the GOP initialized only the external monitor.
Signed-off-by: Hans d
Add support for PMIC MIPI sequences using the new
intel_soc_pmic_exec_mipi_pmic_seq_element function.
This fixes the DSI LCD panel not lighting up when not initialized by the
GOP (because an external monitor was connected) on GPD win and GPD pocket
devices.
Specifically the LCD panel seems to nee
DSI LCD panels describe an initialization sequence in the Video BIOS
Tables using so called MIPI sequences. One possible element in these
sequences is a PMIC specific element of 15 bytes.
Although this is not really an ACPI opregion, the ACPI opregion code is the
closest thing we have. We need to
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #4 from Alex Deucher ---
Can you boot the system without amdgpu loaded (e.g., append
modprobe.blacklist=amdgpu)? Or is this a general platform problem?
--
You are receiving this mail because:
You are the assignee for the bug._
On Wed, Dec 12, 2018 at 7:08 PM Dave Airlie wrote:
>
> On Thu, 13 Dec 2018 at 07:13, Alex Deucher wrote:
> >
> > Hi Dave,
> >
> > Updates for 4.21:
> > - Powerplay updates for newer polaris variants
> > - Add cursor plane update fast path
> > - Enable gpu reset by default on CI parts
> > - Fix co
https://bugzilla.kernel.org/show_bug.cgi?id=201273
--- Comment #20 from Alex Deucher (alexdeuc...@gmail.com) ---
Can you try one of these branches?
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.21-wip
Do they help?
On Fri, Nov 16, 2018 at 10:09:15PM +0530, Jagan Teki wrote:
> Feiyang FY07024DI26A30-D is 1024x600, 4-lane MIPI-DSI LCD panel.
>
> Add panel driver for it.
>
> Signed-off-by: Jagan Teki
> ---
> MAINTAINERS | 6 +
> drivers/gpu/drm/panel/Kconfig
Hi,
On 13-12-18 14:08, Ville Syrjälä wrote:
On Thu, Dec 13, 2018 at 01:40:27PM +0100, Hans de Goede wrote:
Hi,
On 13-12-18 13:14, Ville Syrjälä wrote:
+static int intel_cht_wc_exec_mipi_pmic_seq_element(struct regmap *regmap,
+ const u8 *da
HI,
On 13-12-18 14:45, Jani Nikula wrote:
On Thu, 13 Dec 2018, Hans de Goede wrote:
DSI LCD panels describe an initialization sequence in the Video BIOS
Tables using so called MIPI sequences. One possible element in these
sequences is a PMIC specific element of 15 bytes.
Although this is not
https://bugzilla.kernel.org/show_bug.cgi?id=201585
--- Comment #14 from Alexander Walker (a...@alexwalker.info) ---
Also experiencing this on AMD Vega 56 on 4.20.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 14 ---
drivers/gpu/drm/virtio/virtgpu_display.c | 1 -
drivers/gpu/drm/virtio/virtgpu_drv.c | 9 +-
drivers/gpu/drm/virtio/virtgpu_fb.c | 191 ---
drivers/gpu/drm/virtio/virtgpu_
On Thu, 13 Dec 2018, Hans de Goede wrote:
> Add support for PMIC MIPI sequences using the new
> intel_soc_pmic_exec_mipi_pmic_seq_element function.
>
> This fixes the DSI LCD panel not lighting up when not initialized by the
> GOP (because an external monitor was connected) on GPD win and GPD pock
On Thu, 13 Dec 2018, Ville Syrjälä wrote:
> On Thu, Dec 13, 2018 at 01:40:27PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> On 13-12-18 13:14, Ville Syrjälä wrote:
>> > On Thu, Dec 13, 2018 at 12:21:35PM +0100, Hans de Goede wrote:
>> >> Implement the exec_mipi_pmic_seq_element callback for the CHT W
On Thu, 13 Dec 2018, Hans de Goede wrote:
> DSI LCD panels describe an initialization sequence in the Video BIOS
> Tables using so called MIPI sequences. One possible element in these
> sequences is a PMIC specific element of 15 bytes.
>
> Although this is not really an ACPI opregion, the ACPI opr
https://bugs.freedesktop.org/show_bug.cgi?id=109049
--- Comment #5 from Chris Wilson ---
Regression from
commit 08d1bdd4cc57e89d037205687a61d2b6ff94
Author: Rex Zhu
Date: Wed Oct 24 16:10:33 2018 +0800
drm/amdgpu: Limit vm max ctx number to 4096
driver need to reserve resource f
https://bugs.freedesktop.org/show_bug.cgi?id=109049
Chris Wilson changed:
What|Removed |Added
Summary|[CI][BAT] |[CI][BAT]
|igt@kms_ato
https://bugs.freedesktop.org/show_bug.cgi?id=109049
--- Comment #4 from Chris Wilson ---
Now limited to 4095 contexts. Isn't that a coincidence!
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-de
https://bugs.freedesktop.org/show_bug.cgi?id=109049
Chris Wilson changed:
What|Removed |Added
QA Contact|intel-gfx-bugs@lists.freede |
|sktop.org
Hi, Dave
Two minor fixes for the previous vmwgfx-next pull:
The following changes since commit 9a01135b98b9d5a7033c544245da7aad0d886758:
drm/vmwgfx: Use the standard atomic helpers for page-flip (2018-12-05
10:09:55 +0100)
are available in the Git repository at:
git://people.freedesktop.o
On Thu, Dec 13, 2018 at 01:40:27PM +0100, Hans de Goede wrote:
> Hi,
>
> On 13-12-18 13:14, Ville Syrjälä wrote:
> > On Thu, Dec 13, 2018 at 12:21:35PM +0100, Hans de Goede wrote:
> >> Implement the exec_mipi_pmic_seq_element callback for the CHT Whiskey Cove
> >> PMIC.
> >>
> >> On some CHT devic
Hi Steve,
On Tue, 2018-10-16 at 17:00 -0700, Steve Longerbeam wrote:
> The function ipu_csi_init_interface() was inverting the F-bit for
> NTSC case, in the CCIR_CODE_1/2 registers. The result being that
> for NTSC bottom-top field order, the CSI would swap fields and
> capture in top-bottom order
1 - 100 of 149 matches
Mail list logo
