On Sat, Nov 22, 2014 at 7:12 PM, Wolfram Sang wrote:
> Hi,
>
> Please quote only relevant parts of the message (like I did). This
> improves readability a lot.
>
My bad, will minimize the overhead in the future.
>>
>> Would it make sense to have:
>> WRITE_START
>> WRITE_NEXT
>> WRITE_STOP
>> WRI
On Tue, Nov 18, 2014 at 5:04 PM, Wolfram Sang wrote:
> From: Wolfram Sang
>
> The first user of the i2c-slave interface is an eeprom simulator. It is
> a shared memory which can be accessed by the remote master via I2C and
> locally via sysfs.
>
> Signed-off-by: Wolfram Sang
> ---
>
> Changes si
On Thu, Aug 28, 2014 at 5:53 PM, leroy christophe
wrote:
>
> I've been able to identify the origin of the issue. It happens since the
> below commit.
> Do you know what should be done to fix that ?
>
> Christophe
>
>
Actually, more things are wrong with what the driver is doing.
If inside spi_ad
On Sun, Jan 27, 2013 at 3:29 PM, Roland Stigge wrote:
> On 27/01/13 14:07, Stijn Devriendt wrote:
>>> +Example:
>>> +
>>> +blockgpio {
>>> +compatible = "linux,gpio-block";
>>> +
>>> +
On Sun, Jan 27, 2013 at 2:58 PM, Roland Stigge wrote:
> On 27/01/13 14:19, Stijn Devriendt wrote:
>>> +Block GPIO
>>> +--
>>> +
>>> +The above described interface concentrates on handling single GPIOs.
>>> However,
>>> +in appli
On Sun, Jan 27, 2013 at 2:48 PM, Roland Stigge wrote:
> On 27/01/13 13:18, Stijn Devriendt wrote:
>>>> In my patch, I go out of the way of this kind of thing for a simple reason:
>>>> You may generate incorrect timing by doing this.
>>>
>>> You are rig
On Tue, Jan 22, 2013 at 1:06 PM, Roland Stigge wrote:
> The recurring task of providing simultaneous access to GPIO lines (especially
> for bit banging protocols) needs an appropriate API.
>
> This patch adds a kernel internal "Block GPIO" API that enables simultaneous
> access to several GPIOs. T
On Tue, Jan 22, 2013 at 1:06 PM, Roland Stigge wrote:
> This patch adds device tree support to the block GPIO API.
>
> Signed-off-by: Roland Stigge
>
> ---
> Documentation/devicetree/bindings/gpio/gpio-block.txt | 36 ++
> drivers/gpio/Makefile |1
> dri
On Thu, Jan 24, 2013 at 1:19 PM, Roland Stigge wrote:
> On 01/24/2013 01:02 PM, Stijn Devriendt wrote:
>>> +static void lpc32xx_gpio_set_block_p3(struct gpio_chip *chip,
>>> + unsigned long mask,
>>> +
On Tue, Jan 22, 2013 at 1:06 PM, Roland Stigge wrote:
> This patch adds block GPIO support to several gpio drivers.
>
> This implements block GPIO only for some selected drivers since block GPIO is
> an optional feature which may not be suitable for every GPIO hardware. (With
> automatic fallback
On Sun, Sep 30, 2012 at 5:09 PM, Roland Stigge wrote:
> Hi Stijn,
>
> On 30/09/12 16:52, Stijn Devriendt wrote:
>>> One question: How did you solve the one-value-per-file in the sysfs
>>> interface?
>>>
>> By exporting the group as a whole:
>> /sys/
On Sun, Sep 30, 2012 at 12:34 PM, Roland Stigge wrote:
> On 29/09/12 21:57, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> Problem here is that it's only an intermediate format since hardware
>>> often needs special preparation of the data.
>>>
>>> But will evaluate what makes most sense.
>> the key
On Sun, Sep 30, 2012 at 12:50 PM, Roland Stigge wrote:
> On 30/09/12 11:35, Stijn Devriendt wrote:
>> In our kernel tree we have similar code. If you like I can request
>> permission
>> to share. I can, however, already give you an update on the basic
>> structure,
On Thu, Sep 27, 2012 at 11:22 PM, Roland Stigge wrote:
>
> The recurring task of providing simultaneous access to GPIO lines
> (especially
> for bit banging protocols) needs an appropriate API.
>
> This patch adds a kernel internal "Block GPIO" API that enables
> simultaneous
> access to several G
14 matches
Mail list logo
