From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Jacopo Mondi" <jacopo@jmondi.org>,
linux-media@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v4 0/4] i2c: adv748x: add support for CSI-2 TXA to work in 1-, 2- and 4-lane mode
Date: Fri, 11 Jan 2019 12:52:47 +0000 [thread overview]
Message-ID: <cd28246e-407a-c5fe-c6d8-23213ba96b54@ideasonboard.com> (raw)
In-Reply-To: <20181129020147.22115-1-niklas.soderlund+renesas@ragnatech.se>
Hi Niklas,
Thank you for this series. I think it really helps towards breaking down
those pre-defined tables of register data.
--
Kieran
On 29/11/2018 02:01, Niklas Söderlund wrote:
> Hi,
>
> This series allows the TXA CSI-2 transmitter of the adv748x to function
> in 1-, 2- and 4- lane mode. Currently the driver fixes the hardware in
> 4-lane mode. The driver looks at the standard DT property 'data-lanes'
> to determine which mode it should operate in.
>
> Patch 1/4 lists the 'data-lanes' DT property as mandatory for endpoints
> describing the CSI-2 transmitters. Patch 2/4 refactors the
> initialization sequence of the adv748x to be able to reuse more code.
> Patch 3/4 adds the DT parsing and storing of the number of lanes. Patch
> 4/4 merges the TXA and TXB power up/down procedure while also taking the
> configurable number of lanes into account.
>
> The series is based on the latest media-tree master and is tested on
> Renesas M3-N in 1-, 2- and 4- lane mode.
>
> Niklas Söderlund (4):
> dt-bindings: adv748x: make data-lanes property mandatory for CSI-2
> endpoints
> i2c: adv748x: reuse power up sequence when initializing CSI-2
> i2c: adv748x: store number of CSI-2 lanes described in device tree
> i2c: adv748x: configure number of lanes used for TXA CSI-2 transmitter
>
> .../devicetree/bindings/media/i2c/adv748x.txt | 11 +-
> drivers/media/i2c/adv748x/adv748x-core.c | 235 ++++++++++--------
> drivers/media/i2c/adv748x/adv748x.h | 1 +
> 3 files changed, 142 insertions(+), 105 deletions(-)
>
--
Regards
--
Kieran
prev parent reply other threads:[~2019-01-11 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 2:01 [PATCH v4 0/4] i2c: adv748x: add support for CSI-2 TXA to work in 1-, 2- and 4-lane mode Niklas Söderlund
2018-11-29 2:01 ` [PATCH v4 1/4] dt-bindings: adv748x: make data-lanes property mandatory for CSI-2 endpoints Niklas Söderlund
2018-11-29 18:58 ` Laurent Pinchart
2018-12-07 23:08 ` Rob Herring
2019-01-11 12:47 ` Kieran Bingham
2018-11-29 2:01 ` [PATCH v4 2/4] i2c: adv748x: reuse power up sequence when initializing CSI-2 Niklas Söderlund
2019-01-11 12:48 ` Kieran Bingham
2018-11-29 2:01 ` [PATCH v4 3/4] i2c: adv748x: store number of CSI-2 lanes described in device tree Niklas Söderlund
2019-01-11 12:50 ` Kieran Bingham
2018-11-29 2:01 ` [PATCH v4 4/4] i2c: adv748x: configure number of lanes used for TXA CSI-2 transmitter Niklas Söderlund
2019-01-11 12:51 ` Kieran Bingham
2019-01-11 12:52 ` Kieran Bingham [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=cd28246e-407a-c5fe-c6d8-23213ba96b54@ideasonboard.com \
--to=kieran.bingham@ideasonboard.com \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
/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).