On Thu, Jul 23, 2020 at 10:41 PM Miguel Borges de Freitas <miguelborgesdefreitas@xxxxxxxxx> wrote: > > Hi Alexandre, > > Having a way to dynamically change the configuration would definitely > be helpful in most cases. I decided to go with a DT property because > in the case this patch tries to solve (the cubox-i) there isn't simply > any other option - the default mode won't work due to the missing hw > components. So, I thought that by defining it as a DT property it > could somehow be locked to the hardware definition. > Keep me posted > > Regards > > PS: Sorry for the second message, forgot to disable html and the > message couldn't be delivered to all recipients. > > Alexandre Belloni <alexandre.belloni@xxxxxxxxxxx> escreveu no dia > quinta, 23/07/2020 à(s) 20:57: > > > > > > > > > I'm all for common properties, but is this common across vendors? > > > > > > > This is but this shouldn't be a DT property as it has to be changed > > dynamically. I'm working on an ioctl interface to change this > > configuration. > > > > Thanks for sending this patch. I think there are two paths forward if an ioctl interface is being added. 1) Change the property to reflect that this is the default state the RTC should be initialized to. 2) Just move this configuration into the bootloader and then verify that the bootloader doesn't reset this value. -Jon
