From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Eduard Gavin <egavinc@gmail.com>
Subject: Re: [PATCH] tvp5150: Fix breakage for serial usage
Date: Tue, 26 Jan 2016 19:06:22 +0200 [thread overview]
Message-ID: <1906458.x8tqLB8j7k@avalon> (raw)
In-Reply-To: <20160126070955.3dcef1d4@recife.lan>
Hi Mauro,
On Tuesday 26 January 2016 07:09:55 Mauro Carvalho Chehab wrote:
> Em Mon, 25 Jan 2016 18:01:21 -0200 Mauro Carvalho Chehab escreveu:
> > Em Mon, 25 Jan 2016 21:32:21 +0200 Laurent Pinchart escreveu:
> > > Hi Mauro,
> > >
> > > Let's see, I can't test em28xx, could you try remove the CONF_SHARED_PIN
> > > change and replacing the write in s_stream with a read-modify-write that
> > > disables the output (bits 3, 2 and 0) ? If that works I'll test it with
> > > the omap3 isp when I'll be back home.
> >
> > Didn't work. I'll do more tests later (or tomorrow).
>
> The root cause weren't at tvp5150 side, but, instead, at em28xx that
> were only calling s_stream() to disable the stream, but never enabling it.
>
> I'm wander why it was doing such thing. Well, s_stream() came years
> after the em28xx driver, so I suspect it was a hack to fix some issue
> with a particular device. Let's hope that the change won't cause any
> regressions on such hardware.
Let's blame history :-)
> The good news is that em28xx doesn't need MISC_CTL to be filled with
> 0x6f to stream. Just 0x09 is enough. So, the same initialization
> needed by OMAP3 will work there.
>
> I'm posting the patch in a few.
Great, thanks.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2016-01-26 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 16:44 [PATCH] tvp5150: Fix breakage for serial usage Mauro Carvalho Chehab
2016-01-25 16:50 ` Mauro Carvalho Chehab
2016-01-25 17:23 ` Laurent Pinchart
2016-01-25 17:35 ` Mauro Carvalho Chehab
2016-01-25 17:38 ` Laurent Pinchart
2016-01-25 18:13 ` Mauro Carvalho Chehab
2016-01-25 18:42 ` Laurent Pinchart
2016-01-25 19:07 ` Mauro Carvalho Chehab
2016-01-25 19:32 ` Laurent Pinchart
2016-01-25 20:01 ` Mauro Carvalho Chehab
2016-01-26 9:09 ` Mauro Carvalho Chehab
2016-01-26 17:06 ` Laurent Pinchart [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=1906458.x8tqLB8j7k@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=egavinc@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=hans.verkuil@cisco.com \
--cc=javier@osg.samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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