public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: HoP <jpetrous@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] isl6421.c - added optional features: tone control and temporary diseqc overcurrent
Date: Sat, 31 Oct 2009 07:52:48 -0200	[thread overview]
Message-ID: <4AEC08F0.70205@redhat.com> (raw)
In-Reply-To: <846899810910241711s6fb5939fq3a693a92a2a76310@mail.gmail.com>

HoP escreveu:
> Hi,
>
> this is my first kernel patch, so all comments are welcome.
>   
First of all, please check all your patches with checkpatch, to be sure
that they don't have any CodingStyle troubles. There are some on your
patch (the better is to read README.patches for more info useful
for developers).
> Attached patch adds two optional (so, disabled by default
> and therefore could not break any compatibility) features:
>
> 1, tone_control=1
> When enabled, ISL6421 overrides frontend's tone control
> function (fe->ops.set_tone) by its own one.
>   
On your comments, the better is to describe why someone would need
to use such option. You should also add a quick hint about that at the
option description.
> 2, overcurrent_enable=1
> When enabled, overcurrent protection is disabled during
> sending diseqc command. Such option is usable when ISL6421
> catch overcurrent threshold and starts limiting output.
> Note: protection is disabled only during sending
> of diseqc command, until next set_tone() usage.
> What typically means only max up to few hundreds of ms.
> WARNING: overcurrent_enable=1 is dangerous
> and can damage your device. Use with care
> and only if you really know what you do.
>   
I'm not sure if it is a good idea to have this... Why/when someone would 
need this?

If we go ahead and add this one, you should add a notice about it at the 
parameter.
I would also print a big WARNING message at the dmesg if the module were 
loaded
with this option turned on.
> /Honza
>
> Signed-off-by: Jan Petrous <jpetrous@gmail.com>
> ---
>   


  reply	other threads:[~2009-10-31  9:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25  0:11 [PATCH] isl6421.c - added optional features: tone control and temporary diseqc overcurrent HoP
2009-10-31  9:52 ` Mauro Carvalho Chehab [this message]
2009-11-03 23:10   ` HoP
2009-11-04  0:37     ` hermann pitton
2009-11-04  7:20       ` HoP
2009-11-04  8:35         ` Ales Jurik
2009-11-04 11:24           ` 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=4AEC08F0.70205@redhat.com \
    --to=mchehab@redhat.com \
    --cc=jpetrous@gmail.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