[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50902079.30406@gmail.com>
Date: Tue, 30 Oct 2012 11:46:17 -0700
From: David Daney <ddaney.cavm@...il.com>
To: Pantelis Antoniou <panto@...oniou-consulting.com>
CC: Wolfram Sang <w.sang@...gutronix.de>,
"Ben Dooks (embedded platforms)" <ben-linux@...ff.org>,
linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
Koen Kooi <koen@...inion.thruhere.net>,
Matt Porter <mporter@...com>, Russ Dill <Russ.Dill@...com>,
linux-omap@...r.kernel.org
Subject: Re: [PATCH] i2c-EEPROM: Export memory accessor
On 10/31/2012 08:56 AM, Pantelis Antoniou wrote:
> Various platforms need access to the EEPROM in other
> places besides their platform registration callbacks.
> Export the memory accessor to the i2c_client
i2c_clients are *not* intrinsically memory, so adding this to the
generic i2c_client structure doesn't really make sense. What would the
semantics of this interface be with respect to temperature sensors and
GPIO expanders?
NACK.
> and implement
> it for the at24 driver.
>
> And before you ask, no, the platform callback can't be used
> for anything that depends on DT.
Why can't you just allocate (and populate) a struct at24_platform_data
for the device if it isn't supplied by whatever created the device?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists