On Tue, May 05, 2015 at 12:46:32PM +0100, Srinivas Kandagatla wrote:
> Hi Stephen,
>
> Sorry I took so long to reply.
>
>
> On 09/04/15 15:45, Stephen Boyd wrote:
> >On 04/07, Srinivas Kandagatla wrote:
> >>On 07/04/15 19:45, Stephen Boyd wrote:
> >>>On 03/30, Srinivas Kandagatla wrote:
> >>>
>
On Tue, May 05, 2015 at 12:46:32PM +0100, Srinivas Kandagatla wrote:
Hi Stephen,
Sorry I took so long to reply.
On 09/04/15 15:45, Stephen Boyd wrote:
On 04/07, Srinivas Kandagatla wrote:
On 07/04/15 19:45, Stephen Boyd wrote:
On 03/30, Srinivas Kandagatla wrote:
Do you have an
On Mon, Mar 30, 2015 at 10:57:50PM +0100, Srinivas Kandagatla wrote:
> +
> + for (i = 0; i < cell->nblocks; i++) {
> + rc = regmap_raw_read(eeprom->regmap, cell->blocks[i].offset,
> + buf + offset, cell->blocks[i].count);
I *think* this is
On Mon, Mar 30, 2015 at 10:57:50PM +0100, Srinivas Kandagatla wrote:
+
+ for (i = 0; i cell-nblocks; i++) {
+ rc = regmap_raw_read(eeprom-regmap, cell-blocks[i].offset,
+ buf + offset, cell-blocks[i].count);
I *think* this is probably OK but
Hi Stephen,
Sorry I took so long to reply.
On 09/04/15 15:45, Stephen Boyd wrote:
On 04/07, Srinivas Kandagatla wrote:
On 07/04/15 19:45, Stephen Boyd wrote:
On 03/30, Srinivas Kandagatla wrote:
Do you have an overview of how to use these APIs? Maybe some
Documentation/ is in order? I'm
Hi Stephen,
Sorry I took so long to reply.
On 09/04/15 15:45, Stephen Boyd wrote:
On 04/07, Srinivas Kandagatla wrote:
On 07/04/15 19:45, Stephen Boyd wrote:
On 03/30, Srinivas Kandagatla wrote:
Do you have an overview of how to use these APIs? Maybe some
Documentation/ is in order? I'm
On 04/07, Srinivas Kandagatla wrote:
> On 07/04/15 19:45, Stephen Boyd wrote:
> >On 03/30, Srinivas Kandagatla wrote:
> >
> >Do you have an overview of how to use these APIs? Maybe some
> >Documentation/ is in order? I'm mostly interested in how the
> >blocks array is supposed to work and how this
On 04/07, Srinivas Kandagatla wrote:
On 07/04/15 19:45, Stephen Boyd wrote:
On 03/30, Srinivas Kandagatla wrote:
Do you have an overview of how to use these APIs? Maybe some
Documentation/ is in order? I'm mostly interested in how the
blocks array is supposed to work and how this hooks up
Thanks Stephen for review,
On 07/04/15 19:45, Stephen Boyd wrote:
On 03/30, Srinivas Kandagatla wrote:
@@ -130,6 +138,37 @@ static struct class eeprom_class = {
.dev_release= eeprom_release,
};
+static int of_eeprom_match(struct device *dev, const void *eeprom_np)
+{
+
On 03/30, Srinivas Kandagatla wrote:
> @@ -130,6 +138,37 @@ static struct class eeprom_class = {
> .dev_release= eeprom_release,
> };
>
> +static int of_eeprom_match(struct device *dev, const void *eeprom_np)
> +{
> + return dev->of_node == eeprom_np;
> +}
> +
> +static struct
On 03/30, Srinivas Kandagatla wrote:
@@ -130,6 +138,37 @@ static struct class eeprom_class = {
.dev_release= eeprom_release,
};
+static int of_eeprom_match(struct device *dev, const void *eeprom_np)
+{
+ return dev-of_node == eeprom_np;
+}
+
+static struct eeprom_device
Thanks Stephen for review,
On 07/04/15 19:45, Stephen Boyd wrote:
On 03/30, Srinivas Kandagatla wrote:
@@ -130,6 +138,37 @@ static struct class eeprom_class = {
.dev_release= eeprom_release,
};
+static int of_eeprom_match(struct device *dev, const void *eeprom_np)
+{
+
This patch adds just consumers part of the framework just to enable easy
review.
Up until now, EEPROM drivers were stored in drivers/misc, where they all had to
duplicate pretty much the same code to register a sysfs file, allow in-kernel
users to access the content of the devices they were
This patch adds just consumers part of the framework just to enable easy
review.
Up until now, EEPROM drivers were stored in drivers/misc, where they all had to
duplicate pretty much the same code to register a sysfs file, allow in-kernel
users to access the content of the devices they were
14 matches
Mail list logo