All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>
Cc: "Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
	"Rob Herring" <robh+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Wolfram Sang" <wsa@kernel.org>,
	"Matti Vaittinen" <Matti.Vaittinen@fi.rohmeurope.com>,
	"Mauro Carvalho Chehab" <mchehab@kernel.org>,
	"Peter Rosin" <peda@axentia.se>,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Mark Brown" <broonie@kernel.org>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Michael Tretter" <m.tretter@pengutronix.de>,
	"Shawn Tu" <shawnx.tu@intel.com>,
	"Hans Verkuil" <hverkuil@xs4all.nl>,
	"Mike Pagano" <mpagano@gentoo.org>,
	"Krzysztof Hałasa" <khalasa@piap.pl>,
	"Marek Vasut" <marex@denx.de>,
	"Luca Ceresoli" <luca@lucaceresoli.net>
Subject: Re: [PATCH v5 1/8] i2c: core: let adapters be notified of client attach/detach
Date: Mon, 19 Dec 2022 11:48:51 +0200	[thread overview]
Message-ID: <Y6Azg9GJ/ntUlS+P@smile.fi.intel.com> (raw)
In-Reply-To: <20221219095143.4b49b447@booty>

On Mon, Dec 19, 2022 at 09:51:43AM +0100, Luca Ceresoli wrote:
> On Sun, 11 Dec 2022 18:55:39 +0200
> Laurent Pinchart <laurent.pinchart@ideasonboard.com> wrote:
> > On Thu, Dec 08, 2022 at 12:39:59PM +0200, Tomi Valkeinen wrote:

...

> > This may be a stupid question, but couldn't you instead use the
> > BUS_NOTIFY_ADD_DEVICE and BUS_NOTIFY_DEL_DEVICE bus notifiers ?
> 
> I'm not sure they would be the correct tool for this task. Bus
> notifiers inform about new events on the 'struct bus_type, i.e. any
> event on the global i2c bus type. In the i2c world this means being
> notified about new _adapters_, which is exactly what
> drivers/i2c/i2c-dev.c does.
> 
> Here, however, we need to be informed about new _clients_ being added
> under a specific adapter.

This is for example exactly what ACPI integration in I2C framework does. But...

> I'm not sure whether the bus notifiers can
> inform about new clients in addition of new adapters, but they at least
> seem unable to provide per-adapter notification.

...personally I don't like notifiers, they looks like overkill for this task.

> Does that seem correct?

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-12-19  9:49 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 10:39 [PATCH v5 0/8] i2c-atr and FPDLink Tomi Valkeinen
2022-12-08 10:39 ` [PATCH v5 1/8] i2c: core: let adapters be notified of client attach/detach Tomi Valkeinen
2022-12-08 12:30   ` Andy Shevchenko
2022-12-08 16:10     ` Tomi Valkeinen
2022-12-11 16:55   ` Laurent Pinchart
2022-12-19  8:51     ` Luca Ceresoli
2022-12-19  9:48       ` Andy Shevchenko [this message]
2022-12-26 16:54         ` Laurent Pinchart
2022-12-27 20:07           ` Andy Shevchenko
2022-12-08 10:40 ` [PATCH v5 2/8] i2c: add I2C Address Translator (ATR) support Tomi Valkeinen
2022-12-08 12:53   ` Andy Shevchenko
2022-12-08 16:01     ` Tomi Valkeinen
2022-12-08 18:09       ` Andy Shevchenko
2022-12-08 10:40 ` [PATCH v5 3/8] dt-bindings: media: add bindings for TI DS90UB913 Tomi Valkeinen
2022-12-11 17:13   ` Laurent Pinchart
2022-12-11 17:21     ` Laurent Pinchart
2022-12-13 13:36       ` Tomi Valkeinen
2022-12-26 16:46         ` Laurent Pinchart
2023-01-04  8:12           ` Tomi Valkeinen
2023-01-04 12:52             ` Laurent Pinchart
2022-12-13 13:21     ` Tomi Valkeinen
2022-12-08 10:40 ` [PATCH v5 4/8] dt-bindings: media: add bindings for TI DS90UB953 Tomi Valkeinen
2022-12-09 21:27   ` Rob Herring
2023-01-04  8:26     ` Tomi Valkeinen
2022-12-11 17:34   ` Laurent Pinchart
2022-12-13 14:06     ` Tomi Valkeinen
2022-12-08 10:40 ` [PATCH v5 5/8] dt-bindings: media: add bindings for TI DS90UB960 Tomi Valkeinen
2022-12-09 21:30   ` Rob Herring
2022-12-11 17:58   ` Laurent Pinchart
2022-12-13 14:25     ` Tomi Valkeinen
2022-12-26 16:52       ` Laurent Pinchart
2023-01-04  8:59         ` Tomi Valkeinen
2023-01-04 12:57           ` Laurent Pinchart
2023-01-04 14:05             ` Tomi Valkeinen
2023-01-05  6:54               ` Laurent Pinchart
2022-12-08 10:40 ` [PATCH v5 6/8] media: i2c: add DS90UB960 driver Tomi Valkeinen
2022-12-08 13:34   ` kernel test robot
2022-12-08 14:55   ` kernel test robot
2022-12-08 10:40 ` [PATCH v5 7/8] media: i2c: add DS90UB913 driver Tomi Valkeinen
2022-12-08 14:35   ` kernel test robot
2022-12-11 18:33   ` Laurent Pinchart
2022-12-14  6:29     ` Tomi Valkeinen
2022-12-14  6:36       ` Tomi Valkeinen
2022-12-26 16:56         ` Laurent Pinchart
2022-12-26 19:25           ` Tomi Valkeinen
2023-01-04 13:55             ` Laurent Pinchart
2023-01-04 14:13               ` Tomi Valkeinen
2023-01-04 15:32                 ` Laurent Pinchart
2023-01-04 15:43                   ` Tomi Valkeinen
2022-12-26 17:01       ` Laurent Pinchart
2022-12-27 20:09         ` Andy Shevchenko
2023-01-04 13:29           ` Laurent Pinchart
2022-12-14  6:48     ` Tomi Valkeinen
2022-12-08 10:40 ` [PATCH v5 8/8] media: i2c: add DS90UB953 driver Tomi Valkeinen
2022-12-08 10:42 ` [PATCH v5 0/8] i2c-atr and FPDLink Tomi Valkeinen
2022-12-08 12:26   ` Andy Shevchenko
2022-12-08 14:40     ` Tomi Valkeinen
2022-12-08 15:57       ` Andy Shevchenko
2022-12-08 15:58         ` Andy Shevchenko
2022-12-08 16:05           ` Tomi Valkeinen

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=Y6Azg9GJ/ntUlS+P@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=Matti.Vaittinen@fi.rohmeurope.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hverkuil@xs4all.nl \
    --cc=khalasa@piap.pl \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=luca@lucaceresoli.net \
    --cc=m.tretter@pengutronix.de \
    --cc=marex@denx.de \
    --cc=mchehab@kernel.org \
    --cc=mpagano@gentoo.org \
    --cc=peda@axentia.se \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shawnx.tu@intel.com \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=wsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.