mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alain Volmat <alain.volmat@foss.st.com>
To: Benjamin Mugnier <benjamin.mugnier@foss.st.com>,
	Sylvain Petinot <sylvain.petinot@foss.st.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hugues Fruchet <hugues.fruchet@foss.st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Alain Volmat <alain.volmat@foss.st.com>,
	<linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v2 0/2] media: stm32: correct s_stream calls in dcmi & st-mipid02
Date: Fri, 21 Jul 2023 14:03:13 +0200	[thread overview]
Message-ID: <20230721120316.1172445-1-alain.volmat@foss.st.com> (raw)

Currently the stm32 dcmi driver is calling s_stream to all subdevs until
reaching the sensor subdev.  This serie corrects this by having a subdev
only calling s_stream on its source subdev.

v2: correct an uninitialized variable (ret) in st_mipid02 patch

Alain Volmat (2):
  media: i2c: st_mipid02: cascade s_stream call to the source subdev
  media: stm32: dcmi: only call s_stream on the source subdev

 drivers/media/i2c/st-mipid02.c               | 13 +++-
 drivers/media/platform/st/stm32/stm32-dcmi.c | 63 +++++---------------
 2 files changed, 26 insertions(+), 50 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-07-21 12:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21 12:03 Alain Volmat [this message]
2023-07-21 12:03 ` [PATCH v2 1/2] media: i2c: st_mipid02: cascade s_stream call to the source subdev Alain Volmat
2023-07-25  7:56   ` Benjamin Mugnier
2023-07-21 12:03 ` [PATCH v2 2/2] media: stm32: dcmi: only call s_stream on " Alain Volmat
2023-07-25  8:34   ` Hugues FRUCHET

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=20230721120316.1172445-1-alain.volmat@foss.st.com \
    --to=alain.volmat@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=benjamin.mugnier@foss.st.com \
    --cc=hugues.fruchet@foss.st.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mchehab@kernel.org \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=sylvain.petinot@foss.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

all inboxes | Powered by JetHome®