All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Patrice Chotard <patrice.chotard@st.com>
Cc: Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	linus.walleij@linaro.org, gnurou@gmail.com,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Stefan Agner <stefan@agner.ch>, Lucas Stach <dev@lynxeye.de>,
	thierry.reding@gmail.com
Subject: Re: [PATCH 0/8] STMPE fixes/rework and add STMPE1600 support
Date: Wed, 20 Apr 2016 10:02:59 -0600	[thread overview]
Message-ID: <5717A833.3020304@wwwdotorg.org> (raw)
In-Reply-To: <5717325F.6080808@st.com>

On 04/20/2016 01:40 AM, Patrice Chotard wrote:
> On 04/19/2016 05:53 PM, Stephen Warren wrote:
>> On 04/19/2016 06:18 AM, patrice.chotard@st.com wrote:
>>> From: Patrice Chotard <patrice.chotard@st.com>
>>>
>>> This series cleans and fixes some bugs in MFD/GPIO STMPE drivers and
>>> prepare
>>>   the ground to add new STMPE1600 support.
>>>
>>> STMPE1600 datasheet is available here :
>>> http://www2.st.com/content/st_com/en/products/interfaces-and-transceivers/
>>>
>>> i-o-expanders-and-level-translators/i-o-expanders/stmpe1600.html
>>>
>>> Only STMPE1600 has been tested on STM32 platform. As i have no board
>>> with
>>> others STMPE
>>> variant(STMPE610/STMPE801/STMPE811/STMPE1601/STMPE1801/STMPE2401
>>> and STMPE2403), i put in CC boards's maintainers which are using
>>> others STMPE variant.
>>>
>>> If they can kindly check that no regression has been introduce by
>>> this series
>>
>>> For TEGRA ARCHITECTURE SUPPORT
>>>     _ Stephen Warren <swarren@wwwdotorg.org>
>>>     _ Thierry Reding <thierry.reding@gmail.com>
>>>     _ Alexandre Courbot <gnurou@gmail.com>
>>
>> I don't know what STMPE is, and I don't believe it is used on Tegra;
>> what makes you think it is?
...
> I put you in copy as STMPE811 is used on tegra30-apalis and
> tegra30-colibri platforms.

Ah. You'd best contact the individual board owners, since those are 
3rd-party Tegra boards and I don't believe anyone at NVIDIA has them to 
test with etc. I added likely candidates to Cc and dropped all the 
individuals unrelated to Tegra to keep the CC list low.

WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] STMPE fixes/rework and add STMPE1600 support
Date: Wed, 20 Apr 2016 10:02:59 -0600	[thread overview]
Message-ID: <5717A833.3020304@wwwdotorg.org> (raw)
In-Reply-To: <5717325F.6080808@st.com>

On 04/20/2016 01:40 AM, Patrice Chotard wrote:
> On 04/19/2016 05:53 PM, Stephen Warren wrote:
>> On 04/19/2016 06:18 AM, patrice.chotard at st.com wrote:
>>> From: Patrice Chotard <patrice.chotard@st.com>
>>>
>>> This series cleans and fixes some bugs in MFD/GPIO STMPE drivers and
>>> prepare
>>>   the ground to add new STMPE1600 support.
>>>
>>> STMPE1600 datasheet is available here :
>>> http://www2.st.com/content/st_com/en/products/interfaces-and-transceivers/
>>>
>>> i-o-expanders-and-level-translators/i-o-expanders/stmpe1600.html
>>>
>>> Only STMPE1600 has been tested on STM32 platform. As i have no board
>>> with
>>> others STMPE
>>> variant(STMPE610/STMPE801/STMPE811/STMPE1601/STMPE1801/STMPE2401
>>> and STMPE2403), i put in CC boards's maintainers which are using
>>> others STMPE variant.
>>>
>>> If they can kindly check that no regression has been introduce by
>>> this series
>>
>>> For TEGRA ARCHITECTURE SUPPORT
>>>     _ Stephen Warren <swarren@wwwdotorg.org>
>>>     _ Thierry Reding <thierry.reding@gmail.com>
>>>     _ Alexandre Courbot <gnurou@gmail.com>
>>
>> I don't know what STMPE is, and I don't believe it is used on Tegra;
>> what makes you think it is?
...
> I put you in copy as STMPE811 is used on tegra30-apalis and
> tegra30-colibri platforms.

Ah. You'd best contact the individual board owners, since those are 
3rd-party Tegra boards and I don't believe anyone at NVIDIA has them to 
test with etc. I added likely candidates to Cc and dropped all the 
individuals unrelated to Tegra to keep the CC list low.

  reply	other threads:[~2016-04-20 16:02 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 12:18 [PATCH 0/8] STMPE fixes/rework and add STMPE1600 support patrice.chotard
2016-04-19 12:18 ` patrice.chotard
2016-04-19 12:18 ` patrice.chotard at st.com
2016-04-19 12:18 ` [PATCH 1/8] mfd: stmpe: Add STMPE_IDX_SYS_CTRL/2 enum patrice.chotard
2016-04-19 12:18   ` patrice.chotard
2016-04-19 12:18   ` patrice.chotard at st.com
2016-04-20 14:32   ` Linus Walleij
2016-04-20 14:32     ` Linus Walleij
2016-04-26  8:19   ` Lee Jones
2016-04-26  8:19     ` Lee Jones
2016-04-26  8:19     ` Lee Jones
2016-04-19 12:18 ` [PATCH 2/8] mfd: stmpe: Add reset support for all STMPE variant patrice.chotard
2016-04-19 12:18   ` patrice.chotard
2016-04-19 12:18   ` patrice.chotard at st.com
2016-04-20 14:34   ` Linus Walleij
2016-04-20 14:34     ` Linus Walleij
2016-04-26  8:18   ` Lee Jones
2016-04-26  8:18     ` Lee Jones
2016-04-26  8:18     ` Lee Jones
2016-04-19 12:18 ` [PATCH 3/8] gpio: stmpe: fix edge and rising/falling edge detection patrice.chotard
2016-04-19 12:18   ` patrice.chotard
2016-04-19 12:18   ` patrice.chotard at st.com
2016-04-19 12:38   ` kbuild test robot
2016-04-19 12:38     ` kbuild test robot
2016-04-19 12:38     ` kbuild test robot
2016-04-20 14:37   ` Linus Walleij
2016-04-20 14:37     ` Linus Walleij
2016-04-21 13:48     ` Patrice Chotard
2016-04-21 13:48       ` Patrice Chotard
2016-04-21 13:48       ` Patrice Chotard
2016-04-19 12:18 ` [PATCH 4/8] gpio: stmpe: write int status register only when needed patrice.chotard
2016-04-19 12:18   ` patrice.chotard
2016-04-19 12:18   ` patrice.chotard at st.com
2016-04-20 14:38   ` Linus Walleij
2016-04-20 14:38     ` Linus Walleij
2016-04-19 12:18 ` [PATCH 5/8] Documentation: dt: add stmpe1600 compatible string to stmpe mfd patrice.chotard
2016-04-19 12:18   ` patrice.chotard
2016-04-19 12:18   ` patrice.chotard at st.com
2016-04-20 14:39   ` Linus Walleij
2016-04-20 14:39     ` Linus Walleij
2016-04-19 12:18 ` [PATCH 6/8] mfd: Add STMPE1600 support patrice.chotard
2016-04-19 12:18   ` patrice.chotard
2016-04-19 12:18   ` patrice.chotard at st.com
2016-04-20 14:43   ` Linus Walleij
2016-04-20 14:43     ` Linus Walleij
2016-04-21 13:51     ` Patrice Chotard
2016-04-21 13:51       ` Patrice Chotard
2016-04-21 13:51       ` Patrice Chotard
2016-04-19 12:18 ` [PATCH 7/8] gpio: stmpe: " patrice.chotard
2016-04-19 12:18   ` patrice.chotard
2016-04-19 12:18   ` patrice.chotard at st.com
2016-04-20 14:53   ` Linus Walleij
2016-04-20 14:53     ` Linus Walleij
2016-04-22  7:17     ` Patrice Chotard
2016-04-22  7:17       ` Patrice Chotard
2016-04-22  7:17       ` Patrice Chotard
2016-04-19 12:18 ` [PATCH 8/8] gpio: stmpe: configure GPIO as output by default patrice.chotard
2016-04-19 12:18   ` patrice.chotard
2016-04-19 12:18   ` patrice.chotard at st.com
2016-04-20 14:56   ` Linus Walleij
2016-04-20 14:56     ` Linus Walleij
2016-04-19 12:41 ` [PATCH 0/8] STMPE fixes/rework and add STMPE1600 support Thierry Reding
2016-04-19 12:41   ` Thierry Reding
2016-04-20 16:15   ` Marcel Ziswiler
2016-04-20 16:15     ` Marcel Ziswiler
2016-04-20 16:15     ` Marcel Ziswiler
2016-04-19 15:53 ` Stephen Warren
2016-04-19 15:53   ` Stephen Warren
2016-04-20  7:40   ` Patrice Chotard
2016-04-20  7:40     ` Patrice Chotard
2016-04-20  7:40     ` Patrice Chotard
2016-04-20 16:02     ` Stephen Warren [this message]
2016-04-20 16:02       ` Stephen Warren
2016-04-21  2:39       ` Marcel Ziswiler
2016-04-21  2:39         ` Marcel Ziswiler
2016-04-21  2:39         ` Marcel Ziswiler
2016-04-20 14:25   ` Linus Walleij
2016-04-20 14:25     ` Linus Walleij

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=5717A833.3020304@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=dev@lynxeye.de \
    --cc=gnurou@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel.ziswiler@toradex.com \
    --cc=patrice.chotard@st.com \
    --cc=stefan@agner.ch \
    --cc=thierry.reding@gmail.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.