https://bugzilla.kernel.org/show_bug.cgi?id=201795
thomas.lassdiesonner...@gmx.de changed:
What|Removed |Added
Kernel Version|4.19.4 |4.19.8
--
You are
https://bugzilla.kernel.org/show_bug.cgi?id=201795
--- Comment #10 from thomas.lassdiesonner...@gmx.de ---
Still there with 4.19.8
I know it is probably low priority. Just keeping this report up to date.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #10 from Brian Schott ---
Ignore that previous comment. I'm getting some strange results here and may
have marked a commit with an intermittent crash as "good" while bisecting.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #9 from Brian Schott ---
020aa2ec15fc4a5ffdfcab7dc0db648a137abc41 lets me log in before the system
freezes.
770af5859d6903049b7f39ed4f4e6612b63fd82d locks up before LightDM can start.
I'll do a bit more testing.
--
You are
Hi Uma,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on v4.20-rc6 next-20181214]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Hi,
On Fri, Dec 14, 2018 at 3:58 PM Doug Anderson wrote:
>
> Hi,
>
> On Fri, Dec 14, 2018 at 2:16 PM Jordan Crouse wrote:
> >
> > Add documentation for the interconnect and interconnect-names bindings
> > for the GPU node as detailed by bindings/interconnect/interconnect.txt.
> >
> >
Hi,
On Fri, Dec 14, 2018 at 2:16 PM 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(+)
Looks good to me. This could go into Andy's
Since there are no clients using these threads,
cleaning it up.
changes in v2:
- switch all the dependent clients to use system wq
before removing the disp_threads (Sean Paul)
changes in v3:
- none
changes in v4:
- none
changes in v5:
- Rebase on latest
msm maintains a separate structure to define vblank
work definitions and a list to track events submitted
to the workqueue. We can avoid this redundant list
and its protection mechanism, if we subclass the
work object to encapsulate vblank event parameters.
changes in v2:
- subclass
msm is using msm wq for dispatching commit and vblank
events. Switch idle power collapse feature also to use
msm wq to handle delayed work handlers so that
msm can get rid of redundant display threads.
changes in v2:
- patch introduced in v2
changes in v3:
- none
changes in v4:
DPU was using one thread per display to dispatch async commits and
vblank requests. Since clean up already happened in msm to use the
common thread for all the display commits, display threads are only
used to cater vblank requests. Since a single thread is sufficient
to do the job without any
Hi,
On Fri, Dec 14, 2018 at 2:16 PM Jordan Crouse wrote:
>
> 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
> ---
>
use kthread_destroy_worker to destroy workers and
release their associated kthreads.
changes in v3:
- introduced in the series
changes in v4:
- none
changes in v5:
- none
Signed-off-by: Jeykumar Sankaran
---
drivers/gpu/drm/msm/msm_drv.c | 6 ++
1 file changed, 2
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
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
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/
v2: Fix interconnect supplier to
https://bugs.freedesktop.org/show_bug.cgi?id=109064
Bug ID: 109064
Summary: temp_comp_access::get_required_live_range:
enclosing_scope_first_write is NULL
Product: Mesa
Version: 18.3
Hardware: Other
OS: All
On Fri, Dec 14, 2018 at 11:44:10AM +0100, Lucas Stach wrote:
> Hi Dave,
>
> nothing major this time, mostly some cleanups that were found on the
> way of reworking the code in preparation for new feature additions.
dim: dea492e0cfcbe8ca592406fefc7ceeaf53f63380 is lacking review
dim:
On Sat, Dec 15, 2018 at 02:11:01AM +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
> ---
> Changes for v2:
> - use simple structure for command init
> - update proper comments on power, reset
https://bugs.freedesktop.org/show_bug.cgi?id=108754
Alex Deucher changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=108585
Alex Deucher changed:
What|Removed |Added
See Also||https://bugs.freedesktop.or
https://bugs.freedesktop.org/show_bug.cgi?id=108754
--- Comment #2 from Alex Deucher ---
(In reply to Dan Horák from comment #1)
> Not a problem anymore with 4.20.0-0.rc6.git0.1.fc30.op.1.ppc64le (contains
> the reset fix from https://bugs.freedesktop.org/show_bug.cgi?id=108585#c15)
Should
https://bugs.freedesktop.org/show_bug.cgi?id=108585
--- Comment #18 from Alex Deucher ---
(In reply to Dan Horák from comment #17)
> Fedora/ppc64le users can find a pre-built kernel with the patchset at
> https://copr.fedorainfracloud.org/coprs/sharkcz/talos-kernel/build/817728/
Should these
https://bugs.freedesktop.org/show_bug.cgi?id=109063
Bug ID: 109063
Summary: libdrm amdgpu.ids is missing raven ridge gpu ids
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On 2018-12-11 5:07 p.m., Nick Desaulniers wrote:
> On Tue, Dec 11, 2018 at 1:42 PM Nathan Chancellor
> wrote:
>>
>> On Tue, Dec 11, 2018 at 01:25:00PM -0800, Nick Desaulniers wrote:
>>> On Mon, Dec 10, 2018 at 3:42 PM Nathan Chancellor
>>> wrote:
Clang warns when an expression that
Red and Blue colors will be interchanged on display with
current format maps for RGB565 and BGR565.
Change both format maps to display correct colors.
Signed-off-by: Tanmay Shah
---
drivers/gpu/drm/msm/disp/dpu1/dpu_formats.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
https://bugs.freedesktop.org/show_bug.cgi?id=108992
--- Comment #8 from Alex Deucher ---
Can you bisect?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
On 2018-12-11 5:37 a.m., Chunming Zhou wrote:
> v2: adapt to new transfer ioctl
>
> Signed-off-by: Chunming Zhou
+igt-dev
I think intel-gfx still works for IGT development but most of the IGT work
happens on igt-...@lists.freedesktop.org now.
Harry
> ---
> include/drm-uapi/drm.h | 33
https://bugzilla.kernel.org/show_bug.cgi?id=201991
--- Comment #2 from fin4...@hotmail.com ---
(In reply to nancy from comment #1)
> (In reply to fin4478 from comment #0)
>
> > simple app for the amdgpu sys interface
>
>
>
> You might consider if you are trying out radeon-profile.
>
>
tree: git://people.freedesktop.org/~agd5f/linux.git amd-18.50
head: 88a0039cb034176ee3416dd0c3a49feea2f446ab
commit: a26f88704ef76f0213692b3b04f210de6e9e8676 [1284/1415] drm/scheduler: fix
build error due to change in scheduler struct
config: arm-allmodconfig (attached as .config)
compiler:
On 2018-12-15 00:04, jshek...@codeaurora.org wrote:
On 2018-12-14 23:53, Tanmay Shah wrote:
Red and Blue colors will be interchanged on display with
current format maps for RGB565 and BGR565.
Change both format maps to dispaly correct colors.
spelling: dispaly/display
Signed-off-by:
On 2018-12-14 23:53, Tanmay Shah wrote:
Red and Blue colors will be interchanged on display with
current format maps for RGB565 and BGR565.
Change both format maps to dispaly correct colors.
Signed-off-by: Tanmay Shah
LGTM.
Reviewed-by: Jayant Shekhar
---
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
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
Previous version of the series was here:
https://lists.freedesktop.org/archives/dri-devel/2018-December/200505.html
The only change in this version is dropping the extra LUT size test I
added in v2; Alexandru pointed out that that already gets tested when a
new atomic blob is uploaded.
Matt
https://bugs.freedesktop.org/show_bug.cgi?id=103949
--- Comment #3 from Jerry Zuo ---
The issue is just getting fixed. Will show up soon.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Fri, Dec 14, 2018 at 09:43:08AM +, Alexandru-Cosmin Gheorghe wrote:
...
> > +int drm_color_lut_check(struct drm_property_blob *lut,
> > +uint32_t tests)
> > +{
> > + struct drm_color_lut *entry;
> > + int i;
> > +
> > + if (!lut)
> > + return 0;
> > +
> >
Red and Blue colors will be interchanged on display with
current format maps for RGB565 and BGR565.
Change both format maps to dispaly correct colors.
Signed-off-by: Tanmay Shah
---
drivers/gpu/drm/msm/disp/dpu1/dpu_formats.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
https://bugzilla.kernel.org/show_bug.cgi?id=201991
nancy (nancy...@gmx.com) changed:
What|Removed |Added
CC||nancy...@gmx.com
--- Comment
Remove unused functions and macros from dpu hw interrupts
file.
changes in v2:
Removed clear_interrupt_status (Jordan Crouse)
Signed-off-by: Jayant Shekhar
---
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_interrupts.c | 44 ---
drivers/gpu/drm/msm/disp/dpu1/dpu_hw_interrupts.h |
The pull request you sent on Fri, 14 Dec 2018 11:54:15 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2018-12-14
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/92de1de51e99910ff0b45b340c95994573a1ad23
Thank you!
--
Deet-doot-dot, I am a bot.
Hi,
On Thu, Dec 13, 2018 at 8:41 PM Viresh Kumar wrote:
>
> On 12-12-18, 14:18, Jordan Crouse wrote:
> > + gpu_opp_table: opp-table {
> > + compatible = "operating-points-v2-qcom-level";
>
> I think you need to mention "operating-points-v2" as well
On Fri, Dec 14, 2018 at 05:11:51PM +0100, Daniel Vetter wrote:
> On Fri, Dec 14, 2018 at 04:27:10PM +0900, Inki Dae wrote:
> > 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
On Thu, Dec 13, 2018 at 08:25:42PM -0500, Lyude Paul wrote:
> 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
>*
From: Daniele Castagna
Currently, YUV hardware overlays are converted to RGB using
a color space conversion different than BT.601.
The result is that colors of e.g. NV12 buffers don't match
colors of YUV hardware overlays.
In order to fix this, enable YUV2YUV and set appropriate coefficients
On Fri, Dec 14, 2018 at 02:38:52PM +0100, Andrzej Hajda wrote:
> rr_cache_dir function cannot assume REPO/.git is a directory. On the other
> side it should be backward compatible - if rr-cache directory/link already
> exists it should be returned.
>
> Signed-off-by: Andrzej Hajda
> ---
> Hi,
>
On Fri, Dec 14, 2018 at 02:38:51PM +0100, Andrzej Hajda wrote:
> Assumption that git directory is always located at REPO/.git is incorrect,
> especially in case of git worktrees. There is already function to deal
> with it correctly - git_dir, let's then use it.
>
> Signed-off-by: Andrzej Hajda
Paul Kocialkowski writes:
> Despite what the HVS documentation indicates, the VC4 does not actually
> support SAND tiling modes for any RGB format and only semiplanar YUV420
> formats (NV12/NV21) can be used in these tiling modes.
>
> The driver currently claims to support RGB formats for the
On Fri, Dec 14, 2018 at 04:27:10PM +0900, Inki Dae wrote:
> 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, pulled into drm-next.
-Daniel
>
> Thanks,
> Inki Dae
>
On Fri, Nov 30, 2018 at 05:22:50PM +0530, Jayant Shekhar wrote:
> Alpha enable in the pixel format will help in
> selecting the blend rule. By keeping alpha enable
> to true we are allowing foreground alpha to blend
> with the layer. If alpha is don't care, then we
> should not allow pixel alpha
On Thu, Dec 13, 2018 at 10:51:03AM -0800, Jeykumar Sankaran wrote:
> 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 |
On Fri, Dec 14, 2018 at 02:19:12PM +0530, Jayant Shekhar wrote:
> Remove unused functions and macros from dpu hw interrupts
> file.
>
> Signed-off-by: Jayant Shekhar
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_interrupts.c | 30
>
On Thu, Dec 13, 2018 at 10:51:04AM -0800, Jeykumar Sankaran wrote:
> 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
On Thu, Dec 13, 2018 at 10:51:04AM -0800, Jeykumar Sankaran wrote:
> 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
On Thu, Dec 13, 2018 at 10:51:03AM -0800, Jeykumar Sankaran wrote:
> 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 |
On Fri, Dec 07, 2018 at 06:38:32PM -0800, Jeykumar Sankaran wrote:
> First set of clean up patches for DPU resource manager.
> Removes/realigns some of the redudant RM interfaces.
> Eventual plan is to migrate resource maintenence using
> private state objects.
>
> Thanks and Regards,
> Jeykumar
Just a reminder. Any new comments in light of all the discussion ?
Andrey
On 12/12/2018 08:08 AM, Grodzovsky, Andrey wrote:
> BTW, the problem I pointed out with drm_sched_entity_kill_jobs_cb is not
> an issue with this patch set since it removes the cb from
> s_fence->finished in general so we
On Thu, Dec 06, 2018 at 06:41:43PM -0800, Jeykumar Sankaran wrote:
> Since there are no clients using these threads,
> cleaning it up.
>
> changes in v2:
> - switch all the dependent clients to use system wq
> before removing the disp_threads (Sean Paul)
> changes in v3:
> -
Hi Kevin,
FYI, the error/warning still remains.
tree: git://people.freedesktop.org/~agd5f/linux.git amd-18.50
head: 88a0039cb034176ee3416dd0c3a49feea2f446ab
commit: 7d0741bab20cb328c2c778764efc340896242ccb [790/1415] drm/amdkcl: [RHEL
6] support kmap_atomic funciton for ttm module
config:
tree: git://people.freedesktop.org/~agd5f/linux.git amd-18.50
head: 88a0039cb034176ee3416dd0c3a49feea2f446ab
commit: a26f88704ef76f0213692b3b04f210de6e9e8676 [1284/1415] drm/scheduler: fix
build error due to change in scheduler struct
config: arm64-allmodconfig (attached as .config)
compiler:
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Matt Roper
>Sent: Friday, December 14, 2018 3:25 AM
>To: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org
>Cc: Shankar, Uma ; Sharma, Swati2
>
>Subject: [PATCH v2 2/2]
>-Original Message-
>From: Roper, Matthew D
>Sent: Friday, December 14, 2018 3:25 AM
>To: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org
>Cc: Roper, Matthew D ; Shankar, Uma
>; Sharma, Swati2 ; Brian
>Starkey
>Subject: [PATCH v2 1/2] drm: Add color management LUT
From: Thara Gopinath
This patch replaces jiffies based accoutning for runtime_active_time
and runtime_suspended_time with ktime base accounting. This makes the
runtime debug counters inline with genpd and other pm subsytems which
uses ktime based accounting.
Signed-off-by: Thara Gopinath
[move
On Tue, Dec 04, 2018 at 05:49:12PM +, Liviu Dudau wrote:
> On Mon, Dec 03, 2018 at 11:32:01AM +, Ayan Halder wrote:
> > The constraints are as follows (for Mali-DP 500, 550, 650) :-
> >
> > 1. AFBC is not supported for the formats defined in
> > malidp_hw_format_is_linear_only()
> >
> >
With jiffies been replaced by raw ns in PM core accounting, 915 driver is
updated to use this new time infrastructure.
Signed-off-by: Vincent Guittot
---
drivers/gpu/drm/i915/i915_pmu.c | 12 ++--
drivers/gpu/drm/i915/i915_pmu.h | 4 ++--
2 files changed, 8 insertions(+), 8
pm runtime uses the timer infrastructure for autosuspend. This implies that
the minimum time before autosuspending a device is in the range
of 1 tick included to 2 ticks excluded
-On arm64 this means between 4ms and 8ms with default jiffies configuration
-And on arm, it is between 10ms and 20ms
Move pm_runtime on hrtimer and raw ns time to get finer granularity
Patch 1 moves runtime_pm autosuspend on hrtimer framework
Patch 2 moves time accounting on raw ns. This patch initially used
ktime instead of raw ns but it was easier to move i915 driver on raw ns
than on ktime
Patch 3 fixes
On Fri, Dec 14, 2018 at 04:35:11PM +0530, Jagan Teki wrote:
> On Fri, Dec 14, 2018 at 1:25 AM Sean Paul wrote:
> >
> > 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,
Despite what the HVS documentation indicates, the VC4 does not actually
support SAND tiling modes for any RGB format and only semiplanar YUV420
formats (NV12/NV21) can be used in these tiling modes.
The driver currently claims to support RGB formats for the associated
modifiers, so remove them
On Tue, Dec 04, 2018 at 04:57:46PM +, Liviu Dudau wrote:
Hi Liviu,
> On Mon, Dec 03, 2018 at 11:32:00AM +, Ayan Halder wrote:
> > We have added some new formats to be supported on DP500/DP550/DP650.
>
> Make a bit more descriptive commit message here, please!
>
I will keep the following
https://bugs.freedesktop.org/show_bug.cgi?id=107826
Jeremy Newton changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #4 from Jeremy
https://bugzilla.kernel.org/show_bug.cgi?id=201991
Bug ID: 201991
Summary: amdgpu: clock management is disabled for the 4K
resolution with polaris 10
Product: Drivers
Version: 2.5
Kernel Version: 4.18.0,4.20.0-rc6,
Hi Kevin,
FYI, the error/warning still remains.
tree: git://people.freedesktop.org/~agd5f/linux.git amd-18.50
head: 88a0039cb034176ee3416dd0c3a49feea2f446ab
commit: 7d0741bab20cb328c2c778764efc340896242ccb [790/1415] drm/amdkcl: [RHEL
6] support kmap_atomic funciton for ttm module
config:
On Tue, Dec 04, 2018 at 04:50:51PM +, Liviu Dudau wrote:
Hi Liviu,
Please let me know if you agree with my comments. Then I will send a
v4 patch for this.
> On Mon, Dec 03, 2018 at 11:31:58AM +, Ayan Halder wrote:
> > Added the AFBC decoder registers for DP500 , DP550 and DP650.
> >
Hi all,
This small patchset fixes issues with dim used on git worktree's. It was not
widely tested - as I am little bit afraid to break drm infrastructure, and
I do not know if and how it interacts with other maintainer tools.
Especially in case of the last patch I am not sure what I am really
Assumption that git directory is always located at REPO/.git is incorrect,
especially in case of git worktrees. There is already function to deal
with it correctly - git_dir, let's then use it.
Signed-off-by: Andrzej Hajda
---
dim | 13 -
1 file changed, 4 insertions(+), 9
git_dir function returns git directory for current working directory.
Allowing specifying any directory allows to reuse it more widely.
Signed-off-by: Andrzej Hajda
---
dim | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/dim b/dim
index 70939ff..df66c58 100755
---
rr_cache_dir function cannot assume REPO/.git is a directory. On the other
side it should be backward compatible - if rr-cache directory/link already
exists it should be returned.
Signed-off-by: Andrzej Hajda
---
Hi,
I am not sure of the purpose of rr-cache symbolic link, dim does not use
it
Hi Thierry,
can you please have a look at this one?
Regards,
Lucas
Am Montag, den 12.11.2018, 18:41 +0100 schrieb Lucas Stach:
> The horizontal blanking periods are too short, as the values are
> specified for a single LVDS channel. Since this panel is dual LVDS
> they need to be doubled. With
https://bugs.freedesktop.org/show_bug.cgi?id=107826
--- Comment #3 from qnerd ---
Thank you, that clears the situation.
I am aware of using the all-open variant using PRIME,
and indeed it does work quite nicely.
What about OpenCl though?
Can you get away using the all-open driver and just
https://bugs.freedesktop.org/show_bug.cgi?id=108919
--- Comment #12 from Adam Lyall ---
Just adding this same bug affects Tonga based GPUs as well.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Thu, 06 Dec 2018, Daniel Thompson wrote:
> On Wed, Dec 05, 2018 at 01:50:44PM -0600, Rob Herring wrote:
> > Convert string compares of DT node names to use of_node_name_eq helper
> > instead. This removes direct access to the node name pointer.
> >
> > For instances using of_node_cmp, this
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
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.
Reviewed-by: Mika
Hi All,
The main reason for sending out this v5 is because the CI failed v4
(even though it liked v1-v3 and nothing significant changed), this
was likely a false positive, so the main goal of this version is to give
this another CI run.
Besides that I've dropped the unnecessary #include from the
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
Am Freitag, 30. November 2018, 14:42:58 CET schrieb Neil Armstrong:
> From: Zheng Yang
>
> To get input/output bus_format/enc_format dynamically, this patch
> introduce following funstion in plat_data:
> - get_input_bus_format
> - get_output_bus_format
> - get_enc_in_encoding
>
Am Freitag, 30. November 2018, 14:42:57 CET schrieb Neil Armstrong:
> In order to support the HDMI2.0 YUV420 display modes, this patch
> adds support for the YUV420 TMDS Clock divided by 2 and the controller
> passthrough mode.
>
> YUV420 Synopsys PHY support will need some specific configuration
Am Freitag, 30. November 2018, 14:42:59 CET schrieb Neil Armstrong:
> Now the DW-HDMI Controller supports the HDMI2.0 modes, enable support
> for these modes in the connector if the platform supports them.
> We limit these modes to DW-HDMI IP version >= 0x200a which
> are designed to support
Am Freitag, 30. November 2018, 14:42:54 CET schrieb Neil Armstrong:
> Add support for SCDC Setup for TMDS Clock > 3.4GHz and enable TMDS
> Scrambling when supported or mandatory.
>
> This patch also adds an helper to setup the control bit to support
> the high TMDS Bit Period/TMDS Clock-Period
On Fri, Dec 14, 2018 at 12:05 PM Mika Westerberg
wrote:
>
> On Fri, Dec 14, 2018 at 11:48:35AM +0100, Hans de Goede wrote:
> > > > +#include
> > >
> > > Why is this include needed?
> >
> > It is no longer needed in v4, since the parsing of the raw
> > MIPI sequence data (which needed this
Hi,
On 14-12-18 10:49, Mika Westerberg wrote:
On Thu, Dec 13, 2018 at 04:35:32PM +0100, Hans de Goede wrote:
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,
On Fri, Dec 14, 2018 at 6:19 PM Chris Wilson wrote:
>
> Ta, I did not know of that relationship. Perfect details for the
> changelog to explain how this does improve page reclaim even in the
> absence of a GEM shrinker. :)
OK, I will update the changelog.
Hi Dave,
nothing major this time, mostly some cleanups that were found on the
way of reworking the code in preparation for new feature additions.
Regards,
Lucas
The following changes since commit 6fce3a406108ee6c8a61e2a33e52e9198a626ea0:
drm/etnaviv: fix bogus fence complete check in timeout
Quoting Kuo-Hsin Yang (2018-12-14 10:09:11)
> On Fri, Dec 14, 2018 at 5:51 PM Chris Wilson wrote:
> >
> > Quoting Kuo-Hsin Yang (2018-12-14 09:33:19)
> > > On Fri, Dec 14, 2018 at 4:59 PM Chris Wilson
> > > wrote:
> > > >
> > > >
> > > > Do you have a driver in mind (msm?) to demonstrate the
On Fri, Dec 14, 2018 at 5:51 PM Chris Wilson wrote:
>
> Quoting Kuo-Hsin Yang (2018-12-14 09:33:19)
> > On Fri, Dec 14, 2018 at 4:59 PM Chris Wilson
> > wrote:
> > >
> > >
> > > Do you have a driver in mind (msm?) to demonstrate the use case?
> >
> > On Samsung Chromebook Plus, the drm/rockchip
Quoting Kuo-Hsin Yang (2018-12-14 09:33:19)
> On Fri, Dec 14, 2018 at 4:59 PM Chris Wilson wrote:
> >
> >
> > Do you have a driver in mind (msm?) to demonstrate the use case?
>
> On Samsung Chromebook Plus, the drm/rockchip driver may call
> rockchip_gem_get_pages()/drm_gem_get_pages() to pin a
Hi,
On Thu, Dec 13, 2018 at 01:55:25PM -0800, Matt Roper wrote:
> 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.
On Thu, Dec 13, 2018 at 08:25:33PM -0500, Lyude Paul wrote:
> 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
Reviewed-by: Daniel Vetter
>
Am 14.12.18 um 09:41 schrieb Daniel Vetter:
On Fri, Dec 14, 2018 at 08:41:34AM +0100, Christian König wrote:
Fix a broken build because of a typo in
"drm/scheduler: Add drm_sched_suspend/resume_timeout()".
Signed-off-by: Christian König
Maybe core and cross-driver changes should go in
1 - 100 of 114 matches
Mail list logo
