From: Jagan Teki <jagan@amarulasolutions.com>
To: Yong Deng <yong.deng@magewell.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Maxime Ripard <maxime.ripard@bootlin.com>,
Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-media@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Michael Trimarchi <michael@amarulasolutions.com>,
linux-amarula@amarulasolutions.com, devicetree@vger.kernel.org,
linux-sunxi@googlegroups.com,
Jagan Teki <jagan@amarulasolutions.com>
Subject: [PATCH v8 0/5] media/sun6i: Allwinner A64 CSI support
Date: Mon, 28 Jan 2019 14:28:42 +0530 [thread overview]
Message-ID: <20190128085847.7217-1-jagan@amarulasolutions.com> (raw)
Add CSI support for Allwinner A64. Here is previous series[1]
Changes for v8:
- update proper enable and disable sequnce for clk_mod
- fix warning for patch "media: sun6i: Add A64 CSI block support"
- collect Maxime Acked-by
Changes for v7:
- Drop quirk change, and add as suggusted by Maxime
- Use csi instead csi0 in pinctrl function
Changes for v6:
- set the mod rate in seett_power instead of probe
Changes for v5:
- Add mod_rate quirk for better handling clk_set code
Changes for v4:
- update the compatible string order
- add proper commit message
- included BPI-M64 patch
- skipped amarula-a64 patch
Changes for v3:
- update dt-bindings for A64
- set mod clock via csi driver
- remove assign clocks from dtsi
- remove i2c-gpio opendrian
- fix avdd and dovdd supplies
- remove vcc-csi pin group supply
[1] https://patchwork.kernel.org/cover/10779831/
Jagan Teki (5):
dt-bindings: media: sun6i: Add A64 CSI compatible
media: sun6i: Add A64 CSI block support
arm64: dts: allwinner: a64: Add A64 CSI controller
arm64: dts: allwinner: a64: Add pinmux setting for CSI MCLK on PE1
[DO NOT MERGE] arm64: dts: allwinner: bananapi-m64: Add HDF5640 camera module
.../devicetree/bindings/media/sun6i-csi.txt | 1 +
.../dts/allwinner/sun50i-a64-bananapi-m64.dts | 65 +++++++++++++++++++
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 25 +++++++
.../platform/sunxi/sun6i-csi/sun6i_csi.c | 11 ++++
4 files changed, 102 insertions(+)
--
2.18.0.321.gffc6fa0e3
next reply other threads:[~2019-01-28 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 8:58 Jagan Teki [this message]
2019-01-28 8:58 ` [PATCH v8 1/5] dt-bindings: media: sun6i: Add A64 CSI compatible Jagan Teki
2019-01-28 8:58 ` [PATCH v8 2/5] media: sun6i: Add A64 CSI block support Jagan Teki
2019-01-28 11:02 ` Maxime Ripard
2019-01-28 8:58 ` [PATCH v8 3/5] arm64: dts: allwinner: a64: Add A64 CSI controller Jagan Teki
2019-01-28 11:02 ` Maxime Ripard
2019-01-28 8:58 ` [PATCH v8 4/5] arm64: dts: allwinner: a64: Add pinmux setting for CSI MCLK on PE1 Jagan Teki
2019-01-28 8:58 ` [DO NOT MERGE] [PATCH v8 5/5] arm64: dts: allwinner: bananapi-m64: Add HDF5640 camera module Jagan Teki
2019-02-11 8:22 ` [PATCH v8 0/5] media/sun6i: Allwinner A64 CSI support Jagan Teki
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=20190128085847.7217-1-jagan@amarulasolutions.com \
--to=jagan@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mchehab@kernel.org \
--cc=michael@amarulasolutions.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.org \
--cc=yong.deng@magewell.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).