From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Danny Kukawka <danny.kukawka@bisect.de>
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] fix NULL pointer dereference in DSS2 VENC sysfs debug attr on OMAP4
Date: Wed, 25 Jan 2012 12:49:53 +0200 [thread overview]
Message-ID: <1327488593.1858.22.camel@deskari> (raw)
In-Reply-To: <1327419882-13578-1-git-send-email-danny.kukawka@bisect.de>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
On Tue, 2012-01-24 at 16:44 +0100, Danny Kukawka wrote:
> Commit ba02fa37de80bea10d706f39f076dd848348320a disabled the
> venc driver registration on OMAP4. Since the driver never gets
> probed/initialised your get a dereferenceed NULL pointer if you
> try to get info from /sys/kernel/debug/omapdss/venc
>
> Return info message about disabled venc if venc_dump_regs() gets called.
>
> Signed-off-by: Danny Kukawka <danny.kukawka@bisect.de>
> ---
> drivers/video/omap2/dss/venc.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/video/omap2/dss/venc.c b/drivers/video/omap2/dss/venc.c
> index b3e9f90..82865be 100644
> --- a/drivers/video/omap2/dss/venc.c
> +++ b/drivers/video/omap2/dss/venc.c
> @@ -699,6 +699,11 @@ void venc_dump_regs(struct seq_file *s)
> {
> #define DUMPREG(r) seq_printf(s, "%-35s %08x\n", #r, venc_read_reg(r))
>
> + if (cpu_is_omap44xx()) {
> + seq_printf(s, "VENC currently disabled on OMAP44xx\n");
> + return;
> + }
> +
> if (venc_runtime_get())
> return;
>
Thanks. A bit hacky, but so is the whole omap4/venc problem. I'll apply
to dss tree.
Tomi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-25 10:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 15:44 [PATCH] fix NULL pointer dereference in DSS2 VENC sysfs debug attr on OMAP4 Danny Kukawka
2012-01-25 10:49 ` Tomi Valkeinen [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=1327488593.1858.22.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=danny.kukawka@bisect.de \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@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