From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Julien Stephan <jstephan@baylibre.com>
Cc: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Louis Kuo <louis.kuo@mediatek.com>,
Phi-bang Nguyen <pnguyen@baylibre.com>,
Florian Sylvestre <fsylvestre@baylibre.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Andy Hsieh <andy.hsieh@mediatek.com>,
Conor Dooley <conor+dt@kernel.org>,
daoyuan huang <daoyuan.huang@mediatek.com>,
devicetree@vger.kernel.org,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
linux-media@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Moudy Ho <moudy.ho@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>
Subject: Re: [PATCH v2 2/4] media: platform: mediatek: isp_30: add mediatek ISP3.0 sensor interface
Date: Fri, 4 Aug 2023 18:05:07 +0300 [thread overview]
Message-ID: <20230804150507.GI12951@pendragon.ideasonboard.com> (raw)
In-Reply-To: <72ixohoacq4vgj7nqg4l5gt5bs5e5ewain6a5ovqs3winx3qzz@sbg5lfohq5mq>
On Fri, Aug 04, 2023 at 04:50:05PM +0200, Julien Stephan wrote:
> On Mon, Jul 03, 2023 at 01:02:02PM +0200, AngeloGioacchino Del Regno wrote:
> > Il 30/06/23 12:01, Julien Stephan ha scritto:
> ..snip..
> > > +
> > > +static const struct mtk_seninf_format_info mtk_seninf_formats[] = {
> > > + {
> > > + .code = MEDIA_BUS_FMT_SBGGR8_1X8,
> > > + .flags = MTK_SENINF_FORMAT_BAYER,
> >
> > Each entry fits in one line.
> >
> > { .code = MEDIA_BUS_FMT_SBGGR8_1X8, .flags = MTK_SENINF_FORMAT_BAYER },
> >
>
> Hi Angelo,
>
> Actually not all entries fit in one line. The last 4 ones don't:
>
> { .code = MEDIA_BUS_FMT_SGRBG10_DPCM8_1X8, .flags = MTK_SENINF_FORMAT_DPCM | MTK_SENINF_FORMAT_INPUT_ONLY },
> which is 115 chars..
>
> so what is the best? put all in one line except the last 4 one? or keep
> them all as is?
I'd keep them all as is.
> > > + }, {
> ..snip..
> > > + udelay(1);
> > > + mtk_seninf_input_update(input, SENINF_CTRL, CSI2_SW_RST, 0);
> >
> > Is there any way to check if the CSI port did reset, or is it *guaranteed* to get
> > out of reset in a microsecond after deasserting SW_RST?
>
> I will double check this
>
> > > +}
> > > +
> ..snip..
> > > +
> > > + val = mtk_seninf_mux_read(mux, SENINF_MUX_CTRL);
> >
> > rst_mask = SENINF_MUX_CTRL_SENINF_IRQ_SW_RST | SENINF_MUX_CTRL_SENINF_MUX_SW_RST;
> >
> > writel(mux->base + SENINF_MUX_CTRL, val | rst_mask);
> > writel(mux->base + SENINFMUX_CTRL, val & ~rst_mask);
> >
> > that's better, right? :-)
With mtk_seninf_mux_write() instead of writel(), yes :-)
> right :)
>
> > > + mtk_seninf_mux_write(mux, SENINF_MUX_CTRL, val |
> > > + SENINF_MUX_CTRL_SENINF_IRQ_SW_RST |
> > > + SENINF_MUX_CTRL_SENINF_MUX_SW_RST);
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-08-04 15:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 10:01 [PATCH v2 0/4] Add Mediatek ISP3.0 Julien Stephan
2023-06-30 10:01 ` [PATCH v2 1/4] dt-bindings: media: add mediatek ISP3.0 sensor interface Julien Stephan
2023-06-30 11:23 ` Rob Herring
2023-06-30 14:32 ` Rob Herring
2023-06-30 10:01 ` [PATCH v2 2/4] media: platform: mediatek: isp_30: " Julien Stephan
2023-07-01 23:13 ` Chun-Kuang Hu
2023-07-01 23:35 ` Chun-Kuang Hu
2023-07-02 9:20 ` Chun-Kuang Hu
2023-07-03 12:18 ` Laurent Pinchart
2023-07-03 12:30 ` AngeloGioacchino Del Regno
2023-07-03 11:02 ` AngeloGioacchino Del Regno
2023-08-04 14:50 ` Julien Stephan
2023-08-04 15:05 ` Laurent Pinchart [this message]
2023-06-30 10:01 ` [PATCH v2 3/4] dt-bindings: media: add mediatek ISP3.0 camsv Julien Stephan
2023-06-30 11:23 ` Rob Herring
2023-06-30 14:33 ` Rob Herring
2023-06-30 10:01 ` [PATCH v2 4/4] media: platform: mediatek: isp_30: " Julien Stephan
2023-07-02 9:50 ` Chun-Kuang Hu
2023-07-03 12:21 ` AngeloGioacchino Del Regno
2023-08-03 9:53 ` Julien Stephan
2023-08-03 22:30 ` Laurent Pinchart
2023-08-04 7:34 ` AngeloGioacchino Del Regno
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=20230804150507.GI12951@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=agordeev@linux.ibm.com \
--cc=andy.hsieh@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daoyuan.huang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=fsylvestre@baylibre.com \
--cc=gor@linux.ibm.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jstephan@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louis.kuo@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=moudy.ho@mediatek.com \
--cc=pnguyen@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 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).