On Thu, Mar 10, 2011 at 05:07:17PM +0900, Magnus Damm wrote:
> Hi Simon,
> 
> On Thu, Mar 10, 2011 at 4:58 PM, Simon Horman <ho...@verge.net.au> wrote:
> > This allows a ROM-able zImage to be written to eSD and for SuperH Mobile
> > ARM to boot directly from the SDHI hardware block.
> >
> > This is achieved by the MaskROM loading the first portion of the image into
> > MERAM and then jumping to it.  This portion contains loader code which
> > copies the entire image to SDRAM and jumps to it. From there the zImage
> > boot code proceeds as normal, uncompressing the image into its final
> > location and then jumping to it.
> >
> > Cc: Magnus Damm <magnus.d...@gmail.com>
> > Cc: Kuninori Morimoto <kuninori.morimoto...@renesas.com>
> > Signed-off-by: Simon Horman <ho...@verge.net.au>
> 
> Nice to see some SDHI loader code!
> 
> > --- /dev/null
> > +++ b/arch/arm/boot/compressed/sdhi-shmobile.c
> 
> > +#define PORT179CR      0xe60520b3
> > +#define PORT180CR      0xe60520b4
> > +#define PORT181CR      0xe60520b5
> > +#define PORT182CR      0xe60520b6
> > +#define PORT183CR      0xe60520b7
> > +#define PORT184CR      0xe60520b8
> > +
> > +#define SMSTPCR3       0xe615013c
> > +#define SDGENCNTA      0xfe40009c
> 
> These...
> 
> > +       /* Initialise SDHI1 */
> > +       /* PORT184CR: GPIO_FN_SDHICMD1 Control */
> > +       __raw_writeb(CR_FUNCTION1, PORT184CR);
> > +       /* PORT179CR: GPIO_FN_SDHICLK1 Control */
> > +       __raw_writeb(CR_INPUT_ENABLE|CR_FUNCTION1, PORT179CR);
> > +       /* PORT181CR: GPIO_FN_SDHID1_3 Control */
> > +       __raw_writeb(CR_FUNCTION1, PORT183CR);
> > +       /* PORT182CR: GPIO_FN_SDHID1_2 Control */
> > +       __raw_writeb(CR_FUNCTION1, PORT182CR);
> > +       /* PORT183CR: GPIO_FN_SDHID1_1 Control */
> > +       __raw_writeb(CR_FUNCTION1, PORT181CR);
> > +       /* PORT180CR: GPIO_FN_SDHID1_0 Control */
> > +       __raw_writeb(CR_FUNCTION1, PORT180CR);
> > +
> > +       /* Enable clock to SDHI1 hardware block */
> > +       __raw_writel(__raw_readl(SMSTPCR3) & ~(1 << 13), SMSTPCR3);
> 
> ...and these are sh7372 specific.
> 
> If possible I'd like to reuse your SDHI code on sh73a0, so please
> consider splitting up the code in a SDHI specific portion and in a
> processor specific portion.

Sure.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to