From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: krzk+dt@kernel.org
Cc: p.zabel@pengutronix.de, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, robh@kernel.org, conor+dt@kernel.org,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
matthias.bgg@gmail.com, andi.shyti@kernel.org, djakov@kernel.org,
broonie@kernel.org, jitao.shi@mediatek.com, ck.hu@mediatek.com,
dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, justin.yeh@mediatek.com,
jason-jh.lin@mediatek.com, kernel@collabora.com,
chunkuang.hu@kernel.org
Subject: Re: [PATCH 2/6] dt-bindings: soc: mediatek: mutex: Allow #trigger-source-cells
Date: Thu, 9 Jul 2026 15:58:23 +0200 [thread overview]
Message-ID: <fba4f7d6-d480-4f1a-8d80-3dd0a797b61e@collabora.com> (raw)
In-Reply-To: <20260701122043.19612-3-angelogioacchino.delregno@collabora.com>
On 7/1/26 14:20, AngeloGioacchino Del Regno wrote:
> This hardware controls trigger sources, and there's even a generic
> binding just for that: allow #trigger-source-cells in MuteX, so
> that this is allowed to provide triggers to external HW.
>
> Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Hey Krzysztof, I noticed you gave your A-b/R-b on the other two bindings commits
but you skipped this.
Did you have any doubts on this one that I may clarify for you, or was it just
that this one slipped through while reviewing?
Cheers,
Angelo
> ---
> .../devicetree/bindings/soc/mediatek/mediatek,mutex.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
> index 1ba086ad749d..429ea149068e 100644
> --- a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
> +++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mutex.yaml
> @@ -57,6 +57,9 @@ properties:
> items:
> - description: MUTEX Clock
>
> + '#trigger-source-cells':
> + const: 1
> +
> mediatek,gce-events:
> description:
> The event id which is mapping to the specific hardware event signal
> @@ -119,6 +122,7 @@ examples:
> interrupts = <GIC_SPI 169 IRQ_TYPE_LEVEL_LOW>;
> power-domains = <&spm MT8173_POWER_DOMAIN_MM>;
> clocks = <&mmsys CLK_MM_MUTEX_32K>;
> + #trigger-source-cells = <1>;
> mediatek,gce-events = <CMDQ_EVENT_MUTEX0_STREAM_EOF>,
> <CMDQ_EVENT_MUTEX1_STREAM_EOF>;
> };
next prev parent reply other threads:[~2026-07-09 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 12:20 [PATCH 0/6] MediaTek MMSYS/Mute-X new-style part 1 AngeloGioacchino Del Regno
2026-07-01 12:20 ` [PATCH 1/6] dt-bindings: soc: mediatek: mutex: Improve title and description AngeloGioacchino Del Regno
2026-07-02 7:52 ` Krzysztof Kozlowski
2026-07-01 12:20 ` [PATCH 2/6] dt-bindings: soc: mediatek: mutex: Allow #trigger-source-cells AngeloGioacchino Del Regno
2026-07-09 13:58 ` AngeloGioacchino Del Regno [this message]
2026-07-01 12:20 ` [PATCH 3/6] dt-bindings: display: mediatek: Allow trigger-sources on relevant HW AngeloGioacchino Del Regno
2026-07-02 7:59 ` Krzysztof Kozlowski
2026-07-01 12:20 ` [PATCH 4/6] soc: mediatek: mtk-mutex: Add new functions to add/remove triggers AngeloGioacchino Del Regno
2026-07-01 12:20 ` [PATCH 5/6] soc: mediatek: mtk-mmsys: Rework routes to specify component ID AngeloGioacchino Del Regno
2026-07-01 12:20 ` [PATCH 6/6] soc: mediatek: mtk-mmsys: Use MMSYS_ROUTE() in default routing table AngeloGioacchino Del Regno
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=fba4f7d6-d480-4f1a-8d80-3dd0a797b61e@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=airlied@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andi.shyti@kernel.org \
--cc=broonie@kernel.org \
--cc=chunkuang.hu@kernel.org \
--cc=ck.hu@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jason-jh.lin@mediatek.com \
--cc=jitao.shi@mediatek.com \
--cc=justin.yeh@mediatek.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthias.bgg@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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