On Thu, Sep 12, 2013 at 5:30 PM, Emilio López <emilio@xxxxxxxxxxxxx> wrote: > This driver's only job is to claim and ensure the necessary clock > for memory operation on a DT-powered machine remains enabled. > > Signed-off-by: Emilio López <emilio@xxxxxxxxxxxxx> > --- > > I believe this new patch should resolve all the concerns raised; as > always, all feedback is welcome :) I think you're going about this the wrong way. If you have a problem with a clock not staying on, shouldn't you just marking it appropriately in the clock table instead, making sure it's initialized with at least one reference to it? I believe that is how some of the other platforms handle this, and it's a lot cleaner than adding a fake binding and a fake driver just to grab a single clock. -Olof -- 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
