All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Julian Calaby <julian.calaby@gmail.com>
Cc: Janakiram Sistla <janakiram.sistla@gmail.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch 0/1] Adding radio type FM
Date: Fri, 13 Nov 2009 04:41:46 +0100	[thread overview]
Message-ID: <1258083706.7715.16.camel@violet> (raw)
In-Reply-To: <646765f40911121929p5aa416c3o99f33bd5b5d8c5cb@mail.gmail.com>

Hi Julian,

please stop CCing majordomo@vger.kernel.org since that one is not a
mailing list.

> <janakiram.sistla@gmail.com> wrote:
> > Resending with added comments from John.
> > From 1b1493392faeb6702ff364447b135e481930b397 Mon Sep 17 00:00:00 2001
> > From: Janakiram Sistla <janakiram.sistla@gmail.com>
> > Date: Fri, 13 Nov 2009 08:16:26 +0530
> > Subject: [PATCH 1/1] Adding radio type FM
> >
> > Adding radio type FM in RFKILL_TYPE_.FM also belongs to
> > same class of with both TX/RX capability.
> > Also Added input type for the above same.
> >
> > Signed-off-by: Janakiram Sistla <janakiram.sistla@gmail.com>
> > ---
> >  include/linux/input.h  |    1 +
> >  include/linux/rfkill.h |    1 +
> >  net/rfkill/core.c      |    2 ++
> >  net/rfkill/input.c     |    9 +++++++++
> >  4 files changed, 13 insertions(+), 0 deletions(-)
> >
> > diff --git a/include/linux/input.h b/include/linux/input.h
> > index 0ccfc30..f03ae90 100644
> > --- a/include/linux/input.h
> > +++ b/include/linux/input.h
> > @@ -376,6 +376,7 @@ struct input_absinfo {
> >  #define KEY_DISPLAY_OFF                245     /* display device to off state */
> >
> >  #define KEY_WIMAX              246
> > +#define KEY_FM                 247
> >
> >  /* Range 248 - 255 is reserved for special needs of AT keyboard driver */
> >
> > diff --git a/include/linux/rfkill.h b/include/linux/rfkill.h
> > index 3392c59..03f5598 100644
> > --- a/include/linux/rfkill.h
> > +++ b/include/linux/rfkill.h
> > @@ -45,6 +45,7 @@ enum rfkill_type {
> >        RFKILL_TYPE_WIMAX,
> >        RFKILL_TYPE_WWAN,
> >        RFKILL_TYPE_GPS,
> > +       RFKILL_TYPE_FM,
> >        NUM_RFKILL_TYPES,
> >  };
> >
> > diff --git a/net/rfkill/core.c b/net/rfkill/core.c
> > index ba2efb9..b8ac206 100644
> > --- a/net/rfkill/core.c
> > +++ b/net/rfkill/core.c
> > @@ -592,6 +592,8 @@ static const char *rfkill_get_type_str(enum
> > rfkill_type type)
> >                return "wwan";
> >        case RFKILL_TYPE_GPS:
> >                return "gps";
> > +       case RRFKILL_TYPE_FM:
> > +               return "fm";
> >        default:
> >                BUG();
> >        }
> > diff --git a/net/rfkill/input.c b/net/rfkill/input.c
> > index a7295ad..f51b16d 100644
> > --- a/net/rfkill/input.c
> > +++ b/net/rfkill/input.c
> > @@ -212,6 +212,9 @@ static void rfkill_event(struct input_handle
> > *handle, unsigned int type,
> >                case KEY_WIMAX:
> >                        rfkill_schedule_toggle(RFKILL_TYPE_WIMAX);
> >                        break;
> > +               case KEY_FM:
> > +                       rfkill_schedule_toggle(RFKILL_TYPE_FM);
> > +                       break;
> >                }
> >        } else if (type == EV_SW && code == SW_RFKILL_ALL)
> >                rfkill_schedule_evsw_rfkillall(data);
> > @@ -290,6 +293,12 @@ static const struct input_device_id rfkill_ids[] = {
> >                .keybit = { [BIT_WORD(KEY_UWB)] = BIT_MASK(KEY_UWB) },
> >        },
> >        {
> > +               .flags = INPUT_DEVICE_ID_MATCH_EVBIT |
> > +                               INPUT_DEVICE_ID_MATCH_KEYBIT,
> > +               .evbit = { BIT_MASK(EV_KEY) },
> > +               .keybit = { [BIT_WORD(KEY_FM)] = BIT_MASK(KEY_UWB) },
> 
> Surely both instances of KEY_UWB should be changed.

which makes it even more clearly that this code path has never been
tested. So lets leave this KEY_FM business out and just submit the
RFKILL additions.

You don't need to emulate a key event to use RFKILL anyway. The new
RFKILL subsystem supports /dev/rfkill and there is the rfkill userspace
utility. Which you wanna send a patch to extend it with FM support.

Regards

Marcel



  reply	other threads:[~2009-11-13  3:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  3:09 [patch 0/1] Adding radio type FM Janakiram Sistla
2009-11-13  3:09 ` John W. Linville
2009-11-13  3:25   ` Janakiram Sistla
2009-11-13  3:29     ` Julian Calaby
2009-11-13  3:41       ` Marcel Holtmann [this message]
2009-11-13  3:45         ` Julian Calaby
2009-11-13  5:19           ` Janakiram Sistla
2009-11-13  5:30             ` Marcel Holtmann
2009-11-13  3:22 ` Marcel Holtmann
2009-11-13  5:32   ` Janakiram Sistla
2009-11-13 18:19     ` Janakiram Sistla
2009-11-14 13:19   ` Janakiram Sistla
2009-11-14 16:34     ` Marcel Holtmann
2009-11-14 17:37       ` Janakiram Sistla
2009-11-14 18:05         ` Marcel Holtmann
2009-11-16  2:36           ` [PATCH 1/1] " Janakiram Sistla
2009-11-16  2:43             ` Marcel Holtmann
2009-11-16  4:25               ` Janakiram Sistla

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=1258083706.7715.16.camel@violet \
    --to=marcel@holtmann.org \
    --cc=janakiram.sistla@gmail.com \
    --cc=julian.calaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.