Make the device-dax 'size' attribute writable to allow capacity to be
split between multiple instances in a region. The intended consumers of
this capability are users that want to split a scarce memory resource
between device-dax and System-RAM access, or users that want to have
multiple security
Break the requirement that device-dax instances are physically
contiguous. With this constraint removed it allows fragmented available
capacity to be fully allocated.
This capability is useful to mitigate the "noisy neighbor" problem with
memory-side-cache management for virtual machines, or any o
In support of device-dax growing the ability to front physically
dis-contiguous ranges of memory, update devm_memremap_pages() to track
multiple ranges with a single reference counter and devm instance.
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Benjamin Herrenschmidt
Cc: Dan Williams
Cc: Vis
From: Joao Martins
Introduce a new module parameter for dax_hmem which
initializes all region devices as free, rather than allocating
a pagemap for the region by default.
All hmem devices created with dax_hmem.region_idle=1 will have full
available size for creating dynamic dax devices.
Signed-
From: Joao Martins
Introduce @align to struct dev_dax.
When creating a new device, we still initialize to the default
dax_region @align. Child devices belonging to a region may wish
to keep a different alignment property instead of a global
region-defined one.
Signed-off-by: Joao Martins
Link:
In support of interrogating the physical address layout of a device with
dis-contiguous ranges, introduce a sysfs directory with 'start', 'end',
and 'page_offset' attributes. The alternative is trying to parse
/proc/iomem, and that file will not reflect the extent layout until the
device is enabled
From: Joao Martins
Introduce a device align attribute. While doing so,
rename the region align attribute to be more explicitly
named as so, but keep it named as @align to retain the API
for tools like daxctl.
Changes on align may not always be valid, when say certain
mappings were created with 2
From: Joao Martins
Add a sysfs attribute which denotes a range from the dax region
to be allocated. It's an write only @mapping sysfs attribute in
the format of '-' to allocate a range. @start and
@end use hexadecimal values and the @pgoff is implicitly ordered
wrt to previous writes to @mapping
The passed in dev_pagemap is only required in the pmem case as the
libnvdimm core may have reserved a vmem_altmap for dev_memremap_pages()
to place the memmap in pmem directly. In the hmem case there is no
agent reserving an altmap so it can all be handled by a core internal
default.
Pass the reso
The 'struct resource' in 'struct dev_pagemap' is only used for holding
resource span information. The other fields, 'name', 'flags', 'desc',
'parent', 'sibling', and 'child' are all unused wasted space.
This is in preparation for introducing a multi-range extension of
devm_memremap_pages().
The b
Use sysfs_streq() in device_find_child_by_name() to allow it to use a
sysfs input string that might contain a trailing newline.
The other "device by name" interfaces,
{bus,driver,class}_find_device_by_name(), already account for sysfs
strings.
Cc: "Rafael J. Wysocki"
Reviewed-by: Greg Kroah-Hart
Several related issues around this unneeded attribute:
- The dax_kmem_res property allows the kmem driver to stash the adjusted
resource range that was used for the hotplug operation, but that can be
recalculated from the original base range.
- kmem is using an open coded release_resource() +
In preparation for a facility that enables dax regions to be
sub-divided, introduce infrastructure to track and allocate region
capacity.
The new dax_region/available_size attribute is only enabled for volatile
hmem devices, not pmem devices that are defined by nvdimm namespace
boundaries. This is
All callers specify the same flags to alloc_dax_region(), so there is no
need to allow for anything other than PFN_DEV|PFN_MAP, or carry a
->pfn_flags around on the region. Device-dax instances are always page
backed.
Cc: Vishal Verma
Signed-off-by: Dan Williams
---
drivers/dax/bus.c |
Add a seed device concept for dynamic dax regions to be able to split
the region amongst multiple sub-instances. The seed device, similar to
libnvdimm seed devices, is a device that starts with zero capacity
allocated and unbound to a driver. In contrast to libnvdimm seed devices
explicit 'create'
The hmem enabling in commit 'cf8741ac57ed ("ACPI: NUMA: HMAT: Register
"soft reserved" memory as an "hmem" device")' only registered ranges to
the hmem driver for each soft-reservation that also appeared in the
HMAT. While this is meant to encourage platform firmware to "do the
right thing" and pub
Changes since v2 [1]:
- Rebase on next/master to resolve conflicts with pending mem-hotplug
and memremap_pages() changes in -mm
- Drop attempt at a generic phys_to_target_node() implementation and
just follow the default fallback approach taken with
memory_add_physaddr_to_nid() (Mike)
- Fix
In preparation to set a fallback value for dev_dax->target_node,
introduce generic fallback helpers for phys_to_target_node()
A generic implementation based on node-data or memblock was proposed,
but as noted by Mike:
"Here again, I would prefer to add a weak default for
phys_to_target_n
In support of detecting whether a resource might have been been claimed,
report the parent to the walk_iomem_res_desc() callback. For example,
the ACPI HMAT parser publishes "hmem" platform devices per target range.
However, if the HMAT is disabled / missing a fallback driver can attach
devices to
In preparation for exposing "Soft Reserved" memory ranges without an
HMAT, move the hmem device registration to its own compilation unit and
make the implementation generic.
The generic implementation drops usage acpi_map_pxm_to_online_node()
that was translating ACPI proximity domain values and i
In preparation for adding more parameters to instance creation, move
existing parameters to a new struct.
Cc: Vishal Verma
Signed-off-by: Dan Williams
---
drivers/dax/bus.c | 14 +++---
drivers/dax/bus.h | 16
drivers/dax/hmem/hmem.c |8 +++-
dri
In preparation for adding a new numa= option clean up the existing ones
to avoid ifdefs in numa_setup(), and provide feedback when the option is
numa=fake= option is invalid due to kernel config. The same does not
need to be done for numa=noacpi, since the capability is already hard
disabled at com
In preparation for attaching a platform device per iomem resource teach
the efi_fake_mem code to create an e820 entry per instance. Similar to
E820_TYPE_PRAM, bypass merging resource when the e820 map is sanitized.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc
Disable parsing of the HMAT for debug, to workaround broken platform
instances, or cases where it is otherwise not wanted.
Cc: x...@kernel.org
Cc: "Rafael J. Wysocki"
Cc: Dave Hansen
Cc: Andy Lutomirski
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter
> -Original Message-
> From: dri-devel On Behalf Of Hyun
> Kwon
> Sent: Thursday, July 30, 2020 7:33 PM
> To: Laurent Pinchart
> Cc: Dan Carpenter ; dri-
> de...@lists.freedesktop.org; Daniel Vetter
> Subject: Re: [PATCH v2 1/1] drm: xlnx: zynqmp: Use switch - case for link rate
> down
On Thu, Jul 30, 2020 at 09:37:48PM +0200, Marek Vasut wrote:
> On 7/30/20 9:13 PM, Mark Brown wrote:
> > On Thu, Jul 30, 2020 at 06:28:07PM +0200, Marek Vasut wrote:
> >> about it ? I can over-complicate this and split it into multiple
> >> drivers, but I don't think it's worth the complexity, con
https://bugzilla.kernel.org/show_bug.cgi?id=207901
--- Comment #28 from Lyude Paul (ly...@redhat.com) ---
(In reply to Ilia Mirkin from comment #27)
> DP -> HDMI is, most likely, just passive, so the displays are being driven
> as HDMI rather than as DP. DP is the problematic protocol...
Hi-so, m
On Tue, 28 Jul 2020 22:12:41 +0200, Marek Vasut wrote:
> Add DT bindings for Chefree CH101OLHLWH-002 10.1" 1280x800 LCD.
> This panel is connected via LVDS.
>
> Signed-off-by: Marek Vasut
> To: dri-devel@lists.freedesktop.org
> Cc: Rob Herring
> Cc: Sam Ravnborg
> Cc: devicet...@vger.kernel.org
On Tue, 28 Jul 2020 22:12:40 +0200, Marek Vasut wrote:
> The Chefree Technology Corp. is an LCD panel manufacturer.
>
> Signed-off-by: Marek Vasut
> To: dri-devel@lists.freedesktop.org
> Cc: Rob Herring
> Cc: Sam Ravnborg
> Cc: devicet...@vger.kernel.org
> ---
> Documentation/devicetree/bindin
On Fri, 31 Jul 2020 at 23:23, Christian König wrote:
>
> Am 31.07.20 um 06:04 schrieb Dave Airlie:
> > From: Dave Airlie
> >
> > This will allow different abstractions later.
>
> Mhm, I'm questioning if this is really worth it and not just overkill.
>
> Running "sed -i 's/&bdev->man/bdev->man/'"
Hi Vinod,
On Fri, Jul 31, 2020 at 10:17:44PM +0530, Vinod Koul wrote:
> On 31-07-20, 18:24, Laurent Pinchart wrote:
> > Hello,
> >
> > This small series fixes a Kconfig dependency issue with the recently
> > merged Xilixn DPSUB DRM/KMS driver. The fix is in patch 3/3, but
> > requires a separate
On Sun, 26 Jul 2020 13:12:00 +0200, Konrad Dybcio wrote:
> Signed-off-by: Konrad Dybcio
> ---
> Documentation/devicetree/bindings/usb/qcom,dwc3.yaml | 1 +
> drivers/usb/dwc3/dwc3-qcom.c | 1 +
> 2 files changed, 2 insertions(+)
>
Acked-by: Rob Herring
_
On Sun, 26 Jul 2020 13:11:59 +0200, Konrad Dybcio wrote:
> QUSB on these SoCs actually uses *almost* the same
> configuration that msm8996 does, so we can reuse
> the phy_cfg from there with just a single change
> (se clock scheme).
>
> Signed-off-by: Konrad Dybcio
> ---
> Documentation/devicetr
On Fri, Jul 31, 2020 at 2:32 AM Kunihiko Hayashi
wrote:
> On 2020/07/29 4:17, John Stultz wrote:
> > Do you have a upstream driver that you plan to make use this new call?
>
> Unfortunately I don't have an upstream driver using this call.
>
> This call is called from dma-buf heaps "importer" or "c
On Fri, 31 Jul 2020 11:18:33 +0300, Laurentiu Palcu wrote:
> From: Laurentiu Palcu
>
> Add bindings for iMX8MQ Display Controller Subsystem.
>
> Signed-off-by: Laurentiu Palcu
> ---
> Changes in v9:
> * Include imx8mq-clock.h in the example so we can use clock names
>instead of their value
On Fri, 31 Jul 2020 18:24:30 +0300, Laurent Pinchart wrote:
> This small series fixes a Kconfig dependency issue with the recently
> merged Xilixn DPSUB DRM/KMS driver. The fix is in patch 3/3, but
> requires a separate fixes in patches 1/3 and 2/3 to avoid circular
> dependencies:
>
> dri
On Wed, 29 Jul 2020 19:29:07 +0300, Laurent Pinchart wrote:
> This small series fixes a Kconfig dependency issue with the recently
> merged Xilixn DPSUB DRM/KMS driver. The fix is in patch 3/3, but
> requires a separate fixes in patches 1/3 and 2/3 to avoid circular
> dependencies:
>
> drive
Hello everybody!
I'm currently working on a writeback connector screenshooter for Weston.
In order to test it, I'm using VKMS with Rodrigo's writeback connector
patch: https://lkml.org/lkml/2020/5/11/449
Here is the link with the MR in Weston with more details of how I've
tested it:
https:/
On Fri, Jul 31, 2020 at 6:47 PM Melissa Wen wrote:
>
> On 07/31, Sidong Yang wrote:
> > On Fri, Jul 31, 2020 at 11:08:34AM +0200, dan...@ffwll.ch wrote:
> > > On Thu, Jul 30, 2020 at 07:09:25AM -0300, Melissa Wen wrote:
> > > > On 07/29, Daniel Vetter wrote:
> > > > > On Wed, Jul 29, 2020 at 9:09
add vblank timestamp support via drm helpers
Signed-off-by: Robert Beckett
---
drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c| 71 -
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 7 ++
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.h | 5 ++
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
On 31-07-20, 18:24, Laurent Pinchart wrote:
> Hello,
>
> This small series fixes a Kconfig dependency issue with the recently
> merged Xilixn DPSUB DRM/KMS driver. The fix is in patch 3/3, but
> requires a separate fixes in patches 1/3 and 2/3 to avoid circular
> dependencies:
>
> drivers
On 07/31, Sidong Yang wrote:
> On Fri, Jul 31, 2020 at 11:08:34AM +0200, dan...@ffwll.ch wrote:
> > On Thu, Jul 30, 2020 at 07:09:25AM -0300, Melissa Wen wrote:
> > > On 07/29, Daniel Vetter wrote:
> > > > On Wed, Jul 29, 2020 at 9:09 PM Melissa Wen
> > > > wrote:
> > > > >
> > > > > Melissa Wen
https://bugzilla.kernel.org/show_bug.cgi?id=207383
--- Comment #112 from Duncan (1i5t5.dun...@cox.net) ---
(In reply to Paul Menzel from comment #107)
> Everyone seeing this, it’d be great, if you tested
>
> [PATCH] drm/amd/display: Clear dm_state for fast updates
For the record, with no rep
On Fri, Jul 31, 2020 at 11:08:34AM +0200, dan...@ffwll.ch wrote:
> On Thu, Jul 30, 2020 at 07:09:25AM -0300, Melissa Wen wrote:
> > On 07/29, Daniel Vetter wrote:
> > > On Wed, Jul 29, 2020 at 9:09 PM Melissa Wen wrote:
> > > >
> > > > Melissa Wen
> > > >
> > > > On Sat, Jul 25, 2020 at 3:12 PM Da
Enabling a whole subsystem from a single driver 'select' is frowned
upon and won't be accepted in new drivers, that need to use 'depends on'
instead. Existing selection of DMADEVICES will then cause circular
dependencies. Replace them with a dependency.
Signed-off-by: Laurent Pinchart
Acked-by: R
Hello,
This small series fixes a Kconfig dependency issue with the recently
merged Xilixn DPSUB DRM/KMS driver. The fix is in patch 3/3, but
requires a separate fixes in patches 1/3 and 2/3 to avoid circular
dependencies:
drivers/i2c/Kconfig:8:error: recursive dependency detected!
Enabling a whole subsystem from a single driver 'select' is frowned
upon and won't be accepted in new drivers, that need to use 'depends on'
instead. Existing selection of DMADEVICES will then cause circular
dependencies. Replace them with a dependency.
Signed-off-by: Laurent Pinchart
Acked-by: R
The dpsub driver uses the DMA engine API, and thus selects DMA_ENGINE to
provide that API. DMA_ENGINE depends on DMADEVICES, which can be
deselected by the user, creating a possibly unmet indirect dependency:
WARNING: unmet direct dependencies detected for DMA_ENGINE
Depends on [n]: DMADEVICES [
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
This is probably something we could consider removing, vmwgfx
is the only user, and we might be able to faciliate it another way
but for now just consolidate it all into accessors.
I always found the "use_type" wording confusing and
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
The driver now controls these, the core just controls the system
memory one.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/ttm/ttm_bo.c| 2 --
include/drm/ttm/ttm_bo_driver.h | 6 --
2 files changed, 4 insertions(+), 4 d
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
Just store the device in the private so the link
can be removed from the manager
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | 7 +--
1 file changed, 5 insertio
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
This link isn't needed anymore, drop it from the init interface.
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c
On Thu, Jul 30, 2020 at 10:44 AM Jim Quinlan wrote:
>
> On Wed, Jul 29, 2020 at 10:28 AM Rob Herring wrote:
> >
> > On Wed, Jul 29, 2020 at 12:19 AM Christoph Hellwig wrote:
> > >
> > > On Tue, Jul 28, 2020 at 02:24:51PM -0400, Jim Quinlan wrote:
> > > > I started using devm_kcalloc() but at lea
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
This isn't needed anymore by any drivers.
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
include/drm/ttm/ttm_bo_driver.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/drm/ttm/ttm_bo_driver.h b/incl
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo_manager.c | 32 +---
1 file changed, 20 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo_man
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
This makes it easier to move these to a driver allocated system
No, sorry that looks like going into the wrong direction to me.
I already wanted to suggest to get rid of the size argument instead.
Christian.
Signed-off-by: Dave
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c | 35 +++
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | 36 +---
2 files changed, 44 in
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Acked-by: Christian König
---
drivers/gpu/drm/vmwgfx/vmwgfx_gmrid_manager.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_gmrid_manager.c
b/drivers/gpu/drm/
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Acked-by: Christian König
---
drivers/gpu/drm/nouveau/nouveau_ttm.c | 9 -
1 file changed, 9 deletions(-)
diff --git a/drivers/gpu/drm/nouveau/nouveau_ttm.c
b/drivers/gpu/drm/nouveau/nouvea
Am 31.07.20 um 06:05 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
index 92d
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
This will allow different abstractions later.
Mhm, I'm questioning if this is really worth it and not just overkill.
Running "sed -i 's/&bdev->man/bdev->man/'" on all drivers when we make
the switch to a pointer should do it as wel
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
drivers should all be cleaning up their memory managers
themselves now, so let the core just clean the system one up.
Remove the legacy cleaning interface.
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/g
On Fri, Jul 31, 2020 at 05:21:38PM +1000, Dave Airlie wrote:
> On Fri, 31 Jul 2020 at 17:14, Thomas Zimmermann wrote:
> >
> > Hi
> >
> > Am 31.07.20 um 06:04 schrieb Dave Airlie:
> > > From: Dave Airlie
> > >
> > > This will allow different abstractions later.
> >
> > You should consider moving t
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
Now no drivers have been converted, drop the non-driver path.
I'm not a native speak, but that sounds odd.
Apart from that patch is Reviewed-by: Christian König
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/ttm/ttm_bo_mana
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
Allow the takedown path callback to be optional as well.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/ttm/ttm_bo.c | 8 +---
drivers/gpu/drm/ttm/ttm_bo_manager.c | 21 +++--
include/drm/ttm/ttm_bo_d
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/radeon/radeon_ttm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c
b/drivers/gpu/drm/rad
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_gtt_mgr.c | 15 +++
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 10 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_tt
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/ttm/ttm_bo.c| 6 ++
include/drm/ttm/ttm_bo_driver.h | 12
2 files changed, 14 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
This makes it easier to cleanup things
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/dr
Am 31.07.20 um 11:46 schrieb dan...@ffwll.ch:
On Fri, Jul 31, 2020 at 02:05:05PM +1000, Dave Airlie wrote:
From: Dave Airlie
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/ttm/ttm_bo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/driver
Am 31.07.20 um 11:29 schrieb dan...@ffwll.ch:
On Fri, Jul 31, 2020 at 11:17:26AM +0200, Christian König wrote:
Am 31.07.20 um 06:04 schrieb Dave Airlie:
I started pulling on a thread, and it led me down a hole.
We might want to make that hole even bigger :)
How about we rename the ttm_mem_reg
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
This lets the generic mm manager be initialised by the driver.
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo_manager.c | 23 ---
include/drm/ttm/ttm_bo_driver.h
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 19 ---
drivers/gpu/drm/ttm/ttm_bo_manager.c | 27 +--
include/drm/ttm/ttm_bo_api.h
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
Remove the exit path, since this can't fail now.
Signed-off-by: Dave Airlie
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 30 +-
1 file changed, 17 insertions(+), 13 deletions(-)
From: Oleksandr Andrushchenko
Hello,
This series contains an assorted set of fixes and improvements for
the Xen para-virtualized display driver and grant device driver which
I have collected over the last couple of months:
1. Minor fixes to grant device driver and drm/xen-front.
2. New format
From: Oleksandr Andrushchenko
Version 2 of the Xen displif protocol adds XENDISPL_OP_GET_EDID
request which allows frontends to request EDID structure per
connector. This request is optional and if not supported by the
backend then visible area is still defined by the relevant
XenStore's "resolut
From: Oleksandr Andrushchenko
The patch c575b7eeb89f: "drm/xen-front: Add support for Xen PV
display frontend" from Apr 3, 2018, leads to the following static
checker warning:
drivers/gpu/drm/xen/xen_drm_front_gem.c:140 xen_drm_front_gem_create()
warn: passing zero to 'ERR_CAST'
From: Oleksandr Andrushchenko
Add YUYV to supported formats, so the frontend can work with the
formats used by cameras and other HW.
Signed-off-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/xen/xen_drm_front_conn.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/xen/xen_d
From: Oleksandr Andrushchenko
This is the sync up with the canonical definition of the
display protocol in Xen.
1. Add protocol version as an integer
Version string, which is in fact an integer, is hard to handle in the
code that supports different protocol versions. To simplify that
also add t
From: Oleksandr Andrushchenko
While importing a dmabuf it is possible that the data of the buffer
is put with offset which is indicated by the SGT offset.
Respect the offset value and forward it to the backend.
Signed-off-by: Oleksandr Andrushchenko
---
drivers/gpu/drm/xen/xen_drm_front.c
From: Oleksandr Andrushchenko
It is possible that the scatter-gather table during dmabuf import has
non-zero offset of the data, but user-space doesn't expect that.
Fix this by failing the import, so user-space doesn't access wrong data.
Fixes: 37ccb44d0b00 ("xen/gntdev: Implement dma-buf import
On Thu, Jul 30, 2020 at 1:05 PM Nicolas Saenz Julienne
wrote:
>
> Hi Jim,
>
> On Fri, 2020-07-24 at 16:33 -0400, Jim Quinlan wrote:
> > static void __init of_unittest_pci_dma_ranges(void)
> > diff --git a/drivers/pci/controller/pcie-brcmstb.c
> > b/drivers/pci/controller/pcie-brcmstb.c
> > index
On Wed, Jul 29, 2020 at 10:28 AM Rob Herring wrote:
>
> On Wed, Jul 29, 2020 at 12:19 AM Christoph Hellwig wrote:
> >
> > On Tue, Jul 28, 2020 at 02:24:51PM -0400, Jim Quinlan wrote:
> > > I started using devm_kcalloc() but at least two reviewers convinced me
> > > to just use kcalloc(). In addi
On Fri, Jul 31, 2020 at 02:05:18PM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> The driver now controls these, the core just controls the system
> memory one.
>
> Signed-off-by: Dave Airlie
> ---
> drivers/gpu/drm/ttm/ttm_bo.c| 2 --
> include/drm/ttm/ttm_bo_driver.h | 6 --
> 2 f
On Fri, Jul 31, 2020 at 02:05:20PM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> This is probably something we could consider removing, vmwgfx
> is the only user, and we might be able to faciliate it another way
>
> but for now just consolidate it all into accessors.
>
> Signed-off-by: Dave
On Fri, Jul 31, 2020 at 02:05:05PM +1000, Dave Airlie wrote:
> From: Dave Airlie
>
> Signed-off-by: Dave Airlie
> ---
> drivers/gpu/drm/ttm/ttm_bo.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
> index 92de
On Fri, Jul 31, 2020 at 11:17:26AM +0200, Christian König wrote:
> Am 31.07.20 um 06:04 schrieb Dave Airlie:
> > I started pulling on a thread, and it led me down a hole.
>
> We might want to make that hole even bigger :)
>
> How about we rename the ttm_mem_reg into ttm_resource and
> ttm_mem_typ
On Thu, Jul 30, 2020 at 05:25:24PM -0300, Melissa Wen wrote:
> The previous memset operation was not correctly zeroing the alpha
> channel to compute the crc, and as a result, the IGT subtest
> kms_cursor_crc/pipe-A-cursor-alpha-transparent fails.
>
> Fixes: db7f419c06d7c ("drm/vkms: Compute CRC w
On Wed, Jul 29, 2020 at 05:54:16PM +0300, Marius Iacob wrote:
> From 06ba7d3e64e55262bf818084904eec7b7320a2ad Mon Sep 17 00:00:00 2001
> From: Marius Iacob
> Date: Wed, 29 Jul 2020 16:51:41 +0300
> Subject: [PATCH] Added orientation quirk for ASUS tablet model T103HAF
Please format the patch per
On Thu, Jul 30, 2020 at 10:14:43AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 29.07.20 um 15:57 schrieb dan...@ffwll.ch:
> > On Wed, Jul 29, 2020 at 03:41:46PM +0200, Thomas Zimmermann wrote:
> >> Most platforms allow for accessing framebuffer I/O memory with regular
> >> load and store operation
On Wed, Jul 29, 2020 at 06:36:03PM +0200, Sam Ravnborg wrote:
> Hi Daniel.
>
> On Wed, Jul 29, 2020 at 03:53:28PM +0200, dan...@ffwll.ch wrote:
> > On Wed, Jul 29, 2020 at 03:41:45PM +0200, Thomas Zimmermann wrote:
> > > DRM fb helpers require read and write functions for framebuffer
> > > memory.
On Wed, Jul 29, 2020 at 01:35:52AM -0400, Steve Cohen wrote:
> Add back the removed documentation for drm_gem_open_ioctl.
> This patch is submitted in response to [1].
>
> [1]
> https://lore.kernel.org/linux-arm-msm/20200728085244.GY6419@phenom.ffwll.local/
>
> Signed-off-by: Steve Cohen
> ---
Am 31.07.20 um 06:04 schrieb Dave Airlie:
I started pulling on a thread, and it led me down a hole.
We might want to make that hole even bigger :)
How about we rename the ttm_mem_reg into ttm_resource and
ttm_mem_type_manager into ttm_resource_manager.
Neither amdgpu's OA/GWS resources nor
On Wed, Jul 29, 2020 at 02:23:15AM +, Xu Qiang wrote:
> A soft deadlock occurs when call hrtimer_cancel in softirq context:
>
> a) The main frequency of the machine is very slow
> b) output->period_ns is very small, even only 1 ns
>
> The problem can be solved in the following way
Am 31.07.20 um 06:04 schrieb Dave Airlie:
From: Dave Airlie
This will allow the driver to control the ordering here better.
Eventually the old path will be removed.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/ttm/ttm_bo.c| 34 +++--
include/drm/ttm/ttm_b
On Wed, Jul 29, 2020 at 02:28:01AM +0200, Paul Cercueil wrote:
>
>
> Le mer. 29 juil. 2020 à 0:00, dan...@ffwll.ch a écrit :
> > On Tue, Jul 28, 2020 at 10:17:36PM +0200, Sam Ravnborg wrote:
> > > Hi Paul.
> > >
> > > On Tue, Jul 28, 2020 at 05:16:39PM +0200, Paul Cercueil wrote:
> > > > Here
On Thu, Jul 30, 2020 at 07:09:25AM -0300, Melissa Wen wrote:
> On 07/29, Daniel Vetter wrote:
> > On Wed, Jul 29, 2020 at 9:09 PM Melissa Wen wrote:
> > >
> > > Melissa Wen
> > >
> > > On Sat, Jul 25, 2020 at 3:12 PM Daniel Vetter wrote:
> > > >
> > > > On Sat, Jul 25, 2020 at 7:45 PM Melissa Wen
Hi,
On Fri, Jul 31, 2020 at 11:18:30AM +0300, Laurentiu Palcu wrote:
> From: Laurentiu Palcu
>
> This adds initial support for iMX8MQ's Display Controller Subsystem (DCSS).
> Some of its capabilities include:
> * 4K@60fps;
> * HDR10;
> * one graphics and 2 video pipelines;
> * on-the-fly deco
Hi,
On Fri, Jul 31, 2020 at 11:18:28AM +0300, Laurentiu Palcu wrote:
> From: Laurentiu Palcu
>
> Hi,
>
> This patchset adds initial DCSS support for iMX8MQ chip. Initial support
> includes only graphics plane support (no video planes), no HDR10 capabilities,
> no graphics decompression (only lin
Hi,
On Fri, Jul 31, 2020 at 11:18:33AM +0300, Laurentiu Palcu wrote:
> From: Laurentiu Palcu
>
> Add bindings for iMX8MQ Display Controller Subsystem.
>
> Signed-off-by: Laurentiu Palcu
> ---
> Changes in v9:
> * Include imx8mq-clock.h in the example so we can use clock names
>instead of t
1 - 100 of 149 matches
Mail list logo
