lkml.org 
[lkml]   [2007]   [Apr]   [10]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
    /
    DateWed, 11 Apr 2007 08:30:45 +0800
    From"Eric Miao" <>
    SubjectRe: [RFC, PATCH 1/3] gpiodev - API definitions
    it looks ok, but I have several questions:
    
    1. why should we bind this to platform_device, what if the gpio device
    is not actually a "platform_device", say, a I2C device, a SPI device or
    even a USB device?
    
    2. I still doubt the benefit of using of a structure for a gpio, isn't a gpio
    number not enough?
    
    3. If one is going to use a GPIO, he has to initialize a "struct gpio"
    before that, how is he suppose to know the value for "gpio->gpio_dev"?
    
    4. how can we optimize to a direct register access instruction (e.g.
    to GPDR in PXA) for bit-banging operation (pardon me, I don't exactly
    remember the name for such operation, maybe bit-banging)
    -
    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: 2007-04-11 02:33    [from the cache]
    ©2003-2008