On 24-10-31 17:33:35, Johan Hovold wrote:
On Thu, Oct 31, 2024 at 06:13:45PM +0200, Abel Vesa wrote:
On 24-10-31 15:05:52, Johan Hovold wrote:
On Mon, Oct 21, 2024 at 09:23:24AM +0200, Johan Hovold wrote:
On Fri, Oct 18, 2024 at 03:49:34PM +0300, Abel Vesa wrote:
Cc: stable@vger.kernel.org # 6.8
I assume there are no existing devicetrees that need this since then we would have heard about it sooner. Do we still need to backport it?
None of the DTs I managed to scan seem to have this problem.
Maybe backporting it is not worth it then.
Thanks for confirming. Which (new) driver and DT are you seeing this with?
The Parade PS8830 retimer and its DT node. The v3 of that patchset will not trigger it unless the pinctrl properties are being added to the retimer node.
When exactly are you hitting this?
Here is one of the examples.
[ 5.768283] x1e80100-tlmm f100000.pinctrl: error -EINVAL: pin-185 (aux_bridge.aux_bridge.3) [ 5.768289] x1e80100-tlmm f100000.pinctrl: error -EINVAL: could not request pin 185 (GPIO_185) from group gpio185 on device f100000.pinctrl [ 5.768293] aux_bridge.aux_bridge aux_bridge.aux_bridge.3: Error applying setting, reverse things back
I meant with which driver and DT you hit this with.
Abel, even if Neil decided to give me the finger here, please answer the above so that it's recorded in the archives at least.
Sorry for not replying in time before the patch was merge.
That's not your fault.
Johan