From: thatslyude@gmail.com
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Damjan Georgievski <gdamjan@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Duggan <aduggan@synaptics.com>
Subject: Re: [PATCH 3/3] Input: synaptics-rmi4 - log when we create a guest serio port
Date: Fri, 19 Jan 2018 13:10:18 -0500 [thread overview]
Message-ID: <1516385418.2814.5.camel@gmail.com> (raw)
In-Reply-To: <20180119004955.247190-4-dmitry.torokhov@gmail.com>
Reviewed-by: Lyude Paul <lyude@redhat.com>
On Thu, 2018-01-18 at 16:49 -0800, Dmitry Torokhov wrote:
> To ease analyzing boot behavior from logs, let's log when we are about to
> register the pass-through serio port.
>
> Also, let's drop "Synaptics" prefix from the port name, as RMI4 is good
> enough indicator already, and having the prefix means that the name does
> not fit into serio->name field. While at it move from hard-coded seio->phys
> to one mentioning the sensor ID (such as "rmi4-00.fn03/serio0").
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
> drivers/input/rmi4/rmi_f03.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/input/rmi4/rmi_f03.c b/drivers/input/rmi4/rmi_f03.c
> index 7ccbb370a9a81..88822196d6b72 100644
> --- a/drivers/input/rmi4/rmi_f03.c
> +++ b/drivers/input/rmi4/rmi_f03.c
> @@ -184,14 +184,15 @@ static int rmi_f03_register_pt(struct f03_data *f03)
> serio->close = rmi_f03_pt_close;
> serio->port_data = f03;
>
> - strlcpy(serio->name, "Synaptics RMI4 PS/2 pass-through",
> - sizeof(serio->name));
> - strlcpy(serio->phys, "synaptics-rmi4-pt/serio1",
> - sizeof(serio->phys));
> + strlcpy(serio->name, "RMI4 PS/2 pass-through", sizeof(serio-
> >name));
> + snprintf(serio->phys, sizeof(serio->phys), "%s/serio0",
> + dev_name(&f03->fn->dev));
> serio->dev.parent = &f03->fn->dev;
>
> f03->serio = serio;
>
> + printk(KERN_INFO "serio: %s port at %s\n",
> + serio->name, dev_name(&f03->fn->dev));
> serio_register_port(serio);
>
> return 0;
prev parent reply other threads:[~2018-01-19 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 0:49 [PATCH 0/3] RMI4: improve trackpoint detection Dmitry Torokhov
2018-01-19 0:49 ` [PATCH 1/3] Input: synaptics_rmi4 - do not delete interrupt memory too early Dmitry Torokhov
2018-01-19 1:05 ` thatslyude
2018-01-19 0:49 ` [PATCH 2/3] Input: synaptics_rmi4 - unmask F03 interrupts when port is opened Dmitry Torokhov
2018-01-19 18:08 ` thatslyude
2018-01-19 0:49 ` [PATCH 3/3] Input: synaptics-rmi4 - log when we create a guest serio port Dmitry Torokhov
2018-01-19 18:10 ` thatslyude [this message]
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=1516385418.2814.5.camel@gmail.com \
--to=thatslyude@gmail.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gdamjan@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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