On 8/23/19 12:56 PM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 11:32 AM shuah wrote:
On 8/23/19 11:54 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 10:34 AM shuah wrote:
On 8/23/19 11:27 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 10:05 AM shuah wrote:
On 8/23/19
Hi Harry,
Thanks for your feedback, I'll prepare a V2.
On 08/23, Wentland, Harry wrote:
> On 2019-08-22 6:46 p.m., Siqueira, Rodrigo wrote:
> > DP 1.4 specification defines Link Training Tunable PHY Repeater (LTTPR)
> > which is required to add support for systems with Thunderbolt or other
> >
Instead of having drm_dp_dpcd_read/write and
drm_dp_mst_dpcd_read/write as entry points into the
aux code, have drm_dp_dpcd_read/write handle both.
This means that DRM drivers can make MST DPCD read/writes.
v2: Fix spacing
v3: Dump dpcd access on MST read/writes
Reviewed-by: Lyude Paul
Add necessary support for MST DSC.
(Display Stream Compression over Multi-Stream Transport)
v4: Split patchset and rebase onto drm-tip
v5: Clean up formatting, make new quirk
David Francis (5):
drm/dp_mst: Add PBN calculation for DSC modes
drm/dp_mst: Parse FEC capability on MST ports
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 function for this
As of DP1.4, ENUM_PATH_RESOURCES returns a bit indicating
if FEC can be supported up to that point in the MST network.
The bit is the first byte of the ENUM_PATH_RESOURCES ack reply,
bottom-most bit (refer to section 2.11.9.4 of DP standard,
v1.4)
That value is needed for FEC and DSC support
On Fri, Aug 23, 2019 at 11:32 AM shuah wrote:
>
> On 8/23/19 11:54 AM, Brendan Higgins wrote:
> > On Fri, Aug 23, 2019 at 10:34 AM shuah wrote:
> >>
> >> On 8/23/19 11:27 AM, Brendan Higgins wrote:
> >>> On Fri, Aug 23, 2019 at 10:05 AM shuah wrote:
>
> On 8/23/19 10:48 AM, Brendan
(And CC'ing Andrzej Hajda and Neil Armstrong as the new DRM bridge
maintainers, as well as Boris Brezillon, to make sure they're aware of
the problem)
I would really appreciate if we could delay merging this series and
other similar changes until we find a proper solution.
On Fri, Aug 23, 2019
On 8/23/19 1:20 PM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 12:04 PM shuah wrote:
On 8/23/19 12:56 PM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 11:32 AM shuah wrote:
On 8/23/19 11:54 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 10:34 AM shuah wrote:
On 8/23/19 11:27
Hi Dave, Daniel,
A few new bits for 5.4, mostly ongoing new asic support. This is pretty much it
for 5.4. We have a few patches for display enablement of renoir which should be
out next week (just wrapping up IP review).
The following changes since commit
Currently, we don't call dma_set_max_seg_size() for i915 because we
intentionally do not limit the segment length that the device supports.
However, this results in a warning being emitted if we try to map
anything larger than SZ_64K on a kernel with CONFIG_DMA_API_DEBUG_SG
enabled:
[
On 8/23/19 11:54 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 10:34 AM shuah wrote:
On 8/23/19 11:27 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 10:05 AM shuah wrote:
On 8/23/19 10:48 AM, Brendan Higgins wrote:
On Fri, Aug 23, 2019 at 8:33 AM shuah wrote:
Hi Brendan,
On
On 2019-08-22 5:50 p.m., Wayne Lin wrote:
> For HDMI2.0 CTS item - HF1-35, it verifies if the source generates
> video timing "64:27" video format correctly.
>
> eg: (vic-76) 1920x1080p@60Hz,24bpp
>
> This patch add on "64:27" and "256:135" to drm_aspect_ratio_enum_list.
> Thereafter, one can
On Thu, Aug 22, 2019 at 05:50:02PM -0400, Wayne Lin wrote:
> For HDMI2.0 CTS item - HF1-35, it verifies if the source generates
> video timing "64:27" video format correctly.
>
> eg: (vic-76) 1920x1080p@60Hz,24bpp
>
> This patch add on "64:27" and "256:135" to drm_aspect_ratio_enum_list.
>
Hans Verkuil writes:
> From: Dariusz Marcinkiewicz
>
> Fill in the connector info, allowing userspace to associate
> the CEC device with the drm connector.
Acked-by: Eric Anholt
signature.asc
Description: PGP signature
___
dri-devel mailing list
Add a type field to the drm_panel structure to report the panel type,
using DRM_MODE_CONNECTOR_* macros (the values that make sense are LVDS,
eDP, DSI and DPI). This will be used to initialise the corresponding
connector type.
Update all panel drivers accordingly. The panel-simple driver only
Panels must be initialised with drm_panel_init(). Add the missing
function call in the panel-raspberrypi-touchscreen.c and
panel-sitronix-st7789v.c drivers.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/panel/panel-raspberrypi-touchscreen.c | 1 +
Instead of requiring all drivers to set the dev and funcs fields of
drm_panel manually after calling drm_panel_init(), pass the data as
arguments to the function. This simplifies the panel drivers, and will
help future refactoring when adding new arguments to drm_panel_init().
The panel drivers
Hello,
This series is the second version of a previously unnamed series that
contained
[PATCH 1/2] drm/panel: Add and fill drm_panel type field
[PATCH 2/2] drm/bridge: panel: Use drm_panel.type instead of explicit
connector_type
The purpose of the change is to allow panels to report their
The drm panel bridge creates a connector using a connector type explicit
passed by the display controller or bridge driver that instantiates the
panel bridge. Now that drm_panel reports its connector type, we can use
it to avoid passing an explicit (and often incorrect) connector type to
Add drm_dp_mst_dsc_aux_for_port. To enable DSC, the DSC_ENABLED
register might have to be written on the leaf port's DPCD,
its parent's DPCD, or the MST manager's DPCD. This function
finds the correct aux for the job.
As part of this, add drm_dp_mst_is_virtual_dpcd. Virtual DPCD
is a DP feature
This field on drm_dp_mst_branch was never filled
It is initialized to zero when the port is kzallocced.
When a port is added to the list, increment num_ports,
and when a port is removed from the list, decrement num_ports.
v2: remember to decrement on port removal
v3: don't explicitly init to 0
On Thu, Aug 22, 2019 at 5:28 PM Lionel Landwerlin <
lionel.g.landwer...@intel.com> wrote:
> On 22/08/2019 21:24, Jason Ekstrand wrote:
>
> On Thu, Aug 22, 2019 at 9:55 AM Lionel Landwerlin <
> lionel.g.landwer...@intel.com> wrote:
>
>> We've added a set of new APIs to manipulate syncobjs holding
Hi Hans,
Thank you for the patch.
On Fri, Aug 23, 2019 at 01:24:27PM +0200, Hans Verkuil wrote:
> Set the connector info to help userspace associate the CEC adapter
> with the HDMI connector.
>
> This required that the cec initialization and unregistering the
> CEC adapter takes place in the
On Fri, Aug 23, 2019 at 12:04 PM shuah wrote:
>
> On 8/23/19 12:56 PM, Brendan Higgins wrote:
> > On Fri, Aug 23, 2019 at 11:32 AM shuah wrote:
> >>
> >> On 8/23/19 11:54 AM, Brendan Higgins wrote:
> >>> On Fri, Aug 23, 2019 at 10:34 AM shuah wrote:
>
> On 8/23/19 11:27 AM, Brendan
Quoting Lyude Paul (2019-08-22 21:31:26)
> Currently, we don't call dma_set_max_seg_size() for i915 because we
> intentionally do not limit the segment length that the device supports.
> However, this results in a warning being emitted if we try to map
> anything larger than SZ_64K on a kernel
Adding DSC functionality to drm_dp_mst_atomic_check() is a good idea.
However, until amdgpu switches over to that system, I wouldn't be able
to test those changes. Making that switch is on our TODO list, and it would
fix a number of problems with our current MST implementation, but
it's going to
https://bugzilla.kernel.org/show_bug.cgi?id=204611
tones...@hotmail.com changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving this
On Fri, Aug 23, 2019 at 04:28:05PM -0400, David Francis wrote:
> 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,
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
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
Reviewed-by: Stephen Boyd
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,
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
Reviewed-by: Stephen Boyd
---
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
Reviewed-by: Stephen Boyd
---
MAINTAINERS | 11 +++
1 file changed, 11 insertions(+)
diff --git a/MAINTAINERS
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
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
Reviewed-by:
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
Reviewed-by: Stephen Boyd
---
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
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:
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 `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
Reviewed-by: Stephen Boyd
---
include/kunit/assert.h
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
## TL;DR
This revision addresses comments from Shuah by fixing a couple
checkpatch warnings and fixing some comment readability issues. No API
or major structual changes have been made since v13.
## Background
This patch set proposes KUnit, a lightweight unit testing and mocking
framework for
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
Reviewed-by: Stephen Boyd
---
include/kunit/test.h | 836 +++
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,
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
On Fri, 2019-08-23 at 16:28 -0400, David Francis wrote:
> 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
>
The ingenic driver supports DPI panels only at the moment, so hardcode
their type to DPI instead of Unknown.
Signed-off-by: Laurent Pinchart
---
Paul, as the driver has been merged in v5.3-rc1, this is a candidate for
a v5.3 fix. Keeping the connector type as unknown could cause a
userspace
Here is yet another pass at the dma-buf heaps patchset Andrew
and I have been working on which tries to destage a fair chunk
of ION functionality.
The 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
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.
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
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!
Cc: Laura Abbott
Cc:
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
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!
https://bugzilla.kernel.org/show_bug.cgi?id=204181
Tom Seewald (tseew...@gmail.com) changed:
What|Removed |Added
CC||tseew...@gmail.com
Although hmm_range_fault() calls find_vma() to make sure that a vma exists
before calling walk_page_range(), hmm_vma_walk_hole() can still be called
with walk->vma == NULL if the start and end address are not contained
within the vma range.
hmm_range_fault() /* calls find_vma() but no range
Normally, callers to handle_mm_fault() are supposed to check the
vma->vm_flags first. hmm_range_fault() checks for VM_READ but doesn't
check for VM_WRITE if the caller requests a page to be faulted in
with write permission (via the hmm_range.pfns[] value).
If the vma is write protected, this can
I have been working on converting Jerome's hmm_dummy driver and self
tests into a stand-alone set of tests to be included in
tools/testing/selftests/vm and came across these two bug fixes in the
process. The tests aren't quite ready to be posted as a patch.
I'm posting the fixes now since I
Hi Thomas,
On Thu, Aug 22, 2019 at 07:25:11PM +0200, Thomas Zimmermann wrote:
> Hi
>
> I was traveling and could reply earlier. Sorry for taking so long.
No problem! I guessed so :)
>
> Am 13.08.19 um 11:36 schrieb Feng Tang:
> > Hi Thomas,
> >
> > On Mon, Aug 12, 2019 at 03:25:45PM +0800,
Hey Linus,
Although the tree built for me fine on arm here, it appears either
header cleanups in next or some kconfig combo it breaks, so this
contains a fix to mediatek to include dma-mapping.h explicitly.
There was also one nouveau fix that came in late that I was going to
leave until next
Hi all,
On Fri, 23 Aug 2019 17:00:39 -0700 (PDT) "kernelci.org bot"
wrote:
>
> 2drivers/gpu/drm/mediatek/mtk_drm_drv.c:291:8: error: implicit
> declaration of function 'dma_set_max_seg_size'; did you mean
> 'drm_rect_adjust_size'? [-Werror=implicit-function-declaration]
> 2
On Sat, 24 Aug 2019 at 13:53, Stephen Rothwell wrote:
>
> Hi all,
>
> On Fri, 23 Aug 2019 17:00:39 -0700 (PDT) "kernelci.org bot"
> wrote:
> >
> > 2drivers/gpu/drm/mediatek/mtk_drm_drv.c:291:8: error: implicit
> > declaration of function 'dma_set_max_seg_size'; did you mean
> >
On Fri, 23 Aug 2019 03:34:06 +0300
Laurent Pinchart wrote:
> Hi Boris,
>
> On Thu, Aug 22, 2019 at 06:41:25PM +0200, Boris Brezillon wrote:
> > On Tue, 20 Aug 2019 04:16:35 +0300 Laurent Pinchart wrote:
> >
> > > +/**
> > > + * enum drm_bridge_ops - Bitmask of operations supported by the
From: Thomas Hellstrom
The FAULT_FLAG_ALLOW_RETRY semantics is tricky and appears poorly
documented. Add a comment to the TTM fault() implementation to avoid
future confusion.
Cc: Christian Koenig
Signed-off-by: Thomas Hellstrom
---
drivers/gpu/drm/ttm/ttm_bo_vm.c | 11 +++
1 file
https://bugzilla.kernel.org/show_bug.cgi?id=197327
xtornado (xtorn...@gmail.com) changed:
What|Removed |Added
CC||xtorn...@gmail.com
---
From: Thomas Hellstrom
The FAULT_FLAG_ALLOW_RETRY semantics is tricky and appears poorly
documented. Add a comment to the TTM fault() implementation to avoid
future confusion.
Cc: Christian Koenig
Signed-off-by: Thomas Hellstrom
---
v2: Incorrect email to Christian :)
---
From: Thomas Hellstrom
With SEV encryption, all DMA memory must be marked decrypted
(AKA "shared") for devices to be able to read it. In the future we might
want to be able to switch normal (encrypted) memory to decrypted in exactly
the same way as we handle caching states, and that would
From: Thomas Hellstrom
The TTM dma pool allocates coherent pages for use with TTM. When SEV is
active, such allocations become very expensive since the linear kernel
map has to be changed to mark the pages decrypted. So to avoid too many
such allocations and frees, cache the decrypted pages even
The sti_hdmi.c file include despite not even
using any GPIOs.
What it does use is devm_ioremap_nocache() which comes from
implicitly by including that header.
Fix this up by including the right header instead.
Cc: Benjamin Gaignard
Cc: Vincent Abriou
Signed-off-by: Linus Walleij
---
On 19/08/2019 17:12, Rob Herring wrote:
> Calling dma_unmap_sg() in drm_gem_shmem_free_object() is too late if the
> backing pages have already been released by the shrinker. The result is
> the following abort:
>
> Unable to handle kernel paging request at virtual address 898ed000
> Mem
On 19/08/2019 17:12, Rob Herring wrote:
> This fixes 2 issues found by lockdep. First, drm_gem_shmem_purge()
> now uses mutex_trylock for the pages_lock to avoid a circular
> dependency.
NIT: This is in the previous patch.
> Second, it drops the call to panfrost_mmu_unmap() which takes several
>
On 19/08/2019 17:12, Rob Herring wrote:
> We can't hold the mm_lock spinlock as panfrost_mmu_map() can sleep:
>
> BUG: sleeping function called from invalid context at
> kernel/locking/mutex.c:909
> in_atomic(): 1, irqs_disabled(): 0, pid: 974, name: glmark2-es2-drm
> 1 lock held by
On 19/08/2019 17:12, Rob Herring wrote:
> Lockdep reports a circular locking dependency with pages_lock taken in
> the shrinker callback. The deadlock can't actually happen with current
> users at least as a BO will never be purgeable when pages_lock is held.
> To be safe, let's use
The DPU has some kind of idea that it wants to be able to
bring up power using GPIO lines. The struct dss_gpio is however
completely unused and should this be done, it should be done
using the GPIO descriptor framework rather than this API
which relies on the global GPIO numberspace. Delete this
There is elaborate code in the HDMI connector handling to
leave the connector in the state it was at power-on and
only touch the GPIOs when the connector .enable() and
.disable() callbacks are called.
I don't think this is what we normally want, initialize
the connector as OFF (possibly saving
This DSI driver uses the new descriptor API so these old
GPIO API includes are surplus.
Cc: Rob Clark
Cc: Sean Paul
Cc: linux-arm-...@vger.kernel.org
Cc: freedr...@lists.freedesktop.org
Reviewed-by: Brian Masney
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Rebased on v5.3-rc1
-
This file is not using any symbols from so just
drop this include.
Cc: Rob Clark
Cc: Sean Paul
Cc: linux-arm-...@vger.kernel.org
Cc: freedr...@lists.freedesktop.org
Reviewed-by: Brian Masney
Signed-off-by: Linus Walleij
---
ChangeLog v1->v2:
- Rebased on v5.3-rc1
- Collected review tag
---
After untangling the MSM HDMI GPIO code we see that the code
is deliberately setting the output value of the HPD (hot plug
detect) line to high, even though it is being used as input
which is of course the only viable use of a HPD pin.
This seems dubious: GPIO lines set up as input will have high
https://bugs.freedesktop.org/show_bug.cgi?id=110795
--- Comment #32 from Tomas ---
Hi,
I have applied the patch to drivers amdgpu-pro-19.30-855429-ubuntu-18.04, and
something is wrong. The process doesn't find as seems some components?
See output i got on the cli. Have I overlooked something?
https://bugs.freedesktop.org/show_bug.cgi?id=110795
--- Comment #33 from Tomas ---
System is Ubuntu 19.04, 5.0.0-25-generic #26-Ubuntu SMP Thu Aug 1 12:04:58 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
--
You are receiving this mail because:
You are the assignee for the
On 21/08/2019 23:26, Aaro Koskinen wrote:
Hi,
On Wed, Aug 21, 2019 at 09:32:26PM +0300, Laurent Pinchart wrote:
When refactoring port lookup for DSS outputs, commit d17eb4537a7e
("drm/omap: Factor out common init/cleanup code for output devices")
incorrectly hardcoded usage of DT port 0. This
Hi Dave and Daniel,
(atempt v2:
for some reason my dim didn't recognized the path apparently
)
Here goes the final pull request targeting 5.4.
It's important to highlight that we got a conflict on a backmerge yesterday
which had already been solved on linux-next with a fix up patch:
From:
On Thu, 22 Aug 2019, Ramalingam C wrote:
> Handled the need for exposing enum port to mei_hdcp driver, by
> converting the port into ddi index as per ME FW.
>
> Hence enum port definition moved into I915 driver itself.
For future reference, please consider using the imperative style in the
Hi Dave and Daniel,
Here goes the final pull request targeting 5.4.
It's important to highlight that we got a conflict on a backmerge yesterday
which had already been solved on linux-next with a fix up patch:
From: Stephen Rothwell
Date: Wed, 14 Aug 2019 12:48:39 +1000
Subject: [PATCH] drm:
From: Thomas Hellstrom
The new header is intended to be used by drivers using the backdoor.
Follow the kvm example using alternatives self-patching to
choose between vmcall, vmmcall and io instructions.
Also define two new CPU feature flags to indicate hypervisor support
for vmcall- and vmmcall
From: Thomas Hellstrom
Use the definition provided by include/asm/vmware.h
CC: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc:
Cc:
Signed-off-by: Thomas Hellstrom
Reviewed-by: Doug Covelli
Acked-by: Dmitry Torokhov
---
drivers/input/mouse/vmmouse.c | 6
From: Thomas Hellstrom
Use the definition provided by include/asm/vmware.h
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc:
Cc:
Signed-off-by: Thomas Hellstrom
Reviewed-by: Doug Covelli
---
drivers/gpu/drm/vmwgfx/vmwgfx_msg.c | 21 +
On Thu, Aug 22, 2019 at 03:13:14PM +0200, Daniel Vetter wrote:
> On Thu, Aug 22, 2019 at 11:06:45AM +0200, Gerd Hoffmann wrote:
> > No need for a home-grown version, the generic helper should work just
> > fine. It also handles vgacon removal these days, see commit
> > 1c74ca7a1a9a
https://bugs.freedesktop.org/show_bug.cgi?id=110795
--- Comment #34 from Andrew Shark ---
@Tomas, it is strange that it did not asked a password after "Creating local
repository..." which is before "Installing OpenGL PRO...". Probably you already
had a previous version of repository (it happens
On Fri, Aug 23, 2019 at 10:14 AM Gerd Hoffmann wrote:
> On Thu, Aug 22, 2019 at 03:13:14PM +0200, Daniel Vetter wrote:
> > On Thu, Aug 22, 2019 at 11:06:45AM +0200, Gerd Hoffmann wrote:
> > > No need for a home-grown version, the generic helper should work just
> > > fine. It also handles vgacon
On Fri, Aug 23, 2019 at 1:14 AM Andrew Morton wrote:
>
> On Tue, 20 Aug 2019 22:24:40 +0200 Daniel Vetter wrote:
>
> > Hi Peter,
> >
> > Iirc you've been involved at least somewhat in discussing this. -mm folks
> > are a bit undecided whether these new non_block semantics are a good idea.
> >
Hi Daniel, Dave,
Here is what should be the final drm-misc-next PR for 5.4.
Thanks!
Maxime
drm-misc-next-2019-08-23:
drm-misc-next for 5.4:
UAPI Changes:
Cross-subsystem Changes:
Core Changes:
- dma-buf: dma-fence selftests
Driver Changes:
- kirin: Various cleanups and reworks
-
On Tue, Aug 20, 2019 at 10:24:40PM +0200, Daniel Vetter wrote:
> On Tue, Aug 20, 2019 at 10:19:01AM +0200, Daniel Vetter wrote:
> > In some special cases we must not block, but there's not a
> > spinlock, preempt-off, irqs-off or similar critical section already
> > that arms the might_sleep()
On Fri, Aug 23, 2019 at 10:30:35AM +0200, Daniel Vetter wrote:
> On Fri, Aug 23, 2019 at 10:14 AM Gerd Hoffmann wrote:
> >
> > Whole series or just the i915 patch?
>
> Ok I just checked and this all landed in 5.1 already, I thought it was
> more recent. I think that's good enough, push it all
https://bugs.freedesktop.org/show_bug.cgi?id=110795
--- Comment #35 from Etienne Lorrain ---
(In reply to Andrew Shark from comment #31)
> (In reply to Etienne Lorrain from comment #30)
> I do not understand what problem you are talking about. Package just refuses
> to install because of
On 23/08/2019 03:33, Rob Herring wrote:
> Add Steven Price and Alyssa Rosenzweig as reviewers as they have been the
> primary reviewers already.
>
> Cc: Steven Price
> Cc: Alyssa Rosenzweig
> Cc: Tomeu Vizoso
> Signed-off-by: Rob Herring
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2
On 23/08/2019 02:52, Rob Herring wrote:
> On Thu, Aug 22, 2019 at 4:32 AM Steven Price wrote:
>>
>> When modifying panfrost_devfreq_target() to support a device without a
>> regulator defined I missed the check on the error path. Let's add it.
>>
>> Reported-by: Dan Carpenter
>> Fixes:
On 23/08/2019 02:33, Rob Herring wrote:
> Add Steven Price and Alyssa Rosenzweig as reviewers as they have been the
> primary reviewers already.
>
> Cc: Steven Price
> Cc: Alyssa Rosenzweig
> Cc: Tomeu Vizoso
> Signed-off-by: Rob Herring
Acked-by: Steven Price
Steve
> ---
> MAINTAINERS |
Hi all,
Commit
88b703527ba7 ("drm/nouveau/kms/gf119-: add ctm property support")
is missing a Signed-off-by from its committer.
--
Cheers,
Stephen Rothwell
pgpFK0PXpb9VH.pgp
Description: OpenPGP digital signature
___
dri-devel mailing list
1 - 100 of 175 matches
Mail list logo
