Am 28.08.2018 um 18:58 schrieb Michel Dänzer:
From: Michel Dänzer
The first parameter of list_cut_position() must point to an initialized
list.
Noticed thanks to KASAN pointing out something's fishy here.
Fixes: "drm/ttm: add bulk move function on LRU"
Signed-off-by: Michel Dänzer
Reviewed
GEN11 supports 6 sprite planes. Making the change
in intel_device_info.c accordingly
Signed-off-by: vsrini4
---
drivers/gpu/drm/i915/intel_device_info.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_device_info.c
b/drivers/gpu/drm/i915/intel_
On Tue, Aug 28, 2018 at 10:44:43PM +0530, Souptick Joarder wrote:
> We have introduce a new return type vm_fault_t for
> fault handler. Update the document for the same.
Have you built the documentation and checked the html looks better with
the changed spacing? rst can be a bit weird about some
Hello!
This is the series of patches that will add support for the Cadence's DPI/DP
bridge. Please note that this is a preliminary version of the driver and there
will be more patches in the future with updates, fixes and improvements.
Please keep that in mind when looking at FIXME/TODO/XXX commen
From: Quentin Schulz
Signed-off-by: Damian Kos
---
.../bindings/display/bridge/cdns,mhdp.txt | 43 +++
1 file changed, 43 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/bridge/cdns,mhdp.txt
diff --git a/Documentation/devicetree/bindings/display
On 2018-08-27 15:31, Pavel Machek wrote:
Hi!
On Fri 2018-08-24 15:57:42, Kiran Gunda wrote:
Update the bindings with the new properties used for
PMI8998.
Changes from V3:
- Removed the default values.
Why?
As per Bjorn's comment I have removed the default values.
Do you want to add t
From: Quentin Schulz
DP 1.4 introduced a DP_EXTENDED_RCVR_CAPA_FIELD_PRESENT bit in
DP_TRAINING_AUX_RD_INTERVAL register. If set, DPCD registers from DP_DPCD_REV
to DP_ADAPTER_CAP should be retrieved starting from DP_DPCD_REV_EXTENDED.
All registers are copied except DP_DPCD_REV, DP_MAX_LINK_RATE
From: Quentin Schulz
This patch finally adds the preliminary driver for Cadence MHDP DPI/DP bridge.
Changes made in the low level driver (cdn-dp-reg.*):
- moved it to from drivers/gpu/drm/rockchip to
drivers/gpu/drm/bridge/cdns-mhdp-common.*
- functions for sending/receiving commands are now p
We have introduce a new return type vm_fault_t for
fault handler. Update the document for the same.
Signed-off-by: Souptick Joarder
---
Documentation/gpu/drm-mm.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/gpu/drm-mm.rst b/Documentation/gpu/drm-mm.r
On 2018-08-27 20:24, Bjorn Andersson wrote:
On Fri 24 Aug 03:27 PDT 2018, Kiran Gunda wrote:
diff --git a/drivers/video/backlight/qcom-wled.c
b/drivers/video/backlight/qcom-wled.c
[..]
struct wled {
@@ -135,16 +146,22 @@ struct wled {
struct regmap *regmap;
struct mutex lock;
Hi Jordan,
On Mon, Aug 27, 2018 at 8:42 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 | 121 +++
> 1 file changed, 121 insertions(+)
>
> diff --git a/arc
- Extracted common fields from cdn_dp_device to a new cdns_mhdp_device
structure which will be used by two separate drivers later on.
- Moved some datatypes (audio_format, audio_info, vic_pxl_encoding_format,
video_info) from cdn-dp-core.c to cdn-dp-reg.h.
- Changed prefixes from cdn_dp to cdns
On 2018-07-06 14:43, Russell King - ARM Linux wrote:
> On Fri, Jul 06, 2018 at 11:03:46AM +0100, Russell King - ARM Linux wrote:
>> On Wed, Apr 25, 2018 at 11:01:15PM +0300, Jyri Sarha wrote:
>>> Oh yes. But in this case the substandard solution is already there and
>>> it is already widely used, d
From: Quentin Schulz
dp_link_status and dp_get_lane_status are pretty generic and can be used for
other means, so let's make it "public".
This adds drm_dp_link_status and drm_dp_get_lane_status to the header file and
add the appropriate EXPORT_SYMBOL for it so that it can be used by other
driver
On 28.8.2018 10:12, Sandy Huang wrote:
This path add support rv1108 and px30 rgb output interface driver.
Hi Sandy,
Seems like you forgot to address Rob's comment regarding the "driver" word.
Also fix the typo: s/path/patch
The subject could be improved as well: s/devicetree\/bindings/dt-bindin
On Tue, Jul 31, 2018 at 12:05 AM Gustavo Padovan wrote:
>
> Hi Souptick,
>
> On Thu, Jul 26, 2018 at 08:15:49PM +0530, Souptick Joarder wrote:
> > Use new return type vm_fault_t for fault handler.
> >
> > Signed-off-by: Souptick Joarder
> > ---
> > v2: Updated patch title
> >
> > drivers/gpu/drm
On 2018-08-27 15:39, Pavel Machek wrote:
On Fri 2018-08-24 15:57:44, Kiran Gunda wrote:
Restructure the driver to add the support for new WLED
peripherals.
Signed-off-by: Kiran Gunda
Acked-by: Daniel Thompson
---
Changes from V3:
- This is the new patch after splitting the
"backligh
On 28.08.2018 16:35, Liviu Dudau wrote:
> Hi Andrzej,
>
> Chirping in, as it was originally my work that Linus is adopting.
>
> On Mon, Aug 27, 2018 at 01:53:00PM +0200, Andrzej Hajda wrote:
>> On 24.08.2018 14:23, Linus Walleij wrote:
>>> This adds bindings for a virtual display to be used with di
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #8 from Michel Dänzer (mic...@daenzer.net) ---
Comment 4 looks similar to the following reports, both of which have comments
saying current kernels work better:
https://bugs.freedesktop.org/105684
https://bugs.freedesktop.org/106225
On Wed, Aug 29, 2018 at 10:16:34AM +0200, Andrzej Hajda wrote:
> On 28.08.2018 16:35, Liviu Dudau wrote:
> > Hi Andrzej,
> >
> > Chirping in, as it was originally my work that Linus is adopting.
> >
> > On Mon, Aug 27, 2018 at 01:53:00PM +0200, Andrzej Hajda wrote:
> >> On 24.08.2018 14:23, Linus W
https://bugs.freedesktop.org/show_bug.cgi?id=107518
--- Comment #11 from Luigi Laurini ---
Same bug present in amd64 architecture under kvm guest with RX 480 passed
through.
The first time i boot the guest the performance are ok, but if i reboot the
guest without rebooting the host, the messages
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #39 from CheatCodesOfLife ---
Created attachment 141342
--> https://bugs.freedesktop.org/attachment.cgi?id=141342&action=edit
logs after building the patched mesa
Hi,
Thanks for the logging patch.
I have applied patched that in
On 28.08.2018 15:45, Linus Walleij wrote:
> On Mon, Aug 27, 2018 at 1:53 PM Andrzej Hajda wrote:
>
>> On 24.08.2018 14:23, Linus Walleij wrote:
>>> This adds bindings for a virtual display to be used with displays
>>> inside entirely virtual environments which do not emulate things
>>> like monito
On Wed, Aug 29, 2018 at 11:58:20AM +0200, Andrzej Hajda wrote:
> On 28.08.2018 15:45, Linus Walleij wrote:
> > On Mon, Aug 27, 2018 at 1:53 PM Andrzej Hajda wrote:
> >
> >> On 24.08.2018 14:23, Linus Walleij wrote:
> >>> This adds bindings for a virtual display to be used with displays
> >>> insid
On 29.08.2018 12:01, Liviu Dudau wrote:
> On Wed, Aug 29, 2018 at 11:58:20AM +0200, Andrzej Hajda wrote:
>> On 28.08.2018 15:45, Linus Walleij wrote:
>>> On Mon, Aug 27, 2018 at 1:53 PM Andrzej Hajda wrote:
>>>
On 24.08.2018 14:23, Linus Walleij wrote:
> This adds bindings for a virtual d
Quoting Lucas De Marchi (2018-08-29 01:35:31)
> The 2 PCI IDs that are used for the command line overrid mechanism
> were left defined.
What makes them so special? Why not just match on the override devid?
-Chris
___
dri-devel mailing list
dri-devel@list
we can fetch timeline point fence after expanded.
v2: The parameter fence is the result of the function and should come last.
Signed-off-by: Chunming Zhou
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 2 +-
drivers/gpu/drm/drm_syncobj.c | 5 +++--
drivers/gp
stub fence will be used by timeline syncobj as well.
Signed-off-by: Chunming Zhou
Cc: Jason Ekstrand
Reviewed-by: Christian König
---
drivers/gpu/drm/drm_syncobj.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/drm_syncobj.c b/drivers
That is certainly totally nonsense. dma_fence_enable_sw_signaling()
is the function who is calling this callback.
Signed-off-by: Chunming Zhou
Cc: Jason Ekstrand
Reviewed-by: Christian König
Acked-by: Daniel Vetter
---
drivers/gpu/drm/drm_syncobj.c | 1 -
1 file changed, 1 deletion(-)
diff -
we can place a fence to a timeline point after expanded.
v2: change func parameter order
Signed-off-by: Chunming Zhou
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 2 +-
drivers/gpu/drm/drm_syncobj.c | 14 --
drivers/gpu/drm/i915/i915_ge
VK_KHR_timeline_semaphore:
This extension introduces a new type of semaphore that has an integer payload
identifying a point in a timeline. Such timeline semaphores support the
following operations:
* CPU query - A host operation that allows querying the payload of the
timeline semaphore.
On Wed, 29 Aug 2018, vsrini4 wrote:
> GEN11 supports 6 sprite planes. Making the change
> in intel_device_info.c accordingly
>
> Signed-off-by: vsrini4
Please fix your git name. It's supposed to be your real name, not
username.
Thanks,
Jani.
> ---
> drivers/gpu/drm/i915/intel_device_info.c |
Hi Noralf,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc1 next-20180829]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On Wed, Aug 29, 2018 at 12:23:18PM +0200, Andrzej Hajda wrote:
> On 29.08.2018 12:01, Liviu Dudau wrote:
> > On Wed, Aug 29, 2018 at 11:58:20AM +0200, Andrzej Hajda wrote:
> >> On 28.08.2018 15:45, Linus Walleij wrote:
> >>> On Mon, Aug 27, 2018 at 1:53 PM Andrzej Hajda wrote:
> >>>
> On 24.0
Am Dienstag, 28. August 2018, 09:44:55 CEST schrieb Sandy Huang:
> Align with other drivers, tab + 2 space key for description.
> and edp/hdmi/dsi can be used on both rk3288 and rk3399.
>
> Signed-off-by: Sandy Huang
applied to drm-misc
___
dri-devel
Introduced new XYUV scan-in format for framebuffer and
added support for it to i915 driver.
Stanislav Lisovskiy (2):
drm: Introduce new DRM_FORMAT_XYUV
drm/i915: Adding YUV444 packed format(DRM_FORMAT_XYUV) support.
drivers/gpu/drm/drm_fourcc.c | 1 +
drivers/gpu/drm/i915/intel_displ
PLANE_CTL_FORMAT_AYUV is already supported, according to hardware
specification.
v2: Edited commit message, removed redundant whitespaces.
v3: Fixed fallthrough logic for the format switch cases.
v4: Yet again fixed fallthrough logic, to reuse code from other case
labels.
v5: Started to use
v5: This is YUV444 packed format same as AYUV, but without alpha,
as supported by i915.
v6: Removed unneeded initializer for new XYUV format.
v7: Added is_yuv field initialization according to latest
drm_fourcc format structure initialization changes.
Signed-off-by: Stanislav Lisovskiy
Am Sonntag, 26. August 2018, 20:47:12 CEST schrieb Gustavo A. R. Silva:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struc
Am 29.08.2018 um 12:44 schrieb Chunming Zhou:
VK_KHR_timeline_semaphore:
This extension introduces a new type of semaphore that has an integer payload
identifying a point in a timeline. Such timeline semaphores support the
following operations:
* CPU query - A host operation that allows query
On Tue, Aug 28, 2018 at 04:50:37PM -0400, Sean Paul wrote:
> From: Sean Paul
>
> The atomic_check is a bit too aggressive with respect to planes which
> leave the active area. This caused a bunch of log spew when the cursor
> got to the edge of the screen and stopped it from going all the way.
>
Am Dienstag, 28. August 2018, 10:32:30 CEST schrieb Sandy Huang:
> 1. interrupt register define error lead to enable interrupt failed;
> 2. px30 unsupport hdmi output;
> 3. there are some hardware designed bug, we must swap win2 gate and
>enable offset, otherwise will appear vop iommu pagefault
Hi Michal,
Am Dienstag, 28. August 2018, 10:31:15 CEST schrieb Michal Vokáč:
> On 28.8.2018 10:12, Sandy Huang wrote:
> > This path add support rv1108 and px30 rgb output interface driver.
>
> Hi Sandy,
> Seems like you forgot to address Rob's comment regarding the "driver" word.
> Also fix the t
On 29.08.2018 13:00, Liviu Dudau wrote:
> On Wed, Aug 29, 2018 at 12:23:18PM +0200, Andrzej Hajda wrote:
>> On 29.08.2018 12:01, Liviu Dudau wrote:
>>> On Wed, Aug 29, 2018 at 11:58:20AM +0200, Andrzej Hajda wrote:
On 28.08.2018 15:45, Linus Walleij wrote:
> On Mon, Aug 27, 2018 at 1:53 PM
Use the dma mapping api and properly add iommu mappings for
objects, unless virtio is in iommu quirk mode.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 1 +
drivers/gpu/drm/virtio/virtgpu_vq.c | 46 +---
2 files changed, 38 insertions(
Gerd Hoffmann (2):
drm/virtio: add virtio_gpu_object_detach() function
drm/virtio: add iommu support.
drivers/gpu/drm/virtio/virtgpu_drv.h | 5 ++--
drivers/gpu/drm/virtio/virtgpu_fb.c | 2 +-
drivers/gpu/drm/virtio/virtgpu_ttm.c | 3 +--
drivers/gpu/drm/virtio/virtgpu_vq.c | 52 ++
The new function balances virtio_gpu_object_attach().
Also make virtio_gpu_cmd_resource_inval_backing() static and switch
call sites to the new virtio_gpu_object_attach() function.
Signed-off-by: Gerd Hoffmann
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 4 ++--
drivers/gpu/drm/virtio/virtgpu_fb
On Tue, Aug 28, 2018 at 05:01:13PM -0700, Jeykumar Sankaran wrote:
> On 2018-08-28 15:52, Sean Paul wrote:
> > On Tue, Aug 28, 2018, 6:04 PM Jeykumar Sankaran
> > wrote:
> >
> > > On 2018-08-28 13:50, Sean Paul wrote:
> > > > From: Sean Paul
> > > >
> > > > The atomic_check is a bit too aggress
https://bugs.freedesktop.org/show_bug.cgi?id=107518
--- Comment #12 from Luigi Laurini ---
I've to rectify my last affirmation about the patch.
I've patched the 4.18.5 kernel, compiled and rebooted the guest without
rebooting the host.
The guest vm was already in a bad state (300 MHz (MCLK)). U
https://bugs.freedesktop.org/show_bug.cgi?id=104362
--- Comment #6 from Andrey Grodzovsky ---
Did you do pm-hibernate before the hang happened ? I see a hibernate print just
before the hang in the previous log ?
In latest log i see no prints of hang.
--
You are receiving this mail because:
You
Quoting Lucas De Marchi (2018-08-29 01:35:32)
> We don't need to call IS_GEN() for each gen >= 9: we can rather use the
> new intel_is_genx() helper to iterate the pciids array once.
>
> Signed-off-by: Lucas De Marchi
> ---
> intel/intel_bufmgr_gem.c | 8 +---
> intel/intel_decode.c | 8
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #40 from Andrey Grodzovsky ---
Marek Olšák, I still don't see the expected debug output. I looked for 'Buffer
list'
CheatCodesOfLife, can you verify please you are running the patched version of
MESA ? We tested yesterday the new pri
Just another ping...
Daniel, Dave - maybe you could give some advise on that ?
P.S I tried with Intel card (i915) driver on 4.18.1 kernel to do the
same to get some reference point, but it just hanged.
Andrey
On 08/27/2018 12:04 PM, Andrey Grodzovsky wrote:
Hi everybody , I am trying to re
On Tuesday, 2018-07-31 16:30:12 -0700, Tom Anderson wrote:
> Ping.
Hey, sorry this one almost fell through the cracks.
I believe this patch is correct, so it has my
Reviewed-by: Eric Engestrom
I'll run a couple build tests just to make sure and push it later :)
> Please let me know if there's
https://bugs.freedesktop.org/show_bug.cgi?id=99857
--- Comment #6 from copperly ---
I am running 4.15.0-33-generic, which is up to date with cinnamon's
repositories. Should I really try to upgrade? I beleive when I was on kubuntu
and having the same problem I was running 4.17 or 4.18.
--
You ar
On Wed, Aug 29, 2018 at 4:43 PM, Andrey Grodzovsky
wrote:
> Just another ping...
>
> Daniel, Dave - maybe you could give some advise on that ?
>
> P.S I tried with Intel card (i915) driver on 4.18.1 kernel to do the same to
> get some reference point, but it just hanged.
drm_device hot-unplug is
https://bugs.freedesktop.org/show_bug.cgi?id=99857
--- Comment #7 from Andrey Grodzovsky ---
Well, your dmesg shows 4.9 kernel which is really old, so I would give a try.
If you still have it on 4.18 a new log can be more useful to look at.
I think you can always just manually install *.deb pack
Thanks.
Andrey
On 08/29/2018 11:07 AM, Daniel Vetter wrote:
On Wed, Aug 29, 2018 at 4:43 PM, Andrey Grodzovsky
wrote:
Just another ping...
Daniel, Dave - maybe you could give some advise on that ?
P.S I tried with Intel card (i915) driver on 4.18.1 kernel to do the same to
get some referen
https://bugs.freedesktop.org/show_bug.cgi?id=107652
--- Comment #10 from mikhail.v.gavri...@gmail.com ---
Created attachment 141348
--> https://bugs.freedesktop.org/attachment.cgi?id=141348&action=edit
dmesg (4.19.0-0.rc1.git0.1)
--
You are receiving this mail because:
You are the assignee for
On Wed, Aug 29, 2018 at 11:32:35AM +0100, Chris Wilson wrote:
> Quoting Lucas De Marchi (2018-08-29 01:35:31)
> > The 2 PCI IDs that are used for the command line overrid mechanism
> > were left defined.
>
> What makes them so special? Why not just match on the override devid?
because it's a name
Hi all,
I need an advice for the following DRM MSM initialization problem:
drm/msm/msm_drv.c msm_pdev_probe() fails with the following message
(screenshot below)
[ 54.833779] irq: no irq domain found for /soc/mdss@1a0 !
[ 54.839019] CPU: 6 PID: 1132 Comm: modprobe Tainted: GW
Hi Sam
Yes, looks like I missed Philip's comments.
Will reply to his mail and fix them in v7.
Thanks for pointing it out.
Abhinav
On 2018-08-28 21:34, Sam Ravnborg wrote:
Hi Abhinav.
On Tue, Aug 28, 2018 at 03:39:46PM -0700, Abhinav Kumar wrote:
From: "abhin...@codeaurora.org"
Add suppor
On Wed, Aug 29, 2018 at 04:34:13PM +, Dima Antonets wrote:
> Hi all,
>
Hi Dmitriy,
I don't have an answer for you, but I've Cc'd the msm lists in case someone
there does.
Sean
> I need an advice for the following DRM MSM initialization problem:
> drm/msm/msm_drv.c msm_pdev_probe() fails wi
From: Sean Paul
The atomic_check is a bit too aggressive with respect to planes which
leave the active area. This caused a bunch of log spew when the cursor
got to the edge of the screen and stopped it from going all the way.
This patch removes the conservative bounds checks from atomic and clip
On Wed, Aug 29, 2018 at 02:28:47PM +0300, Stanislav Lisovskiy wrote:
> PLANE_CTL_FORMAT_AYUV is already supported, according to hardware
> specification.
>
> v2: Edited commit message, removed redundant whitespaces.
>
> v3: Fixed fallthrough logic for the format switch cases.
>
> v4: Yet again f
Actually, I've just spotted this drm_dev_unplug, does it make sense to
use it in our pci_driver.remove hook
instead of explicitly doing drm_dev_unregister and drm_dev_put(dev) ?
This way at least any following IOCTL will fail with ENODEV.
Andrey
On 08/29/2018 11:07 AM, Daniel Vetter wrote:
On Wed, Jul 25, 2018 at 05:46:41PM +0200, Andrzej Hajda wrote:
> The patch adds common part of DSI node for Exynos5250 platforms
> and a required mipi-phy node.
>
> Signed-off-by: Andrzej Hajda
> Signed-off-by: Maciej Purski
> ---
> arch/arm/boot/dts/exynos5250.dtsi | 21 +
>
Take a look at what the udl drm driver does. It's a usb display chip.
Alex
From: amd-gfx on behalf of Andrey
Grodzovsky
Sent: Wednesday, August 29, 2018 2:28:42 PM
To: Daniel Vetter; Noralf Trønnes
Cc: Dave Airlie; amd-...@lists.freedesktop.org; ML dri-devel;
https://bugzilla.kernel.org/show_bug.cgi?id=200621
--- Comment #9 from Jon (jon...@gmail.com) ---
Thanks for your input, I appreciate you taking the time to look into this.
This system was 100% stable for months, but somewhere around 4.17.X the issue
started and has persisted through several kern
On Wed, Jul 25, 2018 at 05:46:42PM +0200, Andrzej Hajda wrote:
> The patch adds bridge and panel nodes.
> It adds also DSI properties specific for arndale board and
> regulators required by the bridge.
>
> Signed-off-by: Andrzej Hajda
> Signed-off-by: Maciej Purski
> ---
> arch/arm/boot/dts/exy
On Thu, Jul 26, 2018 at 03:22:09PM +0200, Andrzej Hajda wrote:
> HDMI-DDC for unknown reasons doesn't work with Exynos I2C
> controllers. Fortunately i2c-gpio comes to the rescue.
>
> Signed-off-by: Andrzej Hajda
> ---
> arch/arm/boot/dts/exynos5250-arndale.dts | 28 ---
> a
On Thu, Jul 26, 2018 at 12:12:28PM +0200, Andrzej Hajda wrote:
> HDMI-HPD was set active low, moreover by default pincontrol
> chip sets pull-down on the pin. As a result HDMI driver
> assumes TV is always connected regardless of actual state.
> The patch fixes it.
>
> Signed-off-by: Andrzej Hajda
On Wed, 2018-08-29 at 21:10 +0300, Ville Syrjälä wrote:
> On Wed, Aug 29, 2018 at 02:28:47PM +0300, Stanislav Lisovskiy wrote:
> > PLANE_CTL_FORMAT_AYUV is already supported, according to hardware
> > specification.
> >
> > v2: Edited commit message, removed redundant whitespaces.
> >
> > v3: F
On Wed, Aug 29, 2018 at 12:39 AM Abhinav Kumar wrote:
> From: "abhin...@codeaurora.org"
>
> Add the device tree bindings for Truly NT35597 panel driver.
> This panel driver supports both single DSI and dual DSI.
>
> However, this patch series supports only dual DSI.
>
> Changes in v6:
> - Chan
On Tue, Aug 28, 2018 at 04:02:18PM -0700, Jeykumar Sankaran wrote:
> With patch [1], DPU is broken since it continues to use
> incorrect connector_type to identify the display type. Update
> DPU to use the encoder type to get the info.
>
> [1] https://patchwork.kernel.org/patch/10568269/
This plu
Hi Dave,
Fixes for 4.19:
- SR-IOV fixes
- Kasan and page fault fix on device removal
- S3 stability fix for CZ/ST
- VCE regression fixes for CIK parts
- Avoid holding the mn_lock when allocating memory
- DC memory leak fix
- BO eviction fix
The following changes since commit 9d1d02ff36783f954a206
https://bugs.freedesktop.org/show_bug.cgi?id=107689
john-s...@gmx.net changed:
What|Removed |Added
Attachment #141300|0 |1
is obsolete|
https://bugzilla.kernel.org/show_bug.cgi?id=200517
Peter Wu (pe...@lekensteyn.nl) changed:
What|Removed |Added
CC||pe...@lekensteyn.nl
---
https://bugs.freedesktop.org/show_bug.cgi?id=105760
Peter Wu changed:
What|Removed |Added
CC||pe...@lekensteyn.nl
--- Comment #59 from Pet
On Mon, Aug 27, 2018 at 01:39:02PM -0400, Lyude Paul wrote:
> On Mon, 2018-08-27 at 11:43 +0300, Jani Nikula wrote:
> > On Sat, 25 Aug 2018, Lyude Paul wrote:
> > > From: Jan-Marek Glogowski
> > >
> > > This re-applies the workaround for "some DP sinks, [which] are a
> > > little nuts" from comm
On Wed, 2018-08-29 at 14:22 -0700, Rodrigo Vivi wrote:
> On Mon, Aug 27, 2018 at 01:39:02PM -0400, Lyude Paul wrote:
> > On Mon, 2018-08-27 at 11:43 +0300, Jani Nikula wrote:
> > > On Sat, 25 Aug 2018, Lyude Paul wrote:
> > > > From: Jan-Marek Glogowski
> > > >
> > > > This re-applies the workar
More consistent with the rest of the codebase, no functional changes
here.
Signed-off-by: Lyude Paul
Reviewed-by: Karol Herbst
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 2 +-
drivers/gpu/drm/nouveau/nouveau_connector.c | 2 +-
drivers/gpu/drm/nouveau/nouveau_connector.h | 4 ++--
3 file
Currently module unloading is broken in nouveau due to a rather annoying
race condition resulting from nouveau_backlight.c having gone a bit
stale over time:
[ 1960.791143]
==
[ 1960.791394] BUG: KASAN: use-after-free in nouveau_back
Remember, ida IDs start at 0, not 1!
Signed-off-by: Lyude Paul
Reviewed-by: Karol Herbst
Cc: sta...@vger.kernel.org
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c
b/drivers/gpu/
Next version of https://patchwork.freedesktop.org/series/48596/ . Made
some important changes to the refactoring patch, but everything else is
the same.
Lyude Paul (5):
drm/nouveau: Check backlight IDs are >= 0, not > 0
drm/nouveau: Move backlight device into nouveau_connector
drm/nouveau: s
Still no functional changes.
Signed-off-by: Lyude Paul
Reviewed-by: Karol Herbst
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c
b/drivers/gpu/drm/nouveau/nouveau_backl
There's literally no difference between any of the backlight init
functions besides the backlight properties they set and the backlight
callbacks that they set, so move all of the duplicated backlight init
code out of there and into nouveau_backlight_init().
This gets rid of a lot of copy pasta!
Next version of https://patchwork.freedesktop.org/series/48596/ . Added
NV_INFO_ONCE and made "Move backlight device into nouveau_connector" use
that instead so we don't print the GMUX warning more then once.
Lyude Paul (5):
drm/nouveau: Add NV_PRINTK_ONCE and variants
drm/nouveau: Move backli
Since we're about to use this in nouveau_backlight.c. Same thing as
DRM_WARN_ONCE, DRM_INFO_ONCE, etc...
Signed-off-by: Lyude Paul
Cc: Karol Herbst
---
drivers/gpu/drm/nouveau/nouveau_drv.h | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/nouveau_drv.h
b/driv
Currently module unloading is broken in nouveau due to a rather annoying
race condition resulting from nouveau_backlight.c having gone a bit
stale over time:
[ 1960.791143]
==
[ 1960.791394] BUG: KASAN: use-after-free in nouveau_back
More consistent with the rest of the codebase, no functional changes
here.
Signed-off-by: Lyude Paul
Reviewed-by: Karol Herbst
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 2 +-
drivers/gpu/drm/nouveau/nouveau_connector.c | 2 +-
drivers/gpu/drm/nouveau/nouveau_connector.h | 4 ++--
3 file
Still no functional changes.
Signed-off-by: Lyude Paul
Reviewed-by: Karol Herbst
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c
b/drivers/gpu/drm/nouveau/nouveau_backl
There's literally no difference between any of the backlight init
functions besides the backlight properties they set and the backlight
callbacks that they set, so move all of the duplicated backlight init
code out of there and into nouveau_backlight_init().
This gets rid of a lot of copy pasta!
Remember, ida IDs start at 0, not 1!
Signed-off-by: Lyude Paul
Reviewed-by: Karol Herbst
Cc: sta...@vger.kernel.org
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c
b/drivers/gpu/
Forgot to send 6 patches instead of five since there's one new one now,
whoops!
No actual changes, next version of
https://patchwork.freedesktop.org/series/48596/
Lyude Paul (6):
drm/nouveau: Check backlight IDs are >= 0, not > 0
drm/nouveau: Add NV_PRINTK_ONCE and variants
drm/nouveau: Mov
Since we're about to use this in nouveau_backlight.c. Same thing as
DRM_WARN_ONCE, DRM_INFO_ONCE, etc...
Signed-off-by: Lyude Paul
Cc: Karol Herbst
---
drivers/gpu/drm/nouveau/nouveau_drv.h | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/nouveau/nouveau_drv.h
b/driv
Still no functional changes.
Signed-off-by: Lyude Paul
Reviewed-by: Karol Herbst
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_backlight.c
b/drivers/gpu/drm/nouveau/nouveau_backl
Currently module unloading is broken in nouveau due to a rather annoying
race condition resulting from nouveau_backlight.c having gone a bit
stale over time:
[ 1960.791143]
==
[ 1960.791394] BUG: KASAN: use-after-free in nouveau_back
There's literally no difference between any of the backlight init
functions besides the backlight properties they set and the backlight
callbacks that they set, so move all of the duplicated backlight init
code out of there and into nouveau_backlight_init().
This gets rid of a lot of copy pasta!
More consistent with the rest of the codebase, no functional changes
here.
Signed-off-by: Lyude Paul
Reviewed-by: Karol Herbst
---
drivers/gpu/drm/nouveau/nouveau_backlight.c | 2 +-
drivers/gpu/drm/nouveau/nouveau_connector.c | 2 +-
drivers/gpu/drm/nouveau/nouveau_connector.h | 4 ++--
3 file
1 - 100 of 124 matches
Mail list logo
