>-----Original Message----- >From: Shawn Guo [mailto:[email protected]] >Sent: Monday, May 20, 2013 11:21 AM >To: Lu Jingchang-B35083 >Cc: [email protected]; [email protected]; >[email protected]; [email protected]; [email protected] >Subject: Re: [PATCH v3] clocksource: add MVF600 pit timer support > >On Mon, May 20, 2013 at 03:08:54AM +0000, Lu Jingchang-B35083 wrote: >> [Lu Jingchang-B35083] >> I am not sure MVF5xx and MVF7xx have the same PIT block, if you have >information that it is the same on other Vybrid SoCs, it is ok to change >the driver name to mvf. Thanks! > >Even the PIT block on other Vybrid SoCs have differences from the one >integrated on mvf600, we can handle them using device tree compatible >string. And that's why we need to encode SoC name in compatible. > [Lu Jingchang-B35083] Ok, I will rename the driver and the configure option, thanks! >> [Lu Jingchang-B35083] >> PIT0 and PIT1 can be chained to build a 64-bit timer, so PIT2 and PIT3 >are selected as the clocksource and clockevent device, and leave PIT0 and >PIT1 unused for anyone else who needs them. Thanks! > >This could be an useful info to be in the comment. > [Lu Jingchang-B35083] I will add a comment for this, thanks!
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
