From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Nick Dyer <nick@shmanahar.org>
Cc: Chris Healy <cphealy@gmail.com>,
Andrew Duggan <aduggan@synaptics.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH v3 1/2] Input: synaptics-rmi4 - add sysfs attribute update_fw_status
Date: Tue, 31 Jan 2017 15:43:01 -0800 [thread overview]
Message-ID: <20170131234301.GA37992@dtor-ws> (raw)
In-Reply-To: <20170131090257.GG8311@dtor-ws>
On Tue, Jan 31, 2017 at 01:02:57AM -0800, Dmitry Torokhov wrote:
> On Sat, Jan 28, 2017 at 07:06:01PM +0000, Nick Dyer wrote:
> > The attribute returns the percentage complete. If the firmware update fails, it
> > reports a negative error code.
> >
> > Signed-off-by: Nick Dyer <nick@shmanahar.org>
> > Tested-by: Chris Healy <cphealy@gmail.com>
> > Acked-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
>
> Applied, thank you.
>
> > ---
> > drivers/input/rmi4/rmi_f34.c | 40 +++++++++++++++++++++++++++++++++++++++-
> > drivers/input/rmi4/rmi_f34.h | 4 ++++
> > drivers/input/rmi4/rmi_f34v7.c | 11 +++++++++++
> > 3 files changed, 54 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/input/rmi4/rmi_f34.c b/drivers/input/rmi4/rmi_f34.c
> > index c3285ce..048e593 100644
> > --- a/drivers/input/rmi4/rmi_f34.c
> > +++ b/drivers/input/rmi4/rmi_f34.c
> > @@ -157,6 +157,9 @@ static int rmi_f34_write_blocks(struct f34_data *f34, const void *data,
> > i + 1, block_count);
> >
> > data += f34->v5.block_size;
> > + f34->update_progress += f34->v5.block_size;
> > + f34->update_status = (f34->update_progress * 100) /
> > + f34->update_size;
> > }
> >
> > return 0;
> > @@ -186,6 +189,8 @@ static int rmi_f34_flash_firmware(struct f34_data *f34,
> > struct rmi_function *fn = f34->fn;
> > int ret;
> >
> > + f34->update_progress = 0;
> > + f34->update_size = syn_fw->image_size + syn_fw->config_size;
By the way, this breaks on big endian boxes. I fixed it up locally.
Please try incorporating 'sparse' into your workflow.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2017-01-31 23:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-28 19:06 [PATCH v3 0/2] Synaptics RMI4 sysfs attributes Nick Dyer
2017-01-28 19:06 ` [PATCH v3 1/2] Input: synaptics-rmi4 - add sysfs attribute update_fw_status Nick Dyer
2017-01-31 9:02 ` Dmitry Torokhov
2017-01-31 23:43 ` Dmitry Torokhov [this message]
2017-01-28 19:06 ` [PATCH v3 2/2] Input: synaptics-rmi4 - add sysfs interfaces for hardware IDs Nick Dyer
2017-01-31 9:02 ` Dmitry Torokhov
2017-01-31 21:17 ` [PATCH v4] " Nick Dyer
2017-01-31 23:51 ` Dmitry Torokhov
2017-01-30 10:08 ` [PATCH v3 0/2] Synaptics RMI4 sysfs attributes Benjamin Tissoires
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=20170131234301.GA37992@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=cphealy@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=nick@shmanahar.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.