[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190620092116.y7aqun6jjjn4mgow@katana>
Date: Thu, 20 Jun 2019 11:21:16 +0200
From: Wolfram Sang <wsa@...-dreams.de>
To: Steve Twiss <stwiss.opensource@...semi.com>
Cc: "wsa+renesas@...g-engineering.com" <wsa+renesas@...g-engineering.com>,
"bgolaszewski@...libre.com" <bgolaszewski@...libre.com>,
"kieran.bingham+renesas@...asonboard.com"
<kieran.bingham+renesas@...asonboard.com>,
"lee.jones@...aro.org" <lee.jones@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-renesas-soc@...r.kernel.org"
<linux-renesas-soc@...r.kernel.org>,
"peda@...ntia.se" <peda@...ntia.se>,
Support Opensource <Support.Opensource@...semi.com>
Subject: Re: [PATCH] mfd: da9063: occupy second I2C address, too
> Is this a safety clause? What I mean is, shouldn't the hardware design make
> sure there are not two devices located on the same I2C bus with the same slave
> address?
It is more about preventing userspace to accidently access this address,
and thus the registers behind it.
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists