On Thu, Dec 10, 2015 at 4:11 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote: > On Thursday 10 December 2015 13:43:16 John Stultz wrote: >> On Thu, Dec 10, 2015 at 12:24 PM, Rob Herring <robh+dt@xxxxxxxxxx> wrote: >> > The fact that we are using notifiers for reset reason and triggering >> > is probably some indication that some infrastructure is needed. But I >> > don't think you need to do that here as long as it is all kernel >> > internals. We'll make the 2nd guy do it. >> >> >> >> Though, just so I understand better, what is problematic w/ the reset >> notifiers? They provide the reboot command argument, which is the core >> of what is needed. It actually seemed like it was almost designed with >> this problem in mind. > > Notifiers in general are a bit of a kludge. We often use them in places > that have not been abstracted well enough yet, and they make it > less obvious what is actually going on when something happens, or > in what order things are called. Exactly. > I'm actually less worried about the notifier side here than about > the general problem of the communication channel. The reboot reason > is only one of a number of things that the kernel needs to communicate > to the boot loader. Other things may include: If only there was a standard interface for firmware variable storage... > - boot device > - location of the kernel > - command line > - properties of the /chosen DT node in general > - boot scripts > - ethernet MAC addresses > - bootloader console configuration A major distinction here is many of these would be persistent (i.e. in flash). As much of this goes into to the DT anyway, a standard way for userspace to update the DT could solve this. That would not really work for handling a one time case unless you supported boot with an alternate DT. I've also seen storing of SD tuning parameters to avoid tuning at boot up. Although, the tuning doesn't add that much to the boot time relative to Android boot, so I don't really see the point. Rob -- 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
