From: Nick Dyer <nick.dyer@itdev.co.uk>
To: Heiko Schocher <hs@denx.de>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Tomasz Figa <t.figa@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Henrik Rydberg <rydberg@euromail.se>,
linux-input@vger.kernel.org, Benson Leung <bleung@chromium.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [RFC PATCH] input, touch, atmel_mxt_ts: use atmel driver
Date: Wed, 11 Jun 2014 13:06:51 +0100 [thread overview]
Message-ID: <5398465B.7060101@itdev.co.uk> (raw)
In-Reply-To: <1402468526-9165-1-git-send-email-hs@denx.de>
Heiko Schocher wrote:
> try to bring the driver from
> https://github.com/ndyer/linux for-next
>
> to mainline. Post this as a RFC, to see if this is possible...
>
> based on:
> commit dda0a5570574cfe467c1c794cf7a17e1d742ec02 ("Input:
> atmel_mxt_ts - implement improved debug message interface")
>
> from Nick Dyer <nick.dyer@itdev.co.uk>
>
> added:
> - remove some (not all) checkpatch warnings
> - Add support for voltage regulator
> - Add support for Device Tree support
My thinking has been that the maintainers will more likely accept a series
of small patches than to make such a huge change to the entire driver, my
for-next tree is where I'm working on this, and I plan to post another set
of 15 patches soon, when I've fixed up some issues to do with probe/remove
cycles.
You should note that my for-next branch has moved on slightly since you
have taken this, because I have implemented device tree support and changed
the config download to use the request_firmware_async() function.
Your device tree stuff for mach-goni.c looks really useful, however - if
you can send me a patch for that against my current for-next branch I can
include it with my version of the device tree support.
all the best
Nick
WARNING: multiple messages have this Message-ID (diff)
From: nick.dyer@itdev.co.uk (Nick Dyer)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] input, touch, atmel_mxt_ts: use atmel driver
Date: Wed, 11 Jun 2014 13:06:51 +0100 [thread overview]
Message-ID: <5398465B.7060101@itdev.co.uk> (raw)
In-Reply-To: <1402468526-9165-1-git-send-email-hs@denx.de>
Heiko Schocher wrote:
> try to bring the driver from
> https://github.com/ndyer/linux for-next
>
> to mainline. Post this as a RFC, to see if this is possible...
>
> based on:
> commit dda0a5570574cfe467c1c794cf7a17e1d742ec02 ("Input:
> atmel_mxt_ts - implement improved debug message interface")
>
> from Nick Dyer <nick.dyer@itdev.co.uk>
>
> added:
> - remove some (not all) checkpatch warnings
> - Add support for voltage regulator
> - Add support for Device Tree support
My thinking has been that the maintainers will more likely accept a series
of small patches than to make such a huge change to the entire driver, my
for-next tree is where I'm working on this, and I plan to post another set
of 15 patches soon, when I've fixed up some issues to do with probe/remove
cycles.
You should note that my for-next branch has moved on slightly since you
have taken this, because I have implemented device tree support and changed
the config download to use the request_firmware_async() function.
Your device tree stuff for mach-goni.c looks really useful, however - if
you can send me a patch for that against my current for-next branch I can
include it with my version of the device tree support.
all the best
Nick
next prev parent reply other threads:[~2014-06-11 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 6:35 [RFC PATCH] input, touch, atmel_mxt_ts: use atmel driver Heiko Schocher
2014-06-11 6:35 ` Heiko Schocher
2014-06-11 12:06 ` Nick Dyer [this message]
2014-06-11 12:06 ` Nick Dyer
2014-06-11 12:15 ` Heiko Schocher
2014-06-11 12:15 ` Heiko Schocher
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=5398465B.7060101@itdev.co.uk \
--to=nick.dyer@itdev.co.uk \
--cc=bleung@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hs@denx.de \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=rydberg@euromail.se \
--cc=t.figa@samsung.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 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.