<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/exynos, branch linux-5.18.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.18.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.18.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2022-08-17T12:41:04Z</updated>
<entry>
<title>drm/exynos/exynos7_drm_decon: free resources when clk_set_parent() failed.</title>
<updated>2022-08-17T12:41:04Z</updated>
<author>
<name>Jian Zhang</name>
</author>
<published>2022-07-12T04:56:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c30c1c05d6bf9f41d21639641b5fab53d419038a'/>
<id>urn:sha1:c30c1c05d6bf9f41d21639641b5fab53d419038a</id>
<content type='text'>
[ Upstream commit 48b927770f8ad3f8cf4a024a552abf272af9f592 ]

In exynos7_decon_resume, When it fails, we must use clk_disable_unprepare()
to free resource that have been used.

Fixes: 6f83d20838c09 ("drm/exynos: use DRM_DEV_ERROR to print out error
message")
Reported-by: Hulk Robot &lt;hulkci@huawei.com&gt;
Signed-off-by: Jian Zhang &lt;zhangjian210@huawei.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'driver-core-5.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core</title>
<updated>2022-03-28T19:41:28Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2022-03-28T19:41:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=266d17a8c0d857a579813ad185cd1640b0d6ccac'/>
<id>urn:sha1:266d17a8c0d857a579813ad185cd1640b0d6ccac</id>
<content type='text'>
Pull driver core updates from Greg KH:
 "Here is the set of driver core changes for 5.18-rc1.

  Not much here, primarily it was a bunch of cleanups and small updates:

   - kobj_type cleanups for default_groups

   - documentation updates

   - firmware loader minor changes

   - component common helper added and take advantage of it in many
     drivers (the largest part of this pull request).

  All of these have been in linux-next for a while with no reported
  problems"

* tag 'driver-core-5.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (54 commits)
  Documentation: update stable review cycle documentation
  drivers/base/dd.c : Remove the initial value of the global variable
  Documentation: update stable tree link
  Documentation: add link to stable release candidate tree
  devres: fix typos in comments
  Documentation: add note block surrounding security patch note
  samples/kobject: Use sysfs_emit instead of sprintf
  base: soc: Make soc_device_match() simpler and easier to read
  driver core: dd: fix return value of __setup handler
  driver core: Refactor sysfs and drv/bus remove hooks
  driver core: Refactor multiple copies of device cleanup
  scripts: get_abi.pl: Fix typo in help message
  kernfs: fix typos in comments
  kernfs: remove unneeded #if 0 guard
  ALSA: hda/realtek: Make use of the helper component_compare_dev_name
  video: omapfb: dss: Make use of the helper component_compare_dev
  power: supply: ab8500: Make use of the helper component_compare_dev
  ASoC: codecs: wcd938x: Make use of the helper component_compare/release_of
  iommu/mediatek: Make use of the helper component_compare/release_of
  drm: of: Make use of the helper component_release_of
  ...
</content>
</entry>
<entry>
<title>drm/exynos: fimd: add BGR support for exynos4/5</title>
<updated>2022-03-04T08:13:52Z</updated>
<author>
<name>Martin Jücker</name>
</author>
<published>2022-01-29T22:01:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2d684f4e155c1e80ff63bd503930171c460eac5b'/>
<id>urn:sha1:2d684f4e155c1e80ff63bd503930171c460eac5b</id>
<content type='text'>
In the downstream kernels for exynos4 and exynos5 devices, there is an
undocumented register that controls the order of the RGB output. It can
be set to either normal order or reversed, which enables BGR support for
those SoCs.

This patch enables the BGR support for all the SoCs that were found to
have at least one device with this logic in the corresponding downstream
kernels.

Signed-off-by: Martin Jücker &lt;martin.juecker@gmail.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: Search for TE-gpio in DSI panel's node</title>
<updated>2022-03-04T08:13:51Z</updated>
<author>
<name>Marek Szyprowski</name>
</author>
<published>2022-01-24T13:52:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fedc89821990013608bc210c9aef5bb33a1345a7'/>
<id>urn:sha1:fedc89821990013608bc210c9aef5bb33a1345a7</id>
<content type='text'>
TE-gpio, if defined, is placed in the panel's node, not the parent DSI
node. Change the devm_gpiod_get_optional() to gpiod_get_optional() and
pass proper device node to it. The code already has a proper cleanup
path, so it looks that the devm_* variant has been applied accidentally
during the conversion to gpiod API.

Fixes: ee6c8b5afa62 ("drm/exynos: Replace legacy gpio interface for gpiod interface")
Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;
Fixed a typo.
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: Don't fail if no TE-gpio is defined for DSI driver</title>
<updated>2022-03-04T08:13:51Z</updated>
<author>
<name>Marek Szyprowski</name>
</author>
<published>2022-01-21T10:00:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8e3fa9d841db7517c1dcc365a911eaeacee09f20'/>
<id>urn:sha1:8e3fa9d841db7517c1dcc365a911eaeacee09f20</id>
<content type='text'>
TE-gpio is optional and if it is not found then gpiod_get_optional()
returns NULL. In such case the code will continue and try to convert NULL
gpiod to irq what in turn fails. The failure is then propagated and driver
is not registered.

Fix this by returning early from exynos_dsi_register_te_irq() if no
TE-gpio is found.

Fixes: ee6c8b5afa62 ("drm/exynos: Replace legacy gpio interface for gpiod interface")
Signed-off-by: Marek Szyprowski &lt;m.szyprowski@samsung.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: gsc: Use platform_get_irq() to get the interrupt</title>
<updated>2022-03-04T08:13:51Z</updated>
<author>
<name>Lad Prabhakar</name>
</author>
<published>2021-12-22T19:01:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=25b522796223197063660f73db5212b5312c2660'/>
<id>urn:sha1:25b522796223197063660f73db5212b5312c2660</id>
<content type='text'>
platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.

In preparation for removal of static setup of IRQ resource from DT core
code use platform_get_irq().

Signed-off-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos/fimc: Use platform_get_irq() to get the interrupt</title>
<updated>2022-03-04T08:13:51Z</updated>
<author>
<name>Lad Prabhakar</name>
</author>
<published>2021-12-22T19:01:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=61f5fc8d5d577f201c39c886309fa30d91c9e392'/>
<id>urn:sha1:61f5fc8d5d577f201c39c886309fa30d91c9e392</id>
<content type='text'>
platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.

In preparation for removal of static setup of IRQ resource from DT core
code use platform_get_irq().

Signed-off-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos/exynos_drm_fimd: Use platform_get_irq_byname() to get the interrupt</title>
<updated>2022-03-04T08:13:51Z</updated>
<author>
<name>Lad Prabhakar</name>
</author>
<published>2021-12-22T19:01:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9df3f43acf9ad389484f4d24345672206ca315df'/>
<id>urn:sha1:9df3f43acf9ad389484f4d24345672206ca315df</id>
<content type='text'>
platform_get_resource_byname(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.

In preparation for removal of static setup of IRQ resource from DT core
code use platform_get_irq_byname().

Signed-off-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos: mixer: Use platform_get_irq() to get the interrupt</title>
<updated>2022-03-04T08:13:51Z</updated>
<author>
<name>Lad Prabhakar</name>
</author>
<published>2021-12-22T19:01:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6a91548e6b5ca9805dda068ed55a71f3bf33208e'/>
<id>urn:sha1:6a91548e6b5ca9805dda068ed55a71f3bf33208e</id>
<content type='text'>
platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.

In preparation for removal of static setup of IRQ resource from DT core
code use platform_get_irq().

Signed-off-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
<entry>
<title>drm/exynos/exynos7_drm_decon: Use platform_get_irq_byname() to get the interrupt</title>
<updated>2022-03-04T08:13:51Z</updated>
<author>
<name>Lad Prabhakar</name>
</author>
<published>2021-12-22T19:01:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=970dc5ed6b6aa8bd6cca138436e89f0cb0b8be85'/>
<id>urn:sha1:970dc5ed6b6aa8bd6cca138436e89f0cb0b8be85</id>
<content type='text'>
platform_get_resource_byname(pdev, IORESOURCE_IRQ, ..) relies on static
allocation of IRQ resources in DT core code, this causes an issue
when using hierarchical interrupt domains using "interrupts" property
in the node as this bypassed the hierarchical setup and messed up the
irq chaining.

In preparation for removal of static setup of IRQ resource from DT core
code use platform_get_irq_byname().

Signed-off-by: Lad Prabhakar &lt;prabhakar.mahadev-lad.rj@bp.renesas.com&gt;
Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
</content>
</entry>
</feed>
