On Tue, Nov 15, 2022 at 12:18:00PM +0100, Marijn Suijten wrote: > On 2022-11-14 16:15:25, Brian Masney wrote: > > On Fri, Nov 11, 2022 at 12:37:32PM +0100, Thierry Reding wrote: > > > From: Thierry Reding <treding@xxxxxxxxxx> > > > > > > The OF node store in chip->fwnode is used to explicitly override the FW > > > node for a GPIO chip. For chips that use the default FW node (i.e. that > > > of their parent device), this will be NULL and cause the chip not to be > > > fully registered. > > > > > > Instead, use the GPIO device's FW node, which is set to either the node > > > of the parent device or the explicit override in chip->fwnode. > > > > > > Fixes: 8afe82550240 ("gpiolib: of: Prepare of_gpiochip_add() / of_gpiochip_remove() for fwnode") > > > Tested-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> > > > Signed-off-by: Thierry Reding <treding@xxxxxxxxxx> > > > > Reviewed-by: Brian Masney <bmasney@xxxxxxxxxx> > > Tested-by: Brian Masney <bmasney@xxxxxxxxxx> > > > > I separately sent a similar type of patch to fix the same issue today: > > https://lore.kernel.org/linux-arm-msm/20221114202943.2389489-1-bmasney@xxxxxxxxxx/T/#u > > For completeness, your linked patch fixes a synchronous external abort > on multiple Qualcomm platforms pointed out in [1]. This patch however > does not, are you sure they fix the exact same issue? > > [1]: https://lore.kernel.org/linux-arm-msm/20221115110800.35gl3j43lmbxm3jb@xxxxxxxxxxxxxx/ Thierry's patch fixes the issue that I encountered in of_gpiochip_match_node_and_xlate() on the Qualcomm sa8540p automotive board. I don't get the stack dump that you encountered. I am having issues with probe deferrals on UFS when trying to acquire the reset-gpio. The patch I posted feels hacky (hence the RFC) but if the maintainers agree with it then I can clean up the commit message and post a v2. Brian