From: Nick Dyer <nick@shmanahar.org>
To: Cameron Gutman <aicommander@gmail.com>
Cc: Andrew Duggan <aduggan@synaptics.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Thorsten Leemhuis <linux@leemhuis.info>,
Jiri Kosina <jikos@kernel.org>,
cheiny@synaptics.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Synaptics RMI4 touchpad regression in 4.11-rc1
Date: Tue, 14 Mar 2017 19:53:38 +0000 [thread overview]
Message-ID: <20170314195338.GA12169@bm.shmanahar.org> (raw)
In-Reply-To: <03d8e6ac-1ba4-36a6-cc07-0c07e61f754f@gmail.com>
On Mon, Mar 13, 2017 at 10:10:22PM -0700, Cameron Gutman wrote:
> >>>>> Compared to hid-multitouch, the RMI stack seems to have
> >>>>> completely broken palm rejection and introduced some random
> >>>>> jumpiness during fine pointing motions. I don't know if these
> >>>>> issues are caused by the above errors or are a separate issue.
> >
> > The error about the bootloader version not being recognized just
> > means that updating the firmware is not supported on this touchpad.
> > It is only the F34 firmware update functionality which is failing to
> > load. The palm rejection and jumps are not related to this error.
> >
>
> Maybe that code path should be changed to not make as much noise when
> it runs on known unsupported hardware. Something like the attached
> patch?
> ---
> diff --git a/drivers/input/rmi4/rmi_f34v7.c b/drivers/input/rmi4/rmi_f34v7.c
> index 56c6c39..1291d9a 100644
> --- a/drivers/input/rmi4/rmi_f34v7.c
> +++ b/drivers/input/rmi4/rmi_f34v7.c
> @@ -1369,9 +1369,9 @@ int rmi_f34v7_probe(struct f34_data *f34)
> } else if (f34->bootloader_id[1] == 7) {
> f34->bl_version = 7;
> } else {
> - dev_err(&f34->fn->dev, "%s: Unrecognized bootloader version\n",
> - __func__);
> - return -EINVAL;
> + dev_info(&f34->fn->dev, "%s: Unsupported bootloader version: %u\n",
> + __func__, f34->bootloader_id[1]);
> + return -ENODEV;
> }
>
> memset(&f34->v7.blkcount, 0x00, sizeof(f34->v7.blkcount));
I'm afraid I'm responsible for this. I agree it's very unlikely to be
related to your other issues.
One approach to suppress the extra output would be to turn off
CONFIG_RMI_F34. I think your proposed change in wording would be fine,
though.
cheers
Nick
next prev parent reply other threads:[~2017-03-14 20:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 1:55 Synaptics RMI4 touchpad regression in 4.11-rc1 Cameron Gutman
2017-03-12 2:10 ` Cameron Gutman
2017-03-13 9:11 ` Thorsten Leemhuis
2017-03-13 13:13 ` Benjamin Tissoires
2017-03-13 13:15 ` Benjamin Tissoires
2017-03-14 1:35 ` Andrew Duggan
2017-03-14 5:10 ` Cameron Gutman
2017-03-14 8:14 ` Thorsten Leemhuis
2017-03-15 1:20 ` Andrew Duggan
2017-03-14 19:53 ` Nick Dyer [this message]
2017-03-15 1:19 ` Andrew Duggan
2017-03-17 16:57 ` Benjamin Tissoires
2017-03-17 19:23 ` Andrew Duggan
2017-03-20 5:00 ` Peter Hutterer
2017-03-29 1:50 ` Andrew Duggan
2017-03-29 6:03 ` Peter Hutterer
2017-03-29 8:50 ` Benjamin Tissoires
2017-03-30 0:23 ` Andrew Duggan
2017-03-31 8:57 ` Benjamin Tissoires
2017-03-31 22:23 ` Andrew Duggan
2017-11-20 14:03 ` Mantas Mikulėnas
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=20170314195338.GA12169@bm.shmanahar.org \
--to=nick@shmanahar.org \
--cc=aduggan@synaptics.com \
--cc=aicommander@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=cheiny@synaptics.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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;
as well as URLs for NNTP newsgroup(s).