linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>
Cc: lee@kernel.org, giometti@enneenne.com,
	gregkh@linuxfoundation.org, raymond.tan@intel.com,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] mfd: intel_ehl_pse_gpio: Introduce Intel Elkhart Lake PSE GPIO and TIO
Date: Mon, 3 Mar 2025 10:24:43 +0200	[thread overview]
Message-ID: <Z8VnSyH_DBuJpW2o@smile.fi.intel.com> (raw)
In-Reply-To: <20250303044745.268964-2-raag.jadav@intel.com>

On Mon, Mar 03, 2025 at 10:17:41AM +0530, Raag Jadav wrote:
> Intel Elkhart Lake Programmable Service Engine (PSE) includes two PCI
> devices that expose two different capabilities of GPIO and Timed I/O
> as a single PCI function through shared MMIO.

...

> +INTEL GPIO MFD DRIVER

This also needs to be more precise and follow the name. We have more Intel GPIO
drivers, and MFD doesn't ring any bell about the platform or so. Are you going
to support all of them (existing and comining)?

> +M:	Raag Jadav <raag.jadav@intel.com>
> +S:	Supported
> +F:	drivers/mfd/intel_ehl_pse_gpio.c

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-03-03  8:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03  4:47 [PATCH v2 0/5] Introduce Intel Elkhart Lake PSE TIO Raag Jadav
2025-03-03  4:47 ` [PATCH v2 1/5] mfd: intel_ehl_pse_gpio: Introduce Intel Elkhart Lake PSE GPIO and TIO Raag Jadav
2025-03-03  8:24   ` Andy Shevchenko [this message]
2025-03-03 11:39     ` Raag Jadav
2025-03-03 11:45       ` Andy Shevchenko
2025-03-03 12:14         ` Raag Jadav
2025-03-03 12:22           ` Andy Shevchenko
2025-03-03 12:47             ` Raag Jadav
2025-03-03 13:20               ` Andy Shevchenko
2025-03-04  5:25                 ` Raag Jadav
2025-03-04 11:33                   ` Andy Shevchenko
2025-03-03  4:47 ` [PATCH v2 2/5] gpio: elkhartlake: depend on MFD_INTEL_EHL_PSE_GPIO Raag Jadav
2025-03-03  8:21   ` Andy Shevchenko
2025-03-03 11:38     ` Raag Jadav
2025-03-03 11:44       ` Andy Shevchenko
2025-03-03 12:13         ` Raag Jadav
2025-03-03 12:21           ` Andy Shevchenko
2025-03-03 12:46             ` Raag Jadav
2025-03-03 13:19               ` Andy Shevchenko
2025-03-03 14:01                 ` Raag Jadav
2025-03-03 14:20                   ` Andy Shevchenko
2025-03-04  5:22                     ` Raag Jadav
2025-03-04 11:31                       ` Andy Shevchenko
2025-03-04 14:24                   ` Andy Shevchenko
2025-03-03  4:47 ` [PATCH v2 3/5] pps: generators: tio: split pps_gen_tio.h Raag Jadav
2025-03-03  4:47 ` [PATCH v2 4/5] pps: generators: tio: move to match_data() model Raag Jadav
2025-03-03  4:47 ` [PATCH v2 5/5] pps: generators: tio: Introduce Intel Elkhart Lake PSE TIO Raag Jadav

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=Z8VnSyH_DBuJpW2o@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=giometti@enneenne.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=raag.jadav@intel.com \
    --cc=raymond.tan@intel.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).