lkml.org 
[lkml]   [2021]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] media: atomisp: better describe get_frame_info issues
Em Fri, 29 Oct 2021 12:01:57 +0300
Andy Shevchenko <andy.shevchenko@gmail.com> escreveu:

> > + 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

\
 
 \ /
  Last update: 2021-11-02 07:55    [W:2.727 / U:1.144 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site