From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Hans de Goede <johannes.goede@oss.qualcomm.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Daniel Scally" <dan.scally@ideasonboard.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Antti Laakso" <antti.laakso@linux.intel.com>,
"Alexander Patrakov" <patrakov@gmail.com>,
"Leif Skunberg" <diamondback@cohunt.app>,
"Sahan Nissanka" <adee.sahan@gmail.com>,
linux-media@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 3/5] platform/x86: int3472: Add support for DOVDD and DVDD GPIO types
Date: Mon, 19 Oct 2026 12:01:40 +0300 [thread overview]
Message-ID: <atXcdApv8uR0E8Kq@ashevche-desk.local> (raw)
In-Reply-To: <20261016141716.130220-4-johannes.goede@oss.qualcomm.com>
On Fri, Oct 16, 2026 at 04:17:14PM +0200, Hans de Goede wrote:
> Add defines for INT3472_GPIO_TYPE_DOVDD (type 0x0f) and
> INT3472_GPIO_TYPE_DVDD (type 0x11) and map them to regulators with
> matching names.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-19 9:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 14:17 [PATCH 0/5] platform/x86: int3472: Fix AVDD and add DOVDD + DVDD mappings Hans de Goede
2026-10-16 14:17 ` [PATCH 1/5] media: ov05c10: Support full range of power rails Hans de Goede
2026-10-17 7:20 ` Andy Shevchenko
2026-10-19 10:27 ` Dan Scally
2026-10-16 14:17 ` [PATCH 2/5] platform/x86: int3472: Rename DOVDD GPIO type to AVDD Hans de Goede
2026-10-19 7:32 ` Andy Shevchenko
2026-10-19 10:54 ` Dan Scally
2026-10-16 14:17 ` [PATCH 3/5] platform/x86: int3472: Add support for DOVDD and DVDD GPIO types Hans de Goede
2026-10-19 9:01 ` Andy Shevchenko [this message]
2026-10-19 11:02 ` Dan Scally
2026-10-16 14:17 ` [PATCH 4/5] platform/x86: int3472: Rename avdd_second_sensor to power_enable_second_sensor Hans de Goede
2026-10-19 10:52 ` Andy Shevchenko
2026-10-19 10:54 ` Dan Scally
2026-10-16 14:17 ` [PATCH 5/5] platform/x86: int3472: Properly map the AVDD GPIO type to a "avdd" regulator Hans de Goede
2026-10-19 11:01 ` Andy Shevchenko
2026-10-19 11:02 ` Dan Scally
2026-10-20 1:41 ` [PATCH 0/5] platform/x86: int3472: Fix AVDD and add DOVDD + DVDD mappings Alexander Patrakov
2026-10-20 1:49 ` [PATCH 1/3] media: ipu-bridge: Add sensor configuration for OV5675 (OVTI5678) Alexander Patrakov
2026-10-20 1:50 ` [PATCH 2/3] media: i2c: ov5675: Defer the probe until the endpoint exists Alexander Patrakov
2026-10-20 6:34 ` Andy Shevchenko
2026-10-20 8:39 ` Sakari Ailus
2026-10-20 1:50 ` [PATCH 3/3] media: i2c: ov5675: Add the OVTI5678 RGB-IR variant Alexander Patrakov
2026-10-20 6:42 ` Andy Shevchenko
2026-10-20 6:46 ` Alexander Patrakov
2026-10-20 8:42 ` Sakari Ailus
2026-10-20 8:57 ` Andy Shevchenko
2026-10-20 12:13 ` Uwe Kleine-König
2026-10-21 5:57 ` Andy Shevchenko
2026-10-21 7:57 ` Uwe Kleine-König
2026-10-20 6:07 ` [PATCH 1/3] media: ipu-bridge: Add sensor configuration for OV5675 (OVTI5678) Andy Shevchenko
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=atXcdApv8uR0E8Kq@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=adee.sahan@gmail.com \
--cc=andy@kernel.org \
--cc=antti.laakso@linux.intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=diamondback@cohunt.app \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-media@vger.kernel.org \
--cc=patrakov@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sakari.ailus@linux.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