From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Benoit Parrot <bparrot@ti.com>
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
"Cyprian Wronka" <cwronka@cadence.com>,
"Richard Sproul" <sproul@cadence.com>,
"Alan Douglas" <adouglas@cadence.com>,
"Steve Creaney" <screaney@cadence.com>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Boris Brezillon" <boris.brezillon@free-electrons.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Hans Verkuil" <hans.verkuil@cisco.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
nm@ti.com
Subject: Re: [PATCH 2/2] v4l: cadence: Add Cadence MIPI-CSI2 TX driver
Date: Wed, 11 Oct 2017 13:55:44 +0200 [thread overview]
Message-ID: <20171011115544.w7eswyhke6dskgbb@flea> (raw)
In-Reply-To: <20170929182125.GB3163@ti.com>
[-- Attachment #1: Type: text/plain, Size: 2833 bytes --]
Hi Benoit,
On Fri, Sep 29, 2017 at 06:21:25PM +0000, Benoit Parrot wrote:
> > +struct csi2tx_priv {
> > + struct device *dev;
> > + atomic_t count;
> > +
> > + void __iomem *base;
> > +
> > + struct clk *esc_clk;
> > + struct clk *p_clk;
> > + struct clk *pixel_clk[CSI2TX_STREAMS_MAX];
> > +
> > + struct v4l2_subdev subdev;
> > + struct media_pad pads[CSI2TX_PAD_MAX];
> > + struct v4l2_mbus_framefmt pad_fmts[CSI2TX_PAD_MAX];
> > +
> > + bool has_internal_dphy;
>
> I assume dphy support is for a subsequent revision?
Yes, the situation is similar to the CSI2-RX driver.
> > + /*
> > + * We use the stream ID there, but it's wrong.
> > + *
> > + * A stream could very well send a data type that is
> > + * not equal to its stream ID. We need to find a
> > + * proper way to address it.
> > + */
>
> I don't quite get the above comment, from the code below it looks like
> you are using the current fmt as a source to provide the correct DT.
> Am I missing soemthing?
Yes, so far the datatype is inferred from the format set. Is there
anything wrong with that?
>
> > + writel(CSI2TX_DT_CFG_DT(fmt->dt),
> > + csi2tx->base + CSI2TX_DT_CFG_REG(stream));
> > +
> > + writel(CSI2TX_DT_FORMAT_BYTES_PER_LINE(mfmt->width * fmt->bpp) |
> > + CSI2TX_DT_FORMAT_MAX_LINE_NUM(mfmt->height + 1),
> > + csi2tx->base + CSI2TX_DT_FORMAT_REG(stream));
> > +
> > + /*
> > + * TODO: This needs to be calculated based on the
> > + * clock rate.
> > + */
> > + writel(CSI2TX_STREAM_IF_CFG_FILL_LEVEL(4),
> > + csi2tx->base + CSI2TX_STREAM_IF_CFG_REG(stream));
> > + }
> > +
> > + /* Disable the configuration mode */
> > + writel(0, csi2tx->base + CSI2TX_CONFIG_REG);
> > +
> > + return 0;
> > +}
> > +
> > +static int csi2tx_stop(struct csi2tx_priv *csi2tx)
> > +{
> > + /*
> > + * Let the last user turn off the lights
> > + */
> > + if (!atomic_dec_and_test(&csi2tx->count))
> > + return 0;
> > +
> > + /* FIXME: Disable the IP here */
> > +
> > + return 0;
> > +}
>
> At this point both _start() and _stop() only return 0.
> Are there any cases where any of these might fail to "start" or "stop"?
None that I know of.
There might be some errors with the video stream itself, but that
can be detected after the block has been enabled.
> > + csi2tx->lanes = csi2tx_get_num_lanes(&pdev->dev);
> > + if (csi2tx->lanes < 0) {
> > + dev_err(&pdev->dev, "Invalid number of lanes, bailing out.\n");
> > + ret = csi2tx->lanes;
> > + goto err_free_priv;
> > + }
>
> csi2tx->lanes is unsigned so it will never be negative.
Ah, right, I'll change that.
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-10-11 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 11:47 [PATCH 0/2] media: v4l: Add support for the Cadence MIPI-CSI2 TX controller Maxime Ripard
2017-09-22 11:47 ` [PATCH 1/2] dt-bindings: media: Add Cadence MIPI-CSI2 TX Device Tree bindings Maxime Ripard
2017-09-22 12:01 ` Sakari Ailus
2017-09-22 14:52 ` Maxime Ripard
[not found] ` <20170922114703.30511-2-maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-10-03 22:01 ` Rob Herring
[not found] ` <20170922114703.30511-1-maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-09-22 11:47 ` [PATCH 2/2] v4l: cadence: Add Cadence MIPI-CSI2 TX driver Maxime Ripard
[not found] ` <20170922114703.30511-3-maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2017-09-22 12:38 ` Sakari Ailus
2017-09-22 15:30 ` Maxime Ripard
2017-09-26 8:00 ` Sakari Ailus
[not found] ` <20170926080014.7a3lbe23rvzpcmkq-S+BSfZ9RZZmRSg0ZkenSGLdO1Tsj/99ntUK59QYPAWc@public.gmane.org>
2017-10-11 9:47 ` Maxime Ripard
2017-09-29 18:21 ` Benoit Parrot
2017-10-11 11:55 ` Maxime Ripard [this message]
2017-10-11 13:36 ` Benoit Parrot
[not found] ` <20171011133639.GC25400-l0cyMroinI0@public.gmane.org>
2017-10-13 11:38 ` Maxime Ripard
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=20171011115544.w7eswyhke6dskgbb@flea \
--to=maxime.ripard@free-electrons.com \
--cc=adouglas@cadence.com \
--cc=boris.brezillon@free-electrons.com \
--cc=bparrot@ti.com \
--cc=cwronka@cadence.com \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=screaney@cadence.com \
--cc=sproul@cadence.com \
--cc=thomas.petazzoni@free-electrons.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