From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "simba.hsu" <simba.hsu@raydium.corp-partner.google.com>
Cc: furquan@google.com, seanpaul@chromium.org, rrangel@chromium.org,
simba.hsu@rad-ic.com, jeffrey.lin@rad-ic.com, KP.li@rad-ic.com,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver: input: touchscreen: modify Raydium i2c touchscreen driver
Date: Thu, 15 Apr 2021 12:17:19 -0700 [thread overview]
Message-ID: <YHiRP+UvUlXfr0J6@google.com> (raw)
In-Reply-To: <20210415085829.1419147-1-simba.hsu@raydium.corp-partner.google.com>
HI,
On Thu, Apr 15, 2021 at 04:58:29PM +0800, simba.hsu wrote:
> This path makes auto-update available when IC's status is
> Recovery mode.
Could you please explain in more detail what the issue is. Also please
improve the patch subject, as "modify Raydium i2c touchscreen driver"
does not really convey the substance of the patch.
Also, the patch does not apply to my tree, was it based on some other
tree?
>
> Signed-off-by: simba.hsu@raydium.corp-partner.google.com
Please use your Raydium email for signoff.
> Change-Id: I5ae54896a201b949eba7514500a7e75574f5726b
No need to send change-id tags, they are not used in mainline kernel.
> ---
> drivers/input/touchscreen/raydium_i2c_ts.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/touchscreen/raydium_i2c_ts.c b/drivers/input/touchscreen/raydium_i2c_ts.c
> index 444479ef699e..a97403c55f75 100644
> --- a/drivers/input/touchscreen/raydium_i2c_ts.c
> +++ b/drivers/input/touchscreen/raydium_i2c_ts.c
> @@ -298,6 +298,7 @@ static int raydium_i2c_query_ts_BL_info(struct raydium_data *ts)
> 0x10, 0xc0, 0x01, 0x00, 0x04, 0x00};
> int error;
> u8 rbuf[5] = {0, 0, 0, 0, 0};
> + u32 tmpdata = 0;
>
> error = raydium_i2c_send(client,
> RM_CMD_BOOT_WRT, get_hwid, sizeof(get_hwid));
> @@ -315,7 +316,8 @@ static int raydium_i2c_query_ts_BL_info(struct raydium_data *ts)
> error = raydium_i2c_read(client,
> RM_CMD_BOOT_CHK, rbuf, sizeof(rbuf));
> if (!error) {
> - ts->info.hw_ver = cpu_to_le32(rbuf[1]<<24|rbuf[2]<<16|rbuf[3]<<8|rbuf[4]);
> + tmpdata = (rbuf[1]<<24|rbuf[2]<<16|rbuf[3]<<8|rbuf[4]);
> + ts->info.hw_ver = cpu_to_le32(tmpdata);
On the face of it I can't see why the code would behave differently,
nut then there is no raydium_i2c_query_ts_BL_info() in the copy of the
driver I have here.
> dev_err(&client->dev, "HWID %08X\n", ts->info.hw_ver);
> } else {
> ts->info.hw_ver = cpu_to_le32(0xffffffffUL);
> --
> 2.25.1
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2021-04-15 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 8:58 [PATCH] driver: input: touchscreen: modify Raydium i2c touchscreen driver simba.hsu
2021-04-15 16:05 ` Raul Rangel
2021-04-15 19:17 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-15 9:14 simba.hsu
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=YHiRP+UvUlXfr0J6@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=KP.li@rad-ic.com \
--cc=furquan@google.com \
--cc=jeffrey.lin@rad-ic.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rrangel@chromium.org \
--cc=seanpaul@chromium.org \
--cc=simba.hsu@rad-ic.com \
--cc=simba.hsu@raydium.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;
as well as URLs for NNTP newsgroup(s).