On Tue, 3 Dec 2019 22:20:14 +0100
Daniel Vetter wrote:
> On Tue, Dec 3, 2019 at 8:10 PM Sean Paul wrote:
> >
> > On Thu, Oct 17, 2019 at 10:22:16AM +0300, Pekka Paalanen wrote:
> > > On Wed, 16 Oct 2019 15:23:45 +0200
> > > Thomas Zimmermann wrote:
> > >
> > > > Hi
> > > >
> > > > Am 16.10.
Hi John
Am 03.12.19 um 18:55 schrieb John Donnelly:
> Hi ,
>
> See below ,
>
>
>> On Nov 26, 2019, at 3:50 AM, Thomas Zimmermann wrote:
>>
>> Hi
>>
>> Am 26.11.19 um 10:37 schrieb Daniel Vetter:
>>> On Tue, Nov 26, 2019 at 08:25:44AM +0100, Thomas Zimmermann wrote:
There's at least one sy
On Tue, 03 Dec 2019, Daniel Vetter wrote:
> On Tue, Dec 03, 2019 at 06:38:46PM +0200, Jani Nikula wrote:
>> Avoid modifying the fb_ops via info->fbops to let us make the pointer
>> const in the future.
>>
>> Cc: linux-fb...@vger.kernel.org
>> Signed-off-by: Jani Nikula
>> ---
>> drivers/video/f
Hi, Bibby:
You move the mutex protection to [PATCH v2 6/6] drm/mediatek: apply CMDQ
control flow, but the race condition exist in this patch. So you should
move that back in this patch.
Regards,
CK
On Tue, 2019-12-03 at 15:10 +0800, Bibby Hsieh wrote:
> Support to async updates of cursors by usi
Hi, Bibby:
On Tue, 2019-12-03 at 15:10 +0800, Bibby Hsieh wrote:
> layer_on and layer_off both are unused external function,
> remove them from mtk_ddp_comp_funcs structure.
>
Reviewed-by: CK Hu
> Signed-off-by: Bibby Hsieh
> ---
> drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 2 --
> drive
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: ee5e5e7a5e0f ("drm/i915: Add HDCP framework + base
implementation").
The bot has tested the following trees: v5.4.1, v5.3.14, v4.19.87.
v5.4.1: Build OK!
v5.3.14: Build OK!
v4.19.
On Fri, Nov 29, 2019 at 1:07 PM Thierry Reding wrote:
>
> On Fri, Nov 29, 2019 at 11:22:08AM +0100, Rafael J. Wysocki wrote:
> >
[cut]
Sorry for the delay.
First off, let me note that I have seen your most recent patches and
thanks for taking the feedback into account, much appreciated!
Nevert
Currently we always determine the initial panel brightness level by
simply reading the value from DP_EDP_BACKLIGHT_BRIGHTNESS_MSB/LSB. This
seems wrong though, because if the panel is not currently in DPCD
control mode there's not really any reason why there would be any
brightness value programmed
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20191203]
[cannot apply to drm-intel/for-linux-next linus/master v5.4-rc8 v5.4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to
On Tue, Dec 3, 2019 at 11:25 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:76bb8b05 Merge tag 'kbuild-v5.5' of git://git.kernel.org/p..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10bfe282e0
> kernel config:
On Tue, Dec 3, 2019 at 2:22 PM Matthias Kaehlcke wrote:
>
> Hi,
>
> On Fri, Nov 29, 2019 at 12:35:05PM +0530, Harigovindan P wrote:
> > Changes in v1:
> > -Modify commit text to indicate DSI version and SOC detail(Jeffrey
> > Hugo).
> > -Splitting visionox panel driver code out into a
Hi,
On Fri, Nov 29, 2019 at 12:35:05PM +0530, Harigovindan P wrote:
> Changes in v1:
> -Modify commit text to indicate DSI version and SOC detail(Jeffrey
> Hugo).
> -Splitting visionox panel driver code out into a
>different patch(set), since panel drivers are merged into
>
On Tue, 19 Nov 2019 15:17:31 +0100, Paul Cercueil wrote:
> Add a compatible string for the LCD controller found in the JZ4770 SoC.
>
> Signed-off-by: Paul Cercueil
> ---
> Documentation/devicetree/bindings/display/ingenic,lcd.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20191203]
[cannot apply to drm-intel/for-linux-next linus/master v5.4-rc8 v5.4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to
https://bugzilla.kernel.org/show_bug.cgi?id=201957
Łukasz Żarnowiecki (luk...@zarnowiecki.pl) changed:
What|Removed |Added
CC||luk...@zarnow
On Tue, 2019-12-03 at 10:33 +0100, Daniel Vetter wrote:
> On Mon, Dec 02, 2019 at 01:49:47PM -0500, Lyude Paul wrote:
> > Reviewed-by: Lyude Paul
> >
> > I'll go ahead and push this to drm-misc-next, thanks!
>
> drm-misc-next-fixes since it's in the merge window. drm-misc-next is for
> 5.6 alrea
Hi Adam,
On Mon, Dec 02, 2019 at 07:24:09AM -0600, Adam Ford wrote:
> On Mon, Dec 2, 2019 at 7:13 AM Laurent Pinchart wrote:
> > On Thu, Nov 14, 2019 at 11:39:47AM +0200, Tomi Valkeinen wrote:
> > > Hi Tony, Thierry, Laurent,
> > >
> > > After the recent change of moving from omapdrm specific pane
On Tue, Dec 3, 2019 at 8:10 PM Sean Paul wrote:
>
> On Thu, Oct 17, 2019 at 10:22:16AM +0300, Pekka Paalanen wrote:
> > On Wed, 16 Oct 2019 15:23:45 +0200
> > Thomas Zimmermann wrote:
> >
> > > Hi
> > >
> > > Am 16.10.19 um 15:05 schrieb Pekka Paalanen:
> >
> > > > specifically be available in pr
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on next-20191203]
[cannot apply to drm-intel/for-linux-next linus/master v5.4-rc8 v5.4]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to
[AMD Official Use Only - Internal Distribution Only]
Hi Andrey,
Thanks very much.
Best wishes
Emily Deng
From: Grodzovsky, Andrey
Sent: Tuesday, December 3, 2019 12:33 PM
To: Deucher, Alexander ; Deng, Emily
Cc: dri-devel@lists.freedesktop.org; amd-...@lists.freedesktop.org; Koenig,
Chris
Hi Dave, Daniel,
Fixes for 5.5.
The following changes since commit acc61b8929365e63a3e8c8c8913177795aa45594:
Merge tag 'drm-next-5.5-2019-11-22' of
git://people.freedesktop.org/~agd5f/linux into drm-next (2019-11-26 08:40:23
+1000)
are available in the Git repository at:
git://people.fre
Turns out Steven's patch was already in so i just cherry-picked the
change from drm-next-misc
Emily - it's in.
Andrey
On 12/3/19 2:59 PM, Deucher, Alexander wrote:
[AMD Official Use Only - Internal Distribution Only]
Cherry pick whatever dependencies you need or pick the older version
Yuti, you have phy maintainer (Kishon) in cc, but you do not have
linux-ker...@vger.kernel.org list mentioned under "GENERIC PHY
FRAMEWORK" entry in the MAINTAINERS file [1]. Please add that to the
recipient list
in the next round.
Best regards,
Jyri
[1] https://www.kernel.org/doc/linux/MAINTAINE
[AMD Official Use Only - Internal Distribution Only]
Cherry pick whatever dependencies you need or pick the older version of the
patch. Either way works.
Alex
From: Grodzovsky, Andrey
Sent: Tuesday, December 3, 2019 2:57 PM
To: Deucher, Alexander ; Deng, Emily
I don't think i can apply this patch 'as is' as this has dependency on
patch by Steven which also wasn't applied yet - 588b982 Steven
Price 6 weeks ago drm: Don't free jobs in
wait_event_interruptible()
Andrey
On 12/3/19 2:44 PM, Deucher, Alexander wrote:
[AMD Official Use Only
[AMD Official Use Only - Internal Distribution Only]
Hi Alex,
When we will cherry pick those patches to drm-next?
>-Original Message-
>From: Grodzovsky, Andrey
>Sent: Tuesday, December 3, 2019 11:10 AM
>To: Deng, Emily ; Deucher, Alexander
>
>Cc: dri-devel@lists.freedesktop.org; amd-
[AMD Official Use Only - Internal Distribution Only]
Please go ahead an apply whatever version is necessary for amd-staging-drm-next.
Alex
From: Grodzovsky, Andrey
Sent: Tuesday, December 3, 2019 2:10 PM
To: Deng, Emily ; Deucher, Alexander
Cc: dri-devel@lists
On 03/12/2019 19:31, kbuild test robot wrote:
> Hi Yuti,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on drm-exynos/exynos-drm-next]
> [also build test ERROR on v5.4 next-20191203]
> [if your patch is applied to the wrong git tree, ple
On Tue, Nov 26, 2019 at 06:32:52PM +, Jason Gunthorpe wrote:
On Mon, Nov 25, 2019 at 11:33:27AM -0500, Jerome Glisse wrote:
On Fri, Nov 22, 2019 at 11:33:12PM +, Jason Gunthorpe wrote:
> On Fri, Nov 22, 2019 at 12:57:27PM -0800, Niranjana Vishwanathapura wrote:
[...]
> > +static int
>
On Tue, Nov 26, 2019 at 06:45:14PM +, Jason Gunthorpe wrote:
On Mon, Nov 25, 2019 at 08:32:58AM -0800, Niranjan Vishwanathapura wrote:
> And putting the cpu PFN of a ZONE_DEVICE device page into
> sg_dma_address still looks very wrong to me
The below call in patch 7 does convert any cpu PFN
On Tue, Dec 03, 2019 at 07:18:11PM +0530, Jagan Teki wrote:
> The MIPI DSI PHY controller on Allwinner A64 is similar
> on the one on A31.
>
> Add A64 compatible and append A31 compatible as fallback.
>
> Signed-off-by: Jagan Teki
> ---
> Changes for v12:
> - none
>
> .../bindings/phy/allwinne
On Thu, Oct 17, 2019 at 10:22:16AM +0300, Pekka Paalanen wrote:
> On Wed, 16 Oct 2019 15:23:45 +0200
> Thomas Zimmermann wrote:
>
> > Hi
> >
> > Am 16.10.19 um 15:05 schrieb Pekka Paalanen:
>
> > > specifically be available in production. So a new file in some fs
> > > somewhere it should be, a
Yes - Christian just pushed it to drm-next-misc - I guess Alex/Christian
didn't pull to amd-staging-drm-next yet.
Andrey
On 12/2/19 2:24 PM, Deng, Emily wrote:
[AMD Official Use Only - Internal Distribution Only]
Hi Andrey,
Seems this patch is still not in amd-staging-drm-next?
Best wis
On 03/12/2019 15:09, Linus Walleij wrote:
> The TI LCDC picks a GPIO line from the device tree to use
> for DPMS power on/off. We can switch this to use a GPIO
> descriptor pretty easily. Make sure to request the GPIO
> "as is" so that the DPMS state that we start (boot) in is
> preserved.
>
Hmmm
Hi Boris,
On Tue, Dec 03, 2019 at 03:15:04PM +0100, Boris Brezillon wrote:
> This patch series aims at adding support for runtime bus-format
> negotiation between all elements of the
> 'encoder -> bridges -> connector/display' section of the pipeline.
>
> In order to support that, we need drm bri
Hi Boris,
Thank you for the patch.
On Tue, Dec 03, 2019 at 03:15:12PM +0100, Boris Brezillon wrote:
> One of the last remaining objects to not have its atomic state.
>
> This is being motivated by our attempt to support runtime bus-format
> negotiation between elements of the bridge chain.
> Thi
Hi Boris,
Thanks for the patch.
On Tue, Dec 03, 2019 at 03:15:11PM +0100, Boris Brezillon wrote:
> The [pre_]enable/[post_]disable hooks are passed the old atomic state.
> Update the doc and rename the arguments to make it clear.
>
> Signed-off-by: Boris Brezillon
> Reviewed-by: Laurent Pinchar
Hi ,
See below ,
> On Nov 26, 2019, at 3:50 AM, Thomas Zimmermann wrote:
>
> Hi
>
> Am 26.11.19 um 10:37 schrieb Daniel Vetter:
>> On Tue, Nov 26, 2019 at 08:25:44AM +0100, Thomas Zimmermann wrote:
>>> There's at least one system that does not interpret the value of
>>> the device's 'startadd
Hi Linus.
On Tue, Dec 03, 2019 at 04:26:55PM +0100, Linus Walleij wrote:
> The Rpi panel driver doesn't use any symbols from these
> GPIO includes so just drop them.
>
> Cc: Eric Anholt
> Signed-off-by: Linus Walleij
> ---
> drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c | 2 --
> 1 fil
From: Sean Paul
Now that all the groundwork has been laid, we can turn on HDCP 1.4 over
MST. Everything except for toggling the HDCP signalling and HDCP 2.2
support is the same as the DP case, so we'll re-use those callbacks
Signed-off-by: Sean Paul
---
drivers/gpu/drm/i915/display/intel_dp_ms
From: Sean Paul
These functions are all the same for dp and dp_mst, so expose them for
use by the dp_mst hdcp implementation.
Signed-off-by: Sean Paul
---
.../drm/i915/display/intel_display_types.h| 22 +++
drivers/gpu/drm/i915/display/intel_dp.c | 14 ++--
2
From: Sean Paul
In order to act upon content_protection property changes, we'll need to
implement the .update_pipe() hook. We can re-use intel_ddi_update_pipe
for this
Signed-off-by: Sean Paul
---
drivers/gpu/drm/i915/display/intel_ddi.c| 9 +
drivers/gpu/drm/i915/display/intel_dp.
From: Sean Paul
Currently we rely on intel_hdcp_disable() to disable HDCP signalling in
the DDI Function Control register. This patch adds a safety net by also
clearing the bit when we disable the transcoder.
Once we have HDCP over MST and disappearing connectors, we want to make
sure that the s
From: Sean Paul
Now that we can rely on transcoder disable to toggle signalling off,
it's less of a catastrophe if get_hw_state() returns false.
Once we enable MST, this will be a valid exit path and we want to make
sure we're not spamming the logs needlessly.
Signed-off-by: Sean Paul
---
dri
From: Sean Paul
Instead of hand rolling the transfer ourselves in the hdcp hook, inspect
aux messages and add the aksv flag in the aux transfer hook.
IIRC, this was the original implementation and folks wanted this hack to
be isolated to the hdcp code, which makes sense.
However in testing an L
From: Sean Paul
This is a bit of housecleaning for a future patch. Instead of sprinkling
hdcp->value assignments and prop_work scheduling everywhere, introduce a
function to do it for us.
Signed-off-by: Sean Paul
---
drivers/gpu/drm/i915/display/intel_hdcp.c | 67 ---
1 fil
From: Sean Paul
Although DP_MST fake encoders are not subclassed from digital ports,
they are associated with them. Support these encoders.
Signed-off-by: Sean Paul
---
.../drm/i915/display/intel_display_types.h| 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
dif
From: Sean Paul
This patch is required for HDCP over MST. If a port is being used for
multiple HDCP streams, we don't want to fully disable HDCP on a port if
one of them is disabled. Instead, we just disable the HDCP signalling on
that particular pipe and exit early. The last pipe to disable HDCP
From: Sean Paul
HDCP over MST requires us to toggle ddi signalling. Since we'll want to
toggle signalling on the pipe associated with the fake encoder as
opposed to the digital port's base, we need to get it from connector.
This patch converts all existing callers and implementations to use
conn
From: Sean Paul
Hey all,
As the subject says, this set adds support for HDCP 1.4 over MST. Most
of the set is plumbing and refactor to allow the MST support to slot in
organically.
I stubbed out HDCP 2.2 support since I don't have a means of testing it.
If no one picks up the slack, I can come b
From: Sean Paul
This patch fixes a few bugs:
1- We weren't taking into account sha_leftovers when adding multiple
ksvs to sha_text. As such, we were or'ing the end of ksv[j - 1] with
the beginning of ksv[j]
2- In the sha_leftovers == 2 and sha_leftovers == 3 case, bstatus was
being pla
On Tue, Dec 03, 2019 at 06:33:08PM +0100, Daniel Vetter wrote:
> On Tue, Dec 03, 2019 at 05:32:03PM +0100, Thierry Reding wrote:
> > From: Thierry Reding
> >
> > DMA-BUF requires that each device that accesses a DMA-BUF attaches to it
> > separately. To do so the host1x_bo_pin() and host1x_bo_unp
On Tue, Dec 03, 2019 at 05:32:03PM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> DMA-BUF requires that each device that accesses a DMA-BUF attaches to it
> separately. To do so the host1x_bo_pin() and host1x_bo_unpin() functions
> need to be reimplemented so that they can return a mappi
Hi Yuti,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-exynos/exynos-drm-next]
[also build test ERROR on v5.4 next-20191203]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '-
Hello Sasha and Thomas ,
This particular patch has failed on one class of servers that has a slightly
different Sun Vendor. ID for the BMC video device:
I will follow up with additional details in the review comments for the
original message,.
> On Nov 28, 2019, at 8:23 AM, Sasha Levi
On Tue, Dec 03, 2019 at 05:32:02PM +0100, Thierry Reding wrote:
> From: Thierry Reding
>
> Functionality to count the number of contiguous DMA chunks in an SG
> table has been added to the scatterlist library. Use this functionality
> to replace an open-coded version in the GEM/CMA helpers.
>
>
Add very trivial allocation and import test for dma-heaps,
utilizing the vgem driver as a test importer.
A good chunk of this code taken from:
tools/testing/selftests/android/ion/ionmap_test.c
Originally by Laura Abbott
Cc: Benjamin Gaignard
Cc: Sumit Semwal
Cc: Liam Mark
Cc: Pratik Patel
Just wanted to resend v16.
This patchset implements per-heap devices which can be opened
directly and then an ioctl is used to allocate a dmabuf from the
heap.
The interface is similar, but much simpler then IONs, only
providing an ALLOC ioctl.
Also, I've provided relatively simple system and cm
This adds a CMA heap, which allows userspace to allocate
a dma-buf of contiguous memory out of a CMA region.
This code is an evolution of the Android ION implementation, so
thanks to its original author and maintainters:
Benjamin Gaignard, Laura Abbott, and others!
NOTE: This patch only adds th
From: "Andrew F. Davis"
This framework allows a unified userspace interface for dma-buf
exporters, allowing userland to allocate specific types of memory
for use in dma-buf sharing.
Each heap is given its own device node, which a user can allocate
a dma-buf fd from using the DMA_HEAP_IOC_ALLOC.
Add generic helper dmabuf ops for dma heaps, so we can reduce
the amount of duplicative code for the exported dmabufs.
This code is an evolution of the Android ION implementation, so
thanks to its original authors and maintainters:
Rebecca Schultz Zavin, Colin Cross, Laura Abbott, and others!
C
This patch adds system heap to the dma-buf heaps framework.
This allows applications to get a page-allocator backed dma-buf
for non-contiguous memory.
This code is an evolution of the Android ION implementation, so
thanks to its original authors and maintainters:
Rebecca Schultz Zavin, Colin Cr
On 2019-11-26 3:43 p.m., Alex Deucher wrote:
> Shift and mask were reversed. Noticed by chance.
>
> Signed-off-by: Alex Deucher
> ---
> drivers/gpu/drm/radeon/r100.c | 4 ++--
> drivers/gpu/drm/radeon/r200.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/
On Tue, Dec 03, 2019 at 06:38:49PM +0200, Jani Nikula wrote:
> Use const for fb_ops to let us make the fbops struct const in the
> future.
>
> Cc: linux-fb...@vger.kernel.org
> Signed-off-by: Jani Nikula
> ---
> drivers/video/fbdev/intelfb/intelfb.h | 2 +-
> 1 file changed, 1 insertion(+), 1 de
On Tue, Dec 03, 2019 at 06:38:46PM +0200, Jani Nikula wrote:
> Avoid modifying the fb_ops via info->fbops to let us make the pointer
> const in the future.
>
> Cc: linux-fb...@vger.kernel.org
> Signed-off-by: Jani Nikula
> ---
> drivers/video/fbdev/uvesafb.c | 4 ++--
> 1 file changed, 2 inserti
Le sam. 30 nov. 2019 à 14:24, Benjamin Gaignard
a écrit :
>
> Fix the warnings that show up with W=1.
> They are all about unused but set variables.
> If functions returns are not used anymore make them void.
>
> Signed-off-by: Benjamin Gaignard
> ---
> CC: Jani Nikula
>
> changes in version 3:
On Tue, Dec 03, 2019 at 06:38:45PM +0200, Jani Nikula wrote:
> Avoid modifying the fb_ops via info->fbops to let us make the pointer
> const in the future.
>
> Cc: linux-fb...@vger.kernel.org
> Signed-off-by: Jani Nikula
> ---
> drivers/video/fbdev/nvidia/nvidia.c | 20 +++-
> 1
On Tue, Dec 03, 2019 at 06:38:44PM +0200, Jani Nikula wrote:
> Avoid modifying the fb_ops via info->fbops to let us make the pointer
> const in the future. Drop the unnecessary EXPORT_SYMBOL() while at it.
>
> Cc: linux-fb...@vger.kernel.org
> Signed-off-by: Jani Nikula
> ---
> drivers/video/fbd
Le mer. 20 nov. 2019 à 00:29, Benjamin Gaignard
a écrit :
>
> When compiling with W=1 few warnings about unused variables show up.
> This patch removes all the involved variables.
>
Gentle ping to reviewers.
Thanks,
Benjamin
> Signed-off-by: Benjamin Gaignard
> ---
> drivers/gpu/drm/drm_modes.
Le mer. 20 nov. 2019 à 00:28, Benjamin Gaignard
a écrit :
>
> Exported functions prototypes are missing in drm_fb_cma_helper.c
> Include drm_fb_cma_helper to fix that issue.
>
Gentle ping to reviewers.
Thanks,
Benjamin
> Signed-off-by: Benjamin Gaignard
> ---
> drivers/gpu/drm/drm_fb_cma_helpe
Le mer. 20 nov. 2019 à 00:28, Benjamin GAIGNARD
a écrit :
>
>
> On 11/19/19 7:53 PM, Souza, Jose wrote:
> > On Tue, 2019-11-19 at 13:58 +0100, Benjamin Gaignard wrote:
> >> Include drm_crtc_helper_internal.h to provide
> >> drm_connector_get_single_encoder
> >> prototype.
> >>
> >> Fixes: a92462d6
On Tue, Dec 03, 2019 at 06:38:43PM +0200, Jani Nikula wrote:
> Avoid modifying the fb_ops via info->fbops to let us make the pointer
> const in the future.
>
> Cc: linux-fb...@vger.kernel.org
> Signed-off-by: Jani Nikula
> ---
> drivers/video/fbdev/aty/atyfb.h | 2 +-
> drivers/video/fbd
On Mon, Nov 25, 2019 at 10:43:52AM +0100, Daniel Vetter wrote:
> Hi all,
>
> This is prep work for some dma_resv series I'm tinkering with, but I
> figured good to split this out since good idea to land this no matter what
> exactly I'll end up creating in dma_resv. With these everything in
> driv
On Tue, 03 Dec 2019, Jani Nikula wrote:
> This is v3 of https://patchwork.freedesktop.org/series/70198/.
>
> 0day reported some build failures, and I needed to add patches 1-5 and 7
Should be, patches 1-4 and 7.
> to address them. Patch 8 was amended accordingly (dropped some consts),
> but the
On Tue, Dec 3, 2019 at 8:09 PM Chen-Yu Tsai wrote:
>
> On Tue, Dec 3, 2019 at 9:48 PM Jagan Teki wrote:
> >
> > As per the user manual, look like mod clock is not mandatory
> > for all Allwinner MIPI DSI controllers, it is connected to
> > CLK_DSI_SCLK for A31 and not available in A64.
> >
> > So
Now that the fbops member of struct fb_info is const, we can start
making the ops const as well.
v2: fix typo (Christophe de Dinechin)
Cc: Kirti Wankhede
Cc: k...@vger.kernel.org
Reviewed-by: Daniel Vetter
Signed-off-by: Jani Nikula
---
samples/vfio-mdev/mdpy-fb.c | 2 +-
1 file changed, 1 in
Now that the fbops member of struct fb_info is const, we can start
making the ops const as well.
v2: fix typo (Christophe de Dinechin)
Cc: Bruno Prémont
Cc: linux-in...@vger.kernel.org
Reviewed-by: Daniel Vetter
Acked-by: Bruno Prémont
Signed-off-by: Jani Nikula
---
drivers/hid/hid-picolcd_f
Use const for fb_ops to let us make the fbops struct const in the
future.
Cc: linux-fb...@vger.kernel.org
Signed-off-by: Jani Nikula
---
drivers/video/fbdev/intelfb/intelfb.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/intelfb/intelfb.h
b/drivers/vide
Now that the fbops member of struct fb_info is const, we can start
making the ops const as well.
Cc: dri-devel@lists.freedesktop.org
Reviewed-by: Daniel Vetter
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c| 2 +-
drivers/gpu/drm/armada/armada_fbdev.c
Now that the fbops member of struct fb_info is const, we can start
making the ops const as well.
Cc: Miguel Ojeda Sandonis
Cc: Robin van der Gracht
Reviewed-by: Daniel Vetter
Reviewed-by: Miguel Ojeda
Acked-by: Robin van der Gracht
Signed-off-by: Jani Nikula
---
drivers/auxdisplay/cfag12864
Now that the fbops member of struct fb_info is const, we can start
making the ops const as well.
Remove the redundant fbops assignments while at it.
v2:
- actually add const in vivid
- fix typo (Christophe de Dinechin)
Cc: Hans Verkuil
Cc: Andy Walls
Cc: linux-me...@vger.kernel.org
Cc: ivtv-de
Now that the fbops member of struct fb_info is const, we can start
making the ops const as well.
This does not cover all drivers; some actually modify the fbops struct,
for example to adjust for different configurations, and others do more
involved things that I'd rather not touch in practically o
Avoid modifying the fb_ops via info->fbops to let us make the pointer
const in the future.
Cc: linux-fb...@vger.kernel.org
Signed-off-by: Jani Nikula
---
drivers/video/fbdev/aty/atyfb.h | 2 +-
drivers/video/fbdev/aty/atyfb_base.c| 6 +++---
drivers/video/fbdev/aty/mach64_cursor.c |
This is v3 of https://patchwork.freedesktop.org/series/70198/.
0day reported some build failures, and I needed to add patches 1-5 and 7
to address them. Patch 8 was amended accordingly (dropped some consts),
but the other patches remain the same from v2, except the ones I merged
already.
BR,
Jani
Avoid modifying the fb_ops via info->fbops to let us make the pointer
const in the future.
Cc: linux-fb...@vger.kernel.org
Signed-off-by: Jani Nikula
---
drivers/video/fbdev/uvesafb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/video/fbdev/uvesafb.c b/drivers/
Now that we no longer modify the fbops, or hold non-const pointers to
it, we can make it const. After this, we can start making the fbops
const all over the place.
Cc: linux-fb...@vger.kernel.org
Reviewed-by: Daniel Vetter
Signed-off-by: Jani Nikula
---
include/linux/fb.h | 2 +-
1 file changed
Avoid modifying the fb_ops via info->fbops to let us make the pointer
const in the future.
Cc: linux-fb...@vger.kernel.org
Signed-off-by: Jani Nikula
---
drivers/video/fbdev/nvidia/nvidia.c | 20 +++-
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/drivers/video/fb
Avoid modifying the fb_ops via info->fbops to let us make the pointer
const in the future. Drop the unnecessary EXPORT_SYMBOL() while at it.
Cc: linux-fb...@vger.kernel.org
Signed-off-by: Jani Nikula
---
drivers/video/fbdev/mb862xx/mb862xxfb.h | 2 +-
drivers/video/fbdev/mb862xx/mb862xxfb
On Tue, Dec 3, 2019 at 7:23 AM Sharat Masetty wrote:
>
> Fix the cx debugbus related register configuration, to collect accurate
> bus data during gpu snapshot. This helps with complete snapshot dump
> and also complete proper GPU recovery.
>
> Signed-off-by: Sharat Masetty
fwiw, this one we alr
From: Thierry Reding
DMA-BUF requires that each device that accesses a DMA-BUF attaches to it
separately. To do so the host1x_bo_pin() and host1x_bo_unpin() functions
need to be reimplemented so that they can return a mapping, which either
represents an attachment or a map of the driver's own GEM
From: Thierry Reding
Functionality to count the number of contiguous DMA chunks in an SG
table has been added to the scatterlist library. Use this functionality
to replace an open-coded version in the GEM/CMA helpers.
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/drm_gem_cma_helper.c | 22
From: Thierry Reding
Add a few helpers to count the number of contiguous DMA chunks found in
an SG table. This is useful to determine whether or not a mapping can be
used by drivers whose devices need contiguous memory.
Signed-off-by: Thierry Reding
---
include/linux/scatterlist.h | 11 +++
From: Thierry Reding
Implement generic system suspend/resume functions that can be used with
any output type. Currently this only implements disabling and enabling
of the IRQ functionality across system suspend/resume. This prevents an
interrupt from happening before the display driver has fully
From: David Francis
With DSC, bpp can be fractional in multiples of 1/16.
Change drm_dp_calc_pbn_mode to reflect this, adding a new
parameter bool dsc. When this parameter is true, treat the
bpp parameter as having units not of bits per pixel, but
1/16 of a bit per pixel
v2: Don't add separate
From: Thierry Reding
Rename the host1x clients' parent to "host" because that more closely
describes what it is. The parent can be confused with the parent device
in terms of the device hierarchy. Subsequent patches will add a new
member that refers to the parent in that hierarchy.
Signed-off-by
From: Thierry Reding
The Tegra DRM driver heavily relies on the implementations for runtime
suspend/resume to be called at specific times. Unfortunately, there are
some cases where that doesn't work. One example is if the user disables
runtime PM for a given subdevice. Another example is that the
From: Thierry Reding
Export the module device table to ensure the VIC compatible strings are
listed in the module's aliases table. This in turn causes the driver to
be automatically loaded on boot if VIC is the only enabled subdevice of
the logical host1x DRM device.
Reviewed-by: Daniel Vetter
From: Thierry Reding
Subdevices may not be hooked up to an IOMMU via device tree. Detect such
situations and avoid confusing users by not emitting an error message.
Reviewed-by: Daniel Vetter
Signed-off-by: Thierry Reding
---
drivers/gpu/drm/tegra/dc.c | 2 +-
drivers/gpu/drm/tegra/drm.c | 4
From: Thierry Reding
The SOR supports multiple display modes, but only when driving an HDMI
monitor does it make sense to control the +5V power supply. eDP and DP
don't need this, so make it optional.
This fixes a crash observed during system suspend/resume.
Reviewed-by: Daniel Vetter
Signed-o
From: Thierry Reding
The call to tegra_display_hub_cleanup() that takes care of disabling the
window groups is missing from the driver's ->remove() callback. Call it
to make sure the runtime PM reference counts for the display controllers
are balanced.
Signed-off-by: Thierry Reding
---
drivers
1 - 100 of 283 matches
Mail list logo
