All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Luca Ceresoli <luca@lucaceresoli.net>
Cc: "Rob Herring" <robh@kernel.org>,
	"Jacopo Mondi" <jacopo@jmondi.org>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Kieran Bingham" <kieran@bingham.xyz>,
	linux-kernel@vger.kernel.org, "Vladimir Zapolskiy" <vz@mleia.com>,
	linux-renesas-soc@vger.kernel.org,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	linux-i2c@vger.kernel.org,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	linux-i3c@lists.infradead.org,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>
Subject: Re: [RFC PATCH v2 2/6] i2c: allow DT nodes without 'compatible'
Date: Wed, 15 Apr 2020 09:59:11 +0200	[thread overview]
Message-ID: <20200415075911.GA1141@ninjato> (raw)
In-Reply-To: <11ca7487-ac07-f714-8573-20d1a0040212@lucaceresoli.net>


[-- Attachment #1.1: Type: text/plain, Size: 554 bytes --]


> As I said in the reply to v1, I think we should reserve addresses also
> when there is a compatible string but no matching driver, but this is
> another story and can be handled separately.

Unless I misunderstand you, I think they do already. Note that
only 'i2cdetect' shows a device as busy *IFF* there is a driver bound to
it. The internal 'i2c_check_addr_busy' does not care about a driver
being bound. You can check this by trying to use
i2c_new_ancillary_device() with an address which is already described in
DT but which driver is disabled.


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 155 bytes --]

_______________________________________________
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Luca Ceresoli <luca@lucaceresoli.net>
Cc: "Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-i3c@lists.infradead.org,
	"Kieran Bingham" <kieran@ksquared.org.uk>,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Jacopo Mondi" <jacopo@jmondi.org>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Vladimir Zapolskiy" <vz@mleia.com>,
	linux-kernel@vger.kernel.org,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Rob Herring" <robh@kernel.org>
Subject: Re: [RFC PATCH v2 2/6] i2c: allow DT nodes without 'compatible'
Date: Wed, 15 Apr 2020 09:59:11 +0200	[thread overview]
Message-ID: <20200415075911.GA1141@ninjato> (raw)
In-Reply-To: <11ca7487-ac07-f714-8573-20d1a0040212@lucaceresoli.net>

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]


> As I said in the reply to v1, I think we should reserve addresses also
> when there is a compatible string but no matching driver, but this is
> another story and can be handled separately.

Unless I misunderstand you, I think they do already. Note that
only 'i2cdetect' shows a device as busy *IFF* there is a driver bound to
it. The internal 'i2c_check_addr_busy' does not care about a driver
being bound. You can check this by trying to use
i2c_new_ancillary_device() with an address which is already described in
DT but which driver is disabled.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-04-15  7:59 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 15:00 [RFC PATCH v2 0/6] i2c: of: reserve unknown and ancillary addresses Wolfram Sang
2020-03-18 15:00 ` Wolfram Sang
2020-03-18 15:00 ` [RFC PATCH v2 1/6] i2c: use DEFINE for the dummy driver name Wolfram Sang
2020-03-18 15:00   ` Wolfram Sang
2020-04-15  8:09   ` Kieran Bingham
2020-04-15  8:09     ` Kieran Bingham
2020-03-18 15:00 ` [RFC PATCH v2 2/6] i2c: allow DT nodes without 'compatible' Wolfram Sang
2020-03-18 15:00   ` Wolfram Sang
2020-04-10 13:49   ` Luca Ceresoli
2020-04-10 13:49     ` Luca Ceresoli
2020-04-15  7:59     ` Wolfram Sang [this message]
2020-04-15  7:59       ` Wolfram Sang
2020-04-15  8:07       ` Kieran Bingham
2020-04-15  8:07         ` Kieran Bingham
2020-04-15  8:16         ` Wolfram Sang
2020-04-15  8:16           ` Wolfram Sang
2020-04-15  8:38           ` Kieran Bingham
2020-04-15  8:38             ` Kieran Bingham
2020-04-16 14:53       ` Luca Ceresoli
2020-04-16 14:53         ` Luca Ceresoli
2020-04-15  8:48   ` Kieran Bingham
2020-04-15  8:48     ` Kieran Bingham
2020-04-15  9:46     ` Wolfram Sang
2020-04-15  9:46       ` Wolfram Sang
2020-03-18 15:00 ` [RFC PATCH v2 3/6] i2c: of: remove superfluous parameter from exported function Wolfram Sang
2020-03-18 15:00   ` Wolfram Sang
2020-03-19 12:41   ` Boris Brezillon
2020-03-19 12:41     ` Boris Brezillon
2020-04-15  8:13   ` Kieran Bingham
2020-04-15  8:13     ` Kieran Bingham
2020-03-18 15:00 ` [RFC PATCH v2 4/6] i2c: of: error message unification Wolfram Sang
2020-03-18 15:00   ` Wolfram Sang
2020-04-10 17:02   ` Luca Ceresoli
2020-04-10 17:02     ` Luca Ceresoli
2020-04-15  8:17   ` Kieran Bingham
2020-04-15  8:17     ` Kieran Bingham
2020-04-15  8:50     ` Kieran Bingham
2020-04-15  8:50       ` Kieran Bingham
2020-03-18 15:00 ` [RFC PATCH v2 5/6] i2c: of: mark a whole array of regs as reserved Wolfram Sang
2020-03-18 15:00   ` Wolfram Sang
2020-04-10 17:05   ` Luca Ceresoli
2020-04-10 17:05     ` Luca Ceresoli
2020-04-13  9:55   ` Luca Ceresoli
2020-04-13  9:55     ` Luca Ceresoli
2020-04-15  8:10     ` Wolfram Sang
2020-04-15  8:10       ` Wolfram Sang
2020-04-15 10:07   ` Luca Ceresoli
2020-04-15 10:07     ` Luca Ceresoli
2020-03-18 15:00 ` [RFC PATCH v2 6/6] i2c: core: hand over reserved devices when requesting ancillary addresses Wolfram Sang
2020-03-18 15:00   ` Wolfram Sang
2020-04-15 10:07   ` Luca Ceresoli
2020-04-15 10:07     ` Luca Ceresoli
2020-03-28  3:50 ` [RFC PATCH v2 0/6] i2c: of: reserve unknown and " Wolfram Sang
2020-03-28  3:50   ` Wolfram Sang
2020-04-15  8:27 ` Wolfram Sang
2020-04-15  8:27   ` Wolfram Sang
2020-04-15  8:35   ` Kieran Bingham
2020-04-15  8:35     ` Kieran Bingham

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=20200415075911.GA1141@ninjato \
    --to=wsa@the-dreams.de \
    --cc=geert+renesas@glider.be \
    --cc=jacopo@jmondi.org \
    --cc=kieran@bingham.xyz \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=luca@lucaceresoli.net \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=robh@kernel.org \
    --cc=vz@mleia.com \
    --cc=wsa+renesas@sang-engineering.com \
    /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.