Den 11.08.2019 18.41, skrev Sam Ravnborg:
> Hi Noralf.
>
> On Thu, Aug 01, 2019 at 03:52:49PM +0200, Noralf Trønnes wrote:
>> Add support for panels that use the DPI interface.
>> ILI9341 has onboard RAM so the assumption made here is that all such
>> panels support pixel upload over DBI.
>>
>>
Den 11.08.2019 17.24, skrev Sam Ravnborg:
> Hi Noralf.
>
> Most feedback on this driver was covered in comment to 1/4.
> Only a few things caught my eye.
>
> On Thu, Aug 01, 2019 at 03:52:47PM +0200, Noralf Trønnes wrote:
>> Move the driver to drm/panel and take advantage of the new panel
https://bugzilla.kernel.org/show_bug.cgi?id=204559
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
Quoting Koenig, Christian (2019-08-12 15:50:59)
> Am 12.08.19 um 16:43 schrieb Chris Wilson:
> > Quoting Koenig, Christian (2019-08-12 15:34:32)
> >> Am 10.08.19 um 17:34 schrieb Chris Wilson:
> >>> Move the duplicated code within dma-fence.c into the header for wider
> >>> reuse. In the process
Den 11.08.2019 16.16, skrev Sam Ravnborg:
> Hi Noralf.
>
> I really like how this allows us to have a single file for all
> the uses of a driver IC.
> And this patch-set is much easier to grasp than the first RFC.
>
> General things:
>
> - The current design have a tight connection between
On Fri, 09 Aug 2019, Guido Günther wrote:
> This adds all the gpr registers and the define needed for selecting
> the input source in the imx-nwl drm bridge.
>
> Signed-off-by: Guido Günther
> ---
> include/linux/mfd/syscon/imx8mq-iomuxc-gpr.h | 62
> 1 file changed, 62
On Sun, Aug 11, 2019 at 07:08:01PM -0500, Gustavo A. R. Silva wrote:
> Add suffix ULL to constant 1000 in order to avoid a potential integer
> overflow and give the compiler complete information about the proper
> arithmetic to use. Notice that this constant is being used in a context
> that
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #80 from Tom B ---
> I tried something like that before but a huge portion of the commits in that
> range won't build kernels that can boot (at least on my system). I ended up
> resorting to trying reverting individual
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #85 from Mauro Gaspari ---
(In reply to Pierre-Eric Pelloux-Prayer from comment #84)
> (In reply to Mauro Gaspari from comment #82)
> > (In reply to Pierre-Eric Pelloux-Prayer from comment #81)
> > > Can anyone provide a
Am 10.08.19 um 17:34 schrieb Chris Wilson:
> Move the duplicated code within dma-fence.c into the header for wider
> reuse. In the process apply a small micro-optimisation to only prune the
> fence->cb_list once rather than use list_del on every entry.
>
> Signed-off-by: Chris Wilson
> Cc: Tvrtko
https://bugs.freedesktop.org/show_bug.cgi?id=111386
Bug ID: 111386
Summary: Mesa 19.1.1 introduced Tearing
Product: Mesa
Version: 19.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
https://bugzilla.kernel.org/show_bug.cgi?id=204559
Bug ID: 204559
Summary: amdgpu: kernel oops with constant gpu resets while
using mpv
Product: Drivers
Version: 2.5
Kernel Version: 5.2.7
Hardware: x86-64
On Tue, Aug 06, 2019 at 06:31:56AM +, Lowry Li (Arm Technology China) wrote:
> From: "Lowry Li (Arm Technology China)"
>
> The drm_format_info doesn't have any cpp or block_size (both are zero)
> information for arm only afbc format YU08/YU10. we need to compute it
> by ourselves.
>
>
Den 11.08.2019 19.02, skrev Sam Ravnborg:
> Hi Noralf.
>
> On Thu, Aug 01, 2019 at 03:52:49PM +0200, Noralf Trønnes wrote:
>> Add support for panels that use the DPI interface.
>> ILI9341 has onboard RAM so the assumption made here is that all such
>> panels support pixel upload over DBI.
>>
>>
Provide the eld to the generic hdmi-codec driver.
This will let the driver enforce the maximum channel number and set the
channel allocation depending on the hdmi sink.
Cc: Jonas Karlman
Signed-off-by: Jerome Brunet
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi-audio.h | 1 +
https://bugzilla.kernel.org/show_bug.cgi?id=203471
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
From: Sean Paul
Fixes the following warnings:
../drivers/gpu/drm/drm_connector.c:989: WARNING: Unexpected indentation.
../drivers/gpu/drm/drm_connector.c:993: WARNING: Unexpected indentation.
../include/drm/drm_connector.h:544: WARNING: Inline interpreted text or phrase
reference start-string
Would one of you mind pushing? I don't have drm-misc commit bits.
On Mon, Aug 12, 2019 at 9:22 AM Jason Ekstrand wrote:
> This patch only brings the syncobj documentation up-to-date for the
> original form of syncobj. It does not contain any information about the
> design of timeline
This patch only brings the syncobj documentation up-to-date for the
original form of syncobj. It does not contain any information about the
design of timeline syncobjs.
v2: Incorporate feedback from Lionel and Christian:
- Mention actual ioctl and flag names
- Better language around reference
https://bugs.freedesktop.org/show_bug.cgi?id=22
--- Comment #15 from Chí-Thanh Christopher Nguyễn ---
It seems that the graphics corruption on my Dell Latitude 5495 with kernel 5.2
is a different issue. Kai-Heng Feng bisected and identified this in the Ubuntu
Launchpad tracker already.
Fixed two -Wunused-but-set-variable warnings:
/arm/linux/display/aosp-4.14-drm-next/drivers/gpu/drm/arm/display/komeda/komeda_kms.c:
In function ‘komeda_crtc_normalize_zpos’:
/arm/linux/display/aosp-4.14-drm-next/drivers/gpu/drm/arm/display/komeda/komeda_kms.c:150:26:
warning: variable ‘fb’ set
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #2 from Maxim Sheviakov (shoeg...@tutanota.com) ---
Created attachment 284337
--> https://bugzilla.kernel.org/attachment.cgi?id=284337=edit
journalctl --dmesg output
As I can't run dmesg after the system's hung, here's journalctl
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #4 from Alex Deucher (alexdeuc...@gmail.com) ---
Looks like your system has two GPUs. Can you try booting with amdgpu.runpm=0?
Does that fix the issue?
--
You are receiving this mail because:
You are watching the assignee of the
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #81 from Tom B ---
Created attachment 145038
--> https://bugs.freedesktop.org/attachment.cgi?id=145038=edit
5.2.7 dmesg with hard_min_level logged
As mentioned in the previous post, I started logging the value of
hard_min_level.
Am 12.08.19 um 16:43 schrieb Chris Wilson:
> Quoting Koenig, Christian (2019-08-12 15:34:32)
>> Am 10.08.19 um 17:34 schrieb Chris Wilson:
>>> Move the duplicated code within dma-fence.c into the header for wider
>>> reuse. In the process apply a small micro-optimisation to only prune the
>>>
On Wed, Aug 7, 2019 at 2:11 PM Souptick Joarder wrote:
>
> On Wed, Jul 31, 2019 at 12:59 AM Souptick Joarder
> wrote:
> >
> > This is dead code since 3.15. If there is no plan to use
> > it further, this can be removed forever.
> >
>
> Any comment on this patch ?
Any comment on this patch ?
>
Provide the eld to the generic hdmi-codec driver.
This will let the driver enforce the maximum channel number and set the
channel allocation depending on the hdmi sink.
Cc: Jonas Karlman
Signed-off-by: Jerome Brunet
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi-audio.h | 1 +
Set the number of channel in the infoframes
Reviewed-by: Jonas Karlman
Signed-off-by: Jerome Brunet
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
b/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
index
Enable the i2s lanes depending on the number of channel in the stream
Reviewed-by: Jonas Karlman
Signed-off-by: Jerome Brunet
---
.../gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 15 ++-
drivers/gpu/drm/bridge/synopsys/dw-hdmi.h | 6 +-
2 files changed, 19
Properly setup the channel count and layout in dw-hdmi i2s driver so
we are not limited to 2 channels.
Also correct the maximum channel reported by the DAI from 6 to 8 ch
Reviewed-by: Jonas Karlman
Signed-off-by: Jerome Brunet
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 3 ++-
1
Part of the channel count setup done in dw-hdmi ahb should
actually be done whatever the interface providing the data.
Reviewed-by: Jonas Karlman
Let's move it to dw-hdmi driver instead.
Signed-off-by: Jerome Brunet
---
.../drm/bridge/synopsys/dw-hdmi-ahb-audio.c | 20 +++-
The dw-hdmi-i2s supports more formats than just regular i2s.
Add support for left justified, right justified and dsp modes
A and B.
Reviewed-by: Jonas Karlman
Signed-off-by: Jerome Brunet
---
.../drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 26 ---
Hi,
On 12/08/2019 14:07, Jerome Brunet wrote:
> The purpose of this patchset is to improve the support of the i2s
> interface of the synopsys hdmi controller.
>
> Once applied, the interface should support all the usual i2s bus formats,
> 8 channels playback and properly setup the channel number
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #3 from Alex Deucher (alexdeuc...@gmail.com) ---
You can fetch the output before the hang.
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel
Quoting Koenig, Christian (2019-08-12 15:34:32)
> Am 10.08.19 um 17:34 schrieb Chris Wilson:
> > Move the duplicated code within dma-fence.c into the header for wider
> > reuse. In the process apply a small micro-optimisation to only prune the
> > fence->cb_list once rather than use list_del on
Acked-by: Andrey Grodzovsky
Andrey
On 8/9/19 11:31 AM, Christian König wrote:
> The spsc_queue_peek function is accessing queue->head which belongs to
> the consumer thread and shouldn't be accessed by the producer
>
> This is fixing a rare race condition when destroying entities.
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #84 from ReddestDream ---
>Need to figure out what exactly what is generating the line "[drm] Initialized
>amdgpu 3.27.0 20150101 for :44:00.0 on minor 0."
That "Initialized amdgpu" message seems to be coming from here:
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #87 from Tom B ---
> Could be we've got a race condition between the powerplay setup and amdgpu
handing off the card to drm_dev_register to advertise it for normal use.
The question then becomes: Why doesn't the race condition
Am 12.08.19 um 17:42 schrieb Chris Wilson:
> During release of the syncpt, we remove it from the list of syncpt and
> the tree, but only if it is not already been removed. However, during
> signaling, we first remove the syncpt from the list. So, if we
> concurrently free and signal the syncpt,
Add myself as maintainer of KUnit, the Linux kernel's unit testing
framework.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
MAINTAINERS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
From: Avinash Kondareddy
Add unit tests for KUnit managed resources. KUnit managed resources
(struct kunit_resource) are resources that are automatically cleaned up
at the end of a KUnit test, similar to the concept of devm_* managed
resources.
Signed-off-by: Avinash Kondareddy
Signed-off-by:
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: d3862e44daa7 dma-buf/sw-sync: Fix locking around sync_timeline
lists.
The bot has tested the following trees: v5.2.8, v4.19.66, v4.14.138, v4.9.189.
v5.2.8: Build OK!
v4.19.66:
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #83 from ReddestDream ---
> Here's what I found: The value of hard_min_level is 1001 in both 5.0.13 and
> 5.2.7 so the issue is not the value from the dpm table. The dpm table is
> probably correct.
Fantastic! Glad you tested
During release of the syncpt, we remove it from the list of syncpt and
the tree, but only if it is not already been removed. However, during
signaling, we first remove the syncpt from the list. So, if we
concurrently free and signal the syncpt, the free may decide that it is
not part of the tree
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #5 from Maxim Sheviakov (shoeg...@tutanota.com) ---
Created attachment 284341
--> https://bugzilla.kernel.org/attachment.cgi?id=284341=edit
dmesg -w without runpm parameter
Here's the whole dmesg from a fresh boot up until the
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #85 from Tom B ---
> Yeah. I've had boots where I have my 2 4K DP monitors in and I don't get
> powerplay error on boot. In fact, it can go a bit and seem stable.
In addition to that, vega20_set_fclk_to_highest_dpm_level is
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #88 from ReddestDream ---
>The question then becomes: Why doesn't the race condition happen with only one
>screen? Perhaps it's a matter of speed. With a single display, the driver
>detect the displays, read/parse the EDID data,
Hi Inki.
Any plans to take this to the exynos tree?
Sam
On Sat, Aug 03, 2019 at 04:57:35PM +0200, Sam Ravnborg wrote:
> There was a few uses of drmP that was missed in the last
> patch removing this header from exynos.
>
> Remove the final uses of this header.
>
> Signed-off-by: Sam
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #8 from Alex Deucher (alexdeuc...@gmail.com) ---
(In reply to Maxim Sheviakov from comment #7)
> By the way, how *exactly* does disabling runpm affect the system? Does it
> leave the discrete GPU always-on or vice verse? Or does it
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #90 from Tom B ---
I'm not sure this is helpful but I managed to somewhat test the race condition
theory.
If you follow the callstack:
vega20_set_fclk_to_highest_dpm_level -> smum_send_msg_to_smc_with_parameter ->
On Sat, Aug 10, 2019 at 5:10 PM Laurent Pinchart
wrote:
>
> The 'toppoly' vendor prefix is in use and refers to TPO, whose DT vendor
> prefix is already defined as 'tpo'. Add 'toppoly' as an alternative and
> document it as legacy.
>
> Signed-off-by: Laurent Pinchart
> ---
> Changes since v1:
>
Applied. thanks!
Alex
On Mon, Aug 5, 2019 at 6:29 AM Colin King wrote:
>
> From: Colin Ian King
>
> The check on ret is duplicated in two places, it is redundant code.
> Remove it.
>
> Addresses-Coverity: ("Logically dead code")
> Fixes: b94afb61cdae ("drm/amd/powerplay: honor hw limit on
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #6 from Maxim Sheviakov (shoeg...@tutanota.com) ---
Created attachment 284345
--> https://bugzilla.kernel.org/attachment.cgi?id=284345=edit
dmesg -w with runpm=0 parameter
I have left my laptop with a video playing for about half
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #7 from Maxim Sheviakov (shoeg...@tutanota.com) ---
By the way, how *exactly* does disabling runpm affect the system? Does it leave
the discrete GPU always-on or vice verse? Or does it vary on each system?
I have tried running The
https://bugzilla.kernel.org/show_bug.cgi?id=204559
--- Comment #9 from Maxim Sheviakov (shoeg...@tutanota.com) ---
Thanks for your explanation. By the way, disabling runpm also seems to fix the
other issue with disabling the display after activating the lockscreen as a
powersaving measure.
Is
KUnit is a new unit testing framework for the kernel and when used is
built into the kernel as a part of it. Add KUnit to the root Kconfig and
Makefile to allow it to be actually built.
Signed-off-by: Brendan Higgins
Acked-by: Masahiro Yamada
Cc: Michal Marek
Reviewed-by: Greg Kroah-Hartman
Add support for assertions which are like expectations except the test
terminates if the assertion is not satisfied.
The idea with assertions is that you use them to state all the
preconditions for your test. Logically speaking, these are the premises
of the test case, so if a premise isn't true,
A number of test features need to do pretty complicated string printing
where it may not be possible to rely on a single preallocated string
with parameters.
So provide a library for constructing the string as you go similar to
C++'s std::string. string_stream is really just a string builder,
## TL;DR
This revision removes dependence on kunit_stream in favor of
kunit_assert, as suggested by Stephen Boyd. kunit_assert provides a more
structured interface for constructing messages and allows most required
data to be stored on the stack for most expectations until it is
determined that a
Create a common API for test managed resources like memory and test
objects. A lot of times a test will want to set up infrastructure to be
used in test cases; this could be anything from just wanting to allocate
some memory to setting up a driver stack; this defines facilities for
creating "test
Add support for expectations, which allow properties to be specified and
then verified in tests.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
include/kunit/test.h | 843 +++
kunit/test.c | 58
Add core facilities for defining unit tests; this provides a common way
to define test cases, functions that execute code which is under test
and determine whether the code under test behaves as expected; this also
provides a way to group together related test cases in test suites (here
we call
Add documentation for KUnit, the Linux kernel unit testing framework.
- Add intro and usage guide for KUnit
- Add API reference
Signed-off-by: Felix Guo
Signed-off-by: Brendan Higgins
Cc: Jonathan Corbet
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
Add entry for the new proc sysctl KUnit test to the PROC SYSCTL section,
and add Iurii as a maintainer.
Signed-off-by: Brendan Higgins
Cc: Iurii Zaikin
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
Acked-by: Luis Chamberlain
---
MAINTAINERS | 2 ++
1 file changed, 2
From: Felix Guo
The ultimate goal is to create minimal isolated test binaries; in the
meantime we are using UML to provide the infrastructure to run tests, so
define an abstract way to configure and run tests that allow us to
change the context in which tests are built without affecting the
Fix the following warning seen on GCC 7.3:
kunit/test-test.o: warning: objtool: kunit_test_unsuccessful_try() falls
through to next function kunit_test_catch()
kunit_try_catch_throw is a function added in the following patch in this
series; it allows KUnit, a unit testing framework for the
Add `struct kunit_assert` and friends which provide a structured way to
capture data from an expectation or an assertion (introduced later in
the series) so that it may be printed out in the event of a failure.
Signed-off-by: Brendan Higgins
---
include/kunit/assert.h | 183
Add a test for string stream along with a simpler example.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
kunit/Kconfig | 21 +
kunit/Makefile | 4 ++
kunit/example-test.c | 88
From: Iurii Zaikin
KUnit tests for initialized data behavior of proc_dointvec that is
explicitly checked in the code. Includes basic parsing tests including
int min/max overflow.
Signed-off-by: Iurii Zaikin
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan
Add KUnit tests for the KUnit test abort mechanism (see preceding
commit). Add tests both for general try catch mechanism as well as
non-architecture specific mechanism.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
kunit/Makefile| 3 +-
Add support for aborting/bailing out of test cases, which is needed for
implementing assertions.
An assertion is like an expectation, but bails out of the test case
early if the assertion is not met. The idea with assertions is that you
use them to state all the preconditions for your test.
Add defconfig for UML and a fragment that can be used to configure other
architectures for building KUnit tests. Add option to kunit_tool to use
a defconfig to create the kunitconfig.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
---
On Mon, Aug 12, 2019 at 02:13:54PM +0200, Noralf Trønnes wrote:
> Den 11.08.2019 18.41, skrev Sam Ravnborg:
> > On Thu, Aug 01, 2019 at 03:52:49PM +0200, Noralf Trønnes wrote:
> >> Add support for panels that use the DPI interface.
> >> ILI9341 has onboard RAM so the assumption made here is that
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #82 from Tom B ---
In addition, I will note that the file vega20_baco.c has been added in 5.1
details: https://www.phoronix.com/scan.php?page=news_item=AMD-Vega-12-BACO
commit:
On Thu, Aug 8, 2019 at 10:55 AM Neil Armstrong wrote:
>
> The amlogic,meson-dw-hdmi.txt and amlogic,meson-vpu.txt has been
> converted to YAML schemas, update MAINTAINERS to match them again.
>
> Signed-off-by: Neil Armstrong
> ---
> MAINTAINERS | 4 ++--
> 1 file changed, 2 insertions(+), 2
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #89 from Tom B ---
> It should return -EINVAL instead. Maybe then it would reset and try again
> instead of just ignoring it and continuing with initialization anyway,
> leading to instability.
If you look at
https://bugzilla.kernel.org/show_bug.cgi?id=203471
--- Comment #15 from Haxk20 (haxk...@gmail.com) ---
I have tried manually patching 5.3rc4 and even compiling drm-next-5.4 branch
but sadly i still get tearing on the screen.
Is there a config option to enable it or its enabled by default ?
And as
Hi Laurent/Noralf.
On Mon, Aug 12, 2019 at 06:35:42PM +0300, Laurent Pinchart wrote:
> On Mon, Aug 12, 2019 at 02:13:54PM +0200, Noralf Trønnes wrote:
> > Den 11.08.2019 18.41, skrev Sam Ravnborg:
> > > On Thu, Aug 01, 2019 at 03:52:49PM +0200, Noralf Trønnes wrote:
> > >> Add support for panels
Hi Noralf.
> > - drm_panel has proper support for modes.
> > This is today duplicated in mipi_dbi.
> > Could we make it so that when a panel is used then the panel
> > has the mode info - as we then use the panel more in the way we do
> > in other cases?
> > As it is now the mode is
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #91 from ReddestDream ---
>It returns 0 on success and -EIO on failure, which is then in turn returned
>from vega20_set_fclk_to_highest_dpm_leve. Where did you see the check/retry on
>EINVAL? Perhaps -EIO should be -EINVAL?
I
Applied. thanks!
Alex
On Sat, Aug 10, 2019 at 9:55 AM Christophe JAILLET
wrote:
>
> This should be 'dce_audio_mask', not 'dce_aduio_mask'.
>
> Signed-off-by: Christophe JAILLET
> ---
> drivers/gpu/drm/amd/display/dc/dce/dce_audio.c | 2 +-
>
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #86 from ReddestDream ---
>In addition to that, vega20_set_fclk_to_highest_dpm_level is called several
>times before the card is initialized and even on 5.2.7 works. Something
>happens during or just before the initialization
Hi Thomas,
On Fri, Aug 09, 2019 at 04:12:29PM +0800, Rong Chen wrote:
> Hi,
>
> >>Actually we run the benchmark as a background process, do we need to
> >>disable the cursor and test again?
> >There's a worker thread that updates the display from the shadow buffer.
> >The blinking cursor
https://bugs.freedesktop.org/show_bug.cgi?id=22
--- Comment #14 from Chí-Thanh Christopher Nguyễn ---
Created attachment 145035
--> https://bugs.freedesktop.org/attachment.cgi?id=145035=edit
screenshot
Setting AMD_DEBUG="nodcc" system-wide via /etc/profile will help against GUI
freeze,
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #84 from Pierre-Eric Pelloux-Prayer
---
(In reply to Mauro Gaspari from comment #82)
> (In reply to Pierre-Eric Pelloux-Prayer from comment #81)
> > Can anyone provide a apitrace/renderdoc capture that can reliably reproduce
> >
On Thu, 25 Jul 2019, Paul Cercueil wrote:
> It has been replaced with the ingenic-iio driver for the ADC.
>
> Signed-off-by: Paul Cercueil
> Tested-by: Artur Rojek
> ---
> drivers/mfd/Kconfig | 9 --
> drivers/mfd/Makefile | 1 -
> drivers/mfd/jz4740-adc.c | 324
On Wed, Jul 31, 2019 at 02:43:42PM +0200, Greg Kroah-Hartman wrote:
> Platform drivers now have the option to have the platform core create
> and remove any needed sysfs attribute files. So take advantage of that
> and do not register "by hand" a bunch of sysfs files.
>
> Cc: Bartlomiej
On 8/9/19 9:55 PM, Arnd Bergmann wrote:
> On Fri, Aug 9, 2019 at 4:36 PM Bartlomiej Zolnierkiewicz
> wrote:
>> On 8/9/19 1:43 PM, Arnd Bergmann wrote:
>
>>>
>>> That would have been ok as well, but having the addition here was
>>> intentional and seems more logical to me as this is where the
On Mon, Aug 12, 2019 at 03:54:03PM +0800, Chen-Yu Tsai wrote:
> On Mon, Aug 12, 2019 at 3:45 PM Jernej Škrabec
> wrote:
> >
> > Dne torek, 06. avgust 2019 ob 17:57:39 CEST je meg...@megous.com napisal(a):
> > > From: Ondrej Jirman
> > >
> > > This series implements support for Xunlong Orange Pi
On Tue, 23 Jul 2019, Andy Shevchenko wrote:
> Use use fwnode_property_count_uXX() directly, that makes code neater.
>
> Signed-off-by: Andy Shevchenko
> ---
> drivers/video/backlight/lm3630a_bl.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Applied, thanks.
--
Lee Jones [李琼斯]
On Wed, 24 Jul 2019, Christophe JAILLET wrote:
> The description passed to 'devm_gpio_request_one()' should be related to
> LMS283GF05, not LMS285GF05.
>
> Signed-off-by: Christophe JAILLET
> ---
> drivers/video/backlight/lms283gf05.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Dne torek, 06. avgust 2019 ob 17:57:39 CEST je meg...@megous.com napisal(a):
> From: Ondrej Jirman
>
> This series implements support for Xunlong Orange Pi 3 board. There
> are only a few patches remaining.
>
> - ethernet support - just a DT change (patch 1)
> - HDMI support (patches 2-4)
>
>
On Sat, 10 Aug 2019 at 16:36, Chris Wilson wrote:
>
> Same as for the individual fences, we want to report the actual status
> of the fence when queried.
>
> Reported-by: Petri Latvala
> Signed-off-by: Chris Wilson
> Cc: Sumit Semwal
> Cc: Gustavo Padovan
> Cc: Petri Latvala
Reviewed-by:
On Tue, Aug 6, 2019 at 11:57 PM wrote:
>
> From: Ondrej Jirman
>
> Orange Pi 3 has two regulators that power the Realtek RTL8211E. According
> to the phy datasheet, both regulators need to be enabled at the same time,
> but we can only specify a single phy-supply in the DT.
>
> This can be
When test-compiling the BCM2835 pin control driver on m68k:
In file included from arch/m68k/include/asm/io_mm.h:32:0,
from arch/m68k/include/asm/io.h:8,
from include/linux/io.h:13,
from include/linux/irq.h:20,
On Mon, Aug 12, 2019 at 3:45 PM Jernej Škrabec wrote:
>
> Dne torek, 06. avgust 2019 ob 17:57:39 CEST je meg...@megous.com napisal(a):
> > From: Ondrej Jirman
> >
> > This series implements support for Xunlong Orange Pi 3 board. There
> > are only a few patches remaining.
> >
> > - ethernet
Hi, Jitao:
On Sun, 2019-08-11 at 18:40 +0800, Jitao Shi wrote:
> Config the different CMDQ reg address in driver data.
>
> Signed-off-by: Jitao Shi
> ---
> drivers/gpu/drm/mediatek/mtk_dsi.c | 29 -
> 1 file changed, 24 insertions(+), 5 deletions(-)
>
> diff --git
Same as for the individual fences, we want to report the actual status
of the fence when queried.
Reported-by: Petri Latvala
Signed-off-by: Chris Wilson
Cc: Sumit Semwal
Cc: Gustavo Padovan
Cc: Petri Latvala
Reviewed-by: Matthew Auld
---
drivers/dma-buf/sync_file.c | 2 +-
1 file changed,
Quoting Brendan Higgins (2019-08-12 22:02:59)
> On Mon, Aug 12, 2019 at 9:56 PM Stephen Boyd wrote:
> >
> > Quoting Brendan Higgins (2019-08-12 17:41:05)
> > > On Mon, Aug 12, 2019 at 4:59 PM Stephen Boyd wrote:
> > > >
> > > > > kunit_resource_destroy (respective equivalents to devm_kfree, and
Hi Inki.
On Tue, Aug 13, 2019 at 10:03:51PM +0900, Inki Dae wrote:
> Hi,
>
> On 19. 8. 13. 오전 3:51, Sam Ravnborg wrote:
> > Hi Inki.
> >
> > Any plans to take this to the exynos tree?
> >
>
> It will be merged to next.
Thanks, one more off the list.
Sam
1 - 100 of 159 matches
Mail list logo
