Thread (5 messages) 5 messages, 2 authors, 2021-11-02

Re: [PATCH 1/2] media: atomisp: better describe get_frame_info issues

From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Date: 2021-11-02 06:54:26
Also in: linux-media, lkml

Em Fri, 29 Oct 2021 12:01:57 +0300
Andy Shevchenko [off-list ref] escreveu:
quoted
+       switch (type) {
+       case ATOMISP_CSS_VF_FRAME:
+               *info = p_info.vf_output_info[0];
+               dev_dbg(isp->dev, "getting vf frame info.\n");
+               break;
+       case ATOMISP_CSS_SECOND_VF_FRAME:
+               *info = p_info.vf_output_info[1];
+               dev_dbg(isp->dev, "getting second vf frame info.\n");
+               break;
+       case ATOMISP_CSS_OUTPUT_FRAME:
+               *info = p_info.output_info[0];
+               dev_dbg(isp->dev, "getting main frame info.\n");
+               break;
+       case ATOMISP_CSS_SECOND_OUTPUT_FRAME:
+               *info = p_info.output_info[1];
+               dev_dbg(isp->dev, "getting second main frame info.\n");
+               break;
+       case ATOMISP_CSS_RAW_FRAME:
+               *info = p_info.raw_output_info;
+               dev_dbg(isp->dev, "getting raw frame info.\n");  
Can we get break; here followed by default case?
Surely. I'll do such change on a separate patch.

Regards,
Mauro
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help