public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [GIT PULL] HVR-900 R2 and PCTV 330e DVB support
Date: Fri, 25 Mar 2011 12:50:24 -0300	[thread overview]
Message-ID: <4D8CB9C0.1000005@redhat.com> (raw)
In-Reply-To: <AANLkTi=hppcpARY1DOOJwK7kyKPe+2Q415jt8dNh8Z=-@mail.gmail.com>

Hi Devin,

Em 24-03-2011 14:05, Devin Heitmueller escreveu:
> This patch series finally merges in Ralph Metzler's drx-d driver and
> brings up the PCTV 330e and
> HVR-900R2.  The patches have been tested for quite some time by users
> on the Kernel Labs blog,
> and they have been quite happy with them.
> 
> The firmware required can be found here:
> 
> http://kernellabs.com/firmware/drxd/
> 
> The following changes since commit 41f3becb7bef489f9e8c35284dd88a1ff59b190c:
> 
>   [media] V4L DocBook: update V4L2 version (2011-03-11 18:09:02 -0300)
> 
> are available in the git repository at:
>   git://sol.kernellabs.com/dheitmueller/drx.git drxd
> 
> Devin Heitmueller (12):
>       drx: add initial drx-d driver
>       drxd: add driver to Makefile and Kconfig
>       drxd: provide ability to control rs byte
>       em28xx: enable support for the drx-d on the HVR-900 R2
>       drxd: provide ability to disable the i2c gate control function
>       em28xx: fix GPIO problem with HVR-900R2 getting out of sync with drx-d
>       em28xx: include model number for PCTV 330e
>       em28xx: add digital support for PCTV 330e
>       drxd: move firmware to binary blob
>       em28xx: remove "not validated" flag for PCTV 330e
>       em28xx: add remote control support for PCTV 330e
>       drxd: Run lindent across sources

Still lots of CodingStyle issues, but they could be easily cleaned by a few scripting.
I've cleaned them and added at my experimental tree:
	http://git.linuxtv.org/mchehab/experimental.git?a=shortlog;h=refs/heads/drxd

It compiles fine, and I don't think that any of the changes would break DRX-D, but, in
any case, it would be great if you could double check.

I noticed just one issue with the drxd driver: it is still using a semaphore instead
of a mutex:

+       struct semaphore mutex;
...
+static int HI_CfgCommand(struct drxd_state *state)
+{
+       int status = 0;
+
+       down(&state->mutex);

It should be doing:

	s/struct semaphore/struct mutex/
	s/down/mutex_lock/
	s/up/mutex_unlock/
	s/sema_init/mutex_init/

at the places it occur.

I've added a patch for it at the end of the series.

Could you please double check if everything is ok, for me to move this upstream?

Thanks!
Mauro

  parent reply	other threads:[~2011-03-25 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 17:05 [GIT PULL] HVR-900 R2 and PCTV 330e DVB support Devin Heitmueller
2011-03-24 17:34 ` Mauro Carvalho Chehab
2011-03-24 17:36   ` Devin Heitmueller
2011-03-25 15:50 ` Mauro Carvalho Chehab [this message]
     [not found]   ` <AANLkTimW+e8-YC=nFdiKYr=6TKYRozf8uAct21i5QHN0@mail.gmail.com>
2011-03-25 16:45     ` Mauro Carvalho Chehab
2011-04-02 10:43     ` Mauro Carvalho Chehab
2011-04-02 21:01       ` Devin Heitmueller
2011-04-02 22:47         ` Mauro Carvalho Chehab

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=4D8CB9C0.1000005@redhat.com \
    --to=mchehab@redhat.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