[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZEytf1WJa4JNJy6o3CBqOJAZLb-D=_rGQb+naH=TKmZA@mail.gmail.com>
Date: Sat, 5 Jun 2021 00:00:33 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Michael Walle <michael@...le.cc>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
Subject: Re: [PATCH] gpio: regmap: move drvdata to config data
On Fri, Jun 4, 2021 at 1:04 PM Michael Walle <michael@...le.cc> wrote:
> Drop gpio_regmap_set_drvdata() and instead add it to the configuration
> data passed to gpio_regmap_register().
>
> gpio_regmap_set_drvdata() can't really be used in a race free way. This
> is because the gpio_regmap object which is needed by _set_drvdata() is
> returned by gpio_regmap_register(). On the other hand, the callbacks
> which use the drvdata might already be called right after the
> gpiochip_add() call in gpio_regmap_register(). Therefore, we have to
> provide the drvdata early before we call gpiochip_add().
>
> Reported-by: Matti Vaittinen <matti.vaittinen@...rohmeurope.com>
> Signed-off-by: Michael Walle <michael@...le.cc>
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
> Btw, I'm not sure how to handle this "was part of another patch by another
> author" thing. Should I leave the Sob and just add mine?
Ideally just stack Sign-offs it is called the "delivery path".
Yours,
Linus Walleij
Powered by blists - more mailing lists