[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250210195230.490904-1-andriy.shevchenko@linux.intel.com>
Date: Mon, 10 Feb 2025 21:44:49 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org,
platform-driver-x86@...r.kernel.org
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Andy Shevchenko <andy@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Hans de Goede <hdegoede@...hat.com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Alexis GUILLEMET <alexis.guillemet@...asys.com>
Subject: [PATCH v1 0/2] pinctrl: intel: Fix PWM initialisation
It appears that PWM instantiated from pinctrl-intel is configured
to a wrong flow. This mini-series to fix the issue. Note, patch 1
is comprehensive documentation paragraph to explain what the difference
in the programming flow and what the SoCs are affected.
The issue had been reported privately, hence no Closes tag.
I haven't added the Tested-by, so to make sure that it (still) works
I ask Alexis to give the formal Tag here in a response to the series.
The idea is to route this via pin control tree as there are already two patches
against PWM handling in pinctrl-intel. There is no need to backport that, it's
optional, because it wasn't worked from day 1, and hence no Cc: stable@.
Cc: Alexis GUILLEMET<alexis.guillemet@...asys.com>
Andy Shevchenko (2):
pwm: lpss: Clarify the bypass member semantics in struct
pwm_lpss_boardinfo
pinctrl: intel: Fix wrong bypass assignment in
intel_pinctrl_probe_pwm()
drivers/pinctrl/intel/pinctrl-intel.c | 1 -
include/linux/platform_data/x86/pwm-lpss.h | 33 ++++++++++++++++++++--
2 files changed, 30 insertions(+), 4 deletions(-)
--
2.45.1.3035.g276e886db78b
Powered by blists - more mailing lists