From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> To: unlisted-recipients:; (no To-header on input) Cc: linuxarm@huawei.com, mauro.chehab@huawei.com, Mauro Carvalho Chehab <mchehab+huawei@kernel.org>, Bhaskar Chowdhury <unixbhaskar@gmail.com>, Deepak R Varma <drv@mailo.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Hans Verkuil <hverkuil-cisco@xs4all.nl>, Hans de Goede <hdegoede@redhat.com>, Mauro Carvalho Chehab <mchehab@kernel.org>, Randy Dunlap <rdunlap@infradead.org>, Sakari Ailus <sakari.ailus@linux.intel.com>, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, linux-staging@lists.linux.dev Subject: [PATCH 2/3] media: atomisp-ov2680: adjust the maximum frame rate Date: Thu, 11 Nov 2021 17:27:57 +0000 [thread overview] Message-ID: <debf362a0fb0cd42a6c74cec9a720ed3052875f7.1636651027.git.mchehab+huawei@kernel.org> (raw) In-Reply-To: <cover.1636651027.git.mchehab+huawei@kernel.org> The ov2680 supports a maximum bandwidth of 660Mbps and allows up to 60fps when the resolution is below 720p. Adjust the sensor's table to reflect that. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> --- See [PATCH 0/3] at: https://lore.kernel.org/all/cover.1636651027.git.mchehab+huawei@kernel.org/ drivers/staging/media/atomisp/i2c/ov2680.h | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/staging/media/atomisp/i2c/ov2680.h b/drivers/staging/media/atomisp/i2c/ov2680.h index cb3c37d1c38e..4e351196fe34 100644 --- a/drivers/staging/media/atomisp/i2c/ov2680.h +++ b/drivers/staging/media/atomisp/i2c/ov2680.h @@ -822,7 +822,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 1280, .height = 720, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -835,7 +835,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 800, .height = 600, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -848,7 +848,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 720, .height = 592, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -861,7 +861,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 656, .height = 496, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -874,7 +874,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 336, .height = 256, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -887,7 +887,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 352, .height = 288, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -900,7 +900,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 176, .height = 144, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, -- 2.33.1
WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Cc: linuxarm@huawei.com, mauro.chehab@huawei.com, Mauro Carvalho Chehab <mchehab+huawei@kernel.org>, Bhaskar Chowdhury <unixbhaskar@gmail.com>, Deepak R Varma <drv@mailo.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Hans Verkuil <hverkuil-cisco@xs4all.nl>, Hans de Goede <hdegoede@redhat.com>, Mauro Carvalho Chehab <mchehab@kernel.org>, Randy Dunlap <rdunlap@infradead.org>, Sakari Ailus <sakari.ailus@linux.intel.com>, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, linux-staging@lists.linux.dev Subject: [PATCH 2/3] media: atomisp-ov2680: adjust the maximum frame rate Date: Thu, 11 Nov 2021 17:27:57 +0000 [thread overview] Message-ID: <debf362a0fb0cd42a6c74cec9a720ed3052875f7.1636651027.git.mchehab+huawei@kernel.org> (raw) In-Reply-To: <cover.1636651027.git.mchehab+huawei@kernel.org> The ov2680 supports a maximum bandwidth of 660Mbps and allows up to 60fps when the resolution is below 720p. Adjust the sensor's table to reflect that. Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org> --- See [PATCH 0/3] at: https://lore.kernel.org/all/cover.1636651027.git.mchehab+huawei@kernel.org/ drivers/staging/media/atomisp/i2c/ov2680.h | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/staging/media/atomisp/i2c/ov2680.h b/drivers/staging/media/atomisp/i2c/ov2680.h index cb3c37d1c38e..4e351196fe34 100644 --- a/drivers/staging/media/atomisp/i2c/ov2680.h +++ b/drivers/staging/media/atomisp/i2c/ov2680.h @@ -822,7 +822,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 1280, .height = 720, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -835,7 +835,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 800, .height = 600, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -848,7 +848,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 720, .height = 592, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -861,7 +861,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 656, .height = 496, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -874,7 +874,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 336, .height = 256, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -887,7 +887,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 352, .height = 288, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, @@ -900,7 +900,7 @@ static struct ov2680_resolution ov2680_res_preview[] = { { .width = 176, .height = 144, - .fps = 30, + .fps = 60, .pix_clk_freq = 66, .pixels_per_line = 1698,//1704, .lines_per_frame = 1294, -- 2.33.1
next prev parent reply other threads:[~2021-11-11 17:28 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-11 17:27 [PATCH 0/3] atomisp: add support for enum frame rate and sizes Mauro Carvalho Chehab 2021-11-11 17:27 ` Mauro Carvalho Chehab 2021-11-11 17:27 ` [PATCH 1/3] media: atomisp-ov2680: implement enum frame intervals Mauro Carvalho Chehab 2021-11-11 17:27 ` Mauro Carvalho Chehab 2021-11-11 17:27 ` Mauro Carvalho Chehab [this message] 2021-11-11 17:27 ` [PATCH 2/3] media: atomisp-ov2680: adjust the maximum frame rate Mauro Carvalho Chehab 2021-11-11 17:27 ` [PATCH 3/3] media: atomisp: implement enum framesize/frameinterval Mauro Carvalho Chehab 2021-11-11 17:27 ` Mauro Carvalho Chehab 2021-11-12 12:03 ` [PATCH 0/3] atomisp: add support for enum frame rate and sizes Mauro Carvalho Chehab 2021-11-12 12:03 ` Mauro Carvalho Chehab
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=debf362a0fb0cd42a6c74cec9a720ed3052875f7.1636651027.git.mchehab+huawei@kernel.org \ --to=mchehab+huawei@kernel.org \ --cc=drv@mailo.com \ --cc=gregkh@linuxfoundation.org \ --cc=hdegoede@redhat.com \ --cc=hverkuil-cisco@xs4all.nl \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=linux-staging@lists.linux.dev \ --cc=linuxarm@huawei.com \ --cc=mauro.chehab@huawei.com \ --cc=mchehab@kernel.org \ --cc=rdunlap@infradead.org \ --cc=sakari.ailus@linux.intel.com \ --cc=unixbhaskar@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.