mx35pdk lan911x support
xiao jiang
jgq516 at gmail.com
Fri Oct 15 03:13:22 EDT 2010
Hello Uwe,
2010/10/14 Uwe Kleine-König <u.kleine-koenig at pengutronix.de>
> Hello,
>
> On Thu, Oct 14, 2010 at 09:05:39PM +0800, xiao jiang wrote:
> > Hi,
> > 2010/10/14 Fabio Estevam <festevam at gmail.com>
> >
> > > Hi Xiao Jiang,
> > >
> > > 2010/10/14 Uwe Kleine-König <u.kleine-koenig at pengutronix.de>:
> > > > Hello Xiao (hoping this is the part of your name corresponding to
> your
> > > > first name),
> > > >
> > > > On Thu, Oct 14, 2010 at 12:06:25AM -0400, xiao jiang wrote:
> > > >> I saw the mach-mx35_3ds.c are come from you, so I think you are
> the
> > > right
> > > >> person to answer my queston, :).
> > > > It was me, who renamed the file and touched it a few times when
> cleaning
> > > > up and reorganising things for the i.MX machines. Initially it was
> > > > Fabio Estevam who brought the machine into mainline.
> > >
> > > I suggest you to look at MX51 3stack board or MX31 3stack boards, as
> > > they have support for LAN9217 controller.
> > >
> > >
> > Uwe,
> > I forgot to subscribe the list, now it is ok after done it.:)
> >
> > Fabio,
> > Thanks for your hint, I can boot the kernel thru lan9217 now, only a few
> > lines added.
> >
> > diff --git a/arch/arm/mach-mx3/mach-mx35_3ds.c
> > b/arch/arm/mach-mx3/mach-mx35_3ds.c
> > index 1c30d72..7e30a4e 100644
> > --- a/arch/arm/mach-mx3/mach-mx35_3ds.c
> > +++ b/arch/arm/mach-mx3/mach-mx35_3ds.c
> > @@ -35,6 +35,7 @@
> > #include <mach/hardware.h>
> > #include <mach/common.h>
> > #include <mach/iomux-mx35.h>
> > +#include <mach/3ds_debugboard.h>
> >
> > #include "devices-imx35.h"
> > #include "devices.h"
> > @@ -86,6 +87,7 @@ static struct fsl_usb2_platform_data usb_pdata = {
> > /*
> > * Board specific initialization.
> > */
> > +#define EXPIO_PARENT_INT 65
> > static void __init mxc_board_init(void)
> > {
> > mxc_iomux_v3_setup_multiple_pads(mx35pdk_pads,
> > ARRAY_SIZE(mx35pdk_pads));
> > @@ -95,6 +97,10 @@ static void __init mxc_board_init(void)
> > imx35_add_imx_uart0(&uart_pdata);
> >
> > mxc_register_device(&mxc_otg_udc_device, &usb_pdata);
> > +
> > + if (!mxc_expio_init(MX35_CS5_BASE_ADDR, EXPIO_PARENT_INT))
> > + printk(KERN_WARNING "Init of the debugboard failed, all "
> > + "devices on the board are unusable.\n");
> If you intend this patch to go mainline please use pr_warn instead of
> printk(KERN_WARNING ...).
>
> Ok, but I don't want to use hard-code for EXPIO_PARENT_INT, and found there
is no related definition for MX35_GPIO1_1 pin, do I need to create it like
MX31_PIN_GPIO1_1?
Best Regards,
Xiao Jiang
> Best regards
> Uwe
>
> --
> Pengutronix e.K. | Uwe Kleine-König |
> Industrial Linux Solutions | http://www.pengutronix.de/ |
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20101015/c4c3ceb5/attachment-0001.html>
More information about the linux-arm-kernel
mailing list