From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: "Барт Гопник" <bart.gopnik@gmail.com>
Cc: Ezequiel Garcia <elezegarcia@gmail.com>,
Mike Thomas <rmthomas@sciolus.org>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: STK1160 Sharpness
Date: Mon, 17 Nov 2014 08:11:00 -0200 [thread overview]
Message-ID: <20141117081100.72908b15@recife.lan> (raw)
In-Reply-To: <CAL+AA1=Sbe3D4BmV-Pv7SEhUBQutFiYMQ-H=iUWuAsY5aiTEzA@mail.gmail.com>
Em Mon, 17 Nov 2014 12:51:46 +0300
Барт Гопник <bart.gopnik@gmail.com> escreveu:
> (Where) can I find the the full list of the (key) differences between
> SAA7113 and GM7113?
I've no idea. Perhaps you would need to get both datasheets and compare
them.
> If it is not hard to do it, can anybody please implement it?
The hardest part seems to graduate the sharpness levels, as sharpness
actually is split into 3 different controls.
Of course, one interested on doing that would need to have a device
with the needed chipsets and time/interest on doing that.
Adding control framework at stk1160 also requires some time. I can't
volunteer myself of doing that. I don't have any stk1160-based
devices.
> Unfortunately, I'm not very good with system drivers programming.
>
> I'm interesting only in sharpness control because the image quality
> (sharpness) during capture using CVBS input is bad (on my EasyCap
> device). If I use S-Video input, the quality (sharpness) is better.
Yeah, the saa7115 datasheet (freely available at NXP site) mentions that
sharpness control may be needed for some kinds of output.
> It is important to implement it, because the sharpness control
> implemented in hardware (not in software, post-processing filtering).
> Control of other parameters like gamma are also don't work, but I'm
> not sure that gamma control is hardware (not software) implemented
> (I'm not found any info about gamma in saa7113 datasheet).
Regards,
Mauro
prev parent reply other threads:[~2014-11-17 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAL+AA1ntfVxkaHhY8qNciBkHRw0SXOAzBJgV+A9Y7oYtbD38mQ@mail.gmail.com>
[not found] ` <CALF0-+VpPttePKF-VTLJ5Y29_EZtSz96PwN9av1SOkkc414CRA@mail.gmail.com>
[not found] ` <CAL+AA1nUAgOYUeWxrgeHiWaDSkHvh0yXuwA-gjdUomn-s_HVyA@mail.gmail.com>
2014-11-08 22:12 ` STK1160 Sharpness Ezequiel Garcia
2014-11-09 13:12 ` Mauro Carvalho Chehab
2014-11-10 7:53 ` Барт Гопник
2014-11-17 9:51 ` Барт Гопник
2014-11-17 10:11 ` Mauro Carvalho Chehab [this message]
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=20141117081100.72908b15@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=bart.gopnik@gmail.com \
--cc=elezegarcia@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=rmthomas@sciolus.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