From: Joonyoung Shim <jy0922.shim@samsung.com>
To: dheitmueller@kernellabs.com,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [PATCH 07/24] xc5000: properly report i2c write failures
Date: Fri, 07 Feb 2014 17:59:24 +0900 [thread overview]
Message-ID: <52F4A06C.2050606@samsung.com> (raw)
Hi,
Sorry for response about the past post.
> The logic as written would *never* actually return an error condition, since
> the loop would run until the counter hit zero but the check was for a value
> less than zero.
>
> Signed-off-by: Devin Heitmueller <dheitmueller@kernellabs.com>
> ---
> drivers/media/common/tuners/xc5000.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
> diff --git a/drivers/media/common/tuners/xc5000.c b/drivers/media/common/tuners/xc5000.c
> index f660e33..a7fa17e 100644
> --- a/drivers/media/common/tuners/xc5000.c
> +++ b/drivers/media/common/tuners/xc5000.c
> @@ -341,7 +341,7 @@ static int xc_write_reg(struct xc5000_priv *priv, u16 regAddr, u16 i2cData)
> }
> }
> }
> - if (WatchDogTimer < 0)
> + if (WatchDogTimer <= 0)
I can't load firmware like error of below link.
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nonfree/+bug/1263837
<https://bugs.launchpad.net/ubuntu/+source/linux-firmware-nonfree/+bug/1263837>
This error is related with this patch. This fix is right but above error
is created after this fix
because my device makes WatchDogTimer to 0 when load firmware.
Maybe it will be related with XREG_BUSY register but i can't check it.
I removed this fix, but i have faced at other error with "xc5000: PLL
not running after fwload"
So i have commented like below.
static const struct xc5000_fw_cfg xc5000a_1_6_114 = {
.name = XC5000A_FIRMWARE,
.size = 12401,
//.pll_reg = 0x806c,
};
Then, xc5000 device works well.
I don't have xc5000 datasheet so i can't debug xc5000 driver anymore.
Any help?
Thanks.
> result = XC_RESULT_I2C_WRITE_FAILURE;
>
> return result;
>
next reply other threads:[~2014-02-07 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 8:59 Joonyoung Shim [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-07 2:46 [PATCH 00/24] Various HVR-950q and xc5000 fixes Devin Heitmueller
2012-08-07 2:46 ` [PATCH 07/24] xc5000: properly report i2c write failures Devin Heitmueller
[not found] ` <CAPLVkLv6JNvSdSFCY7YNRkmfzHv5+JD7Y5hxvjxdFtRT2JgE2A@mail.gmail.com>
2014-02-07 13:46 ` Devin Heitmueller
2014-02-10 8:25 ` Joonyoung Shim
2014-02-10 13:29 ` Devin Heitmueller
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=52F4A06C.2050606@samsung.com \
--to=jy0922.shim@samsung.com \
--cc=dheitmueller@kernellabs.com \
--cc=linux-media@vger.kernel.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