Hello Doug, On Wed, Sep 17, 2014 at 12:15 AM, Doug Anderson <diand...@chromium.org> wrote: > > I think you can turn off CONFIG_COMMON_CLK_MAX77686 and then this > clock will be left at whatever the bootloader set it to, right? Then > there will be no auto-disabling by the CCF and the RTC will work.
Yes, that's how Daniel was working around the issue. > That's one argument for making the clock "optional". > Indeed. > NOTE: I don't think that the builtin RTC is terribly important for any > exynos-based Chromebooks that I'm aware of. We rely on the RTC that's > part of the Maxim PMIC itself and pretty much ignore the one built-in > to the exynos. I think there are some cases it was used (as a > fallback wakeup source in certain test scripts), but nothing very > important. > Ok, I'll post the patch I shared before that makes the rtc to claim the max77802 32kHz clock as "rtc_src" anyways since that is the right thing to do even if the "rtc_src" ends being optional due DT backward compat. > -Doug Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
