From: Lukasz Majewski <lukma@denx.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Enrico Weigelt <info@metux.net>,
Kate Stewart <kstewart@linuxfoundation.org>,
linux-input@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v5 0/3] mfd: mc13xxx: Fixes and enhancements for NXP's mc34708
Date: Mon, 30 Sep 2019 09:51:59 +0200 [thread overview]
Message-ID: <20190930095159.64e1001a@jawa> (raw)
In-Reply-To: <20190909214440.30674-1-lukma@denx.de>
[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]
Dear Lee,
> This patch set provides several enhancements to mc13xxx MFD family
> of devices by introducing mc34708 as a separate device.
>
> This IC has dedicated pen detection feature, which allows better
> touchscreen experience.
>
> This is the fifth version of this code (v5).
> Discussion regarding previous versions can be found here:
> https://lkml.org/lkml/2018/4/12/351
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1661934.html
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1664296.html
> https://lkml.org/lkml/2019/7/17/705
Gentle ping on this patch series. It is now 3 weeks without any reply...
>
> Sascha Hauer (3):
> mfd: mc13xxx: Add mc34708 adc support
> input: touchscreen mc13xxx: Make platform data optional
> input: touchscreen mc13xxx: Add mc34708 support
>
> drivers/input/touchscreen/mc13783_ts.c | 63 ++++++++++++++---
> drivers/mfd/mc13xxx-core.c | 98
> +++++++++++++++++++++++++- include/linux/mfd/mc34708.h |
> 37 ++++++++++ 3 files changed, 185 insertions(+), 13 deletions(-)
> create mode 100644 include/linux/mfd/mc34708.h
>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-09-30 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 21:44 [PATCH v5 0/3] mfd: mc13xxx: Fixes and enhancements for NXP's mc34708 Lukasz Majewski
2019-09-09 21:44 ` [PATCH v5 1/3] mfd: mc13xxx: Add mc34708 adc support Lukasz Majewski
2019-10-04 13:58 ` Lee Jones
2019-10-04 13:58 ` Lee Jones
2019-09-09 21:44 ` [PATCH v5 2/3] input: touchscreen mc13xxx: Make platform data optional Lukasz Majewski
2019-09-09 21:44 ` [PATCH v5 3/3] input: touchscreen mc13xxx: Add mc34708 support Lukasz Majewski
2019-09-30 7:51 ` Lukasz Majewski [this message]
2019-09-30 7:51 ` [PATCH v5 0/3] mfd: mc13xxx: Fixes and enhancements for NXP's mc34708 Lukasz Majewski
2019-09-30 8:21 ` Greg Kroah-Hartman
2019-09-30 8:21 ` Greg Kroah-Hartman
2019-10-01 6:41 ` Lee Jones
2019-10-01 6:41 ` Lee Jones
2019-10-01 8:19 ` Lukasz Majewski
2019-10-01 8:19 ` Lukasz Majewski
2019-10-04 14:07 ` Lee Jones
2019-10-04 14:07 ` Lee Jones
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=20190930095159.64e1001a@jawa \
--to=lukma@denx.de \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=kstewart@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).