Linux 6.3-rc1

Linux 6.2

Linux 6.2-rc4

Linux 6.0

Add support for Xen dedicated CMA and page allocators

Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>

dmaengine: rcar-dmac: Set DMA mask to 32 bits

Due to the R-Car Gen3 HW restriction.

Please note, that this patch will decrease performance, since swiotlb bounce
buffer (for DMA transfers involving memory outside the 32-bit address space)
will be used.

Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Reviewed-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>

dmaengine: rcar-dmac: Set DMA mask to 32 bits

Due to the R-Car Gen3 HW restriction.

Please note, that this patch will decrease performance, since swiotlb bounce
buffer (for DMA transfers involving memory outside the 32-bit address space)
will be used.

Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Reviewed-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>

drm: Fix possible race conditions while unplugging DRM device

[ Upstream commit 069035c ]

When unplugging a hotpluggable DRM device we first unregister it
with drm_dev_unregister and then set drm_device.unplugged flag which
is used to mark device critical sections with drm_dev_enter()/
drm_dev_exit() preventing access to device resources that are not
available after the device is gone.
But drm_dev_unregister may lead to hotplug uevent(s) fired to
user-space on card and/or connector removal, thus making it possible
for user-space to try accessing a disconnected device.

Fix this by first making sure device is properly marked as
disconnected and only then unregister it.

Fixes: bee330f ("drm: Use srcu to protect drm_device.unplugged")

Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Reported-by: Andrii Chepurnyi <andrii_chepurnyi@epam.com>
Cc: "Noralf Trønnes" <noralf@tronnes.org>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20180522141304.18646-1-andr2000@gmail.com

soc: renesas: rcar-sysc: power domains are always on for r8a7796

R-Car Gen3 SoC has some power domains, which are transitioned by
multiple triggers. According to Hardware Manual, it is necessary
to control that the state transitions do not conflict for each
power domains.

The patterns of conflict are below.

 1. CA5x  vs CA5x : Exclusion control with HW (M3 ES1.1)
 2. CA5x  vs 3DG  : Exclusion control with HW (M3 ES1.1)
 3. CA5x  vs Other: Exclusion control with SW (Not implemented yet)
 4. 3DG   vs Other: Exclusion control with SW (already implemented)
 5. Other vs Other: Exclusion control with SW (already implemented)

This patch fixes pattern 3 by turning on the other power domains
at always. Please note this changes causes an increase of power
consumption.

Signed-off-by: Gaku Inami <gaku.inami.xw@bp.renesas.com>
Reviewed-by: Andrii Anisov andrii_anisov@epam.com

R-Car Linux BSP v3.3.2 Release for H3/M3 (Aug. 08, 2016)