Hi, On Wed, 13 May 2020 at 03:55, Andy Shevchenko <andriy.shevche...@linux.intel.com> wrote: > > On Tue, May 12, 2020 at 05:22:38PM -0600, Simon Glass wrote: > > Hi Andy, > > > > On Tue, 12 May 2020 at 06:32, Andy Shevchenko > > <andriy.shevche...@linux.intel.com> wrote: > > > > > > On Tue, May 12, 2020 at 01:55:49PM +0200, Wolfgang Wallner wrote: > > > > > > > > Since you were involved a lot in the discussion in the part A series, > > > > > would you please let me know if you get some time to review this? > > > > > > > > Unfortunately, I don't have as much time now for review of part B as I > > > > had for > > > > part A. I already started reviewing part B and I will try to continue > > > > when time > > > > allows. > > > > > > I'm busy at the moment and I will be not available for this for few weeks. > > > Code can be fixed iteratively, the most important part now is to see the > > > big > > > picture of the design and approach. > > > > > > Could you remind which patch in the series describes that? I will look at > > > it > > > closer and try to allocate a bit of time to do it. > > > > > > > The big picture was in part A. Part B uses the same mechanism to add > > support for SSDT and DSDT generation, e.g. see [1] and [2]. > > Thank you, then I think what is left are technical (implementation) details > that can be amended in the future.
OK then perhaps part B can be applied and I can send part C, which is the actual coral implementation? Regards, SImon
