From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, mjourdan@baylibre.com,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/5] 32-bit Meson: add the canvas module
Date: Wed, 22 May 2019 18:21:23 -0700 [thread overview]
Message-ID: <7h1s0q55kc.fsf@baylibre.com> (raw)
In-Reply-To: <20190520194353.24445-1-martin.blumenstingl@googlemail.com>
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> This adds the canvas module on Meson8, Meson8b and Meson8m2. The canvas
> IP is used by the video decoder hardware as well as the VPU (video
> output) hardware.
>
> Neither the VPU nor the video decoder driver support the 32-bit SoCs
> yet. However, we can still add the canvas module to have it available
> once these drivers gain support for the older SoCs.
>
> I have tested this on my Meson8m2 board by hacking the VPU driver to
> not re-initialize the VPU (and to use the configuration set by u-boot).
> With that hack I could get some image out of the CVBS connector. No
> changes to the canvas driver were required.
>
> Due to lack of hardware I could not test Meson8, but I'm following (as
> always) what the Amlogic 3.10 vendor kernel uses.
> Meson8b is also not tested because u-boot of my EC-100 doesn't have
> video output enabled (so I couldn't use the same hack I used on my
> Meson8m2 board).
Queued for v5.3...
> Martin Blumenstingl (5):
> dt-bindings: soc: amlogic: canvas: document support for Meson8/8b/8m2
> soc: amlogic: canvas: add support for Meson8, Meson8b and Meson8m2
these two in v5.3/drivers
> ARM: dts: meson8: add the canvas module
> ARM: dts: meson8m2: update the offset of the canvas module
> ARM: dts: meson8b: add the canvas module
and these 3 in v5.3/dt.
Thanks,
Kevin
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, mjourdan@baylibre.com,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/5] 32-bit Meson: add the canvas module
Date: Wed, 22 May 2019 18:21:23 -0700 [thread overview]
Message-ID: <7h1s0q55kc.fsf@baylibre.com> (raw)
In-Reply-To: <20190520194353.24445-1-martin.blumenstingl@googlemail.com>
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> This adds the canvas module on Meson8, Meson8b and Meson8m2. The canvas
> IP is used by the video decoder hardware as well as the VPU (video
> output) hardware.
>
> Neither the VPU nor the video decoder driver support the 32-bit SoCs
> yet. However, we can still add the canvas module to have it available
> once these drivers gain support for the older SoCs.
>
> I have tested this on my Meson8m2 board by hacking the VPU driver to
> not re-initialize the VPU (and to use the configuration set by u-boot).
> With that hack I could get some image out of the CVBS connector. No
> changes to the canvas driver were required.
>
> Due to lack of hardware I could not test Meson8, but I'm following (as
> always) what the Amlogic 3.10 vendor kernel uses.
> Meson8b is also not tested because u-boot of my EC-100 doesn't have
> video output enabled (so I couldn't use the same hack I used on my
> Meson8m2 board).
Queued for v5.3...
> Martin Blumenstingl (5):
> dt-bindings: soc: amlogic: canvas: document support for Meson8/8b/8m2
> soc: amlogic: canvas: add support for Meson8, Meson8b and Meson8m2
these two in v5.3/drivers
> ARM: dts: meson8: add the canvas module
> ARM: dts: meson8m2: update the offset of the canvas module
> ARM: dts: meson8b: add the canvas module
and these 3 in v5.3/dt.
Thanks,
Kevin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: linux-amlogic@lists.infradead.org, mjourdan@baylibre.com,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH v2 0/5] 32-bit Meson: add the canvas module
Date: Wed, 22 May 2019 18:21:23 -0700 [thread overview]
Message-ID: <7h1s0q55kc.fsf@baylibre.com> (raw)
In-Reply-To: <20190520194353.24445-1-martin.blumenstingl@googlemail.com>
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> This adds the canvas module on Meson8, Meson8b and Meson8m2. The canvas
> IP is used by the video decoder hardware as well as the VPU (video
> output) hardware.
>
> Neither the VPU nor the video decoder driver support the 32-bit SoCs
> yet. However, we can still add the canvas module to have it available
> once these drivers gain support for the older SoCs.
>
> I have tested this on my Meson8m2 board by hacking the VPU driver to
> not re-initialize the VPU (and to use the configuration set by u-boot).
> With that hack I could get some image out of the CVBS connector. No
> changes to the canvas driver were required.
>
> Due to lack of hardware I could not test Meson8, but I'm following (as
> always) what the Amlogic 3.10 vendor kernel uses.
> Meson8b is also not tested because u-boot of my EC-100 doesn't have
> video output enabled (so I couldn't use the same hack I used on my
> Meson8m2 board).
Queued for v5.3...
> Martin Blumenstingl (5):
> dt-bindings: soc: amlogic: canvas: document support for Meson8/8b/8m2
> soc: amlogic: canvas: add support for Meson8, Meson8b and Meson8m2
these two in v5.3/drivers
> ARM: dts: meson8: add the canvas module
> ARM: dts: meson8m2: update the offset of the canvas module
> ARM: dts: meson8b: add the canvas module
and these 3 in v5.3/dt.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@baylibre.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-amlogic@lists.infradead.org, mjourdan@baylibre.com,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: Re: [PATCH v2 0/5] 32-bit Meson: add the canvas module
Date: Wed, 22 May 2019 18:21:23 -0700 [thread overview]
Message-ID: <7h1s0q55kc.fsf@baylibre.com> (raw)
In-Reply-To: <20190520194353.24445-1-martin.blumenstingl@googlemail.com>
Martin Blumenstingl <martin.blumenstingl@googlemail.com> writes:
> This adds the canvas module on Meson8, Meson8b and Meson8m2. The canvas
> IP is used by the video decoder hardware as well as the VPU (video
> output) hardware.
>
> Neither the VPU nor the video decoder driver support the 32-bit SoCs
> yet. However, we can still add the canvas module to have it available
> once these drivers gain support for the older SoCs.
>
> I have tested this on my Meson8m2 board by hacking the VPU driver to
> not re-initialize the VPU (and to use the configuration set by u-boot).
> With that hack I could get some image out of the CVBS connector. No
> changes to the canvas driver were required.
>
> Due to lack of hardware I could not test Meson8, but I'm following (as
> always) what the Amlogic 3.10 vendor kernel uses.
> Meson8b is also not tested because u-boot of my EC-100 doesn't have
> video output enabled (so I couldn't use the same hack I used on my
> Meson8m2 board).
Queued for v5.3...
> Martin Blumenstingl (5):
> dt-bindings: soc: amlogic: canvas: document support for Meson8/8b/8m2
> soc: amlogic: canvas: add support for Meson8, Meson8b and Meson8m2
these two in v5.3/drivers
> ARM: dts: meson8: add the canvas module
> ARM: dts: meson8m2: update the offset of the canvas module
> ARM: dts: meson8b: add the canvas module
and these 3 in v5.3/dt.
Thanks,
Kevin
next prev parent reply other threads:[~2019-05-23 1:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 19:43 [PATCH v2 0/5] 32-bit Meson: add the canvas module Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` [PATCH v2 1/5] dt-bindings: soc: amlogic: canvas: document support for Meson8/8b/8m2 Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-21 11:26 ` Maxime Jourdan
2019-05-21 11:26 ` Maxime Jourdan
2019-05-21 11:26 ` Maxime Jourdan
2019-05-20 19:43 ` [PATCH v2 2/5] soc: amlogic: canvas: add support for Meson8, Meson8b and Meson8m2 Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-21 8:07 ` Maxime Jourdan
2019-05-21 8:07 ` Maxime Jourdan
2019-05-21 8:07 ` Maxime Jourdan
2019-05-20 19:43 ` [PATCH v2 3/5] ARM: dts: meson8: add the canvas module Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` [PATCH v2 4/5] ARM: dts: meson8m2: update the offset of " Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` [PATCH v2 5/5] ARM: dts: meson8b: add " Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-20 19:43 ` Martin Blumenstingl
2019-05-23 1:21 ` Kevin Hilman [this message]
2019-05-23 1:21 ` [PATCH v2 0/5] 32-bit Meson: " Kevin Hilman
2019-05-23 1:21 ` Kevin Hilman
2019-05-23 1:21 ` Kevin Hilman
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=7h1s0q55kc.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=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=mjourdan@baylibre.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.