From: Jemma Denson <jdenson@gmail.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH v2] media: isl6421: add checks for current overflow
Date: Sat, 19 Aug 2017 12:44:09 +0100 [thread overview]
Message-ID: <870bb227-ec30-ddcd-11d5-db2bacd37fce@gmail.com> (raw)
In-Reply-To: <18c87cff-a407-8ebc-b758-eeb496f29345@gmail.com>
On 17/08/17 20:50, Jemma Denson wrote:
> On 16/08/17 10:42, Mauro Carvalho Chehab wrote:
>>> I've just tested both your v2 patch and changes I'm suggesting above; both work
>>> fine on my setup. Do you want me to send a v3?
>> Yeah, sure! I'm currently in travel, returning only on Friday, and I don't
>> have the hardware to test. So, if you can send it, I'd appreciate :-)
>> Cheers,
>> Mauro
> Ok, just sent. The if statements ended up being a bit complicated, but I added checking
> if the DCL bit was being overridden (it is by several cards under cx88), only pausing
> for a second if DCL was in use as the datasheet suggested that's only done in that mode,
> and also skipped checking overflow if the device was set to off.
> The latter should cover overflow somehow being picked up during attach and causing the
> attach to fail. Unlikely to happen but we shouldn't fail on what could be a transient
> issue.
Sorry, time for a v4! I wasn't happy with adding a permanent 200ms pause so I've reverted
that back to how you had it before. The pause before re-enabling dcl is only really needed
if it needs time to settle down and so reverting back to always doing a 1000ms on overload
should cover it.
Jemma.
next prev parent reply other threads:[~2017-08-19 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 12:10 [PATCH RFC] media: isl6421: add checks for current overflow Mauro Carvalho Chehab
2017-08-13 18:47 ` Jemma Denson
2017-08-13 19:35 ` [PATCH v2] " Mauro Carvalho Chehab
2017-08-15 19:51 ` Jemma Denson
2017-08-16 9:42 ` Mauro Carvalho Chehab
2017-08-17 19:50 ` Jemma Denson
2017-08-19 11:44 ` Jemma Denson [this message]
2017-08-13 19:40 ` [PATCH RFC] " Mauro Carvalho Chehab
2017-08-17 19:36 ` [PATCH v3] " Jemma Denson
2017-08-19 11:38 ` [PATCH v4] " Jemma Denson
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=870bb227-ec30-ddcd-11d5-db2bacd37fce@gmail.com \
--to=jdenson@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.com \
--cc=sakari.ailus@linux.intel.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: link
Be 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.