Re: [PATCH] Add MPC52xx simple interrupt GPIO support

On Mon, Mar 2, 2009 at 10:16 AM, Anton Vorontsov
[off-list ref] wrote:

On Thu, Feb 26, 2009 at 10:06:59PM -0700, Grant Likely wrote:

quoted

=A0Maybe something like:

struct of_gpio_chip {
=A0 =A0 =A0 =A0 int gpio_cells;
=A0 =A0 =A0 =A0 int (*xlate)(struct of_gpio_chip *of_gc, struct device_n=

ode *np,

quoted

=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0const void *gpio_spec, enum o=

f_gpio_flags *flags);

quoted

=A0 =A0 =A0 =A0 struct gpio_chip gc[1];
};

I'd suggest to not touch of_gpio_chip structure, I'd like to keep
of_gpio_chip struct 1:1 bound to a pure gpio_chip structure. This keeps
things simple and understandable on the low level.

And when you need several gpio controllers bound to some Linux struct,
I would rather suggest this:

struct mpc5200_gpio_controller {
=A0 =A0 =A0 =A0void __iomem *regs;
=A0 =A0 =A0 =A0void (*save_regs)(struct of_mm_gpio_chip *mm_gc);
=A0 =A0 =A0 =A0struct of_gpio_chip of_gc[1];
};

In the of_gc->xlate callback you'll always get &of_gc[0], but since you
know that this is mpc5200 controller, you can add needed offset depending
on gpio_spec.

Fair enough.  That works too.

OTOH, there is even more straightforward solution, all you actually need
is to define "HW GPIO" bindings (which are wkup, which are interrupt, etc=

.),

and then:

void mpc5200_gpio_set(struct gpio_chip *gc, unsigned int gpio, int value)
{
=A0 =A0 =A0 =A0if (mpc5200_is_wkup(gpio))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0write to the wkup registers block;
=A0 =A0 =A0 =A0else if (mpc5200_is_int(gpio))
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0write to the int registers block;
=A0 =A0 =A0 =A0else
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0...
}

That is, the same thing we do for the interrupt controllers.

Ugh, I'd really do not want to use this approach.  The GPIOs path is
too long as is.  When GPIOs are used for things like JTAG or other bus
emulation, every cycle counts.  As much as possible the long path,
such as figuring out which chip, should be preprocessed so that it is
already known by the time the set/get/direction hooks are called.

IRQ controllers typically need to deal with far lower frequencies on
the IRQ line.

(Note that these "if"s can be replaced by a table, as in
arch/powerpc/sysdev/qe_lib/qe_ic.c).

Even with the table it is a cost I don't want in the GPIO handler.  If
it were possible to do so, I'd even like to remove the spinlocks from
the hooks, but that isn't an option at the moment.

g.

--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.