X86 platform drivers
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Alex Hung <alex.hung@canonical.com>,
	Platform Driver <platform-driver-x86@vger.kernel.org>,
	pali@f23x64.localdomain
Subject: Re: [PATCH][V2] intel-hid: support 5 array button
Date: Wed, 8 Feb 2017 18:22:38 -0800	[thread overview]
Message-ID: <20170209022238.GB185952@localhost.localdomain> (raw)
In-Reply-To: <CAHp75Vf3_WVGWKo18RikCJMtF9xgYSHem_wK4vTjXQn1WJvJCA@mail.gmail.com>

On Sat, Feb 04, 2017 at 04:58:33PM +0200, Andy Shevchenko wrote:
> On Sat, Feb 4, 2017 at 3:14 AM, Darren Hart <dvhart@infradead.org> wrote:
> > On Thu, Jan 26, 2017 at 03:33:01PM +0800, Alex Hung wrote:
> >> New firmwares include a feature called 5 button array that supports
> >> super key, volume up/down, rotation lock and power button. Especially,
> >> support for this feature is required to fix power button on some recent
> >> systems.
> 
> >> +static int intel_button_array_input_setup(struct platform_device *device)
> >> +{
> >> +     struct intel_hid_priv *priv = dev_get_drvdata(&device->dev);
> >> +     int ret;
> >> +
> >> +     /* Setup input device for 5 button array */
> >> +     priv->array = input_allocate_device();
> >> +     if (!priv->array)
> >> +             return -ENOMEM;
> >> +
> >> +     ret = sparse_keymap_setup(priv->array, intel_array_keymap, NULL);
> >> +     if (ret)
> >> +             goto err_free_array_device;
> >> +
> >> +     priv->array->dev.parent = &device->dev;
> >> +     priv->array->name = "Intel HID 5 button array";
> >> +     priv->array->id.bustype = BUS_HOST;
> >> +
> >> +     ret = input_register_device(priv->array);
> >> +     if (ret)
> >> +             goto err_free_array_device;
> >> +
> >> +     return 0;
> >> +
> >> +err_free_array_device:
> >> +     input_free_device(priv->array);
> >> +     return ret;
> >
> > This return path is more complex than it could be, since you test for ret before
> > return anyway:
> >
> >  out:
> >  if (ret)
> >          input_free_device(priv->array);
> >  return ret;
> >
> > There is no need for a second return point that I can see. Same for the
> > hid_input_setup function. We can remove 8 lines.
> 
> Darren, if I didn't miss anything the function is purely used in
> ->probe() path and thus devm_ version of input_allocate_device() would
> make this error path gone.

Hi Andy,

These are optional input devices for the driver, so if I understand the
semantics of devm_ correctly, the input device would remain allocated until such
time as the driver is unloaded or if it fails to bind - which for systems with
intel-hid, but no 5 button array, the unused input device would remain allocated
until system shutdown.

Alex, is that correct?

-- 
Darren Hart
Intel Open Source Technology Center

  reply	other threads:[~2017-02-09  2:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  7:33 [PATCH][V2] intel-hid: support 5 array button Alex Hung
2017-01-27 14:16 ` Michał Kępień
2017-02-04  1:14 ` Darren Hart
2017-02-04  1:26   ` Darren Hart
2017-02-04 16:06     ` Pali Rohár
2017-02-08  7:21       ` Michał Kępień
2017-02-08  8:17         ` Pali Rohár
2017-02-08  9:05           ` Alex Hung
2017-02-08  9:07             ` Pali Rohár
2017-02-04 14:58   ` Andy Shevchenko
2017-02-09  2:22     ` Darren Hart [this message]
2017-02-09  3:09       ` Alex Hung
2017-02-09 19:56         ` Andy Shevchenko
2017-02-17  2:43           ` Darren Hart
2017-02-08  8:54   ` Alex Hung
2017-02-13 11:43     ` Michał Kępień
2017-02-13 23:23       ` Andy Shevchenko
2017-02-14  0:06         ` Alex Hung

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=20170209022238.GB185952@localhost.localdomain \
    --to=dvhart@infradead.org \
    --cc=alex.hung@canonical.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=pali@f23x64.localdomain \
    --cc=platform-driver-x86@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