lkml.org 
[lkml]   [2011]   [May]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] drivers: create a pinmux subsystem v2
On Mon, May 16, 2011 at 02:09:20AM +0200, Linus Walleij wrote:
> 2011/5/11 Jamie Iles <jamie@jamieiles.com>:
> > [...]
> >> +static struct foo_pmx_func myfuncs[] = {
> >> +     {
> >> +             .name = "spi0-0",
> >> +             .pins = spi0_0_pins,
> >> +             .num_pins = ARRAY_SIZE(spi0_1_pins),
> >> +     },
> >> +     {
> >> +             .name = "i2c0",
> >> +             .pins = i2c0_pins,
> >> +             .num_pins = ARRAY_SIZE(i2c0_pins),
> >> +     },
> >> +     {
> >> +             .name = "spi0-1",
> >> +             .pins = spi0_1_pins,
> >> +             .num_pins = ARRAY_SIZE(spi0_1_pins),
> >> +     },
> >> +};
> >
> > So I can see how this works well for these examples, but on our devices,
> > we have some interfaces for connecting to radios and these have a pair
> > of 8-bit RX and TX busses.  However, depending on what radio you
> > connect, you may not need all 8 bits of each and this is dependent on
> > the board.  What would be the best way to deal with that in this scheme
> > where say we only wanted 4 bits of each, saving the others for GPIO?
> > Would this need to be a function for each configuration?
>
> Yes. Define a function containing the pins you need, then when that
> function is muxed in by pinmux_get() the remaining pins are still
> available for GPIO.
>
> The framework only deals with functions as groups of pins and
> individual GPIO pins, defining the groups is currently up to each
> platform.

OK, from this and your other emails I think I understand this now. So
for this (using the current, non-device-tree method) case I guess we
could leave the registration of these pins to the board code rather than
the chip specific stuff.

> > [...]
> >> +/**
> >> + * pinmux_request_gpio() - request a single pin to be muxed in to be used
> >> + *   as a GPIO pin
> >> + * @pin: the pin to mux in as GPIO
> >> + * @gpio: the corresponding GPIO pin number
> >> + */
> >> +int pinmux_request_gpio(int pin, unsigned gpio)
> >> +{
> >> +     char gpiostr[16];
> >> +
> >> +     snprintf(gpiostr, 15, "gpio%d", gpio);
> >> +     return pin_request(pin, gpiostr, true);
> >> +}
> >> +EXPORT_SYMBOL_GPL(pinmux_request_gpio);
> >
> > Our devices have two different GPIO controllers, which can be muxed to
> > the same pad (they're slightly different - one is a bit slower but can
> > do sigma-delta output) and our pinmux driver would need to know what
> > GPIO controller it should route to the pad.  Could gpio_request_enable()
> > be passed the GPIO number or is there a better way to do this?
>
> Hmmmm that was really new!
>
> But like we have the more complex config function for pinmux groups:
> extern int pinmux_config(struct pinmux *pmx, u16 param, unsigned long *data);
>
> I believe your case could be handled with a similar more complex
> per-pin config function like this:
> extern int pinmux_config_gpio(int pin, unsigned gpio, u16 param,
> unsigned long *data);
>
> Would that work?

Yes, I think it probably would. I'm travelling for a bit now so won't
get chance to try this for a week or two but I'll try porting our
platform over to this system; it would be great to have a standardized
way of handling pin muxing.

Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2011-05-16 11:39    [W:0.108 / U:5.904 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site