public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Dmitry Rokosov <DDRokosov@sberdevices.ru>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
	"noname.nuno@gmail.com" <noname.nuno@gmail.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	kernel <kernel@sberdevices.ru>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v1] iio: trigger: move trig->owner init to trigger allocate() stage
Date: Sat, 4 Jun 2022 14:59:55 +0100	[thread overview]
Message-ID: <20220604145955.2a1108ca@jic23-huawei> (raw)
In-Reply-To: <20220601174837.20292-1-ddrokosov@sberdevices.ru>

On Wed, 1 Jun 2022 17:48:32 +0000
Dmitry Rokosov <DDRokosov@sberdevices.ru> wrote:

> To provide a new IIO trigger to the IIO core, usually driver executes the
> following pipeline: allocate()/register()/get(). Before, IIO core assigned
> trig->owner as a pointer to the module which registered this trigger at
> the register() stage. But actually the trigger object is owned by the
> module earlier, on the allocate() stage, when trigger object is
> successfully allocated for the driver.
> 
> This patch moves trig->owner initialization from register()
> stage of trigger initialization pipeline to allocate() stage to
> eliminate all misunderstandings and time gaps between trigger object
> creation and owner acquiring.
> 
> Signed-off-by: Dmitry Rokosov <ddrokosov@sberdevices.ru>

Hi Dmitry,

I 'think' this is fine, but its in the high risk category that I'd like
to keep it on list for a few weeks before applying.

Note I'm still keen that in general we keep the flow such that
we do allocate()/register()/get() as there is no guarantee that the get()
will never do anything that requires the trigger to be registered, even
though that is true today.  Which is another way of saying I'm still
keen we fix up any cases that sneak in after your fix up set dealt with
the current ones.

Thanks for following up on this!

Jonathan


  reply	other threads:[~2022-06-04 13:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 17:48 [RFC PATCH v1] iio: trigger: move trig->owner init to trigger allocate() stage Dmitry Rokosov
2022-06-04 13:59 ` Jonathan Cameron [this message]
2022-06-06 11:37   ` Dmitry Rokosov
2022-06-06 15:13     ` Jonathan Cameron
2022-07-01 11:59   ` Dmitry Rokosov
2022-07-13 16:04     ` Jonathan Cameron
2022-07-16 15:25       ` Jonathan Cameron
2022-07-18 11:23         ` Dmitry Rokosov
2022-07-18 17:32           ` Jonathan Cameron
2022-07-19  9:11             ` Dmitry Rokosov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220604145955.2a1108ca@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=DDRokosov@sberdevices.ru \
    --cc=andy.shevchenko@gmail.com \
    --cc=kernel@sberdevices.ru \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noname.nuno@gmail.com \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox