<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>7ae9fb1b7ecbb5d85d07857943f677fd1a559b18 - Merge branch &apos;next&apos; into for-linus</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#7ae9fb1b7ecbb5d85d07857943f677fd1a559b18</link>
        <description>Merge branch &apos;next&apos; into for-linusPrepare input updates for 6.3 merge window.

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Tue, 21 Feb 2023 20:19:49 +0100</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>6f84981772535e670e4e2df051a672af229b6694 - Merge drm/drm-next into drm-misc-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#6f84981772535e670e4e2df051a672af229b6694</link>
        <description>Merge drm/drm-next into drm-misc-nextBackmerging into drm-misc-next to get DRM accelerator infrastructure,which is required by ipuv driver.Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Thu, 19 Jan 2023 10:56:12 +0100</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>407da561244b9d51e6a794d6305ba38ec2c9d907 - Merge tag &apos;v6.2-rc3&apos; into next</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#407da561244b9d51e6a794d6305ba38ec2c9d907</link>
        <description>Merge tag &apos;v6.2-rc3&apos; into nextMerge with mainline to bring in timer_shutdown_sync() API.

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Tue, 10 Jan 2023 05:28:19 +0100</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>0d8eae7b124e2ddaee00f186fe922450faad0ed7 - Merge drm/drm-next into drm-intel-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#0d8eae7b124e2ddaee00f186fe922450faad0ed7</link>
        <description>Merge drm/drm-next into drm-intel-nextSync up with v6.2-rc1.Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Mon, 02 Jan 2023 10:31:03 +0100</pubDate>
        <dc:creator>Jani Nikula &lt;jani.nikula@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>b501d4dc83aa3940189b68045cadc8b3eac73988 - Merge drm/drm-next into drm-intel-gt-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#b501d4dc83aa3940189b68045cadc8b3eac73988</link>
        <description>Merge drm/drm-next into drm-intel-gt-nextSync after v6.2-rc1 landed in drm-next.We need to get some dependencies in place before we can mergethe fixes series from Gwan-gyeong and Chris.References: https://lore.kernel.org/all/Y6x5JCDnh2rvh4lA@intel.com/Signed-off-by: Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Fri, 30 Dec 2022 10:09:09 +0100</pubDate>
        <dc:creator>Rodrigo Vivi &lt;rodrigo.vivi@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>d0e99511834b6828c960e978d9a8cb6e5731250d - Merge wireless into wireless-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#d0e99511834b6828c960e978d9a8cb6e5731250d</link>
        <description>Merge wireless into wireless-nextDue to the two cherry picked commits from wireless to wireless-next we haveseveral conflicts in mt76. To avoid any bugs with conflicts merge wireless intowireless-next.96f134dc1964 wifi: mt76: handle possible mt76_rx_token_consume failuresfe13dad8992b wifi: mt76: dma: do not increment queue head if mt76_dma_add_buf fails

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Tue, 17 Jan 2023 12:36:25 +0100</pubDate>
        <dc:creator>Kalle Valo &lt;kvalo@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>2c55d703391acf7e9101da596d0c15ee03b318a3 - Merge drm/drm-fixes into drm-misc-fixes</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#2c55d703391acf7e9101da596d0c15ee03b318a3</link>
        <description>Merge drm/drm-fixes into drm-misc-fixesLet&apos;s start the fixes cycle.Signed-off-by: Maxime Ripard &lt;maxime@cerno.tech&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Tue, 03 Jan 2023 08:32:12 +0100</pubDate>
        <dc:creator>Maxime Ripard &lt;maxime@cerno.tech&gt;</dc:creator>
    </item>
<item>
        <title>1a931707ad4a46e79d4ecfee56d8f6e8cc8d4f28 - Merge remote-tracking branch &apos;torvalds/master&apos; into perf/core</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#1a931707ad4a46e79d4ecfee56d8f6e8cc8d4f28</link>
        <description>Merge remote-tracking branch &apos;torvalds/master&apos; into perf/coreTo resolve a trivial merge conflict with c302378bc157f6a7 (&quot;libbpf:Hashmap interface update to allow both long and void* keys/values&quot;),where a function present upstream was removed in the perf toolsdevelopment tree.Signed-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Fri, 16 Dec 2022 13:53:53 +0100</pubDate>
        <dc:creator>Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>cdb9d3537711939e4d8fd0de2889c966f88346eb - Merge tag &apos;media/v6.2-1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#cdb9d3537711939e4d8fd0de2889c966f88346eb</link>
        <description>Merge tag &apos;media/v6.2-1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-mediaPull media updates from Mauro Carvalho Chehab: - DVB core changes to avoid refcount troubles and UAF - DVB API/core has gained support for DVB-C2 and DVB-S2X - New sensor drivers: ov08x40, ov4689.c, st-vgxy61 and tc358746.c - Removal of an unused sensor driver: s5k4ecgx - Move microchip_csi2dc to a new directory, named after the   manufacturer - Add media controller support to Microship drivers - Old Atmel/Microship drivers that don&apos;t use media controler got moved   to staging - New drivers added for Renesas RZ/G2L CRU and MIPI CSI-2 support - Allwinner A31 camera sensor driver code was now split into a bridge   and a separate processor driver - Added a virtual stateless decoder driver in order to test core   support for stateless drivers and test userspace apps using it - removed platform-based support for ov9650, as this is not used   anymore - atomisp now uses videobuf2 and supports normal mmap mode - the imx7-media-csi driver got promoted from staging - rcar-vin driver has gained support for gen3 UDS (Up Down Scaler) - most i2c drivers now use I2C .probe_new() kAPI - lots of drivers fixes, cleanups and improvements* tag &apos;media/v6.2-1&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media: (544 commits)  media: s5c73m3: Switch to GPIO descriptors  media: i2c: s5k5baf: switch to using gpiod API  media: i2c: s5k6a3: switch to using gpiod API  media: imx: remove code for non-existing config IMX_GPT_ICAP  media: si470x: Fix use-after-free in si470x_int_in_callback()  media: staging: stkwebcam: Restore MEDIA_{USB,CAMERA}_SUPPORT dependencies  media: coda: Add check for kmalloc  media: coda: Add check for dcoda_iram_alloc  dt-bindings: media: s5c73m3: Fix reset-gpio descriptor  media: dt-bindings: allwinner: h6-vpu-g2: Add IOMMU reference property  media: s5k4ecgx: Delete driver  media: s5k4ecgx: Switch to GPIO descriptors  media: Switch to use dev_err_probe() helper  headers: Remove some left-over license text in include/uapi/linux/v4l2-*  headers: Remove some left-over license text in include/uapi/linux/dvb/  media: usb: pwc-uncompress: Use flex array destination for memcpy()  media: s5p-mfc: Fix to handle reference queue during finishing  media: s5p-mfc: Clear workbit to handle error condition  media: s5p-mfc: Fix in register read and write for H264  media: imx: Use get_mbus_config instead of parsing upstream DT endpoints  ...

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Tue, 13 Dec 2022 20:36:58 +0100</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>78ba0d79b7c854f0e8c2d25b5e8d5ee25374a57e - media: microchip: microchip-isc: implement media controller</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#78ba0d79b7c854f0e8c2d25b5e8d5ee25374a57e</link>
        <description>media: microchip: microchip-isc: implement media controllerAs a top MC video driver, the microchip-isc should not propagate the formatto the subdevice, it should rather check at start_streaming() time if thesubdev is properly configured with a compatible format.Removed the whole format finding logic, and reworked the formatverification at start_streaming time, such that the ISC will return anerror if the subdevice is not properly configured.To achieve this, media_pipeline_start is called and a link_validatecallback is created to check the formats.With this being done, the module parameter &apos;sensor_preferred&apos; makes nosense anymore. The ISC should not decide which format the sensor is using.The ISC should only cope with the situation and inform userspace if thestreaming is possible in the current configuration.The redesign of the format propagation has also risen the question of theenumfmt callback. If enumfmt is called with an mbus_code, the enumfmthandler should only return the formats that are supported for thismbus_code. Otherwise, the enumfmt will report all the formats that the ISCcould output.With this rework, the dynamic list of user formats is removed. It makes nomore sense to identify at complete time which formats the sensor couldemit, and add those into a separate dynamic list.The ISC will start with a simple preconfigured default format, and atlink validate time, decide whether it can use the format that isconfigured on the sink or not.&gt;From now on, the driver also advertises the IO_MC capability.Signed-off-by: Eugen Hristev &lt;eugen.hristev@microchip.com&gt;Reviewed-by: Jacopo Mondi &lt;jacopo@jmondi.org&gt;Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Mon, 07 Nov 2022 15:18:16 +0100</pubDate>
        <dc:creator>Eugen Hristev &lt;eugen.hristev@microchip.com&gt;</dc:creator>
    </item>
<item>
        <title>91b4e487b0c6b83064ad57b7a3a8d38c3245f020 - media: microchip: add ISC driver as Microchip ISC</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#91b4e487b0c6b83064ad57b7a3a8d38c3245f020</link>
        <description>media: microchip: add ISC driver as Microchip ISCThe Atmel ISC driver will be moved to staging to support old users thatare not using the media controller paradigm.The ISC driver was converted to media controller in the public patchseries:https://lore.kernel.org/lkml/20220503095127.48710-1-eugen.hristev@microchip.com/T/#m2c320fa8153c01379a1c35b1d90a00903949513aHowever the conversion cannot be done directly as it would affect existingusers by breaking the old way of configuration for sama5d2 platforms.After discussions with the media maintainers, the decision is to moveAtmel ISC to staging as-is, to keep the Kconfig symbols and the usersto the driver in staging. Thus, all the existing users of the nonmedia-controller paradigm will continue to be happy and use the old configway.The converted driver would support both sama5d2 and sama7g5 platforms withmedia controller paradigm, but it requires userspace configuration of thepipeline for all the pipeline modules.In a simple configuration sensor ==&gt; isc , the old isc driver used to callsubdev s_fmt and control the sensor directly.This was achieved by having a lot of code inside the driver that wasquerying the subdev at probe time and made a list of formats which areusable.Basically the user had nothing to configure, as the isc would handleeverything at the top level. This was an easy way to capture, but also camewith the drawback of lack of flexibility.In a more complicated pipeline sensor ==&gt; controller 1 ==&gt; controller 2 ==&gt; iscthis would not be achievable, as controller 1 and controller 2 might bemedia-controller configurable, and will not propagate the formats down tothe sensor.The new driver Microchip ISC would solve all these problems and exposes padsentities and links to userspace.For the ease of tracking, the patches that convert to media controller comeon top of this patch that simply readds the driver to the new location underthe new Kconfig symbols.To differentiate between the old driver and the new driver, I have renamedthe new driver to Microchip ISC, renaming the Kconfig symbols as well, andall the mentions inside the driver.The only thing that remains common is the fileinclude/linux/atmel-isc-media.h which is the ABI for the v4l2 customcontrols that the ISC exposes.This file is used by both driver, so I kept it as-is.To further avoid confusion all files have been renamed and all functionsnamed isc_* as well.The exported symbols have been renamed with added microchip_ prefix, toavoid symbol duplication with the old driver, and to avoid confusion.Other than that, I have fixed small checkpatch issues when readding thedriver.Signed-off-by: Eugen Hristev &lt;eugen.hristev@microchip.com&gt;Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Mon, 07 Nov 2022 15:18:14 +0100</pubDate>
        <dc:creator>Eugen Hristev &lt;eugen.hristev@microchip.com&gt;</dc:creator>
    </item>
<item>
        <title>37dcaf1ed0fcc71e1f9a656440a6e459958701cd - media: atmel: move microchip_csi2dc to dedicated microchip platform</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#37dcaf1ed0fcc71e1f9a656440a6e459958701cd</link>
        <description>media: atmel: move microchip_csi2dc to dedicated microchip platformThe Atmel ISC will be moved to staging thus the atmel platform will onlyhave the ISI driver.The new media-controller converted ISC driver will be placed inside adedicated microchip platform directory.It is then natural to have the microchip-csi2dc moved to this new platformdirectory.The next step is to add the Microchip ISC driver to the new platformdirectory and reside together with the Microchip CSI2DC driver.Signed-off-by: Eugen Hristev &lt;eugen.hristev@microchip.com&gt;Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Mon, 07 Nov 2022 15:18:13 +0100</pubDate>
        <dc:creator>Eugen Hristev &lt;eugen.hristev@microchip.com&gt;</dc:creator>
    </item>
<item>
        <title>86ff588c9ea47b92bfa99d6d1e466b2573baf51c - media: microchip: microchip-isc: implement media controller</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#86ff588c9ea47b92bfa99d6d1e466b2573baf51c</link>
        <description>media: microchip: microchip-isc: implement media controllerAs a top MC video driver, the microchip-isc should not propagate the formatto the subdevice, it should rather check at start_streaming() time if thesubdev is properly configured with a compatible format.Removed the whole format finding logic, and reworked the formatverification at start_streaming time, such that the ISC will return anerror if the subdevice is not properly configured.To achieve this, media_pipeline_start is called and a link_validatecallback is created to check the formats.With this being done, the module parameter &apos;sensor_preferred&apos; makes nosense anymore. The ISC should not decide which format the sensor is using.The ISC should only cope with the situation and inform userspace if thestreaming is possible in the current configuration.The redesign of the format propagation has also risen the question of theenumfmt callback. If enumfmt is called with an mbus_code, the enumfmthandler should only return the formats that are supported for thismbus_code. Otherwise, the enumfmt will report all the formats that the ISCcould output.With this rework, the dynamic list of user formats is removed. It makes nomore sense to identify at complete time which formats the sensor couldemit, and add those into a separate dynamic list.The ISC will start with a simple preconfigured default format, and atlink validate time, decide whether it can use the format that isconfigured on the sink or not.From now on, the driver also advertises the IO_MC capability.Signed-off-by: Eugen Hristev &lt;eugen.hristev@microchip.com&gt;Reviewed-by: Jacopo Mondi &lt;jacopo@jmondi.org&gt;Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Mon, 07 Nov 2022 15:18:16 +0100</pubDate>
        <dc:creator>Eugen Hristev &lt;eugen.hristev@microchip.com&gt;</dc:creator>
    </item>
<item>
        <title>a5517d53d4a69b8e8c46befc7f905278e78c3459 - media: microchip: add ISC driver as Microchip ISC</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#a5517d53d4a69b8e8c46befc7f905278e78c3459</link>
        <description>media: microchip: add ISC driver as Microchip ISCThe Atmel ISC driver will be moved to staging to support old users thatare not using the media controller paradigm.The ISC driver was converted to media controller in the public patchseries:https://lore.kernel.org/lkml/20220503095127.48710-1-eugen.hristev@microchip.com/T/#m2c320fa8153c01379a1c35b1d90a00903949513aHowever the conversion cannot be done directly as it would affect existingusers by breaking the old way of configuration for sama5d2 platforms.After discussions with the media maintainers, the decision is to moveAtmel ISC to staging as-is, to keep the Kconfig symbols and the usersto the driver in staging. Thus, all the existing users of the nonmedia-controller paradigm will continue to be happy and use the old configway.The converted driver would support both sama5d2 and sama7g5 platforms withmedia controller paradigm, but it requires userspace configuration of thepipeline for all the pipeline modules.In a simple configuration sensor ==&gt; isc , the old isc driver used to callsubdev s_fmt and control the sensor directly.This was achieved by having a lot of code inside the driver that wasquerying the subdev at probe time and made a list of formats which areusable.Basically the user had nothing to configure, as the isc would handleeverything at the top level. This was an easy way to capture, but also camewith the drawback of lack of flexibility.In a more complicated pipeline sensor ==&gt; controller 1 ==&gt; controller 2 ==&gt; iscthis would not be achievable, as controller 1 and controller 2 might bemedia-controller configurable, and will not propagate the formats down tothe sensor.The new driver Microchip ISC would solve all these problems and exposes padsentities and links to userspace.For the ease of tracking, the patches that convert to media controller comeon top of this patch that simply readds the driver to the new location underthe new Kconfig symbols.To differentiate between the old driver and the new driver, I have renamedthe new driver to Microchip ISC, renaming the Kconfig symbols as well, andall the mentions inside the driver.The only thing that remains common is the fileinclude/linux/atmel-isc-media.h which is the ABI for the v4l2 customcontrols that the ISC exposes.This file is used by both driver, so I kept it as-is.To further avoid confusion all files have been renamed and all functionsnamed isc_* as well.The exported symbols have been renamed with added microchip_ prefix, toavoid symbol duplication with the old driver, and to avoid confusion.Other than that, I have fixed small checkpatch issues when readding thedriver.Signed-off-by: Eugen Hristev &lt;eugen.hristev@microchip.com&gt;Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Mon, 07 Nov 2022 15:18:14 +0100</pubDate>
        <dc:creator>Eugen Hristev &lt;eugen.hristev@microchip.com&gt;</dc:creator>
    </item>
<item>
        <title>5c0185625dabf39af1937b647957b112e9f8ae4e - media: atmel: move microchip_csi2dc to dedicated microchip platform</title>
        <link>http://kernelsources.org:8080/source/history/linux/drivers/media/platform/microchip/Kconfig#5c0185625dabf39af1937b647957b112e9f8ae4e</link>
        <description>media: atmel: move microchip_csi2dc to dedicated microchip platformThe Atmel ISC will be moved to staging thus the atmel platform will onlyhave the ISI driver.The new media-controller converted ISC driver will be placed inside adedicated microchip platform directory.It is then natural to have the microchip-csi2dc moved to this new platformdirectory.The next step is to add the Microchip ISC driver to the new platformdirectory and reside together with the Microchip CSI2DC driver.Signed-off-by: Eugen Hristev &lt;eugen.hristev@microchip.com&gt;Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;

            List of files:
            /linux/drivers/media/platform/microchip/Kconfig</description>
        <pubDate>Mon, 07 Nov 2022 15:18:13 +0100</pubDate>
        <dc:creator>Eugen Hristev &lt;eugen.hristev@microchip.com&gt;</dc:creator>
    </item>
</channel>
</rss>
