linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>,
	Matteo Martelli <matteomartelli3@gmail.com>,
	Liam Beguin <liambeguin@gmail.com>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH v4 6/6] iio: adc: Add Intel Dollar Cove TI PMIC ADC driver
Date: Sun, 31 Aug 2025 11:18:45 +0200	[thread overview]
Message-ID: <ac53c02d-45d5-4ca8-9a2c-15a097e627a0@kernel.org> (raw)
In-Reply-To: <CAHp75VcozYvcAbWZ6Yvudzu6jj39fNbGD-8T=F=v+6QxEGxiKA@mail.gmail.com>

Hi Andy,

On 11-Aug-25 9:52 PM, Andy Shevchenko wrote:
> On Mon, Aug 11, 2025 at 5:55 PM Hans de Goede <hansg@kernel.org> wrote:
>>
>> Intel has 2 completely different "Dollar Cove" PMICs for its Bay Trail /
>> Cherry Trail SoCs. One is made by X-Powers and is called the AXP288.
>> The AXP288's GPADC is already supported by the X-Powers AXP288 ADC driver.
>>
>> The other "Dollar Cove" PMIC is made by TI and does not have any clear TI
>> denomination, its MFD driver calls it the "Intel Dollar Cove TI PMIC".
>>
>> Add a driver for the Intel Dollar Cove TI PMIC's general purpose ADC,
>> binding to the "chtdc_ti_adc" MFD cell of the MFD driver.
>>
>> The "cht" in the cell name comes from Cherry Trail, but it turns out that
>> just like the AXP288 the Intel Dollar Cove TI PMIC is also used with both
>> Intel Bay Trail and Intel Cherry Trail SoCs, so this new ADC driver does
>> not include the cht part in its name.
>>
>> This is loosely based on kernel/drivers/iio/adc/iio_dc_ti_gpadc.c
>> from the Acer A1-840 Android kernel source-code archive named:
>> "App. Guide_Acer_20151221_A_A.zip"
>> which is distributed by Acer from the Acer A1-840 support page:
>> https://www.acer.com/us-en/support/product-support/A1-840/downloads

Thank you for the review. I've addressed all your remarks for v5.

...

>> +MODULE_AUTHOR("Ramakrishna Pallala <ramakrishna.pallala@intel.com>");
> 
> Wondering if the address is still alive. In this case perhaps even ask
> for SoB/Co-developed-by? Otherwise if you still wish to have this
> credit make it in the form of "First Last (Intel)".

Good point, I asked about co-maintaining and got a bounce so I'll replace
this with "First Last (Intel)".

Regards,

Hans



  reply	other threads:[~2025-08-31  9:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 15:54 [PATCH v4 0/6] iio: processed channel handling fixes + Intel Dollar Cove TI PMIC ADC driver Hans de Goede
2025-08-11 15:54 ` [PATCH v4 1/6] iio: consumers: Fix handling of negative channel scale in iio_convert_raw_to_processed() Hans de Goede
2025-08-11 19:19   ` Andy Shevchenko
2025-08-12 15:57     ` Jonathan Cameron
2025-08-11 15:54 ` [PATCH v4 2/6] iio: consumers: Fix offset handling " Hans de Goede
2025-08-11 15:54 ` [PATCH v4 3/6] iio: consumers: Add an iio_multiply_value() helper function Hans de Goede
2025-08-11 19:34   ` Andy Shevchenko
2025-08-12 16:00     ` Jonathan Cameron
2025-08-11 15:54 ` [PATCH v4 4/6] iio: Improve iio_read_channel_processed_scale() precision Hans de Goede
2025-08-14 20:33   ` David Lechner
2025-08-11 15:54 ` [PATCH v4 5/6] iio: test: Add kunit tests for iio_multiply_value() Hans de Goede
2025-08-11 19:38   ` Andy Shevchenko
2025-08-16 13:41   ` Jonathan Cameron
2025-08-11 15:54 ` [PATCH v4 6/6] iio: adc: Add Intel Dollar Cove TI PMIC ADC driver Hans de Goede
2025-08-11 19:52   ` Andy Shevchenko
2025-08-31  9:18     ` Hans de Goede [this message]
2025-08-11 19:53 ` [PATCH v4 0/6] iio: processed channel handling fixes + " Andy Shevchenko
2025-08-22 11:05 ` Hans de Goede

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=ac53c02d-45d5-4ca8-9a2c-15a097e627a0@kernel.org \
    --to=hansg@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=liambeguin@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=matteomartelli3@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 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).