From: Kevin Hilman <khilman@baylibre.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Maxime Jourdan <mjourdan@baylibre.com>
Cc: linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: meson-gx: Add canvas provider node to the vpu
Date: Thu, 17 Jan 2019 11:13:39 -0800 [thread overview]
Message-ID: <7ho98fcd24.fsf@baylibre.com> (raw)
In-Reply-To: <c7502035-0986-5d7d-b2b9-a35056146310@baylibre.com>
Neil Armstrong <narmstrong@baylibre.com> writes:
> On 14/01/2019 17:22, Maxime Jourdan wrote:
>> Allows the vpu driver to optionally use a canvas provider node.
>>
>> Signed-off-by: Maxime Jourdan <mjourdan@baylibre.com>
>> ---
>> arch/arm64/boot/dts/amlogic/meson-gx.dtsi | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
>> index 44c5c51ff1fa..9b0ac183ee0c 100644
>> --- a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
>> +++ b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
>> @@ -510,6 +510,7 @@
>> interrupts = <GIC_SPI 3 IRQ_TYPE_EDGE_RISING>;
>> #address-cells = <1>;
>> #size-cells = <0>;
>> + amlogic,canvas = <&canvas>;
>>
>> /* CVBS VDAC output port */
>> cvbs_vdac_port: port@0 {
>>
>
> Acked-by: Neil Armstrong <narmstrong@baylibre.com>
Queued for v5.1 (brancH: v5.1/dt64)
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2019-01-17 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 16:22 [PATCH] arm64: dts: meson-gx: Add canvas provider node to the vpu Maxime Jourdan
2019-01-15 9:36 ` Neil Armstrong
2019-01-17 19:13 ` Kevin Hilman [this message]
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=7ho98fcd24.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjourdan@baylibre.com \
--cc=narmstrong@baylibre.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;
as well as URLs for NNTP newsgroup(s).