Hi Bin, On 14 December 2015 at 22:45, Bin Meng <bmeng...@gmail.com> wrote: > Hi Simon, > > On Tue, Dec 15, 2015 at 10:04 AM, Bin Meng <bmeng...@gmail.com> wrote: >> Hi Simon, >> >> On Tue, Dec 15, 2015 at 6:14 AM, Simon Glass <s...@chromium.org> wrote: >>> Hi Bin, >>> >>> On 13 December 2015 at 23:05, Bin Meng <bmeng...@gmail.com> wrote: >>>> Hi Simon, >>>> >>>> On Tue, Dec 1, 2015 at 12:46 PM, Simon Glass <s...@chromium.org> wrote: >>>>> It seems likely that at some point we will want a generic interrupt >>>>> uclass. >>>>> But this is a big undertaking as it involves unifying code across multiple >>>>> architectures. >>>>> >>>>> As a first step, create a simple IRQ uclass and a driver for x86. This can >>>>> be generalised later as required. >>>>> >>>>> Adjust pirq_init() to probe this driver, which has the effect of creating >>>>> routing tables and setting up the interrupt routing. This is a start >>>>> towards making interrupts fit better with driver model. >>>>> >>>>> Signed-off-by: Simon Glass <s...@chromium.org> >>>>> --- >>>>> >>>> >>>> Reviewed-by: Bin Meng <bmeng...@gmail.com> >>>> >>>> I will test this series when all previous DM changes are applied. >>> >>> Do you mean the series that I just pushed to dm/next. or something else? >>> >> >> Yes, I mean all previous DM changes as I suspect this series has some >> dependency on previous series. I will apply this series on top of >> dm/next and test there. > > patch#4, patch#5 does not apply on top of dm/next. I guess there are > some other dependencies?
I'm not sure, but you can use u-boot-dm/pcid-working for your testing. Regards, Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
