From: Marek Vasut <marex@denx.de>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Inki Dae <inki.dae@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
Tim Harvey <tharvey@gateworks.com>,
Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
Adam Ford <aford173@gmail.com>,
Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Tommaso Merciai <tommaso.merciai@amarulasolutions.com>,
Matteo Lisi <matteo.lisi@engicam.com>,
dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
NXP Linux Team <linux-imx@nxp.com>,
linux-amarula <linux-amarula@amarulasolutions.com>
Subject: Re: [RESEND PATCH v11 13/18] drm: exynos: dsi: Add Exynos based host irq hooks
Date: Wed, 25 Jan 2023 17:46:41 +0100 [thread overview]
Message-ID: <c67cdb83-2fef-ad7c-f2c4-e2a6eb09a3e8@denx.de> (raw)
In-Reply-To: <CAMty3ZBxbwwocAwZ18o8tis54SRC64853b+p8VfzcD=OWrjP6Q@mail.gmail.com>
On 1/25/23 15:04, Jagan Teki wrote:
> On Wed, Jan 25, 2023 at 7:23 PM Marek Vasut <marex@denx.de> wrote:
>>
>> On 1/25/23 07:54, Jagan Teki wrote:
>>> On Wed, Jan 25, 2023 at 2:54 AM Jagan Teki <jagan@amarulasolutions.com> wrote:
>>>>
>>>> On Wed, Jan 25, 2023 at 2:54 AM Jagan Teki <jagan@amarulasolutions.com> wrote:
>>>>>
>>>>> On Wed, Jan 25, 2023 at 2:42 AM Marek Vasut <marex@denx.de> wrote:
>>>>>>
>>>>>> On 1/24/23 22:01, Jagan Teki wrote:
>>>>>>> On Wed, Jan 25, 2023 at 2:18 AM Marek Vasut <marex@denx.de> wrote:
>>>>>>>>
>>>>>>>> On 1/23/23 16:12, Jagan Teki wrote:
>>>>>>>>> Enable and disable of te_gpio's are Exynos platform specific
>>>>>>>>> irq handling, so add the exynos based irq operations and hook
>>>>>>>>> them for exynos plat_data.
>>>>>>>>
>>>>>>>> If this is just an optional generic GPIO IRQ, why not keep it in the
>>>>>>>> core code ? TE (tearing enable?) should be available on MX8M too.
>>>>>>>
>>>>>>> So far the discussion (since from initial versions) with Marek
>>>>>>> Szyprowski, seems to be available in Exynos. So, I keep it separate
>>>>>>> from the DSIM core.
>>>>>>
>>>>>> Isn't TE a generic GPIO IRQ ? If so, it is available also on i.MX8M .
>>>>
>>>> I will check this.
>>>
>>> In order to use TE_GPIO we need te handler implementation, right now
>>> Exynos CRTC DRM drivers have implementation for this. That is the main
>>> reason to keep the TE_GPIO handling in exynos, maybe if we handle that
>>> generically then it is a viable option to move TE_GPIO to the DSIM
>>> core.
>>
>> I think you can do this exactly the same way exynos does it -- check
>> whether te_handler() callback is implemented by the glue code (the one
>> you already have for various exynos and imx8mm/imx8mm SoCs) and if so,
>> call it. If it is not implemented, do not call anything in the TE IRQ
>> handler.
>
> I need to understand how i.MX8MM handles this on TE IRQ in the DSIM
> host side, Can I do this in future patch set as it might involve
> bindings changes as well if it's part of DSIM?
Why not leave an empty te_handler implementation on MX8M for now ?
You can fill that implementation in future patchset, but the generic
part of the code would be in place .
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-25 16:48 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 15:11 [RESEND PATCH v11 00/18] drm: Add Samsung MIPI DSIM bridge Jagan Teki
2023-01-23 15:11 ` [RESEND PATCH v11 01/18] drm: of: Lookup if child node has DSI panel or bridge Jagan Teki
2023-01-23 15:11 ` [RESEND PATCH v11 02/18] drm: bridge: panel: Add devm_drm_of_dsi_get_bridge helper Jagan Teki
2023-01-26 12:12 ` Maxime Ripard
2023-01-26 15:18 ` Jagan Teki
2023-01-27 17:39 ` Jagan Teki
2023-01-30 12:56 ` Maxime Ripard
2023-01-30 13:24 ` Jagan Teki
2023-01-31 12:45 ` Maxime Ripard
2023-01-31 13:47 ` Jagan Teki
2023-01-31 13:59 ` Maxime Ripard
2023-01-31 14:14 ` Jagan Teki
2023-01-30 12:58 ` Maxime Ripard
2023-01-30 13:22 ` Jagan Teki
2023-02-02 16:52 ` Jagan Teki
2023-02-03 8:26 ` Maxime Ripard
2023-02-03 10:43 ` Jagan Teki
2023-02-03 10:49 ` Maxime Ripard
2023-02-03 10:58 ` Jagan Teki
2023-02-03 11:04 ` Maxime Ripard
2023-02-27 11:25 ` Jagan Teki
2023-01-23 15:11 ` [RESEND PATCH v11 03/18] drm: exynos: dsi: Drop explicit call to bridge detach Jagan Teki
2023-01-23 15:11 ` [RESEND PATCH v11 04/18] drm: exynos: dsi: Switch to devm_drm_of_dsi_get_bridge Jagan Teki
2023-01-23 15:11 ` [RESEND PATCH v11 05/18] drm: exynos: dsi: Mark PHY as optional Jagan Teki
2023-01-23 15:12 ` [RESEND PATCH v11 06/18] drm: exynos: dsi: Add platform PLL_P (PMS_P) offset Jagan Teki
2023-01-23 15:12 ` [RESEND PATCH v11 07/18] drm: exynos: dsi: Introduce hw_type platform data Jagan Teki
2023-01-24 20:54 ` Marek Vasut
2023-01-23 15:12 ` [RESEND PATCH v11 08/18] drm: exynos: dsi: Handle proper host initialization Jagan Teki
2023-01-24 21:00 ` Marek Vasut
2023-01-23 15:12 ` [RESEND PATCH v11 09/18] drm: exynos: dsi: Add atomic check Jagan Teki
2023-01-24 20:55 ` Marek Vasut
2023-01-23 15:12 ` [RESEND PATCH v11 10/18] drm: exynos: dsi: Add input_bus_flags Jagan Teki
2023-01-24 20:55 ` Marek Vasut
2023-01-23 15:12 ` [RESEND PATCH v11 11/18] drm: exynos: dsi: Add atomic_get_input_bus_fmts Jagan Teki
2023-01-24 20:45 ` Marek Vasut
2023-01-24 21:16 ` Jagan Teki
2023-01-24 21:19 ` Marek Vasut
2023-01-24 21:22 ` Jagan Teki
2023-01-23 15:12 ` [RESEND PATCH v11 12/18] drm: exynos: dsi: Consolidate component and bridge Jagan Teki
2023-01-24 21:04 ` Marek Vasut
2023-01-23 15:12 ` [RESEND PATCH v11 13/18] drm: exynos: dsi: Add Exynos based host irq hooks Jagan Teki
2023-01-24 20:48 ` Marek Vasut
2023-01-24 21:01 ` Jagan Teki
2023-01-24 21:12 ` Marek Vasut
2023-01-24 21:24 ` Jagan Teki
2023-01-24 21:24 ` Jagan Teki
2023-01-25 6:54 ` Jagan Teki
2023-01-25 13:53 ` Marek Vasut
2023-01-25 14:04 ` Jagan Teki
2023-01-25 16:46 ` Marek Vasut [this message]
2023-01-25 17:12 ` Jagan Teki
2023-01-25 17:27 ` Marek Vasut
2023-01-25 17:35 ` Jagan Teki
2023-01-25 18:03 ` Marek Vasut
2023-01-25 19:24 ` Jagan Teki
2023-01-25 21:53 ` Marek Vasut
2023-01-25 16:02 ` Jagan Teki
2023-01-23 15:12 ` [RESEND PATCH v11 15/18] dt-bindings: display: exynos: dsim: Add NXP i.MX8M Mini/Nano support Jagan Teki
2023-01-24 20:56 ` Marek Vasut
2023-01-23 15:12 ` [RESEND PATCH v11 16/18] drm: bridge: samsung-dsim: Add " Jagan Teki
2023-01-24 20:56 ` Marek Vasut
2023-01-23 15:12 ` [RESEND PATCH v11 17/18] dt-bindings: display: exynos: dsim: Add NXP i.MX8M Plus support Jagan Teki
2023-01-24 20:57 ` Marek Vasut
2023-01-23 15:12 ` [RESEND PATCH v11 18/18] drm: bridge: samsung-dsim: Add " Jagan Teki
2023-01-24 20:59 ` Marek Vasut
2023-01-24 19:12 ` [RESEND PATCH v11 00/18] drm: Add Samsung MIPI DSIM bridge Jagan Teki
[not found] ` <20230123151212.269082-15-jagan@amarulasolutions.com>
2023-01-24 20:57 ` [RESEND PATCH v11 14/18] drm: bridge: Generalize Exynos-DSI driver into a Samsung " Marek Vasut
2023-01-24 21:13 ` [RESEND PATCH v11 00/18] drm: Add Samsung MIPI " Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c67cdb83-2fef-ad7c-f2c4-e2a6eb09a3e8@denx.de \
--to=marex@denx.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=aford173@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=frieder.schrempf@kontron.de \
--cc=inki.dae@samsung.com \
--cc=jagan@amarulasolutions.com \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=matteo.lisi@engicam.com \
--cc=michael@amarulasolutions.com \
--cc=robert.foss@linaro.org \
--cc=sw0312.kim@samsung.com \
--cc=tharvey@gateworks.com \
--cc=tommaso.merciai@amarulasolutions.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox