Hi, Yongqiang:
On Tue, 2019-07-09 at 06:34 +0800, yongqiang@mediatek.com wrote:
> From: Yongqiang Niu
>
> This patch add clock property check before get it
>
> Signed-off-by: Yongqiang Niu
> ---
> drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 10 ++
> 1 file changed, 6 insertions(+), 4
https://bugs.freedesktop.org/show_bug.cgi?id=110898
--- Comment #2 from Fab Stz ---
Newer patch is for 19.20 (bug 03), I attached it to the wrong bug
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing li
https://bugs.freedesktop.org/show_bug.cgi?id=03
--- Comment #1 from Fab Stz ---
Created attachment 144809
--> https://bugs.freedesktop.org/attachment.cgi?id=144809&action=edit
[Patch] to compile amdgpu-dkms 19.20 on debian stretch & buster (v2)
Same patch as before but using #if to manage
On Tue, Jul 16, 2019 at 12:42:07PM +0200, Andrey Konovalov wrote:
> On Mon, Jul 15, 2019 at 8:05 PM Jason Gunthorpe wrote:
> >
> > On Mon, Jul 15, 2019 at 06:01:29PM +0200, Andrey Konovalov wrote:
> > > On Mon, Jun 24, 2019 at 7:40 PM Catalin Marinas
> > > wrote:
> > > >
> > > > On Mon, Jun 24,
In amdgpu_ras_debugfs_ctrl_parse_data(), first fetch str from buf to
get op value, if op == -1 which means no command matched, fetch data
from buf again.
If change buf between two fetches may cause security problems or
unexpected behaivor. amdgpu_ras_debugfs_ctrl_parse_data() was called
by amdgpu_
Fix sparse warning:
drivers/gpu/drm/nouveau/nvkm/subdev/secboot/acr_r352.c:1092:1:
warning: symbol 'acr_r352_ls_gpccs_func' was not declared. Should it be static?
Reported-by: Hulk Robot
Signed-off-by: YueHaibing
---
drivers/gpu/drm/nouveau/nvkm/subdev/secboot/acr_r352.c | 2 +-
1 file change
On Mon, Jul 15, 2019 at 8:05 PM Jason Gunthorpe wrote:
>
> On Mon, Jul 15, 2019 at 06:01:29PM +0200, Andrey Konovalov wrote:
> > On Mon, Jun 24, 2019 at 7:40 PM Catalin Marinas
> > wrote:
> > >
> > > On Mon, Jun 24, 2019 at 04:32:56PM +0200, Andrey Konovalov wrote:
> > > > This patch is a part o
The cpufreq policy notifier's CPUFREQ_ADJUST notification is going to
get removed soon.
The notifier callback pxafb_freq_policy() isn't doing anything apart
from printing a debug message on CPUFREQ_ADJUST notification. There is
no point in keeping an otherwise empty callback and registering the
no
> -Original Message-
> From: liviu.du...@arm.com
> Sent: 2019年3月30日 0:11
> To: Wen He
> Cc: brian.star...@arm.com; mal...@foss.arm.com;
> dri-devel@lists.freedesktop.org
> Subject: Re: [PATCH 2/2] drm/arm/malidp: Setting QoS priority for 4k to avoid
> flicker issue
>
> On Fri, Mar 29,
On Fri, Jul 12, 2019 at 6:48 PM Russell King - ARM Linux admin
wrote:
>
> On Fri, Jul 12, 2019 at 06:04:40PM +0800, Cheng-Yi Chiang wrote:
> > Allow codec driver register callback function for plug event.
> >
> > The callback registration flow:
> > dw-hdmi <--- hw-hdmi-i2s-audio <--- hdmi-codec
>
https://bugs.freedesktop.org/show_bug.cgi?id=105733
Michel Dänzer changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
On Tue, Jul 16, 2019 at 10:14 PM Tzung-Bi Shih wrote:
>
> On Tue, Jul 16, 2019 at 7:58 PM Cheng-Yi Chiang wrote:
> >
> > diff --git a/sound/soc/rockchip/Kconfig b/sound/soc/rockchip/Kconfig
> > index b43657e6e655..d610b553ea3b 100644
> > --- a/sound/soc/rockchip/Kconfig
> > +++ b/sound/soc/rockch
On Tue, Jul 16, 2019 at 10:16 PM Tzung-Bi Shih wrote:
>
> On Tue, Jul 16, 2019 at 7:58 PM Cheng-Yi Chiang wrote:
> >
> > diff --git a/sound/soc/rockchip/rockchip_max98090.c
> > b/sound/soc/rockchip/rockchip_max98090.c
> > index c82948e383da..c81c4acda917 100644
> > --- a/sound/soc/rockchip/rockc
Hi Emil,
Sorry for the delay, finally coming back to this after my vacation.
Am 03.07.19 um 17:14 schrieb Emil Velikov:
> On Wed, 3 Jul 2019 at 15:58, Koenig, Christian
> wrote:
>> Am 03.07.2019 16:51 schrieb Emil Velikov :
>>
>> On Wed, 3 Jul 2019 at 15:33, Koenig, Christian
>> wrote:
>>> Am
Add an op in hdmi_codec_ops so codec driver can register callback
function to handle plug event.
Driver in DRM can use this callback function to report connector status.
Signed-off-by: Cheng-Yi Chiang
---
include/sound/hdmi-codec.h| 17 +
sound/soc/codecs/hdmi-codec.c | 46 +
This patch series supports HDMI jack reporting on RK3288, which uses
DRM dw-hdmi driver and hdmi-codec codec driver.
The previous discussion about reporting jack status using hdmi-notifier
and drm_audio_component is at
https://lore.kernel.org/patchwork/patch/1083027/
The new approach is to use a
Allow codec driver register callback function for plug event.
The callback registration flow:
dw-hdmi <--- hw-hdmi-i2s-audio <--- hdmi-codec
dw-hdmi-i2s-audio implements hook_plugged_cb op
so codec driver can register the callback.
dw-hdmi exports a function dw_hdmi_set_plugged_cb so platform de
In machine driver, create a jack and let hdmi-codec report jack status.
Signed-off-by: Cheng-Yi Chiang
---
sound/soc/rockchip/Kconfig | 3 ++-
sound/soc/rockchip/rockchip_max98090.c | 20
2 files changed, 22 insertions(+), 1 deletion(-)
diff --git a/sound/soc/r
The problem of using auto ID is that the device name will be like
hdmi-audio-codec..auto.
The number might be changed when there are other platform devices being
created before hdmi-audio-codec device.
Use a fixed name so machine driver can set codec name on the DAI link.
Using the fixed name sho
Use two dai_links. One for HDMI and one for max98090.
With this setup, audio can play to speaker and HDMI selectively.
Signed-off-by: Cheng-Yi Chiang
---
sound/soc/rockchip/rockchip_max98090.c | 96 --
1 file changed, 73 insertions(+), 23 deletions(-)
diff --git a/sound/
Configure the display Quality of service (QoS) levels to high priority
if the level is defined as high as in DTS. The ARQOS for DP500 is driven
from the "RQOS" register, needed to program the RQOS register value < 7
for the 4k resolution flicker to disappear on the LS1028A platform.
Signed-off-by:
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #15 from Timothy Pearson (tpear...@raptorengineering.com) ---
Bisect shows that the failing commit is:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-5.1.y&id=cc17d7802b7dcbb073e7be1eee2cf6fa64d9
Hi Dmitry,
thanks for taking a look at this!
On Tue, Jul 16, 2019 at 08:47:44PM +0200, Dmitry Torokhov wrote:
> Hi Ronald,
>
> On Fri, Apr 19, 2019 at 01:19:26AM -0700, Ronald Tschalär wrote:
> > The keyboard and trackpad on recent MacBook's (since 8,1) and
> > MacBookPro's (13,* and 14,*) ar
On Wed, Jul 17, 2019 at 4:33 PM Cheng-Yi Chiang wrote:
>
> This patch series supports HDMI jack reporting on RK3288, which uses
> DRM dw-hdmi driver and hdmi-codec codec driver.
>
> The previous discussion about reporting jack status using hdmi-notifier
> and drm_audio_component is at
>
> https://
On Tue, Jul 16, 2019 at 08:50:22AM +0200, Sam Ravnborg wrote:
> Copied all recipients on the cover letter.
> As the list is long this mail may not hit the mailing lists.
>
> Sam
>
> On Tue, Jul 16, 2019 at 08:42:01AM +0200, Sam Ravnborg wrote:
> > This patch set removes a far share of the r
This file is currently orphaned.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/gpu/drivers.rst| 1 +
Documentation/gpu/msm-crash-dump.rst | 2 --
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/gpu/drivers.rst b/Documentation/gpu/drivers.rst
index 4bf
Hi Wen,
On Wed, Jul 17, 2019 at 05:23:53PM +0800, Wen He wrote:
> Configure the display Quality of service (QoS) levels to high priority
> if the level is defined as high as in DTS. The ARQOS for DP500 is driven
> from the "RQOS" register, needed to program the RQOS register value < 7
> for the 4k
On Wed, Jul 17, 2019 at 04:27:56AM -0700, kernelci.org bot wrote:
Today's -next fails to boot on meson-gxm-khadas-vim2 in a variety
of configurations:
> defconfig:
> gcc-8:
> meson-gxm-khadas-vim2:
> lab-baylibre: new failure (last pass: next-20190705)
> d
This means that tinydrm_spi_bpw_supported() can be removed.
Signed-off-by: Noralf Trønnes
---
.../gpu/drm/tinydrm/core/tinydrm-helpers.c| 32 +--
drivers/gpu/drm/tinydrm/mipi-dbi.c| 5 ++-
include/drm/tinydrm/tinydrm-helpers.h | 1 -
3 files changed, 3 i
Prep work before moving the function to mipi-dbi.
tinydrm_spi_transfer() was made to support one class of drivers in
drivers/staging/fbtft that has not been converted to DRM yet, so strip
away the unused functionality:
- Start byte (header) is not used.
- No driver relies on the automatic 16-bit b
This series removes the remaining bits of tinydrm.ko.
There's only one item left on the tinydrm todo list and that is moving
out mipi_dbi.
Note:
This depends on a commit that just entered Linus' tree:
e6f3f7e4dc76 ("spi: Add spi_is_bpw_supported()")
Series is also available here:
https://github.
The MIPI DBI standard support more pixel formats than what this helper
supports. Add an init function that lets the driver use different
format(s). This avoids open coding mipi_dbi_init() in st7586.
st7586 sets preferred_depth but this is not necessary since it only
supports one format.
Cc: David
The tinydrm helper is going away so move it into the only user mipi-dbi.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/tinydrm/mipi-dbi.c| 15 ---
include/drm/tinydrm/tinydrm-helpers.h | 15 ---
2 files changed, 12 insertions(+), 18 deletions(-)
diff --git a/driv
The SPI event tracing can dump the buffer now so no need for this.
Remove the debug print from tinydrm_spi_transfer() since this info can be
gleaned from the trace event.
Signed-off-by: Noralf Trønnes
---
.../gpu/drm/tinydrm/core/tinydrm-helpers.c| 40 ---
drivers/gpu/drm/tin
tinydrm.ko is going away so let's implement a connector.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/tinydrm/repaper.c | 58 ---
1 file changed, 53 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/tinydrm/repaper.c
b/drivers/gpu/drm/tinydrm/repaper.c
tinydrm_display_pipe_init() has only one user now, so move it to mipi-dbi.
Changes:
- Remove drm_connector_helper_funcs.detect, it's always connected.
- Store the connector and mode in mipi_dbi instead of it's own struct.
Otherwise remove some leftover tinydrm-helpers.h inclusions.
Cc: Eric Anho
tinydrm drivers announce DRM_MODE_CONNECTOR_VIRTUAL for its SPI drivers.
Stop lying and add a SPI connector type
Cc: David Lechner
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/drm_connector.c| 1 +
drivers/gpu/drm/tinydrm/mipi-dbi.c | 3 +--
drivers/gpu/drm/tinydrm/repaper.c | 2 +-
d
spi-bcm2835 can handle >64kB buffers now so there is no need to check
->max_dma_len. The tinydrm_spi_max_transfer_size() max_len argument is
not used by any callers, so not needed.
Then we have the spi_max module parameter. It was added because
staging/fbtft has support for it and there was a repo
This is only used by mipi-dbi drivers so move it there.
The reason this isn't moved to the SPI subsystem is that it will in a
later patch pass a dummy rx buffer for SPI controllers that need this.
Low memory boards (64MB) can run into a problem allocating such a "large"
contiguous buffer on every
On Wed, Jul 17, 2019 at 04:27:56AM -0700, kernelci.org bot wrote:
Today's -next fails to boot on a couple of apq8064 boards:
> arm:
> qcom_defconfig:
> gcc-8:
> qcom-apq8064-cm-qs600: 1 failed lab
> qcom-apq8064-ifc6410: 1 failed lab
In both cases it looks lik
On Wed, Jul 17, 2019 at 01:58:12PM +0200, Noralf Trønnes wrote:
> Prep work before moving the function to mipi-dbi.
>
> tinydrm_spi_transfer() was made to support one class of drivers in
> drivers/staging/fbtft that has not been converted to DRM yet, so strip
> away the unused functionality:
> - S
Hi Noralf.
On Wed, Jul 17, 2019 at 01:58:13PM +0200, Noralf Trønnes wrote:
> This is only used by mipi-dbi drivers so move it there.
>
> The reason this isn't moved to the SPI subsystem is that it will in a
> later patch pass a dummy rx buffer for SPI controllers that need this.
> Low memory boar
https://bugs.freedesktop.org/show_bug.cgi?id=61
nareshrajus...@gmail.com changed:
What|Removed |Added
Status|NEW |ASSIGNED
--
You are receivin
https://bugs.freedesktop.org/show_bug.cgi?id=61
nareshrajus...@gmail.com changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|-
https://bugs.freedesktop.org/show_bug.cgi?id=61
nareshrajus...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|VERIFIED
--
You are receivin
https://bugs.freedesktop.org/show_bug.cgi?id=61
nareshrajus...@gmail.com changed:
What|Removed |Added
Status|VERIFIED|CLOSED
--
You are receiving
Hi Noralf.
Nice series of patches!
On Wed, Jul 17, 2019 at 01:58:07PM +0200, Noralf Trønnes wrote:
> This series removes the remaining bits of tinydrm.ko.
>
> There's only one item left on the tinydrm todo list and that is moving
> out mipi_dbi.
>
> Note:
> This depends on a commit that just
On Wed, Jul 17, 2019 at 01:58:17PM +0200, Noralf Trønnes wrote:
> tinydrm_display_pipe_init() has only one user now, so move it to mipi-dbi.
>
> Changes:
> - Remove drm_connector_helper_funcs.detect, it's always connected.
> - Store the connector and mode in mipi_dbi instead of it's own struct.
>
Hello,
syzbot found the following crash on:
HEAD commit:1438cde7 Add linux-next specific files for 20190716
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1398805860
kernel config: https://syzkaller.appspot.com/x/.config?x=3430a151e1452331
dashboard
This series aims to add a led-backlight driver, similar to pwm-backlight,
but using a LED class device underneath.
A few years ago (2015), Tomi Valkeinen posted a series implementing a
backlight driver on top of a LED device:
https://patchwork.kernel.org/patch/7293991/
https://patchwork.kernel.org
If the LED is acquired by a consumer device with devm_led_get(), it is
automatically released when the device is detached.
Signed-off-by: Jean-Jacques Hiblot
Acked-by: Pavel Machek
---
drivers/leds/led-class.c | 42
include/linux/leds.h | 2 ++
2 fi
From: Tomi Valkeinen
This patch adds a led-backlight driver (led_bl), which is similar to
pwm_bl except the driver uses a LED class driver to adjust the
brightness in the HW. Multiple LEDs can be used for a single backlight.
Signed-off-by: Tomi Valkeinen
Signed-off-by: Jean-Jacques Hiblot
Acke
Add DT binding for led-backlight.
Signed-off-by: Jean-Jacques Hiblot
---
.../bindings/leds/backlight/led-backlight.txt | 28 +++
1 file changed, 28 insertions(+)
create mode 100644
Documentation/devicetree/bindings/leds/backlight/led-backlight.txt
diff --git a/Documentation/de
From: Tomi Valkeinen
This patch adds basic support for a kernel driver to get a LED device.
This will be used by the led-backlight driver.
Only OF version is implemented for now, and the behavior is similar to
PWM's of_pwm_get() and pwm_put().
Signed-off-by: Tomi Valkeinen
Signed-off-by: Jean-
Hello!
Our CI on s390x constantly triggers the following warning in function
con_is_bound() when reading the SysFS attribute
/sys/class/vtconsole/vtcon0/bind.
I verified this to be the case since WARN_CONSOLE_UNLOCKED() was introduced in
function con_is_bound() with commit ddde3c18b700 ("vt: Mo
Commit c440eee1a7a1 ("Staging: fbtft: Switch to the gpio descriptor
interface") breaks GPIO handling. In several places, checks to only set
a GPIO if it was configured ended up backwards.
I have tested this fix. The fixed driver works with a ili9486
display connected to a raspberry pi via SPI.
Fix
On 7/12/19 4:47 AM, Lecopzer Chen wrote:
ion_buffer_add() insert ion_buffer into rbtree every time creating
an ion_buffer but never use it after ION reworking.
Also, buffer_lock protects only rbtree operation, remove it together.
Signed-off-by: Lecopzer Chen
Cc: YJ Chiang
Cc: Lecopzer Chen
--
Den 12.07.2019 20.53, skrev Hans de Goede:
> Add a modesetting driver for Grain Media GM12U320 based devices
> (primarily Acer C120 projector, but there may be compatible devices).
>
> This is based on the fb driver from Viacheslav Nurmekhamitov:
> https://github.com/slavrn/gm12u320
>
> This dr
From: Sean Paul
Although the DisplayPort spec explicitly calls out the 1.62/2.7/5.4/8.1
link rates, the value of LINK_BW_SET is calculated. The DisplayPort
spec says "Main-Link Bandwidth Setting = Value x 0.27Gbps/lane".
A bridge that we're looking to upstream uses 6.75Gbps rate (value 0x19)
[1
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #54 from Sylvain BERTRAND ---
power management related code is in amdgpu, then the right place is here, the
"dri" and
"amdgfx" mailing lists (aka linux gpu driver mailing lists).
As far as I am concerned, when I play dota2, I always
power management related code is in amdgpu, then the right place is here, the
"dri" and
"amdgfx" mailing lists (aka linux gpu driver mailing lists).
As far as I am concerned, when I play dota2, I always switch the GPU dpm to
high and the CPU freq governor to perf (because, all those things steal
Den 17.07.2019 15.09, skrev Sam Ravnborg:
> On Wed, Jul 17, 2019 at 01:58:12PM +0200, Noralf Trønnes wrote:
>> Prep work before moving the function to mipi-dbi.
>>
>> tinydrm_spi_transfer() was made to support one class of drivers in
>> drivers/staging/fbtft that has not been converted to DRM yet
On Wed, Jul 17, 2019 at 12:01:48PM -0400, Sean Paul wrote:
> From: Sean Paul
>
> Although the DisplayPort spec explicitly calls out the 1.62/2.7/5.4/8.1
> link rates, the value of LINK_BW_SET is calculated. The DisplayPort
> spec says "Main-Link Bandwidth Setting = Value x 0.27Gbps/lane".
>
> A
Den 17.07.2019 15.15, skrev Sam Ravnborg:
> Hi Noralf.
>
> On Wed, Jul 17, 2019 at 01:58:13PM +0200, Noralf Trønnes wrote:
>> This is only used by mipi-dbi drivers so move it there.
>>
>> The reason this isn't moved to the SPI subsystem is that it will in a
>> later patch pass a dummy rx buffer
Den 17.07.2019 15.31, skrev Sam Ravnborg:
> Hi Noralf.
>
> Nice series of patches!
>
>
>
> On Wed, Jul 17, 2019 at 01:58:07PM +0200, Noralf Trønnes wrote:
>> This series removes the remaining bits of tinydrm.ko.
>>
>> There's only one item left on the tinydrm todo list and that is moving
>> o
On Wed, Jul 17, 2019 at 07:20:29PM +0300, Ville Syrjälä wrote:
> On Wed, Jul 17, 2019 at 12:01:48PM -0400, Sean Paul wrote:
> > From: Sean Paul
> >
> > Although the DisplayPort spec explicitly calls out the 1.62/2.7/5.4/8.1
> > link rates, the value of LINK_BW_SET is calculated. The DisplayPort
Hello!
The syzkaller [1] has a trouble with fuzzing the Linux kernel with ION Memory
Allocator.
Syzkaller uses several methods [2] to limit memory consumption of the userspace
processes calling the syscalls for testing the kernel:
- setrlimit(),
- cgroups,
- various sysctl.
But these methods d
Hi Doug.
On Fri, Jul 12, 2019 at 09:33:33AM -0700, Douglas Anderson wrote:
> This attempts to address outstanding review feedback from commit
> b8a2948fa2b3 ("drm/panel: simple: Add ability to override typical
> timing"). Specifically:
>
> * It was requested that I document (in the structure def
Hi Sam,
> Am 26.06.2019 um 14:40 schrieb H. Nikolaus Schaller :
>
> Hi Sam,
>
>> Am 26.06.2019 um 09:33 schrieb Sam Ravnborg :
>>
>> Hi Nikolaus.
>>
any progress towards merging this somewhere? It did not yet arrive in
linux-next.
BTW: should also be applied to 5.2
Hi Noralf.
On Wed, Jul 17, 2019 at 06:18:39PM +0200, Noralf Trønnes wrote:
>
>
> Den 17.07.2019 15.09, skrev Sam Ravnborg:
> > On Wed, Jul 17, 2019 at 01:58:12PM +0200, Noralf Trønnes wrote:
> >> Prep work before moving the function to mipi-dbi.
> >>
> >> tinydrm_spi_transfer() was made to suppo
Hi Nikolaus.
> BTW: should also be applied to 5.2
> >>> The drm bits are reviewed. The DT bits needs OK from DT people.
> >>> When we have OK from DT people we can apply them all to drm-misc-next.
> >>
> >> I got OK on irc from Rob to process these.
> >> All patches are now applied to drm-mi
Setting the GPU VA when creating the GEM object doesn't allow for any
conditional adjustments. In preparation to support adjusting the
mapping, restructure the GEM object creation to map the GEM object after
we've created the base shmem object.
Cc: Tomeu Vizoso
Cc: Boris Brezillon
Cc: Robin Murp
Executable buffers have an alignment restriction that they can't cross
16MB boundary as the GPU program counter is 24-bits. This restriction is
currently not handled and we just get lucky. As current userspace
assumes all BOs are executable, that has to remain the default. So add a
new PANFROST_BO_
In preparation to create partial GPU mappings of BOs on page faults,
split out the SG list handling of panfrost_mmu_map().
Cc: Tomeu Vizoso
Cc: Boris Brezillon
Cc: Robin Murphy
Cc: Steven Price
Cc: Alyssa Rosenzweig
Signed-off-by: Rob Herring
---
drivers/gpu/drm/panfrost/panfrost_mmu.c | 52
The midgard/bifrost GPUs need to allocate GPU heap memory which is
allocated on GPU page faults and not pinned in memory. The vendor driver
calls this functionality GROW_ON_GPF.
This implementation assumes that BOs allocated with the
PANFROST_BO_NOEXEC flag are never mmapped or exported. Both of t
Increment the driver version to expose the new BO allocation flags.
Cc: Tomeu Vizoso
Cc: Boris Brezillon
Cc: Robin Murphy
Cc: Steven Price
Cc: Alyssa Rosenzweig
Signed-off-by: Rob Herring
---
drivers/gpu/drm/panfrost/panfrost_drv.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #16 from Shawn Anastasio (sh...@anastas.io) ---
Created attachment 283799
--> https://bugzilla.kernel.org/attachment.cgi?id=283799&action=edit
test patch #1
Though I'm not familiar with this code, a quick spot check shows what I bel
From: Gustavo Padovan
Add implementation for async plane update callbacks
Signed-off-by: Gustavo Padovan
Signed-off-by: Enric Balletbo i Serra
Signed-off-by: Tina Zhang
Signed-off-by: Helen Koike
Tested-by: Tina Zhang
---
Hi,
This is v10, I just fixed the order in how the commit_ready fen
From: Gustavo Padovan
Replace the legacy cursor implementation by the async callbacks
Signed-off-by: Gustavo Padovan
Signed-off-by: Enric Balletbo i Serra
Signed-off-by: Helen Koike
---
Changes in v10: None
Changes in v9:
- v8: https://patchwork.kernel.org/patch/10843397/
- rebased and fi
On 7/17/19 6:58 AM, Noralf Trønnes wrote:
Prep work before moving the function to mipi-dbi.
tinydrm_spi_transfer() was made to support one class of drivers in
drivers/staging/fbtft that has not been converted to DRM yet, so strip
away the unused functionality:
- Start byte (header) is not used.
On 7/17/19 6:58 AM, Noralf Trønnes wrote:
tinydrm drivers announce DRM_MODE_CONNECTOR_VIRTUAL for its SPI drivers.
Stop lying and add a SPI connector type
Cc: David Lechner
Signed-off-by: Noralf Trønnes
---
Acked-by: David Lechner
___
dri-devel m
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #17 from Shawn Anastasio (sh...@anastas.io) ---
On second glance, it seems I got it backwards. pgprot_noncache /is/ actually
being set via the default implementation of arch_dma_mmap_pgprot, but this
creates the opposite issue. In the
On 7/17/19 6:58 AM, Noralf Trønnes wrote:
This is only used by mipi-dbi drivers so move it there.
The reason this isn't moved to the SPI subsystem is that it will in a
later patch pass a dummy rx buffer for SPI controllers that need this.
Low memory boards (64MB) can run into a problem allocatin
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #18 from Shawn Anastasio (sh...@anastas.io) ---
Created attachment 283801
--> https://bugzilla.kernel.org/attachment.cgi?id=283801&action=edit
test patch #2
Here's the new patch that should restore the previous behavior correctly.
On 7/17/19 6:58 AM, Noralf Trønnes wrote:
The tinydrm helper is going away so move it into the only user mipi-dbi.
Signed-off-by: Noralf Trønnes
---
drivers/gpu/drm/tinydrm/mipi-dbi.c| 15 ---
include/drm/tinydrm/tinydrm-helpers.h | 15 ---
2 files changed, 12 in
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #19 from Shawn Anastasio (sh...@anastas.io) ---
Created attachment 283803
--> https://bugzilla.kernel.org/attachment.cgi?id=283803&action=edit
test patch #3
oops, missed a couple of includes and made a typo. Fixed those.
--
You ar
Hi Noralf,
Thank you for the review.
On 17-07-19 17:24, Noralf Trønnes wrote:
Den 12.07.2019 20.53, skrev Hans de Goede:
Add a modesetting driver for Grain Media GM12U320 based devices
(primarily Acer C120 projector, but there may be compatible devices).
This is based on the fb driver from
On 7/17/19 6:58 AM, Noralf Trønnes wrote:
The MIPI DBI standard support more pixel formats than what this helper
supports. Add an init function that lets the driver use different
format(s). This avoids open coding mipi_dbi_init() in st7586.
st7586 sets preferred_depth but this is not necessary s
On 7/17/19 6:58 AM, Noralf Trønnes wrote:
tinydrm_display_pipe_init() has only one user now, so move it to mipi-dbi.
Changes:
- Remove drm_connector_helper_funcs.detect, it's always connected.
- Store the connector and mode in mipi_dbi instead of it's own struct.
Otherwise remove some leftover
From: Rob Clark
drm_cflush_pages() is no-op on arm/arm64. But instead we can use
dma_sync API.
Fixes failures w/ vgem_test.
Signed-off-by: Rob Clark
---
An alternative approach to the series[1] I sent yesterday
On the plus side, it keeps the WC buffers and avoids any drm core
changes. On th
On Thu, Jun 27, 2019 at 11:11 PM CK Hu wrote:
>
> Hi, Jitao:
>
> On Thu, 2019-06-27 at 16:01 +0800, Jitao Shi wrote:
> > DSI panel driver need attach function which is inculde in
> > mipi_dsi_host_ops.
> >
> > If mipi_dsi_host_register is not in probe, dsi panel will
> > probe more delay.
> >
> >
On 2019-07-15 18:28, Sam Ravnborg wrote:
> On Fri, Jul 05, 2019 at 10:47:30PM +0200, Stefan Agner wrote:
>> On 2019-06-30 08:18, Sam Ravnborg wrote:
>> > Drop use of the deprecated drmP.h header file.
>> >
>> > While touching the list of include files divided them
>> > in blocks and sort them withi
On Wed, Jul 17, 2019 at 5:10 AM Mark Brown wrote:
>
> On Wed, Jul 17, 2019 at 04:27:56AM -0700, kernelci.org bot wrote:
>
> Today's -next fails to boot on a couple of apq8064 boards:
>
> > arm:
> > qcom_defconfig:
> > gcc-8:
> > qcom-apq8064-cm-qs600: 1 failed lab
> >
On Sun, Jun 30, 2019 at 6:43 PM CK Hu wrote:
>
> Hi, Jitao:
>
> On Thu, 2019-06-27 at 16:01 +0800, Jitao Shi wrote:
> > Change the method of frame rate calc which can get more accurate
> > frame rate.
> >
> > data rate = pixel_clock * bit_per_pixel / lanes
> > Adjust hfp_wc to adapt the additional
https://bugzilla.kernel.org/show_bug.cgi?id=204145
Robert Bridge (rob...@robbieab.com) changed:
What|Removed |Added
CC||rob...@robbieab.com
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #21 from Timothy Pearson (tpear...@raptorengineering.com) ---
Patch #3 confirmed working when applied against kernel 5.2.1. Thanks Shawn!
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #22 from Shawn Anastasio (sh...@anastas.io) ---
Great! I've posted the patch to the linuxppc-dev mailing list here:
https://patchwork.ozlabs.org/patch/1133466/.
--
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #23 from Timothy Pearson (tpear...@raptorengineering.com) ---
A nit, but might want to mark this bug as a regression and update the kernel
version to 5.2.1?
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=204145
Shawn Anastasio (sh...@anastas.io) changed:
What|Removed |Added
Component|Video(DRI - non Intel) |PPC-64
Kernel Ve
https://bugzilla.kernel.org/show_bug.cgi?id=204145
--- Comment #24 from Shawn Anastasio (sh...@anastas.io) ---
Done. I've also updated the product/component to Platform Specific/PPC-64 since
this wasn't an issue with amdgpu after all.
--
You are receiving this mail because:
You are watching the
1 - 100 of 132 matches
Mail list logo
