On Thu, May 16, 2019 at 11:13:09PM +0200, Wolfram Sang wrote:
> From: Heiner Kallweit
>
> i2c_new_dummy is typically called from the probe function of the
> driver for the primary i2c client. It requires calls to
> i2c_unregister_device in the error path of the probe function and
> in the remove
czw., 16 maj 2019 o 23:13 Wolfram Sang
napisał(a):
>
> From: Heiner Kallweit
>
> i2c_new_dummy is typically called from the probe function of the
> driver for the primary i2c client. It requires calls to
> i2c_unregister_device in the error path of the probe function and
> in the remove function.
Hi Wolfram,
On 16/05/2019 22:13, Wolfram Sang wrote:
> From: Heiner Kallweit
>
> i2c_new_dummy is typically called from the probe function of the
> driver for the primary i2c client. It requires calls to
> i2c_unregister_device in the error path of the probe function and
> in the remove function
On 2019-05-16 23:13, Wolfram Sang wrote:
> From: Heiner Kallweit
>
> i2c_new_dummy is typically called from the probe function of the
> driver for the primary i2c client. It requires calls to
> i2c_unregister_device in the error path of the probe function and
> in the remove function.
> This can
From: Heiner Kallweit
i2c_new_dummy is typically called from the probe function of the
driver for the primary i2c client. It requires calls to
i2c_unregister_device in the error path of the probe function and
in the remove function.
This can be simplified by introducing a device-managed version.
