All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: 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>,
	"Luca Ceresoli" <luca@lucaceresoli.net>,
	"Jacopo Mondi" <jacopo@jmondi.org>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"Vladimir Zapolskiy" <vz@mleia.com>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Subject: Re: [RFC PATCH 3/7] i2c: allow DT nodes without 'compatible'
Date: Wed, 26 Feb 2020 10:30:54 -0600	[thread overview]
Message-ID: <20200226163054.GA26533@bogus> (raw)
In-Reply-To: <20200220172403.26062-4-wsa+renesas@sang-engineering.com>

On Thu, 20 Feb 2020 18:23:59 +0100, Wolfram Sang wrote:
> Sometimes, we have unknown devices in a system and still want to block
> their address. For that, we allow DT nodes with only a 'reg' property.
> These devices will be bound to the "dummy" driver but with the name
> "reserved". That way, we can distinguish them and even hand them over to
> the "dummy" driver later when they are really requested using
> i2c_new_ancillary_device().
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>  Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 1 -
>  Documentation/devicetree/bindings/i2c/i2c.txt        | 4 +++-
>  drivers/i2c/i2c-core-base.c                          | 1 +
>  drivers/i2c/i2c-core-of.c                            | 8 +++-----
>  drivers/i2c/i2c-core.h                               | 1 +
>  5 files changed, 8 insertions(+), 7 deletions(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-renesas-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-i3c-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	"Kieran Bingham" <kieran-7hKh/agyDeatmTQ+vhA3Yw@public.gmane.org>,
	"Niklas Söderlund"
	<niklas.soderlund-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org>,
	"Luca Ceresoli" <luca-ep08DiM7hqZH3+C6az13tg@public.gmane.org>,
	"Jacopo Mondi" <jacopo-AW8dsiIh9cEdnm+yROfE0A@public.gmane.org>,
	"Laurent Pinchart"
	<laurent.pinchart-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>,
	"Vladimir Zapolskiy" <vz-ChpfBGZJDbMAvxtiuMwx3w@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"Wolfram Sang"
	<wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.org>
Subject: Re: [RFC PATCH 3/7] i2c: allow DT nodes without 'compatible'
Date: Wed, 26 Feb 2020 10:30:54 -0600	[thread overview]
Message-ID: <20200226163054.GA26533@bogus> (raw)
In-Reply-To: <20200220172403.26062-4-wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.org>

On Thu, 20 Feb 2020 18:23:59 +0100, Wolfram Sang wrote:
> Sometimes, we have unknown devices in a system and still want to block
> their address. For that, we allow DT nodes with only a 'reg' property.
> These devices will be bound to the "dummy" driver but with the name
> "reserved". That way, we can distinguish them and even hand them over to
> the "dummy" driver later when they are really requested using
> i2c_new_ancillary_device().
> 
> Signed-off-by: Wolfram Sang <wsa+renesas-jBu1N2QxHDJrcw3mvpCnnVaTQe2KTcn/@public.gmane.org>
> ---
>  Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 1 -
>  Documentation/devicetree/bindings/i2c/i2c.txt        | 4 +++-
>  drivers/i2c/i2c-core-base.c                          | 1 +
>  drivers/i2c/i2c-core-of.c                            | 8 +++-----
>  drivers/i2c/i2c-core.h                               | 1 +
>  5 files changed, 8 insertions(+), 7 deletions(-)
> 

Acked-by: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: devicetree@vger.kernel.org,
	"Kieran Bingham" <kieran@ksquared.org.uk>,
	"Wolfram Sang" <wsa+renesas@sang-engineering.com>,
	linux-kernel@vger.kernel.org, "Jacopo Mondi" <jacopo@jmondi.org>,
	"Vladimir Zapolskiy" <vz@mleia.com>,
	linux-renesas-soc@vger.kernel.org,
	"Luca Ceresoli" <luca@lucaceresoli.net>,
	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 3/7] i2c: allow DT nodes without 'compatible'
Date: Wed, 26 Feb 2020 10:30:54 -0600	[thread overview]
Message-ID: <20200226163054.GA26533@bogus> (raw)
In-Reply-To: <20200220172403.26062-4-wsa+renesas@sang-engineering.com>

On Thu, 20 Feb 2020 18:23:59 +0100, Wolfram Sang wrote:
> Sometimes, we have unknown devices in a system and still want to block
> their address. For that, we allow DT nodes with only a 'reg' property.
> These devices will be bound to the "dummy" driver but with the name
> "reserved". That way, we can distinguish them and even hand them over to
> the "dummy" driver later when they are really requested using
> i2c_new_ancillary_device().
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>  Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 1 -
>  Documentation/devicetree/bindings/i2c/i2c.txt        | 4 +++-
>  drivers/i2c/i2c-core-base.c                          | 1 +
>  drivers/i2c/i2c-core-of.c                            | 8 +++-----
>  drivers/i2c/i2c-core.h                               | 1 +
>  5 files changed, 8 insertions(+), 7 deletions(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

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

  parent reply	other threads:[~2020-02-26 16:30 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-20 17:23 [RFC PATCH 0/7] i2c: of: reserve unknown and ancillary addresses Wolfram Sang
2020-02-20 17:23 ` Wolfram Sang
2020-02-20 17:23 ` [RFC PATCH 1/7] i2c: add sanity check for parameter of i2c_verify_client() Wolfram Sang
2020-02-20 17:23   ` Wolfram Sang
2020-02-21  9:36   ` Geert Uytterhoeven
2020-02-21  9:36     ` Geert Uytterhoeven
2020-02-20 17:23 ` [RFC PATCH 2/7] i2c: use DEFINE for the dummy driver name Wolfram Sang
2020-02-20 17:23   ` Wolfram Sang
2020-02-21  9:38   ` Geert Uytterhoeven
2020-02-21  9:38     ` Geert Uytterhoeven
2020-02-20 17:23 ` [RFC PATCH 3/7] i2c: allow DT nodes without 'compatible' Wolfram Sang
2020-02-20 17:23   ` Wolfram Sang
2020-02-20 17:23   ` Wolfram Sang
2020-02-21  9:45   ` Geert Uytterhoeven
2020-02-21  9:45     ` Geert Uytterhoeven
2020-02-21  9:45     ` Geert Uytterhoeven
2020-02-21  9:48     ` Geert Uytterhoeven
2020-02-21  9:48       ` Geert Uytterhoeven
2020-02-21  9:48       ` Geert Uytterhoeven
2020-02-23 23:11     ` Luca Ceresoli
2020-02-23 23:11       ` Luca Ceresoli
2020-03-12 11:19       ` Wolfram Sang
2020-03-12 11:19         ` Wolfram Sang
2020-03-12 11:44         ` Alexandre Belloni
2020-03-12 11:44           ` Alexandre Belloni
2020-03-12 11:44           ` Alexandre Belloni
2020-04-10 13:47         ` Luca Ceresoli
2020-04-10 13:47           ` Luca Ceresoli
2020-02-26 16:30   ` Rob Herring [this message]
2020-02-26 16:30     ` Rob Herring
2020-02-26 16:30     ` Rob Herring
2020-02-20 17:24 ` [RFC PATCH 4/7] i2c: of: remove superfluous parameter from exported function Wolfram Sang
2020-02-20 17:24   ` Wolfram Sang
2020-02-21  9:50   ` Geert Uytterhoeven
2020-02-21  9:50     ` Geert Uytterhoeven
2020-02-21  9:50     ` Geert Uytterhoeven
2020-02-24  8:12   ` Luca Ceresoli
2020-02-24  8:12     ` Luca Ceresoli
2020-02-20 17:24 ` [RFC PATCH 5/7] i2c: of: error message unification Wolfram Sang
2020-02-20 17:24   ` Wolfram Sang
2020-02-21  9:54   ` Geert Uytterhoeven
2020-02-21  9:54     ` Geert Uytterhoeven
2020-02-20 17:24 ` [RFC PATCH 6/7] i2c: of: mark a whole array of regs as reserved Wolfram Sang
2020-02-20 17:24   ` Wolfram Sang
2020-02-21 10:09   ` Geert Uytterhoeven
2020-02-21 10:09     ` Geert Uytterhoeven
2020-03-12 11:21     ` Wolfram Sang
2020-03-12 11:21       ` Wolfram Sang
2020-03-18 14:33     ` Wolfram Sang
2020-03-18 14:33       ` Wolfram Sang
2020-02-28 12:11   ` Luca Ceresoli
2020-02-28 12:11     ` Luca Ceresoli
2020-02-20 17:24 ` [RFC PATCH 7/7] i2c: core: hand over reserved devices when requesting ancillary addresses Wolfram Sang
2020-02-20 17:24   ` Wolfram Sang
2020-02-21 10:13   ` Geert Uytterhoeven
2020-02-21 10:13     ` Geert Uytterhoeven
2020-02-21 10:13     ` Geert Uytterhoeven
2020-02-28 12:11     ` Luca Ceresoli
2020-02-28 12:11       ` Luca Ceresoli
2020-03-12 11:30       ` Wolfram Sang
2020-03-12 11:30         ` Wolfram Sang
2020-03-12 11:21     ` Wolfram Sang
2020-03-12 11:21       ` Wolfram Sang
2020-03-13 12:42     ` Wolfram Sang
2020-03-13 12:42       ` Wolfram Sang
2020-02-21 10:15 ` [RFC PATCH 0/7] i2c: of: reserve unknown and " Geert Uytterhoeven
2020-02-21 10:15   ` Geert Uytterhoeven

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=20200226163054.GA26533@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jacopo@jmondi.org \
    --cc=kieran@ksquared.org.uk \
    --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=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.