[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VcmuVcA_heURNh96zBDtpeNvx0t9buDOxnWNoea2G1uDg@mail.gmail.com>
Date: Mon, 1 Aug 2022 11:29:04 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Hans de Goede <hdegoede@...hat.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Lee Jones <lee.jones@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lee Jones <lee@...nel.org>, Andy Shevchenko <andy@...nel.org>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>
Subject: Re: [PATCH v2 01/10] mfd: intel_soc_pmic: Fix an error handling path
in intel_soc_pmic_i2c_probe()
On Mon, Aug 1, 2022 at 11:14 AM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Mon, Aug 1, 2022 at 10:43 AM Hans de Goede <hdegoede@...hat.com> wrote:
> > On 7/31/22 22:12, Andy Shevchenko wrote:
...
> > > err_del_irq_chip:
> > > + pwm_remove_table(crc_pwm_lookup, ARRAY_SIZE(crc_pwm_lookup));
> > > regmap_del_irq_chip(pmic->irq, pmic->irq_chip_data);
> > > return ret;
> >
> > Note alternatively we could just move the pwm_add_table() to just before the "return 0",
> > there is no strict ordering between adding the mfd devices and the pwm_add_table()
> > (the pwm device only becomes available after the pwm-driver has bound to the mfd
> > instantiated platform device which happens later).
Just to be sure... How is it guaranteed that that happens later?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists