Hi Tom, On Tue, 8 Mar 2022 at 06:26, Tom Rini <tr...@konsulko.com> wrote: > > On Tue, Mar 08, 2022 at 02:11:02PM +0100, Heinrich Schuchardt wrote: > > On 3/4/22 16:42, Simon Glass wrote: > > > It is a common need in U-Boot to have one subsystem notify another > > > when something happens. An example is reading a partition table when a > > > new block device is set up. > > > > > > It is also common to add weak functions and 'hook' functions to modify > > > how U-Boot works. See for example ft_board_setup() and the like. > > > > > > U-Boot would benefit from a generic mechanism to handle these cases, > > > with the ability to hook into various 'events' in a > > > subsystem-independent and transparent way. > > > > > > This series provides a way to create and dispatch events, with a way of > > > registering a 'spy' which watches for events of different types. This > > > allows 'hook' functions to be created in a generic way. > > > > > > It also includes a script to list the hooks in an image, which is a bit > > > easier to debug than weak functions, as well as an 'event' command to > > > do the same from within U-Boot. > > > > > > These 'static' events can be used to replace hooks like misc_init_f(), > > > for example. Also included is basic support for 'dynamic' events, where > > > a spy can be registered at runtime. The need for this is still being > > > figured out. > > > > @Simon, Tom: > > > > What is the status of this series? Takahiro's UEFI integration series > > builds on it. Is it going to be pushed to origin/next soon? > > I'm waiting for Simon to reply to Takahiro's comment on v2 before > applying.
OK I found it and replied. Regards, Simon