From: Alexandre Torgue <alexandre.torgue@st.com>
To: Hugues Fruchet <hugues.fruchet@st.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Yannick Fertre <yannick.fertre@st.com>
Subject: Re: [PATCH v5 0/8] Add support for DCMI camera interface of STMicroelectronics STM32 SoC series
Date: Mon, 12 Jun 2017 12:03:31 +0200 [thread overview]
Message-ID: <f50a3320-a0ef-bdef-d236-f57fd477bccc@st.com> (raw)
In-Reply-To: <1493998287-5828-1-git-send-email-hugues.fruchet@st.com>
Hi Hugues
On 05/05/2017 05:31 PM, Hugues Fruchet wrote:
> This patchset introduces a basic support for Digital Camera Memory Interface
> (DCMI) of STMicroelectronics STM32 SoC series.
>
> This first basic support implements RGB565 & YUV frame grabbing.
> Cropping and JPEG support will be added later on.
>
> This has been tested on STM324x9I-EVAL evaluation board embedding
> an OV2640 camera sensor.
>
.....
>
> Hugues Fruchet (8):
> dt-bindings: Document STM32 DCMI bindings
> [media] stm32-dcmi: STM32 DCMI camera interface driver
> ARM: dts: stm32: Enable DCMI support on STM32F429 MCU
> ARM: dts: stm32: Enable DCMI camera interface on STM32F429-EVAL board
> ARM: dts: stm32: Enable STMPE1600 gpio expander of STM32F429-EVAL
> board
> ARM: dts: stm32: Enable OV2640 camera support of STM32F429-EVAL board
> ARM: configs: stm32: STMPE1600 GPIO expander
> ARM: configs: stm32: DCMI + OV2640 camera support
>
> .../devicetree/bindings/media/st,stm32-dcmi.txt | 46 +
> arch/arm/boot/dts/stm32429i-eval.dts | 56 +
> arch/arm/boot/dts/stm32f429.dtsi | 37 +
> arch/arm/configs/stm32_defconfig | 9 +
> drivers/media/platform/Kconfig | 12 +
> drivers/media/platform/Makefile | 2 +
> drivers/media/platform/stm32/Makefile | 1 +
> drivers/media/platform/stm32/stm32-dcmi.c | 1403 ++++++++++++++++++++
> 8 files changed, 1566 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/st,stm32-dcmi.txt
> create mode 100644 drivers/media/platform/stm32/Makefile
> create mode 100644 drivers/media/platform/stm32/stm32-dcmi.c
>
Patches 3, 4, 5, 6 applied on stm32-dt-for-v4.13
Patch 7 applied on stm32-defconfig-for-v4.13
Patch 8 will not be applied: As SDRAM used on STM32 MCUs is small,
I don't want to penalize other users:
- by increasing static kernel size
- by enabling devices which consume dynamically lot of memory
User will be free to enable it through menuconfig.
Regards
Alex
prev parent reply other threads:[~2017-06-12 10:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 15:31 [PATCH v5 0/8] Add support for DCMI camera interface of STMicroelectronics STM32 SoC series Hugues Fruchet
2017-05-05 15:31 ` [PATCH v5 1/8] dt-bindings: Document STM32 DCMI bindings Hugues Fruchet
2017-05-05 15:31 ` [PATCH v5 2/8] [media] stm32-dcmi: STM32 DCMI camera interface driver Hugues Fruchet
2017-05-06 8:54 ` Hans Verkuil
2017-05-09 7:36 ` Hugues FRUCHET
2017-05-05 15:31 ` [PATCH v5 3/8] ARM: dts: stm32: Enable DCMI support on STM32F429 MCU Hugues Fruchet
[not found] ` <1493998287-5828-1-git-send-email-hugues.fruchet-qxv4g6HH51o@public.gmane.org>
2017-05-05 15:31 ` [PATCH v5 4/8] ARM: dts: stm32: Enable DCMI camera interface on STM32F429-EVAL board Hugues Fruchet
2017-05-05 15:31 ` [PATCH v5 5/8] ARM: dts: stm32: Enable STMPE1600 gpio expander of " Hugues Fruchet
2017-05-05 15:31 ` [PATCH v5 6/8] ARM: dts: stm32: Enable OV2640 camera support " Hugues Fruchet
2017-05-05 15:31 ` [PATCH v5 7/8] ARM: configs: stm32: STMPE1600 GPIO expander Hugues Fruchet
2017-05-05 15:31 ` [PATCH v5 8/8] ARM: configs: stm32: DCMI + OV2640 camera support Hugues Fruchet
2017-06-12 10:03 ` Alexandre Torgue [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=f50a3320-a0ef-bdef-d236-f57fd477bccc@st.com \
--to=alexandre.torgue@st.com \
--cc=benjamin.gaignard@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hugues.fruchet@st.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=yannick.fertre@st.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).