Hi,
Michael Kelly writes:
> At 06:24 AM 6/30/2005, Lothar Wassmann wrote:
> >Hi,
> >
> >Michael Kelly writes:
> > > Bill,
> > >
> > > One issue with the PXA255 edge triggering is that you need
> > > to be sure you poll the state of the interrupt line before you
> > > re-enable the GPIO interrupt.
At 06:24 AM 6/30/2005, Lothar Wassmann wrote:
Hi,
Michael Kelly writes:
> Bill,
>
> One issue with the PXA255 edge triggering is that you need
> to be sure you poll the state of the interrupt line before you
> re-enable the GPIO interrupt. That way if the device is asking
> for more servicing,
On Thu, 2005-06-30 at 14:30 +0200, Robin Farine wrote:
> On Thursday 30 June 2005 14.12, Bill Gatliff wrote:
>
> > Still doesn't explain why I can't use IRQT_LOW for the IRQ type,
> > though...
>
> The pxa does not support level-triggered GPIO interrupts. Thus, the
> pxa-specific interrupt code
On Thursday 30 June 2005 14.12, Bill Gatliff wrote:
> Still doesn't explain why I can't use IRQT_LOW for the IRQ type,
> though...
The pxa does not support level-triggered GPIO interrupts. Thus, the
pxa-specific interrupt code only handles IRQT_RISING and
IRQT_FALLING, it just ignores IRQT_HIGH
Lothar:
Lothar Wassmann wrote:
The PXA requires a minimum pulse width of 1 microsecond (Chapter 4-12
of the PXA255 Developers Manual) on a GPIO pin for proper edge
detection. The ISP116x generates a pulse of 167ns in edge triggered
mode. Thus you cannot use the edge triggered mode of the ISP116
Hi,
Michael Kelly writes:
> Bill,
>
> One issue with the PXA255 edge triggering is that you need
> to be sure you poll the state of the interrupt line before you
> re-enable the GPIO interrupt. That way if the device is asking
> for more servicing, you won't miss it since there will be no
> edge
Hi,
Bill Gatliff writes:
> Odd odd odd. :^)
>
> The only combination which seems to work for me is this:
>
> static struct isp116x_platform_data csb625_isp116x_platform_data = {
> .sel15Kres = 1,
> .int_act_high = 0,
> .int_edge_triggered = 0,
> .no_power_switching = 1,
> };
> ...
> s
Bill,
One issue with the PXA255 edge triggering is that you need
to be sure you poll the state of the interrupt line before you
re-enable the GPIO interrupt. That way if the device is asking
for more servicing, you won't miss it since there will be no
edge to detect.
Maybe you can look at what
On Wed, 29 Jun 2005, Bill Gatliff wrote:
> Guys:
>
>
> Odd odd odd. :^)
>
> The only combination which seems to work for me is this:
>
> static struct isp116x_platform_data
> csb625_isp116x_platform_data = {
> .sel15Kres = 1,
> .int_act_high = 0,
> .int_edge_triggered = 0,
> .no_power_s
Guys:
Odd odd odd. :^)
The only combination which seems to work for me is this:
static struct isp116x_platform_data csb625_isp116x_platform_data = {
.sel15Kres = 1,
.int_act_high = 0,
.int_edge_triggered = 0,
.no_power_switching = 1,
};
...
set_irq_type(IRQ_GPIO(22), IRQT_FALLING);
I ha
On Tue, 28 Jun 2005, Bill Gatliff wrote:
> The isp1161's INT1 line is tied to GPIO22 on my PXA255
> (according to the schematic). Here is my latest platform
> stuff:
>
> #define CSB625_USB_PHYS PXA_CS5_PHYS
> #define CSB625_USB_IRQ 22
>
> static struct resource isp116x_resources[] = {
> [0]
On Tue, 2005-06-28 at 00:27 -0500, Bill Gatliff wrote:
> I'm still not getting the chip to recognize a device when I connect one,
> even though I have corrected a number of things that I think were wrong
> in my platform code. Any suggestions would be appreciated.
I can't tell you what the prob
On Tuesday 28 June 2005 07.27, Bill Gatliff wrote:
> static struct isp116x_platform_data csb625_isp116x_platform_data
> = { .sel15Kres = 1,
> .int_act_high = 1,
> .int_edge_triggered = 1,
> };
Did you try with ".int_edge_triggered = 0"? The pulse the isp116x
generates might be too short for
Olav:
Was that hardware problem related to pulling the WAKEUP pin? Or anything else?
It looked like it was a dead chip! Another prototype board seems to get
past that point. *shrug*
I'm still not getting the chip to recognize a device when I connect one,
even though I have corrected a
On Sat, 25 Jun 2005, Bill Gatliff wrote:
> Guys:
>
>
> > Turns out, an identical board works with my kernel. Odd. :^)
>
> Well, my initial testing board did have a hardware problem
> which I've corrected. Now I'm getting this far:
>
Was that hardware problem related to pulling the WAKEUP
p
15 matches
Mail list logo
