On 15.01.2016 10:50, Javier Martinez Canillas wrote:
On Thu, Jan 14, 2016 at 8:50 AM, Laxman Dewangan <ldewangan@xxxxxxxxxx> wrote:
On Thursday 14 January 2016 06:50 AM, Krzysztof Kozlowski wrote:[snip]
On 14.01.2016 09:50, Krzysztof Kozlowski wrote:
Agreed.The max77802 does exactly the same (BTW, these should be merged asHow about merging max77802 to max77686 first? The only differences I
well... I'll add this to the TODO list) so I think this is necessary.
1. It uses main MFD/PMIC regmap.
This can be solved as part of decoupling code. The driver will get
MFD's regmap and set up its own (only on max77686). The max77802 will
only use parent's regmap.
2. It has different register address.
We need a register-layout/configuration structure. The logic is the
same except few differences (e.g. presence of MAX77802_RTC_AE1).
It may be easier to merge them now, before adding support for max77620?
When I originally posted the max77802 support, I had separate MFD,
RTC, regulator and clock drivers and the feedback (IIRC) was that the
MFD and clock blocks were too similar to the max77686 so I extended
those drivers instead of adding new ones. But that the RTC and
regulator blocks were different so a separate driver was justified...
but it's true that are not that different and rtc-max77686 could be
extended and rtc-max77802 removed.
In fact, the ChromiumOS vendor tree has a single RTC driver for bothSo feel free to take that job from me. :) I will happily do the testing
max77686 and max77802:
I could also work on this next week if you want. After all I feelI could handle this probably next week or in the following week
(assuming someone would test max77802 because I don't have the hardware).
guilty for the code duplication :-)
and provide complains (I mean, comments).