public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Stephen Boyd <swboyd@chromium.org>
Cc: benjamin.tissoires@redhat.com, Jiri Kosina <jikos@kernel.org>,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
	Sean O'Brien <seobrien@chromium.org>,
	Douglas Anderson <dianders@chromium.org>,
	Zhengqiao Xia <xiazhengqiao@huaqin.corp-partner.google.com>
Subject: Re: [PATCH v3 1/4] Input: Extract ChromeOS vivaldi physmap show function
Date: Tue, 15 Feb 2022 21:36:09 -0800	[thread overview]
Message-ID: <YgyNScQJNVjJpqEc@google.com> (raw)
In-Reply-To: <20220211012510.1198155-2-swboyd@chromium.org>

On Thu, Feb 10, 2022 at 05:25:07PM -0800, Stephen Boyd wrote:
> Let's introduce a common library file for the physmap show function
> duplicated between three different keyboard drivers. This largely copies
> the code from cros_ec_keyb.c which has the most recent version of the
> show function, while using the vivaldi_data struct from the hid-vivaldi
> driver. This saves a small amount of space in an allyesconfig build.
> 
> $ ./scripts/bloat-o-meter vmlinux.before vmlinux.after
> 
> add/remove: 3/0 grow/shrink: 2/3 up/down: 412/-720 (-308)
> Function                                     old     new   delta
> vivaldi_function_row_physmap_show              -     292    +292
> _sub_I_65535_1                           1057564 1057616     +52
> _sub_D_65535_0                           1057564 1057616     +52
> e843419@49f2_00062737_9b04                     -       8      +8
> e843419@20f6_0002a34d_35bc                     -       8      +8
> atkbd_parse_fwnode_data                      480     472      -8
> atkbd_do_show_function_row_physmap           316      76    -240
> function_row_physmap_show                    620     148    -472
> Total: Before=285581925, After=285581617, chg -0.00%
> 
> Cc: Jiri Kosina <jikos@kernel.org>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: "Sean O'Brien" <seobrien@chromium.org>
> Cc: Douglas Anderson <dianders@chromium.org>
> Cc: Zhengqiao Xia <xiazhengqiao@huaqin.corp-partner.google.com>
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
>  drivers/hid/Kconfig                   |  1 +
>  drivers/hid/hid-vivaldi.c             | 27 +++++--------------
>  drivers/input/Kconfig                 |  7 +++++
>  drivers/input/Makefile                |  1 +
>  drivers/input/keyboard/Kconfig        |  2 ++
>  drivers/input/keyboard/atkbd.c        | 22 +++++----------
>  drivers/input/keyboard/cros_ec_keyb.c | 32 ++++++++--------------
>  drivers/input/vivaldi-keymap.c        | 39 +++++++++++++++++++++++++++
>  include/linux/input/vivaldi-keymap.h  | 28 +++++++++++++++++++

Since you called the config INPUT_VIVALDIFMAP I think we should call
these files vivaldi-fmap.(h|c) as well. They are not really keymaps.

Anyway, this makes sense to me. Jiri, Benjamin, do you want to merge
this or do you want to take it all throgh your tree?

Thanks.

-- 
Dmitry

  parent reply	other threads:[~2022-02-16  5:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  1:25 [PATCH v3 0/4] Input/HID: Consolidate ChromeOS Vivaldi keyboard logic Stephen Boyd
2022-02-11  1:25 ` [PATCH v3 1/4] Input: Extract ChromeOS vivaldi physmap show function Stephen Boyd
     [not found]   ` <CAOOzhkpDvR14-D9YcZzbAQdQkDmas_XUtV-CLBR7+a3AuxgstQ@mail.gmail.com>
2022-02-16  2:09     ` Stephen Boyd
2022-02-16 16:25       ` Sean O'Brien
2022-02-16  5:36   ` Dmitry Torokhov [this message]
2022-02-16 15:44     ` Jiri Kosina
2022-02-16 19:05     ` Stephen Boyd
2022-02-11  1:25 ` [PATCH v3 2/4] HID: Extract vivaldi hid feature mapping for use in hid-hammer Stephen Boyd
2022-02-11  1:25 ` [PATCH v3 3/4] HID: google: Add support for vivaldi to hid-hammer Stephen Boyd
2022-02-11  1:25 ` [PATCH v3 4/4] HID: google: modify HID device groups of eel Stephen Boyd

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=YgyNScQJNVjJpqEc@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=dianders@chromium.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seobrien@chromium.org \
    --cc=swboyd@chromium.org \
    --cc=xiazhengqiao@huaqin.corp-partner.google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox