From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com
Subject: [PATCH 1/1] microchip-csi2dc: Remove VC support for now
Date: Wed, 2 Feb 2022 17:36:09 +0200 [thread overview]
Message-ID: <20220202153609.240387-1-sakari.ailus@linux.intel.com> (raw)
As part of removing mbus config flags, remove VC flag use in the
microchip-csi2dc driver. The support can be reintroduced later on as part
of the streams patches.
Cc: Eugen Hristev <eugen.hristev@microchip.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
.../media/platform/atmel/microchip-csi2dc.c | 18 ++----------------
1 file changed, 2 insertions(+), 16 deletions(-)
diff --git a/drivers/media/platform/atmel/microchip-csi2dc.c b/drivers/media/platform/atmel/microchip-csi2dc.c
index 6bc549c28e05..6a7f5b4b0e3b 100644
--- a/drivers/media/platform/atmel/microchip-csi2dc.c
+++ b/drivers/media/platform/atmel/microchip-csi2dc.c
@@ -348,24 +348,15 @@ static int csi2dc_get_mbus_config(struct csi2dc_device *csi2dc)
if (ret == -ENOIOCTLCMD) {
dev_dbg(csi2dc->dev,
"no remote mbus configuration available\n");
- goto csi2dc_get_mbus_config_defaults;
+ return 0;
}
if (ret) {
dev_err(csi2dc->dev,
"failed to get remote mbus configuration\n");
- goto csi2dc_get_mbus_config_defaults;
+ return 0;
}
- if (mbus_config.flags & V4L2_MBUS_CSI2_CHANNEL_0)
- csi2dc->vc = 0;
- else if (mbus_config.flags & V4L2_MBUS_CSI2_CHANNEL_1)
- csi2dc->vc = 1;
- else if (mbus_config.flags & V4L2_MBUS_CSI2_CHANNEL_2)
- csi2dc->vc = 2;
- else if (mbus_config.flags & V4L2_MBUS_CSI2_CHANNEL_3)
- csi2dc->vc = 3;
-
dev_dbg(csi2dc->dev, "subdev sending on channel %d\n", csi2dc->vc);
csi2dc->clk_gated = mbus_config.flags &
@@ -375,11 +366,6 @@ static int csi2dc_get_mbus_config(struct csi2dc_device *csi2dc)
csi2dc->clk_gated ? "gated" : "free running");
return 0;
-
-csi2dc_get_mbus_config_defaults:
- csi2dc->vc = 0; /* Virtual ID 0 by default */
-
- return 0;
}
static void csi2dc_vp_update(struct csi2dc_device *csi2dc)
--
2.30.2
next reply other threads:[~2022-02-02 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 15:36 Sakari Ailus [this message]
2022-02-08 5:11 ` [PATCH 1/1] microchip-csi2dc: Remove VC support for now Mauro Carvalho Chehab
2022-02-08 8:00 ` Eugen.Hristev
2022-02-08 8:05 ` Eugen.Hristev
2022-02-08 11:06 ` Laurent Pinchart
2022-02-08 11:16 ` Sakari Ailus
2022-02-08 11:37 ` Eugen.Hristev
2022-02-08 11:36 ` Eugen.Hristev
2022-02-08 12:19 ` Laurent Pinchart
2022-02-15 19:21 ` Sakari Ailus
2022-02-15 20:10 ` Eugen.Hristev
2022-02-17 11:10 ` Sakari Ailus
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=20220202153609.240387-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.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).