Changes in exynos_drm.h

c0bf499f - drm/exynos: Rename Exynos to lowercase

Sat, 04 Jan 2020 15:21:01 +0000

drm/exynos: Rename Exynos to lowercaseFix up inconsistent usage of upper and lowercase letters in "Exynos"name."EXYNOS" is not an abbreviation but a regular trademarked name.Therefore it should be written with lowercase letters starting withcapital letter.The lowercase "Exynos" name is promoted by its manufacturer SamsungElectronics Co., Ltd., in advertisement materials and on website.Signed-off-by: Krzysztof Kozlowski Signed-off-by: Inki Dae List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

3f4bb9f7 - drm: Spelling s/connet/connect/

Thu, 24 Oct 2019 15:17:37 +0000

drm: Spelling s/connet/connect/Fix misspellings of "connector" and "connection"Signed-off-by: Geert Uytterhoeven Signed-off-by: Daniel Vetter Link: https://patchwork.freedesktop.org/patch/msgid/20191024151737.29287-1-geert+renesas@glider.be List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

9913f74f - drm/exynos: ipp: Add IPP v2 framework

Wed, 09 May 2018 23:46:36 +0000

drm/exynos: ipp: Add IPP v2 frameworkThis patch adds Exynos IPP v2 subsystem and userspace API.New userspace API is focused ONLY on memory-to-memory image processing.The two remainging operation modes of obsolete IPP v1 API (framebufferwriteback and local-path output with image processing) can be implementedusing standard DRM features: writeback connectors and additional DRM planeswith scaling features.V2 IPP userspace API is based on stateless approach, which much better fitsto memory-to-memory image processing model. It also provides support forall image formats, which are both already defined in DRM API and supportedby the existing IPP hardware modules.The API consists of the following ioctls:- DRM_IOCTL_EXYNOS_IPP_GET_RESOURCES: to enumerate all available image processing modules,- DRM_IOCTL_EXYNOS_IPP_GET_CAPS: to query capabilities and supported image formats of given IPP module,- DRM_IOCTL_EXYNOS_IPP_GET_LIMITS: to query hardware limitiations for selected image format of given IPP module,- DRM_IOCTL_EXYNOS_IPP_COMMIT: to perform operation described by the provided structures (source and destination buffers, operation rectangle, transformation, etc).The proposed userspace API is extensible. In the future more advanced imageprocessing operations can be defined to support for example blending.Userspace API is fully functional also on DRM render nodes, so it is notlimited to the root/privileged client.Internal driver API also has been completely rewritten. New IPP coreperforms all possible input validation, checks and object life-timecontrol. The drivers can focus only on writing configuration to hardwareregisters. Stateless nature of DRM_IOCTL_EXYNOS_IPP_COMMIT ioctl simplifiesthe driver API. Minimal driver needs to provide a single callback forstarting processing and an array with supported image formats.Signed-off-by: Marek Szyprowski Tested-by: Hoegeun Kwon Merge conflict so merged manually.Signed-off-by: Inki Dae List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

8ded5941 - drm/exynos: ipp: Remove Exynos DRM IPP subsystem

Thu, 14 Dec 2017 15:10:15 +0000

drm/exynos: ipp: Remove Exynos DRM IPP subsystemExynos DRM IPP subsystem is in fact non-functional and frankly speakingdead-code. This patch clearly marks that Exynos DRM IPP subsystem isbroken and never really functional. It will be replaced by a completelyrewritten API.Exynos DRM IPP user-space API can be obsoleted for the followingreasons:1. Exynos DRM IPP user-space API can be optional in Exynos DRM, souserspace should not rely that it is always available and should havea software fallback in case it is not there.2. The only mode which was initially semi-working was memory-to-memoryimage processing. The remaining modes (LCD-"writeback" and "output")were never operational due to missing code (both in mainline and evenvendor kernels).3. Exynos DRM IPP mainline user-space API compatibility formemory-to-memory got broken very early by commit 083500baefd5 ("drm:remove DRM_FORMAT_NV12MT", which removed the support for tiled formats,the main feature which made this API somehow useful on Exynos platforms(video codec that time produced only tiled frames, to implement xvideoor any other video overlay, one has to de-tile them for properdisplay).4. Broken drivers. Especially once support for IOMMU has been added,it revealed that drivers don't configure DMA operations properly and inmany cases operate outside the provided buffers trashing memory around.5. Need for external patches. Although IPP user-space API has been usedin some vendor kernels, but in such cases there were additional patchesapplied (like reverting mentioned 083500baefd5 patch) what means thatthose userspace apps which might use it, still won't work with themainline kernel version.We don't have time machines, so we cannot change it, but Exynos DRM IPPextension should never have been merged to mainline in that form.Exynos IPP subsystem and user-space API will be rewritten, so removecurrent IPP core code and mark existing drivers as BROKEN.Signed-off-by: Marek Szyprowski Acked-by: Daniel Stone Acked-by: Krzysztof Kozlowski Signed-off-by: Inki Dae List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

e2be04c7 - License cleanup: add SPDX license identifier to uapi header files with a license

Wed, 01 Nov 2017 14:09:13 +0000

License cleanup: add SPDX license identifier to uapi header files with a licenseMany user space API headers have licensing information, which is eitherincomplete, badly formatted or just a shorthand for referring to thelicense under which the file is supposed to be. This makes it hard forcompliance tools to determine the correct license.Update these files with an SPDX license identifier. The identifier waschosen based on the license information in the file.GPL/LGPL licensed headers get the matching GPL/LGPL SPDX licenseidentifier with the added 'WITH Linux-syscall-note' exception, which isthe officially assigned exception identifier for the kernel syscallexception: NOTE! This copyright does *not* cover user programs that use kernel services by normal system calls - this is merely considered normal use of the kernel, and does *not* fall under the heading of "derived work".This exception makes it possible to include GPL headers into non GPLcode, without confusing license compliance tools.Headers which have either explicit dual licensing or are just licensedunder a non GPL license are updated with the corresponding SPDXidentifier and the GPLv2 with syscall exception identifier. The formatis: ((GPL-2.0 WITH Linux-syscall-note) OR SPDX-ID-OF-OTHER-LICENSE)SPDX license identifiers are a legally binding shorthand, which can beused instead of the full boiler plate text. The update does not removeexisting license information as this has to be done on a case by casebasis and the copyright holders might have to be consulted. This willhappen in a separate step.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne. See the previous patch in this series for themethodology of how this patch was researched.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

37a96bed - drm/exynos: add extern C guard for the UAPI header

Thu, 07 Apr 2016 17:58:35 +0000

drm/exynos: add extern C guard for the UAPI headerCc: Andrzej Hajda Cc: Inki Dae Signed-off-by: Emil Velikov List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

6564c65f - drm/exynos: add DRM_EXYNOS_GEM_MAP ioctl

Tue, 08 Mar 2016 05:12:59 +0000

drm/exynos: add DRM_EXYNOS_GEM_MAP ioctlThe commit d931589c01a2 ("drm/exynos: remove DRM_EXYNOS_GEM_MAP_OFFSETioctl") removed it same with the ioctl that this patch adds. The reasonthat removed DRM_EXYNOS_GEM_MAP_OFFSET was we could useDRM_IOCTL_MODE_MAP_DUMB. Both did exactly same thing.Now we again will revive it as DRM_EXYNOS_GEM_MAP because of rendernode. DRM_IOCTL_MODE_MAP_DUMB isn't permitted in render node.Signed-off-by: Joonyoung Shim Signed-off-by: Inki Dae List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

cbf0acef - drm/exynos: use arch independent types in uapi header

Fri, 12 Feb 2016 12:13:59 +0000

drm/exynos: use arch independent types in uapi headerUser API structs should not use types which size/alignment/padding dependson architecture. The patch fixes it for all structures exceptdrm_exynos_g2d_userptr, as g2d related stuff seems to be more complicatedand will be reviewed/adjusted later.Signed-off-by: Andrzej Hajda Reviewed-by: Emil Velikov Signed-off-by: Inki Dae List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

19b1e97a - drm: fix inclusion of drm.h in exynos_sarea.h

Mon, 30 Nov 2015 14:10:45 +0000

drm: fix inclusion of drm.h in exynos_sarea.hUsing `#include "drm.h"` instead of `#include ` allow drmheaders to be moved in another directory without changes, like for thelibdrm imports.Signed-off-by: Gabriel Laskar Reviewed-by: Emil Velikov CC: Emil Velikov CC: Mikko Rapeli List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

6615b20f - exynos_drm.h: use __u64 from linux/types.h

Sun, 31 Aug 2014 11:07:31 +0000

exynos_drm.h: use __u64 from linux/types.hFixes userspace compilation error:drm/exynos_drm.h:30:2: error: unknown type name ‘uint64_t’Signed-off-by: Mikko Rapeli List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

832316c7 - drm/exynos: use drm generic mmap interface

Thu, 18 Sep 2014 05:19:01 +0000

drm/exynos: use drm generic mmap interfaceThis patch removes DRM_EXYNOS_GEM_MMAP ictrl feature specificto Exynos drm and instead uses drm generic mmap.We had used the interface specific to Exynos drm to do mmap directly,not to use demand paging which maps each page with physical memoryat page fault handler. We don't need the specific mmap interfacebecause the drm generic mmap which uses vm offset manager stuff canalso do mmap directly.This patch makes a userspace region to be mapped with whole physicalmemory region allocated by userspace request when mmap system call isrequested.Changelog v2:- do not set VM_IO, VM_DONTEXPEND and VM_DONTDUMP. These flags were already set by drm_gem_mmap- do not include , which isn't needed anymore.Signed-off-by: Inki Dae List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

d931589c - drm/exynos: remove DRM_EXYNOS_GEM_MAP_OFFSET ioctl

Wed, 17 Sep 2014 13:48:45 +0000

drm/exynos: remove DRM_EXYNOS_GEM_MAP_OFFSET ioctlThis interface and relevant codes aren't used anymore.Signed-off-by: Inki Dae List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

4f21877c - drm/exynos: consider both case of vflip and hflip.

Sat, 22 Dec 2012 08:49:24 +0000

drm/exynos: consider both case of vflip and hflip.This patch considers both case of vflip and hflip.If we want that the contents in buffer to be rotated to 180 degree,then we can use h,vflip or 180 degree.Changelog v2:- added EXYNOS_DRM_FLIP_BOTH enum value to avoid build warnning.Signed-off-by: Eunchul Kim Signed-off-by: Inki Dae List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

d81aecb5 - drm/exynos: change file license to GPL

Mon, 17 Dec 2012 17:30:17 +0000

drm/exynos: change file license to GPLThis patch changes file license to GPLMost of exynos files had been copied from some randomfile and not updated correctly. So this patch correctsthe file license.Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

cb471f14 - drm/exynos: add ipp subsystem

Fri, 14 Dec 2012 09:10:31 +0000

drm/exynos: add ipp subsystemThis patch adds Image Post Processing(IPP) support for exynos drm driver.IPP supports image scaler/rotator and input/output DMA operationsusing IPP subsystem framework to control FIMC, Rotator and GSC hardwareand supports some user interfaces for user side.And each IPP-based drivers support Memory to Memory operationswith various converting. And in case of FIMC hardware, it also supportsWriteback and Display output operations through local path.Features:- Memory to Memory operation support.- Various pixel formats support.- Image scaling support.- Color Space Conversion support.- Image crop operation support.- Rotate operation support to 90, 180 or 270 degree.- Flip operation support to vertical, horizontal or both.- Writeback operation support to display blended image of FIMD fifo on screenA summary to IPP Subsystem operations:First of all, user should get property capabilities from IPP subsystemand set these properties to hardware registers for desired operations.The properties could be pixel format, position, rotation degree andflip operation.And next, user should set source and destination buffer data usingDRM_EXYNOS_IPP_QUEUE_BUF ioctl command with gem handles to source anddestinition buffers.And next, user can control user-desired hardware with desired operationssuch as play, stop, pause and resume controls.And finally, user can aware of dma operation completion and also getdestination buffer that it contains user-desried result through dequeuecommand.IOCTL commands:- DRM_EXYNOS_IPP_GET_PROPERTY . get ipp driver capabilitis and id.- DRM_EXYNOS_IPP_SET_PROPERTY . set format, position, rotation, flip to source and destination buffers- DRM_EXYNOS_IPP_QUEUE_BUF . enqueue/dequeue buffer and make event list.- DRM_EXYNOS_IPP_CMD_CTRL . play/stop/pause/resume control.Event:- DRM_EXYNOS_IPP_EVENT . a event to notify dma operation completion to user side.Basic control flow:Open -> Get properties -> User choose desired IPP sub driver(FIMC, Rotatoror GSCALER) -> Set Property -> Create gem handle -> Enqueue to source anddestination buffers -> Command control(Play) -> Event is notified to User-> User gets destinition buffer complated -> (Enqueue to source anddestination buffers -> Event is notified to User) * N -> Queue/Dequeue tosource and destination buffers -> Command control(Stop) -> Free gem handle-> CloseChangelog v1 ~ v5:- added comments, code fixups and cleanups.Signed-off-by: Eunchul Kim Signed-off-by: Jinyoung Jeon Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

2a3098ff - drm/exynos: add userptr feature for g2d module

Sun, 04 Nov 2012 13:48:52 +0000

drm/exynos: add userptr feature for g2d moduleThis patch adds userptr feautre for G2D module.The userptr means user space address allocated by malloc().And the purpose of this feature is to make G2D's dma ableto access the user space region.To user this feature, user should flag G2D_BUF_USRPTR tooffset variable of struct drm_exynos_g2d_cmd and fillstruct drm_exynos_g2d_userptr with user space addressand size for it and then should set a pointer todrm_exynos_g2d_userptr object to data variable of structdrm_exynos_g2d_cmd. The last bit of offset variable is usedto check if the cmdlist's buffer type is userptr or not.If userptr, the g2d driver gets user space address and sizeand then gets pages through get_user_pages().(another case is counted as gem handle)Below is sample codes:static void set_cmd(struct drm_exynos_g2d_cmd *cmd, unsigned long offset, unsigned long data){ cmd->offset = offset; cmd->data = data;}static int solid_fill_test(int x, int y, unsigned long userptr){ struct drm_exynos_g2d_cmd cmd_gem[5]; struct drm_exynos_g2d_userptr g2d_userptr; unsigned int gem_nr = 0; ... g2d_userptr.userptr = userptr; g2d_userptr.size = x * y * 4; set_cmd(&cmd_gem[gem_nr++], DST_BASE_ADDR_REG | G2D_BUF_USERPTR, (unsigned long)&g2d_userptr); ...}int main(int argc, char **argv){ unsigned long addr; ... addr = malloc(x * y * 4); ... solid_fill_test(x, y, addr); ...}And next, the pages are mapped with iommu table and the deviceaddress is set to cmdlist so that G2D's dma can access it.As you may know, the pages from get_user_pages() are pinned.In other words, they CAN NOT be migrated and also swapped out.So the dma access would be safe.But the use of userptr feature has performance overhead sothis patch also has memory pool to the userptr feature.Please, assume that user sends cmdlist filled with userptrand size every time to g2d driver, and the get_user_pagesfuncion will be called every time.The memory pool has maximum 64MB size and the userptr thatuser had ever sent, is holded in the memory pool.This meaning is that if the userptr from user is same as onein the memory pool, device address to the userptr in the memorypool is set to cmdlist.And last, the pages from get_user_pages() will be freed onceuser calls free() and the dma access is completed. Actually,get_user_pages() takes 2 reference counts if the user processhas never accessed user region allocated by malloc(). Then, ifthe user calls free(), the page reference count becomes 1 andbecomes 0 with put_page() call. And the reverse holds as well.This means how the pages backed are used by dma and freed.This patch is based on "drm/exynos: add iommu support for g2d", https://patchwork.kernel.org/patch/1629481/Signed-off-by: Inki Dae Signed-off-by: Kyungmin Park List of files: /linux-6.15/include/uapi/drm/exynos_drm.h

718dcedd - UAPI: (Scripted) Disintegrate include/drm

Thu, 04 Oct 2012 17:21:50 +0000

UAPI: (Scripted) Disintegrate include/drmSigned-off-by: David Howells Acked-by: Arnd Bergmann Acked-by: Thomas Gleixner Acked-by: Michael Kerrisk Acked-by: Paul E. McKenney Acked-by: Dave Jones List of files: /linux-6.15/include/uapi/drm/exynos_drm.h