public inbox for linux-input@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan McDowell <noodles@earth.li>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: linux-omap@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [RFC][PATCH] Add support for hook switch on ams-delta
Date: Thu, 4 Jun 2009 19:18:33 +0100	[thread overview]
Message-ID: <20090604181833.GG31770@earth.li> (raw)
In-Reply-To: <200906031103.21758.jkrzyszt@tis.icnet.pl>

On Wed, Jun 03, 2009 at 11:03:20AM +0200, Janusz Krzysztofik wrote:
> Wednesday 03 June 2009 00:04:33 Jonathan McDowell napisał(a):
> > I'm obviously too late as I've seen the "Applied" mail,
> 
> No problem, I'm glad to hear from you.
> 
> > but some 
> > comments:
> >
> > * I don't think SW_HEADPHONE_INSERT is appropriate. input guys, is it 
> >   not reasonable to have SW_PHONE_HOOK or similar?
> 
> I do share you point of view. However, I didn't want to start a discussion if 
> there is a need for another symbol or not before the patch got any 
> acceptance.
> 
> > * We assume the bootloader does the appropriate GPIO pin setup for us,
> >   so I don't think your omap_cfg_reg is required but it doesn't hurt in
> >   the unlikely event we ever replace the Amstrad PBL.
> 
> OK, let it stay there. Do you see a need for replaceing it with a new 
> ams_delta_hook_switch_init() function call that just calls omap_cfg_reg()?

I don't see a need for this; it's always present and not a lot of code
to have in the init function as it stands.

> > * The commented out code to include the GPIO status in sysfs shouldn't
> >   be included.
> 
> Yes, I put it there to get a feedback.
> 
> >   Does the input layer not provide a way to obtain the 
> >   state of the switch?
> 
> Yes, it does, with EVIOCGSW ioctl()[1]. I personally don't like this way of 
> getting the switch status and would rather see it available over sysfs. 
> However, input guys may have their own preferences and gpio-keys driver 
> belongs to them.
 
I think that's a discussion to have with the input guys rather than
putting a hack in the platform file then.

So really the only issue with the patch that remains is if it justifies
adding a new SW_PHONE_HOOK switch type?

J.

-- 
] http://www.earth.li/~noodles/ []  Purranoia: The fear that your cat  [
]  PGP/GPG Key @ the.earth.li   []         is up to something.         [
] via keyserver, web or email.  []                                     [
] RSA: 4096/2DA8B985            []                                     [
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-06-04 18:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 18:57 [RFC][PATCH] Add support for hook switch on ams-delta Janusz Krzysztofik
2009-06-02 22:04 ` Jonathan McDowell
2009-06-03  9:03   ` Janusz Krzysztofik
2009-06-04 18:18     ` Jonathan McDowell [this message]
2009-06-04 22:07       ` Janusz Krzysztofik
2010-03-29 13:46   ` Mark Brown
2010-03-29 13:48     ` Mark Brown

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=20090604181833.GG31770@earth.li \
    --to=noodles@earth.li \
    --cc=jkrzyszt@tis.icnet.pl \
    --cc=linux-input@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