lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 12 Sep 2012 16:16:53 +0300
From:	Ferruh Yigit <fery@...ress.com>
To:	Henrik Rydberg <rydberg@...omail.se>
CC:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Kevin McNeely <kev@...ress.com>,
	Javier Martinez Canillas <javier@...hile0.org>,
	Shawn Landden <shawnlandden@...il.com>,
	Ashish Jangam <ashish.jangam@...tcummins.com>,
	Olivier Sobrie <olivier@...rie.be>,
	"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] Input: cyttsp4 - bus driver for Cypress TMA4XX touchscreen
 devices

On 08/27/2012 08:46 AM, Ferruh Yigit wrote:
> On 08/24/2012 08:34 PM, Henrik Rydberg wrote:
>> Hi Ferruh,
>>
>> As Javier mentioned, there is already a framework for the Cypress
>> devices in the kernel. Please make sure your patches build on what is
>> already there. Until then, I have nothing further to add.
>>
>> Thanks,
>> Henrik
>
> Hi Henrik,
>
> Thank you for your response.
>
> We now understand the requirement for our driver and we will submit a
> new patchset as soon as possible.
>
> Best Regards,
> ferruh
>

Hello Henrik,

After Javier's and your comment, we started an effort to update driver
and re-structured it similar to the existing Gen3 driver. We are close
to submit a patch-set for updated code, but this effort showed that this
new patch-set also won't be an incremental commit to existing driver but
will have to introduce new files.

Existing driver in the kernel is for Cypress Gen3 devices and it is not
a framework to cover Gen4 devices, Gen4 devices has different host
interface.

This re-structure made driver simpler with cost of removing some
features like ttsp bus or merging modular layers that work with
subscription mechanism into one file with direct function calls.
The concern here for our side is, the next generation touchscreen
controllers may cause similar problem with this Gen3 structure while
adding support to Linux kernel for them.

Before finalizing the work, we want to learn if introducing new files
for new driver is acceptable and our effort is inline with your request,
can you please comment on it?

Thanks and Regards,
ferruh

This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ