devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Tomasz Figa <t.figa@samsung.com>
Cc: linux-input@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
	linux-samsung-soc@vger.kernel.org, jy0922.shim@samsung.com,
	kyungmin.park@samsung.com
Subject: Re: [PATCH 0/2] input: touchscreen: atmel_mxt_ts: Add Device Tree support
Date: Thu, 4 Apr 2013 10:30:40 -0700	[thread overview]
Message-ID: <20130404173040.GB12302@core.coreip.homeip.net> (raw)
In-Reply-To: <1365092066-31753-1-git-send-email-t.figa@samsung.com>

Hi Tomasz,

On Thu, Apr 04, 2013 at 06:14:24PM +0200, Tomasz Figa wrote:
> This series is an attempt to add Device Tree support to Atmel maXtouch
> touchscreen driver.
> 
> First patch adds support for VDD voltage regulator to get operating voltage
> using regulator API instead of a driver specific field in platform data.
> 
> Second patch implements Device Tree bindings for the driver and adds
> respective documentation.
> 
> Tested on Universal C210 board.

Please coordinate this effort with Nick Dyer <nick.dyer@itdev.co.uk>,
Daniel Kurtz <djkurtz@chromium.org> and Benson Leung <bleung@chromium.org>
as there is a big update to the atmel_mxt_ts in works and I would prefer
not to disturb it.

Thanks.

-- 
Dmitry

  parent reply	other threads:[~2013-04-04 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 16:14 [PATCH 0/2] input: touchscreen: atmel_mxt_ts: Add Device Tree support Tomasz Figa
2013-04-04 16:14 ` [PATCH 1/2] input: touchscreen: atmel_mxt_ts: Add support for voltage regulator Tomasz Figa
2013-04-04 16:14 ` [PATCH 2/2] input: touchscreen: atmel_mxt_ts: Add support for Device Tree Tomasz Figa
2013-04-04 17:30 ` Dmitry Torokhov [this message]
     [not found]   ` <20130404173040.GB12302-WlK9ik9hQGAhIp7JRqBPierSzoNAToWh@public.gmane.org>
2013-04-11 20:32     ` [PATCH 0/2] input: touchscreen: atmel_mxt_ts: Add Device Tree support Tomasz Figa

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=20130404173040.GB12302@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jy0922.shim@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --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 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).