From: Vinod Koul <vkoul@kernel.org>
To: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, "Csókás,
Bence" <csokas.bence@prolan.hu>
Cc: Mark Brown <broonie@kernel.org>,
Mesih Kilinc <mesihkilinc@gmail.com>,
Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Chen-Yu Tsai <wens@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Amit Singh Tomar <amitsinght@marvell.com>
Subject: Re: (subset) [PATCH v5 0/5] Add support for DMA of F1C100s
Date: Wed, 04 Dec 2024 18:48:58 +0530 [thread overview]
Message-ID: <173331833897.673424.223627111827356616.b4-ty@kernel.org> (raw)
In-Reply-To: <20241122161128.2619172-1-csokas.bence@prolan.hu>
On Fri, 22 Nov 2024 17:11:23 +0100, Csókás, Bence wrote:
> Support for Allwinner F1C100s/200s series audio was
> submitted in 2018 as an RFC series, but was not merged,
> despite having only minor errors. However, this is
> essential for having audio on these SoCs.
> This series was forward-ported/rebased to the best of
> my abilities, on top of Linus' tree as of now:
> commit 28eb75e178d3 ("Merge tag 'drm-next-2024-11-21' of https://gitlab.freedesktop.org/drm/kernel")
>
> [...]
Applied, thanks!
[1/5] dma-engine: sun4i: Add a quirk to support different chips
commit: eeca1b60138189ef1b9636709e578d0c9e0de517
[2/5] dma-engine: sun4i: Add has_reset option to quirk
commit: 1f738d0c2f67ae3551e4543e8dddbfb44cdd9f53
[3/5] dt-bindings: dmaengine: Add Allwinner suniv F1C100s DMA
commit: 1ad2ebf3be836e62792788f4cd105b30ca9178b6
[4/5] dma-engine: sun4i: Add support for Allwinner suniv F1C100s
commit: 61785259d1eb4e4c4acef8551a2524441683dbf3
Best regards,
--
~Vinod
next prev parent reply other threads:[~2024-12-04 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 16:11 Csókás, Bence
2024-11-22 16:11 ` [PATCH v6 1/5] dma-engine: sun4i: Add a quirk to support different chips Csókás, Bence
2024-11-22 16:11 ` [PATCH v6 2/5] dma-engine: sun4i: Add has_reset option to quirk Csókás, Bence
2024-11-22 16:11 ` [PATCH v6 3/5] dt-bindings: dmaengine: Add Allwinner suniv F1C100s DMA Csókás, Bence
2024-11-22 16:11 ` [PATCH v6 4/5] dma-engine: sun4i: Add support for Allwinner suniv F1C100s Csókás, Bence
2024-11-22 16:11 ` [PATCH v6 5/5] ARM: dts: suniv: f1c100s: Add support for DMA Csókás, Bence
2024-12-04 13:18 ` Vinod Koul [this message]
2024-12-04 23:55 ` (subset) [PATCH v5 0/5] Add support for DMA of F1C100s Csókás Bence
2024-12-05 3:22 ` Chen-Yu Tsai
2024-12-05 14:25 ` Chen-Yu Tsai
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=173331833897.673424.223627111827356616.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=amitsinght@marvell.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=csokas.bence@prolan.hu \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mesihkilinc@gmail.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.org \
--cc=wens@kernel.org \
/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
all inboxes | Powered by JetHome®