[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAE-0n51NugMRXEruDdgpNBkBBowQ6NdZBGUrHs5sEBecrmd=Ww@mail.gmail.com>
Date: Mon, 25 Apr 2022 13:12:50 -0700
From: Stephen Boyd <swboyd@...omium.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: linux-kernel@...r.kernel.org, patches@...ts.linux.dev,
linux-input@...r.kernel.org, chrome-platform@...ts.linux.dev,
Benson Leung <bleung@...omium.org>,
Guenter Roeck <groeck@...omium.org>,
Douglas Anderson <dianders@...omium.org>,
Hsin-Yi Wang <hsinyi@...omium.org>
Subject: Re: [PATCH 1/2] Input: cros-ec-keyb: Only register keyboard if
rows/columns exist
Quoting Dmitry Torokhov (2022-04-24 20:47:03)
> >
> > + /*
> > + * No rows and columns? There isn't a matrix but maybe there are
> > + * switches to register in cros_ec_keyb_register_bs() because this is a
> > + * detachable device.
> > + */
> > + if (!device_property_read_bool(dev, "keypad,num-rows") &&
> > + !device_property_read_bool(dev, "keypad,num-cols"))
>
> Why are we abusing device_property_read_bool() for properties that are
> not flags instead of using device_property_present()?
>
Because I wrote this using DT APIs first and wasn't aware that
device_property_present() was a thing. I'll resend it with that API
usage.
Powered by blists - more mailing lists