-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 05/14/2013 03:42 PM, Lubomir Popov wrote: > Hi Tom, > > Just a couple of things to clarify below. > >> On Tue, May 14, 2013 at 07:09:33PM +0300, Lubomir Popov wrote: >>> Hi Tom, >>> >>> On 14/05/13 17:52, Tom Rini wrote: >>>> On Tue, May 14, 2013 at 01:24:41PM +0300, Lubomir Popov >>>> wrote: >>>>> Hi Tom, >>>>> >>>>> I'm currently busy with other work; on the other hand, >>>>> careful rebasing shall require some time, especially the >>>>> Palmas stuff. What would be the deadline for a V2 >>>>> submission? >>>>> >>>>> Meanwhile could you please have a look at the (already old) >>>>> http://patchwork.ozlabs.org/patch/232743/? A simple patch, >>>>> shall be needed if we enable USB (for the uEVM along with >>>>> our board). In general, what are your plans regarding USB >>>>> (.../patch/232742/)? >>>> >>>> Thanks for the reminder, I'll grab 232743 soon. 232742 >>>> looks OK, but >>> do >>>> you have a patch around for uEVM still? >>> Not yet (didn't have the opportunity to test, although some >>> uEVMs should be around at MMS). As you know, a patch shall be >>> needed in the uEVM board file along with the common USB stuff. >> >> Yeah, I can test it as well if you write it up, and may find the >> time if you point me in the right direction. > OK, shall do it.
Thanks! [snip] >>>> [snip] >>> Currently the scrm struct is defined for OMAP4 in the >>> asm/arch-omap4/clocks.h file and I have already done the same >>> for OMAP5 by analogy. I must admit however that this approach >>> does not correspond to the latest way by which groups of OMAP >>> hardware regs are defined, prcm in particular - a struct in >>> omap_common.h, holding only the required regs, no padding and >>> such garbage, and an init with the physical addresses in a .c >>> file for the particular SoC (prcm-regs.c). But still the Panda >>> board, for example, uses the old way for scrm. Therefore I did >>> it the same for OMAP5, which was easier (I'm old and lazy ;) >>> ). >> >> Yes, I'm OK starting off with moving things into omap_common.h >> as-is and then updating them a bit later ala pcrm-regs.c. > Who is starting off, me or you? ;) Since your series needs it (so we aren't writing to magic locations which isn't allowed), you please. Thanks! - -- Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRkqBgAAoJENk4IS6UOR1WFVcQAIo9DgrABUaAwOTfYFXVlGQ6 /MFyQvtwFYtEwW1xtDZ8RWuv1zGI26IIw4XH+xhspj50w7ma9lji575U/tyQCtrN G6xMW8bH/8Cxj+kFUcgeNXSqAF0OLOz8Rvow9dSW2RpnOu3yOPKnvgxjV974x595 IfBK26Xo5ldR6qX12EIwAfHZVRow97Kk25LOBoqR+qxTBrtKPWzywXyvTi94qY/b jcy9L17AQQvNWQofps7noDsFM+acWlQxsTkjbdkynDu8gIQC0JZ8cEUPZ9XsYg+D 8SvXeY5ntCEOwxvB2TZ2GNC9/J5fVXMmewrexH1AdjsO1d0529ZjCX0995whV2pJ xCYi0FAtXKW0fm1gitMXZ0J/pHzNdsr1s+rV0iUtppbhh9mQ+NQplXVPevB0UrWH 1UHHxe1Hsc5ZJHJRvvFyVAo9ySdZ85zrS6+TlMwfjK1LWtQmPJ0DA1Cddz8m/BI+ 6ebQ36qgJuO990YhQ9GlfOV1rjp3RhrCmb+JKwjMN0OahnfAEvp4osCvbMClDXqT VL83+gP1lKJ47B2VfuyqXW+ETBV6hhLprItj8wx+0sJx0rNKc98Q61pO8XSPZwoE 8hWzqeY7Dmlp2QxQ3ZyD5w5+DECGbj7ihCICkjquwHSB5v1R4R1XIwlV/3cd/Mm4 SMnFtv8rUQsfzi48bGt4 =lJAv -----END PGP SIGNATURE----- _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
