From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Todor Tomov <todor.tomov@linaro.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: [PATCH] [RFC] media: camss-vfe: always initialize reg at vfe_set_xbar_cfg()
Date: Wed, 1 Nov 2017 11:25:41 -0200 [thread overview]
Message-ID: <20171101112541.2069bbbc@vento.lan> (raw)
In-Reply-To: <baa710bc-375b-e306-674c-e6ecc6b1d0f5@linaro.org>
Em Wed, 1 Nov 2017 15:09:36 +0200
Todor Tomov <todor.tomov@linaro.org> escreveu:
> On 1.11.2017 15:03, Mauro Carvalho Chehab wrote:
> > Hi Todor,
> >
> > Em Wed, 1 Nov 2017 14:38:02 +0200
> > Todor Tomov <todor.tomov@linaro.org> escreveu:
> >
> >> Hi Mauro,
> >>
> >> Thank you for pointing to this.
> >>
> >> On 1.11.2017 14:16, Mauro Carvalho Chehab wrote:
> >>> if output->wm_num is bigger than 1, the value for reg is
> >> If output->wn_num equals 2, we handle all cases (i == 0, i == 1) and set reg properly.
> >> If output->wn_num is bigger than 2, then reg will not be initialized. However this is something that "cannot happen" and because of this the case is not handled.
> >>
> >> So I think that there is nothing wrong really but we have to do something to remove the warning. I agree with your patch, it is technically not a right value for reg but any cases in which wm_num is bigger than 2 are not supported anyway and should not happen.
> >
> > Thanks for your promptly answer. Well, if i is always at the [0..1] range,
> > then I guess the enclosed patch is actually better.
>
> I don't think that there is a lot of difference practically. If this one fixes the warning too, then it is fine for me. Thank you for working on this.
Yes, it fixes the warning. I guess the main advantage of version 2 is
that, if it would ever be possible to have more than 2 outputs, it
should be clearer that the logic at break need changes.
So, if ok for you, I'll stick with version 2. It would be great if
you could give your ack on that.
Regards,
Mauro
next prev parent reply other threads:[~2017-11-01 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 12:16 [PATCH] [RFC] media: camss-vfe: always initialize reg at vfe_set_xbar_cfg() Mauro Carvalho Chehab
2017-11-01 12:38 ` Todor Tomov
2017-11-01 13:03 ` Mauro Carvalho Chehab
2017-11-01 13:09 ` Todor Tomov
2017-11-01 13:25 ` Mauro Carvalho Chehab [this message]
2017-11-01 13:35 ` Todor Tomov
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=20171101112541.2069bbbc@vento.lan \
--to=mchehab@s-opensource.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=todor.tomov@linaro.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