Changes in Makefile

483fe862 - staging: media: imx: Merge VIDEO_IMX_CSI into VIDEO_IMX_MEDIA

Mon, 24 Apr 2023 09:48:32 +0000

staging: media: imx: Merge VIDEO_IMX_CSI into VIDEO_IMX_MEDIAThe VIDEO_IMX_MEDIA Kconfig symbol used to select helpers shared betweenindependent drivers for different i.MX SoCs, and VIDEO_IMX_MEDIA thenselects drivers specific to the i.MX5 and i.MX6. Now that i.MX7 andi.MX8 support has moved to drivers/media/ and doesn't depend onVIDEO_IMX_CSI, there's no need to have separate Kconfig options. MergeVIDEO_IMX_CSI into VIDEO_IMX_MEDIA.Signed-off-by: Laurent Pinchart Signed-off-by: Hans Verkuil List of files: /linux-6.15/drivers/staging/media/imx/Makefile

cd063027 - media: imx: Unstage the imx8mq-mipi-csi2 driver

Tue, 25 Apr 2023 09:08:04 +0000

media: imx: Unstage the imx8mq-mipi-csi2 driverThe imx8mq-mipi-csi2 MIPI CSI-2 receiver driver is used and maintained.There is no reason to keep it in staging. The accompanying CSI bridgedriver that uses it is in drivers/media/platform/nxp as well.One TODO is to get rid of csi_state's "state" and "lock" variables.Especially make sure suspend/resume is working without them. That canvery well be worked on from the new location.Also add a MAINTAINERS section for the imx8mq-mipi-csi2 mipi receiverdriver.Signed-off-by: Martin Kepplinger Reviewed-by: Laurent Pinchart Signed-off-by: Hans Verkuil List of files: /linux-6.15/drivers/staging/media/imx/Makefile

9f257f50 - media: imx: Unstage the imx7-media-csi driver

Tue, 10 May 2022 18:37:05 +0000

media: imx: Unstage the imx7-media-csi driverThe imx7-media-csi driver, currently in staging, is ready forprime-time. The staging TODO file lists a few items specific to thatdriver, that are already addressed (the "all of the above" part) or canbe addressed later:- The frame interval monitoring support is a software mechanism to monitor the device for unexpected stalls, and should be part of the V4L2 core if desired.- Restricting the support media bus formats based on the SoC integration only aims at reducing userspace confusion by not enumerating options that are known not to be possible, it won't cause regressions if handled later.Move the description of the media bus format restriction TODO item tothe driver, drop the other TODO items, and move the driver out ofstaging.Signed-off-by: Laurent Pinchart Reviewed-by: Paul Elder Acked-by: Rui Miguel Silva Tested-by: Alexander Stein Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

65932226 - media: imx: Decouple imx8mq-mipi-csi2 from imx7-media-csi

Tue, 10 May 2022 15:46:33 +0000

media: imx: Decouple imx8mq-mipi-csi2 from imx7-media-csiThe imx8mq-mipi-csi2 driver targets SoCs that also run theimx7-media-csi driver, but they are distinct. Decouple them in Kconfigto prepare for destaging of the imx7-media-csi driver.Signed-off-by: Laurent Pinchart Reviewed-by: Paul Elder Tested-by: Alexander Stein Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

85fa189b - media: imx: De-stage imx7-mipi-csis

Mon, 21 Feb 2022 17:47:21 +0000

media: imx: De-stage imx7-mipi-csisThe imx7-mipi-csis driver is in a good state and can be destaged.Move the imx7-mipi-csis.c driver to the newly createddrivers/media/platform/imx directory and plumb the relatedoptions in Kconfig and in Makefile.Signed-off-by: Jacopo Mondi Reviewed-by: Laurent Pinchart Acked-by: Rui Miguel Silva Acked-by: Sakari Ailus Signed-off-by: Hans Verkuil List of files: /linux-6.15/drivers/staging/media/imx/Makefile

f33fd8d7 - media: imx: add a driver for i.MX8MQ mipi csi rx phy and controller

Wed, 28 Jul 2021 09:12:44 +0000

media: imx: add a driver for i.MX8MQ mipi csi rx phy and controllerAdd a driver to support the i.MX8MQ MIPI CSI receiver. The hardware sideis based onhttps://source.codeaurora.org/external/imx/linux-imx/tree/drivers/media/platform/imx8/mxc-mipi-csi2_yav.c?h=imx_5.4.70_2.3.0It's built as part of VIDEO_IMX7_CSI because that's documented to supporti.MX8M platforms. This driver adds i.MX8MQ support where currently only thei.MX8MM platform has been supported.Signed-off-by: Martin Kepplinger Signed-off-by: Laurent Pinchart Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

772cb7f2 - media: imx: Compile imx6-media-objs only for CONFIG_VIDEO_IMX_CSI

Mon, 15 Feb 2021 04:26:28 +0000

media: imx: Compile imx6-media-objs only for CONFIG_VIDEO_IMX_CSIimx6-media-objs contains a set of objects that are specific to the i.MX6IPU-based media subsystem. They're not needed for the i.MX7 CSI. Onlycompile them if CONFIG_VIDEO_IMX_CSI is selected.Signed-off-by: Laurent Pinchart Reviewed-by: Rui Miguel Silva Reviewed-by: Ezequiel Garcia Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

b9dbfebb - media: staging: media: imx: Kconfig: support VIDEO_IMX7_CSI for imx8m

Wed, 02 Dec 2020 13:12:51 +0000

media: staging: media: imx: Kconfig: support VIDEO_IMX7_CSI for imx8mAs described in NXPs' linux tree, the imx8m SoC includes the sameCSI bridge hardware that is part of imx7d. We should be able touse the "fsl,imx7-csi" driver for imx8m directly.Since ipuv3 is not relevant for imx8m, move that dependency toVIDEO_IMX_CSI. That makes VIDEO_IMX7_CSI available to support imx8mtoo.Signed-off-by: Martin Kepplinger Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

a8ef0488 - media: imx: add csc/scaler mem2mem device

Wed, 14 Aug 2019 12:24:44 +0000

media: imx: add csc/scaler mem2mem deviceAdd a single imx-media mem2mem video device that uses the IPU IC PP(image converter post processing) task for scaling and colorspaceconversion.On i.MX6Q/DL SoCs with two IPUs currently only the first IPU is used.The hardware only supports writing to destination buffers up to1024x1024 pixels in a single pass, arbitrary sizes can be achievedby rendering multiple tiles per frame.[slongerbeam@gmail.com: use ipu_image_convert_adjust(), fix device_run() error handling, add missing media-device header, unregister and remove the mem2mem device in error paths in imx_media_probe_complete() and in imx_media_remove(), updated for sync subdev registration]Signed-off-by: Philipp Zabel Signed-off-by: Steve Longerbeam Signed-off-by: Hans Verkuil [hverkuil-cisco@xs4all.nl: correct two minor checkpatch issues][hverkuil-cisco@xs4all.nl: sparse warning: make imx6_media_probe_complete static]Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

6b8952db - media: staging/imx: Re-organize modules

Fri, 10 May 2019 21:50:10 +0000

media: staging/imx: Re-organize modulesRe-organize modules, and which objects are linked into those modules, sothat:- imx6-media (renamed from imx-media) is the media driver module for imx5/6 only, and has no symbol exports.- imx6-media-csi (renamed from imx-media-csi) is the subdev driver module for imx5/6 CSI. It is now linked direcly with imx-media-fim, since only the imx5/6 CSI makes use of the frame interval monitor.- imx-media-common now only contains common code between imx5/6 and imx7 media drivers. It contains imx-media-utils, imx-media-of, imx-media-dev-common, and imx-media-capture. In order to acheive that, some functions common to imx5/6 and imx7 have been moved out of imx-media-dev.c and into imx-media-dev-common.c.Signed-off-by: Steve Longerbeam Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

6d01b7ff - media: staging/imx: Switch to sync registration for IPU subdevs

Fri, 10 May 2019 21:50:05 +0000

media: staging/imx: Switch to sync registration for IPU subdevsBecause the IPU sub-devices VDIC and IC are not present in thedevice-tree, platform devices were created for them instead. Thisallowed these sub-devices to be added to the media device's asyncnotifier and registered asynchronously along with the othersub-devices that do have a device-tree presence (CSI and devicesexternal to the IPU and SoC).But that approach isn't really necessary. The IPU sub-devices don'tactually require a backing device (sd->dev is allowed to be NULL).And that approach can't get around the fact that the IPU sub-devicesare not part of a device hierarchy, which makes it awkward to retrievethe parent IPU of these devices.By registering them synchronously, they can be registered from the CSIasync bound notifier, so the init function for them can be given the CSIsubdev, who's dev->parent is the IPU. That is a somewhat cleaner wayto retrieve the parent IPU.So convert to synchronous registration for the VDIC and IC tasksub-devices, at the time a CSI sub-device is bound. There is no longera backing device for them (sd->dev is NULL), but that's ok. Alsoset the VDIC/IC sub-device owner as the IPU, so that a reference canbe taken on the IPU module.Since the VDIC and IC task drivers are no longer platform drivers,they are now statically linked to imx-media module.Signed-off-by: Steve Longerbeam Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

7807063b - media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7

Wed, 06 Feb 2019 15:13:20 +0000

media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7Adds MIPI CSI-2 subdev for i.MX7 to connect with sensors with a MIPICSI-2 interface.Signed-off-by: Rui Miguel Silva Signed-off-by: Hans Verkuil [hverkuil-cisco@xs4all.nl: clean up some alignment warnings]Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

05f63404 - media: staging/imx7: add imx7 CSI subdev driver

Wed, 06 Feb 2019 15:13:19 +0000

media: staging/imx7: add imx7 CSI subdev driverThis add the media entity subdevice and control driver for the i.MX7CMOS Sensor Interface.Signed-off-by: Rui Miguel Silva Acked-by: Sakari Ailus Signed-off-by: Hans Verkuil [hverkuil-cisco@xs4all.nl: clean up some alignment warnings]Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

174bcae1 - media: staging/imx: refactor imx media device probe

Wed, 06 Feb 2019 16:11:37 +0000

media: staging/imx: refactor imx media device probeRefactor and move media device initialization code to a new commonmodule, so it can be used by other devices, this will allow for examplea near to introduce imx7 CSI driver, to use this media device.Signed-off-by: Rui Miguel Silva Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/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/staging/media/imx/Makefile

f5138526 - [media] media: imx: Add MIPI CSI-2 Receiver subdev driver

Wed, 07 Jun 2017 18:34:04 +0000

[media] media: imx: Add MIPI CSI-2 Receiver subdev driverAdds MIPI CSI-2 Receiver subdev driver. This subdev is requiredfor sensors with a MIPI CSI2 interface.- Switch from the v4l2_of_ APIs to the v4l2_fwnode_ APIs.- Add the function csi2ipu_gasket_init() to initialize the gasket at s_power(ON). The gasket needs to be programmed with the correct color component ordering to handle UYVY vs. YUYV ordered mbus formats from sensors. Note that the description of the CSI2IPU_GASKET register in the i.MX6 reference manual is wrong w.r.t bit 2 (the manual refers to this register as CSI2_SW_RST): setting bit 2 selects YUYV order, not UYVY.Signed-off-by: Steve Longerbeam Signed-off-by: Philipp Zabel Suggested-by: Marek Vasut Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

f0d9c892 - [media] media: imx: Add IC subdev drivers

Wed, 07 Jun 2017 18:34:03 +0000

[media] media: imx: Add IC subdev driversThis is a set of three media entity subdevice drivers for the i.MXImage Converter:- Pre-process Router: Takes input frames from CSI0, CSI1, or VDIC. Two output pads enable either or both of the preprocess tasks below. If the input is from one of the CSIs, both proprocess task links can be enabled to process frames from that CSI simultaneously. If the input is the VDIC, only the Pre-processing Viewfinder task link can be enabled.- Pre-processing Encode task: video frames are routed directly from the CSI and can be scaled, color-space converted, and rotated. Scaled output is limited to 1024x1024 resolution. Output frames are routed to the prpenc capture device.- Pre-processing Viewfinder task: this task can perform the same conversions as the pre-process encode task, but in addition can be used for hardware motion compensated deinterlacing. Frames can come either directly from the CSI or from the VDIC. Scaled output is limited to 1024x1024 resolution. Output frames are routed to the prpvf capture device.Signed-off-by: Steve Longerbeam Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

93dae311 - [media] media: imx: Add VDIC subdev driver

Wed, 07 Jun 2017 18:34:02 +0000

[media] media: imx: Add VDIC subdev driverThis is a media entity subdevice driver for the i.MX Video De-Interlacingor Combining Block. So far this entity does not implement the Combiningfunction but only motion compensated deinterlacing. Video frames arereceived from the CSI and are routed to the IC PRPVF entity.Signed-off-by: Steve Longerbeam Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

4a34ec8e - [media] media: imx: Add CSI subdev driver

Wed, 07 Jun 2017 18:34:01 +0000

[media] media: imx: Add CSI subdev driverThis is a media entity subdevice for the i.MX CameraSensor Interface module.- Added support for negotiation of frame intervals.- Fixed cropping rectangle negotiation at input and output pads.- Added support for /2 downscaling, if the output pad dimension(s) are 1/2 the crop dimension(s) at csi_setup() time.Signed-off-by: Steve Longerbeam Signed-off-by: Russell King Signed-off-by: Philipp Zabel [hans.verkuil@cisco.com: add linux/pinctrl/consumer.h include]Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile

64b5a49d - [media] media: imx: Add Capture Device Interface

Wed, 07 Jun 2017 18:34:00 +0000

[media] media: imx: Add Capture Device InterfaceThis is the capture device interface driver that provides the v4l2user interface. Frames can be received from various sources:- directly from CSI for capturing unconverted images directly from camera sensors.- from the IC pre-process encode task.- from the IC pre-process viewfinder task.Signed-off-by: Steve Longerbeam Signed-off-by: Hans Verkuil Signed-off-by: Mauro Carvalho Chehab List of files: /linux-6.15/drivers/staging/media/imx/Makefile