Changes in Makefile

67fbf3a3 - drm/exynos/iommu: merge IOMMU and DMA code

Fri, 12 Oct 2018 10:53:46 +0000

drm/exynos/iommu: merge IOMMU and DMA codeAs DMA code is the only user of IOMMU code both files can be merged.It allows to remove stub functions, after slight adjustment ofexynos_drm_register_dma. Since IOMMU functions are used locally theycan be marked static.Signed-off-by: Andrzej Hajda Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

23755696 - drm/exynos/iommu: integrate IOMMU/DMA internal API

Fri, 12 Oct 2018 10:53:43 +0000

drm/exynos/iommu: integrate IOMMU/DMA internal APIExynos DRM drivers should work with and without IOMMU. Providing commonAPI generic to both scenarios should make code cleaner and allow furthercode improvements.The patch removes including of exynos_drm_iommu.h as the file containsmostly IOMMU specific stuff, instead it exposes exynos_drm_*_dma functionsand puts them into exynos_drm_dma.c.Signed-off-by: Andrzej Hajda Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

69908ed2 - drm/exynos/iommu: remove DRM_EXYNOS_IOMMU Kconfig symbol

Fri, 12 Oct 2018 10:53:42 +0000

drm/exynos/iommu: remove DRM_EXYNOS_IOMMU Kconfig symbolDRM_EXYNOS_IOMMU symbol is not configurable, it is always equal toEXYNOS_IOMMU.Signed-off-by: Andrzej Hajda Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

eb4d9796 - drm/exynos: g2d: Convert to driver component API

Mon, 09 Jul 2018 13:44:30 +0000

drm/exynos: g2d: Convert to driver component APIExynos G2D driver is the last client of the custom Exynos 'sub-driver'framework. In the current state it doesn't really resolve any of theissues it has been designed for, as Exynos DRM is already built onlyas a single kernel module. Remove the custom 'sub-driver' framework andsimply use generic component framework also in G2D driver.Signed-off-by: Marek Szyprowski Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

01fb9185 - drm/exynos: Add driver for Exynos Scaler module

Wed, 09 May 2018 08:59:26 +0000

drm/exynos: Add driver for Exynos Scaler moduleExynos Scaler is a hardware module, which processes graphic data fetchedfrom memory and transfers the resultant dato another memory buffer.Graphics data can be up/down-scaled, rotated, flipped and converted colorspace. Scaler hardware modules are a part of Exynos5420 and newer ExynosSoCs.Signed-off-by: Andrzej Pietrasiewicz Signed-off-by: Marek Szyprowski Acked-by: Rob Herring Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

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/drivers/gpu/drm/exynos/Makefile

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/drivers/gpu/drm/exynos/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

25c6a853 - drm/exynos: build fbdev code conditionally

Tue, 15 Mar 2016 11:43:21 +0000

drm/exynos: build fbdev code conditionallyFbdev code should be compiled only if CONFIG_DRM_FBDEV_EMULATION optionis enabled. The patch fixes exynos-drm code trying to manipulatefbdev data which is not initialized in case CONFIG_DRM_FBDEV_EMULATIONis disabled.Signed-off-by: Andrzej Hajda Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

9b988a0d - drm/exynos: build fbdev code conditionally

Tue, 15 Mar 2016 11:43:21 +0000

59c0ef31 - drm/exynos: dp: rename implementation specific driver part

Mon, 15 Feb 2016 11:09:46 +0000

drm/exynos: dp: rename implementation specific driver partThe core functionality now resides in the generic bridge part so theexynos-specific implementation details can get a more suitable nameing.Tested-by: Caesar Wang Tested-by: Douglas Anderson Tested-by: Javier Martinez Canillas Signed-off-by: Heiko Stuebner Signed-off-by: Yakir Yang List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

3424e3a4 - drm: bridge: analogix/dp: split exynos dp driver to bridge directory

Tue, 29 Mar 2016 01:57:03 +0000

drm: bridge: analogix/dp: split exynos dp driver to bridge directorySplit the dp core driver from exynos directory to bridge directory,and rename the core driver to analogix_dp_*, rename the platformcode to exynos_dp.Beside the new analogix_dp driver would export six hooks."analogix_dp_bind()" and "analogix_dp_unbind()""analogix_dp_suspned()" and "analogix_dp_resume()""analogix_dp_detect()" and "analogix_dp_get_modes()"The bind/unbind symbols is used for analogix platform driver to connectwith analogix_dp core driver. And the detect/get_modes is used for analogixplatform driver to init the connector.They reason why connector need register in helper driver is rockchip drmhaven't implement the atomic API, but Exynos drm have implement it, sothere would need two different connector helper functions, that's why weleave the connector register in helper driver.Acked-by: Inki Dae Tested-by: Caesar Wang Tested-by: Douglas Anderson Tested-by: Heiko Stuebner Tested-by: Javier Martinez Canillas Signed-off-by: Yakir Yang Signed-off-by: Heiko Stuebner List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

4e6319cd - drm/exynos: remove incorrect ccflags from Makefile

Wed, 24 Feb 2016 14:15:22 +0000

drm/exynos: remove incorrect ccflags from MakefileInclude directories are provided by core already, adding them in driveris redundand and causes warnings in case of out-of-tree build.v2: - fixed include in exynos_drm_iommu.c - typo in commit messageSigned-off-by: Andrzej Hajda Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

3cb02b4a - drm/exynos: separate Mixer and HDMI drivers

Mon, 26 Oct 2015 12:03:42 +0000

drm/exynos: separate Mixer and HDMI driversLatest Exynos SoCs does not have Mixer IP, but they still have HDMI IP.Their drivers should be configurable separately.Signed-off-by: Andrzej Hajda Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

2a8cb489 - drm/exynos: merge exynos_drm_buf.c to exynos_drm_gem.c

Sun, 16 Aug 2015 05:38:49 +0000

drm/exynos: merge exynos_drm_buf.c to exynos_drm_gem.cThe struct exynos_drm_gem_obj can have fields of the structexynos_drm_gem_buf then don't need to use exynos_drm_buf.c file.Signed-off-by: Joonyoung Shim Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

01ed50dd - drm/exynos: use prime helpers

Sun, 16 Aug 2015 05:33:08 +0000

drm/exynos: use prime helpersThe dma-buf codes of exynos drm is almost same with prime helpers. Adifference is that consider DMA_NONE when import dma-buf, but it's wrongand we don't consider it any more, so we can use prime interface.Signed-off-by: Joonyoung Shim Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

2b8376c8 - drm/exynos: remove struct exynos_drm_encoder layer

Sat, 15 Aug 2015 15:14:08 +0000

drm/exynos: remove struct exynos_drm_encoder layerstruct exynos_drm_encoder was justing wrapping struct drm_encoder, it hadonly a drm_encoder member and the internal exynos_drm_encoders ops thatwas directly mapped to the drm_encoder helper funcs.So now exynos DRM uses struct drm_encoder directly, this removescompletely the struct exynos_drm_encoder.v2: add empty .mode_fixup() and .mode_set() to DSI and DPI to avoid nullpointer.Signed-off-by: Gustavo Padovan Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

77bbd891 - drm/exynos: mic: add MIC driver

Fri, 12 Jun 2015 12:59:02 +0000

drm/exynos: mic: add MIC driverMIC(Mobile image compressor) is newly added IP in Exynos5433. MICresides between decon and mipi dsim, and compresses frame data by 50%.With dsi, not display port, to send frame data to the panel, thebandwidth is not enough. That is why this compressor is introduced.Signed-off-by: Hyungwon Hwang Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

c8466a91 - drm/exynos: add Exynos5433 decon driver

Fri, 12 Jun 2015 12:59:00 +0000

drm/exynos: add Exynos5433 decon driverDECON(Display and Enhancement Controller) is new IP replacing FIMD inExynos5433. This patch adds Exynos5433 decon driver.Signed-off-by: Joonyoung Shim Signed-off-by: Hyungwon Hwang Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile

96976c3d - drm/exynos: Add DECON driver

Thu, 05 Feb 2015 15:54:04 +0000

drm/exynos: Add DECON driverThis patch is based on exynos-drm-next branch of Inki Dae's tree at:git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.gitDECON(Display and Enhancement Controller) is the new IPin exynos7 SOC for generating video signals using pixel data.DECON driver can be used to drive 2 different interfaces on Exynos7:DECON-INT(video controller) and DECON-EXT(Mixer for HDMI)The existing FIMD driver code was used as a template to createDECON driver. Only DECON-INT is supported as of now, andDECON-EXT support will be added later.The current version of the driver supports video mode displays.Changelog v2:- Change config name, DRM_EXYNOS_DECON to DRM_EXYNOS7_DECON.Signed-off-by: Akshu Agrawal Signed-off-by: Ajay Kumar Signed-off-by: Inki Dae List of files: /linux-6.15/drivers/gpu/drm/exynos/Makefile