From: Anthony Kim <Anthony.Kim@hideep.com>
To: "'Dmitry Torokhov'" <dmitry.torokhov@gmail.com>
Cc: "'robh+dt@kernel.org'" <robh+dt@kernel.org>,
"'linux-input@vger.kernel.org'" <linux-input@vger.kernel.org>,
"'devicetree@vger.kernel.org'" <devicetree@vger.kernel.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
Dennis Hong <Dennis.Hong@hideep.com>
Subject: RE: [PATCH v2 resend 0/1] Input: add support HiDeep touchscreen.
Date: Mon, 6 Nov 2017 04:00:02 +0000 [thread overview]
Message-ID: <93AED97F53D7B941873C33A3FA30928855B9DA@mbox02.hideep.com> (raw)
In-Reply-To: <20171104003552.ve2elx6s4azzyd6q@dtor-ws>
Hi Dmitry,
Thanks for your mention.
>Hi Anthony,
>On Tue, Oct 31, 2017 at 07:17:56PM +0900, Anthony Kim wrote:
>> Hi,
>>
>> I remake patch to base on dmitry's modified code.
>> Please refer as follow.
>> http://www.spinics.net/lists/linux-input/msg53724.html
>>
>> That code is working well almost, but needed to some modified.
>>
>> - v2
>> - Our fw binary data is little endian, but our IC protocol
>> for fw update use big endian. So it need to convert to big endian data
>> and I added about it.
>I understand that _currently_ your firmware binary is little endian, however it is easily remedied on your side. I do not understand why you would want to encumber the kernel running on many devices to do that conversion on fly.
As your mention, I will don't convert to another endian again. I didn't know whether it affected. Just I hoped our IC work well.
And I will test again using big endian binary. If there need to modify, I will send modified patch.
Thanks!
>Thanks.
>--
>Dmitry
prev parent reply other threads:[~2017-11-06 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 10:17 Anthony Kim
2017-10-31 10:17 ` [PATCH v2 resend 1/1] Input: add support for " Anthony Kim
2017-11-04 0:35 ` [PATCH v2 resend 0/1] Input: add support " Dmitry Torokhov
2017-11-06 4:00 ` Anthony Kim [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=93AED97F53D7B941873C33A3FA30928855B9DA@mbox02.hideep.com \
--to=anthony.kim@hideep.com \
--cc=Dennis.Hong@hideep.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®