All of lore.kernel.org
 help / color / mirror / Atom feed
* Device tree for c67x00
@ 2009-06-29 15:25 Jorge Sánchez de Nova
  2009-06-29 19:10 ` Peter Korsgaard
  0 siblings, 1 reply; 7+ messages in thread
From: Jorge Sánchez de Nova @ 2009-06-29 15:25 UTC (permalink / raw)
  To: Linuxppc-dev

[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]

Hi,

 I am trying to load the c67x00 driver in my Xilinx ML403 (PowerPC) based
platform. I am running a merged tree between DENX+Adeos/Xenomai and Xilinx
(2.6.29.4). I have the XPS_EPC core interfaced to the Cypress CY7C67300.
Before, in PPC I used to have something like this in my virtex_devices.c

/*
 * Cypress USB C67x00 shortcut macro for single instance
 */
#define XPAR_C67x00_USB(num) { \
 .name = "c67x00", \
 .id = num, \
 .num_resources = 2, \
 .resource = (struct resource[]) { \
         { \
         .start = XPAR_C67X00_USB_PRH##num##_BASEADDR, \
         .end = XPAR_C67X00_USB_PRH##num##_BASEADDR + 0xf, \
         .flags = IORESOURCE_MEM, \
         }, \
         { \
         .start  = XPAR_OPB_INTC_0_SYSTEM_USB_HPI_INT_PIN_INTR, \
         .end    = XPAR_OPB_INTC_0_SYSTEM_USB_HPI_INT_PIN_INTR, \
         .flags  = IORESOURCE_IRQ, \
          }, \
  }, \
 .dev.platform_data = &(struct c67x00_platform_data) { \
 .sie_config = C67X00_SIE1_HOST | C67X00_SIE2_PERIPHERAL_A, \
 .hpi_regstep = 0x02, /* A0 not connected on 16bit bus */ \
 }, \
}

Together with the xparameters.h #defines. And even if I never managed to get
it working, the kernel was loading it. Now I am trying to have the
equivalent information in the device-tree .dts with no luck. Something like
this:

                xps_epc_0: usb@80800000 {
          compatible = "cy,c67300 cy,c67x00";
                  interrupt-parent = <&xps_intc_0>;
          interrupts = < 0 2 >;
                  reg = < 0x80800000 0x10000 >;
            xlnx,family = "virtex4";
                  } ;

(inspired by another mail in this list).

It doesn't work at all since it doesn't load anything. I have looked at the
driver and there is apparently no openfirmware support for it, so maybe the
dts info won't work without it. Am I wrong? Does this means that the c67x00
needs OF support to work in this configuration? How can I make it otherwise?


Thanks,
Jorge

[-- Attachment #2: Type: text/html, Size: 2160 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread
[parent not found: <20080926230904.3E572C60081@mail63-dub.bigfish.com>]

end of thread, other threads:[~2009-07-06 12:38 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-29 15:25 Device tree for c67x00 Jorge Sánchez de Nova
2009-06-29 19:10 ` Peter Korsgaard
2009-07-06 12:38   ` Jorge Sánchez de Nova
     [not found] <20080926230904.3E572C60081@mail63-dub.bigfish.com>
     [not found] ` <20080926230904.3E572C60081-elvp7KehBMsEb1aXSZwOPPYhGscHeamf@public.gmane.org>
2008-10-05  5:58   ` Grant Likely
     [not found]     ` <20081005055800.GA14172-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
2008-10-06  3:29       ` Stephen Neuendorffer
2008-10-06  7:22       ` Peter Korsgaard
     [not found]         ` <87r66u6vcd.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2008-10-06 13:59           ` Grant Likely

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.