Re: [PATCH v2 1/7] eeprom: Add a simple EEPROM framework for eeprom providers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 






On 24/03/15 17:23, Mark Brown wrote:
On Tue, Mar 24, 2015 at 09:18:14AM +0000, Srinivas Kandagatla wrote:

I did try your suggestion, by which I could remove the regmap from config.
One thing I did not like was eeprom-core getting size/stride info directly
from providers and regmap from regmap apis. I was wondering if we could take
a step further and introduce new regmap helpers like

regmap_get_size(regmap)

This is already there.
Sorry, I can't see any such api atleast in v4.0-rc5 and linux-next? Are you referring to another api which does the same job?


regmap_get_stride(regmap)

Which would be give eeprom-core the size and stride info, doing this way
would cut down regmap related things from eeprom_config structure to minimal
and also the source of information would come from just regmap apis.

Documentation/SubmittingPatches...

Am not sure what you meant here, Am guessing that you asked me to keep the respective maintainers in the loop and follow the guide, when I resend the patch?

--srini
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Device Tree Compilter]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux PCI Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Yosemite Backpacking]
  Powered by Linux