On Tuesday 05 February 2013 at 15:29:09, Grant Likely wrote:
> On Thu, 31 Jan 2013 21:51:36 +0100, Linus Walleij
wrote:
> > On Thu, Jan 31, 2013 at 4:58 PM, Lars Poeschel
wrote:
> > > --- /dev/null
> > > +++ b/Documentation/devicetree/bindings/gpio/gpio-mcp23
Hi Matt!
At first thanks for you efforts on DMA Engine on AM33XX.
On Friday 01 February 2013 at 22:01:17, Matt Porter wrote:
> This series adds DT DMA Engine Client support to the omap_hsmmc.
> It leverages the generic DMA OF helpers in -next and the
> dma_request_slave_channel_compat() wrapper i
From: Lars Poeschel
I wanted to use mcp23s08 driver with a device that boots using device tree.
I modified the driver to allow the DT usage and tested with a mcp23017
which is a i2c device. I could not test the spi path, because I have no
such device.
Regards,
Lars
Lars Poeschel (2):
gpio
From: Lars Poeschel
Explicitly allow -1 as a legal value for the
mcp23s08_platform_data->base. This is the special value lets the
kernel choose a valid global gpio base number.
Signed-off-by: Lars Poeschel
---
drivers/gpio/gpio-mcp23s08.c |4 ++--
1 file changed, 2 insertions(+)
From: Lars Poeschel
This converts the mcp23s08 driver to be able to be used with device
tree.
There is a special "mcp,chips" property, that correspond to the chips
member of the struct mcp23s08_platform_data. It can be used for
multiple mcp23s08/mc23s17 on the same spi chipselect.
Sig
On Wednesday 05 December 2012 at 17:41:53, Wolfram Sang wrote:
> > > The method of accessing EEPROMs is used by way more chips than FRAMs.
> > > So, I'd prefer to have the text updated more generic like "EEPROMs and
> > > similar devices like RAMs, ROMs, etc...". Describing setting .flags in
> > >
As it seems there are no further comments, could this please be included ?
Thanks,
Lars
On Monday 17 December 2012 at 09:34:15, Lars Poeschel wrote:
> From: Lars Poeschel
>
> This driver allows to use a lcd2s 20x4 character display as
> a linux console output device.
>
> S
On Sunday 10 February 2013 at 17:30:47, Wolfram Sang wrote:
> > what happend to this one ? It was a patch updating Kconfig help for
> > at24.
>
> Do you know linux-next? Have a look there...
Thank you for the hint and for commiting it.
Lars
--
To unsubscribe from this list: send the line "unsub
From: Lars Poeschel
This converts the mcp23s08 driver to be able to be used with device
tree.
Explicitly allow -1 as a legal value for the
mcp23s08_platform_data->base. This is the special value lets the
kernel choose a valid global gpio base number.
There is a "mcp,chips" device
From: Lars Poeschel
This adds a simple sysfs interface to the pwm subsystem. It is
heavily inspired by the gpio sysfs interface.
/sys/class/pwm
/export ... asks the kernel to export a PWM to userspace
/unexport ... to return a PWM to the kernel
From: Lars Poeschel
This converts the mcp23s08 driver to be able to be used with device
tree.
There is a "spi-present-mask" device tree property, that allows to
use multiple of this spi chips on the same chipselect.
Signed-off-by: Lars Poeschel
---
v4:
- removed the ability to s
On Thursday 04 April 2013 15:44:08 Linus Walleij wrote:
> On Thu, Apr 4, 2013 at 12:02 PM, Lars Poeschel
wrote:
> > From: Lars Poeschel
> >
> > This converts the mcp23s08 driver to be able to be used with device
> > tree.
> > There is a "spi-present-mask
From: Lars Poeschel
This converts the mcp23s08 driver to be able to be used with device
tree.
There are two properties taken, that correspond to the members of
the struct mcp23s08_platform_data, that is the base member and the
chip array member.
Signed-off-by: Lars Poeschel
---
.../devicetree
From: Lars Poeschel
I wanted to use mcp23s08 driver with a device that boots using device tree.
Therefore I had to modify the driver to be able to take it's platform_data
from the device tree.
I am using a mcp23017 (I2C) device successfully with the patch booted over
device tree. I am not
On Thursday 24 January 2013 at 08:27:01, Wolfram Sang wrote:
> > > > > > I wanted to use a fm24c04 i2c fram chip with linux. I grepped
> > > > > > the source and found nothing. I later found that my chip can be
> > > > > > handled by at24 eeprom driver. It creates a sysfs file called
> > > > > > ee
From: Lars Poeschel
This adds a simple sysfs interface to the pwm subsystem. It is
heavily inspired by the gpio sysfs interface.
/sys/class/pwm
/export ... asks the kernel to export a PWM to userspace
/unexport ... to return a PWM to the kernel
On Tuesday 16 October 2012 at 19:11:10, Linus Walleij wrote:
> On Tue, Oct 16, 2012 at 3:38 PM, Lars Poeschel wrote:
> > I had a look at regmap. This is interesting. But there is no regmap_bus
> > implementation for usb. Are you pointing me in this direction ? ;-)
>
> I wa
On Wednesday 24 October 2012 at 18:31:55, Mark Brown wrote:
> On Wed, Oct 24, 2012 at 09:53:06AM +0200, Linus Walleij wrote:
> > On Tue, Oct 23, 2012 at 5:24 PM, Lars Poeschel
wrote:
> > > Ok, I tried to implement it (at least for the gpioa part of the
> > > driver).
I am not sure if I did something fundamentally wrong or if you did not
understand, what I am trying to do. I am sorry, I am not a native english
writer, maybe I did a bad explanation.
On Thursday 25 October 2012 at 16:00:13, Mark Brown wrote:
> On Thu, Oct 25, 2012 at 12:02:36PM +0200, L
On Thursday 25 October 2012 at 18:06:51, Mark Brown wrote:
> Are you saying that whoever designed this USB device has done it so that
> it takes a byte stream with something like RRVV where RR is the register
> and VV is the value? That's the marshalling, as you'll have seen that's
> done before t
From: Lars Poeschel
This sets the type of the platform devices that are added
to the mfd core to some mfd-cell type. This enables us
to add mfd cells to platform devices, that are in use by
other cores (e.g. the usb core).
Otherwise by removing the mfd cell from a platform device
that already
From: Lars Poeschel
This adds the mfd cell to use the gpio a and gpio b part
of the Nano River Technologies viperboard.
Signed-off-by: Lars Poeschel
---
drivers/gpio/Kconfig | 13 +
drivers/gpio/Makefile |1 +
drivers/gpio/gpio-viperboard.c | 517
From: Lars Poeschel
This adds the mfd cell to use the adc part of the Nano River Technologies
viperboard.
Signed-off-by: Lars Poeschel
---
drivers/iio/adc/Kconfig |7 ++
drivers/iio/adc/Makefile |1 +
drivers/iio/adc/viperboard_adc.c | 181
From: Lars Poeschel
This adds the mfd cell to use the i2c part of the Nano River Technologies
viperboard as i2c master.
Signed-off-by: Lars Poeschel
---
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile |1 +
drivers/i2c/busses/i2c-viperboard.c | 476
From: Lars Poeschel
Add mfd driver for Nano River Technologies viperboard.
Signed-off-by: Lars Poeschel
---
drivers/mfd/Kconfig| 14 +
drivers/mfd/Makefile |1 +
drivers/mfd/viperboard.c | 130
include/linux/mfd
Hi Samuel,
Thanks for your review.
Am 19.09.2012 17:29, schrieb Samuel Ortiz:
Hi Lars,
On Mon, Aug 27, 2012 at 03:08:38PM +0200, la...@wh2.tu-dresden.de
wrote:
From: Lars Poeschel
First version of the driver for Nano River Tech's
viperboard added.
It supports i2c, adc, gpio a and g
Am Freitag 23 August 2013, 21:10:00 schrieb Linus Walleij:
> On Thu, Aug 22, 2013 at 11:56 AM, Lars Poeschel
wrote:
> > From: Lars Poeschel
> >
> > The device tree property should be more descriptive.
> > microchip seems more reasonable than mcp. As there are n
Device mode is currently disabled.
>
> The complete series as used for testing is also available at [1]
>
> [0] git://git.breakpoint.cc/cgit/bigeasy/linux.git nop_phy-rename
> [1] git://git.breakpoint.cc/cgit/bigeasy/linux.git am335x_usb
Tested-by: Lars Poeschel
--
To unsubscribe f
From: Lars Poeschel
The device tree property should be more descriptive.
microchip seems more reasonable than mcp. The old mcp
prefix is still supported but marked as deprecated.
Users of mcp have to switch to the microchip prefix.
Signed-off-by: Lars Poeschel
---
.../devicetree/bindings/gpio
From: Lars Poeschel
Trivial patch to add Microchip Technology Inc. to the list
of devicetree vendor prefixes.
Signed-off-by: Lars Poeschel
---
Documentation/devicetree/bindings/vendor-prefixes.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor
On Friday 23 August 2013 at 21:48:43, Stephen Warren wrote:
> On 08/23/2013 03:40 AM, Lars Poeschel wrote:
> > On Thursday 22 August 2013 at 23:10:53, Stephen Warren wrote:
> >> On 08/21/2013 05:36 PM, Linus Walleij wrote:
> >>> On Thu, Aug 22, 2013 at 1:10 AM, St
On Friday 23 August 2013 at 21:52:20, Stephen Warren wrote:
> On 08/23/2013 12:45 PM, Linus Walleij wrote:
> > On Thu, Aug 22, 2013 at 11:10 PM, Stephen Warren
wrote:
> >> On 08/21/2013 05:36 PM, Linus Walleij wrote:
> >>> On Thu, Aug 22, 2013 at 1:10 AM, Stephen Warren
> >>> wrote: [Me]
> >>>
Hi Andreas!
On Thursday 22 August 2013 at 15:16:18, Andreas Larsson wrote:
> On 2013-08-21 15:38, Lars Poeschel wrote:
> > +static void of_gpio_scan_irq_lines(const struct device_node *const
> > node, +struct device_
On Monday 26 August 2013 at 13:29:07, Andreas Larsson wrote:
> On 2013-08-26 12:56, Lars Poeschel wrote:
> > Hi Andreas!
> >
> > On Thursday 22 August 2013 at 15:16:18, Andreas Larsson wrote:
> >> On 2013-08-21 15:38, Lars Poeschel wrote:
> >>> +stati
tree,
check if these in turn reference the interrupt-controller, and
if they do, loop over the interrupts used by that child and
perform gpio_request() and gpio_direction_input() on these,
making them unreachable from the GPIO side.
The patch has been devised by Linus Walleij and Lars Poeschel.
Ch
From: Lars Poeschel
The device tree property should be more descriptive.
microchip seems more reasonable than mcp. The old mcp
prefix is still supported but marked as deprecated.
Users of mcp have to switch to the microchip prefix.
Acked-by: Mark Rutland
Signed-off-by: Lars Poeschel
From: Lars Poeschel
Trivial patch to add Microchip Technology Inc. to the list
of devicetree vendor prefixes.
Acked-by: Mark Rutland
Signed-off-by: Lars Poeschel
---
Documentation/devicetree/bindings/vendor-prefixes.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation
On Monday 16 September 2013 13:43:50, Stephen Warren wrote:
> On 09/10/2013 06:52 PM, Javier Martinez Canillas wrote:
> > On 09/11/2013 12:34 AM, Stephen Warren wrote:
> >> On 09/10/2013 03:37 PM, Mark Brown wrote:
> >>> On Tue, Sep 10, 2013 at 01:53:47PM -0600, Stephen Warren wrote:
> Doesn't
On Wednesday 04 September 2013 11:29:47, Stephen Warren wrote:
> On 09/03/2013 06:35 AM, Linus Walleij wrote:
> > On Fri, Aug 30, 2013 at 9:53 PM, Stephen Warren
wrote:
> >> I still haven't seen an answer to why we really care about this; how
> >> many times has code actually allocated the same G
On Wednesday 04 September 2013 11:27:12, Stephen Warren wrote:
> On 09/02/2013 03:25 AM, Lars Poeschel wrote:
> > Some leagcy drivers currently do this:
> >
> > request_gpio(gpio);
> > gpio_direction_input(gpio);
> > request_irq(gpio_to_irq(gpio));
> >
On Wednesday 04 September 2013 11:29:00, Stephen Warren wrote:
> On 09/02/2013 03:38 AM, Lars Poeschel wrote:
> > Am Freitag, 30. August 2013, 13:53:45 schrieb Stephen Warren:
> ...
>
> >> Yet the current patch only addresses a limited set of cases, since it
> >>
On Tuesday 10 September 2013 17:19:24, Mark Brown wrote:
> On Wed, Sep 04, 2013 at 02:16:36PM -0600, Stephen Warren wrote:
> > On 09/04/2013 03:05 AM, Lars Poeschel wrote:
> > > The driver that tries to use the GPIO requested by this patch before HAS
> > > to
>
Am Freitag, 30. August 2013, 13:55:26 schrieb Stephen Warren:
> On 08/29/2013 06:24 PM, Javier Martinez Canillas wrote:
> ...
>
> > We have been trying to solve this issue for a few months by now and Linus'
> > approach seems to be the most sensible solution to me.
> >
> > Drivers that request an
Am Freitag, 30. August 2013, 13:53:45 schrieb Stephen Warren:
> On 08/29/2013 01:26 PM, Linus Walleij wrote:
> > On Tue, Aug 27, 2013 at 10:17 PM, Stephen Warren
wrote:
> >> On 08/26/2013 08:07 AM, Lars Poeschel wrote:
> >>> Currently the kernel is ambigously
Am Freitag, 30. August 2013, 14:08:41 schrieb Stephen Warren:
> On 08/29/2013 01:00 PM, Linus Walleij wrote:
> > On Fri, Aug 23, 2013 at 9:52 PM, Stephen Warren
wrote:
> >> On 08/23/2013 12:45 PM, Linus Walleij wrote:
> >>> This is a perfectly OK thing to do as long as it is done like
> >>> this:
d.
>
> Also move gpio_is_input() definition in preparation for the
> next patch that setups the controller's irq_chip driver when
> a caller requests an interrupt line.
>
> Signed-off-by: Javier Martinez Canillas
For both patches:
Tested-by: Lars Poeschel
on an
t;From 4fab49fae62390995868e3b6dee7e0693fce5be9 Mon Sep 17 00:00:00 2001
From: Lars Poeschel
Date: Tue, 4 Dec 2012 15:41:40 +0100
Subject: [PATCH] misc/at24: distinguish between eeprom and fram chips
Add a AT24_FLAGS_FRAM state to the flags to make userspace able to
distinguish if it is using eeprom o
ou know for all the chips out
> there? So, let's still play safe. If you want performance, you need to
> setup the driver properly.
No one knows all chips out there.
For the fm24c04 I use page_size != chip_size. It does not buffer but it has
two pages, 256 bytes each.
-- >8 --
>
On Tuesday 16 October 2012 at 12:58:48, Lars-Peter Clausen wrote:
> On 10/16/2012 11:43 AM, Lars Poeschel wrote:
> > On Tuesday 16 October 2012 at 10:40:26, Lars-Peter Clausen wrote:
> >> On 10/12/2012 04:34 PM, Lars Poeschel wrote:
> >> Btw. I'm wondering why is th
> > > > I wanted to use a fm24c04 i2c fram chip with linux. I grepped the
> > > > source and found nothing. I later found that my chip can be handled
> > > > by at24 eeprom driver. It creates a sysfs file called eeprom to
> > > > read from and write to the chip. Userspace has no chance to
> > > > d
As I got no feedback on the previous patch yet, I answer myself upcounting
the patch version. I had to change the setting of the bus frequency as
there was no usb capable memory used in patch v3
-- >8 --
>From 7a0759ee25a19f7f623543f491be5dee83f195a7 Mon Sep 17 00:00:00 2001
From: Lars Po
On Tuesday 20 November 2012 at 09:34:56, Wolfram Sang wrote:
> I'll try to have a look this week. It fell a bit off because linux-i2c
> was not in CC. I do wonder about the naming, though. VIPERBOARD is
> probably the board name, but not the IP core/SoC name?
I am sorry, that I forgot the CC.
You
From: Lars Poeschel
This driver allows to use a lcd2s 20x4 character display as
a linux console output device.
Signed-off-by: Lars Poeschel
---
drivers/video/console/Kconfig| 10 +
drivers/video/console/Makefile |1 +
drivers/video/console/lcd2scon.c | 396
On Tuesday 20 November 2012 at 14:25:57, Arnd Bergmann wrote:
> On Tuesday 20 November 2012, Lars Poeschel wrote:
> > From: Lars Poeschel
> >
> > This driver allows to use a lcd2s 20x4 character display as
> > a linux console output device.
> >
> > Signed
On Thursday 15 August 2013 at 11:53:15, Tomasz Figa wrote:
> Hi Lars, Linus,
>
> On Tuesday 13 of August 2013 11:46:35 Lars Poeschel wrote:
> > From: Linus Walleij
> >
> > Currently the kernel is ambigously treating GPIOs and interrupts
> > from a GPIO con
7;d be to be able to
instantiate a device from userspace with sysfs, right ?)
The code is ok, so with a modified commit message feel free to add my
Acked-by: Lars Poeschel
> Signed-off-by: Daniel M. Weeks
>
> ---
> drivers/gpio/gpio-mcp23s08.c | 9 -
> 1 file ch
Hi Tony!
On Wednesday 21 August 2013 at 09:50:16, Tony Lindgren wrote:
> Benoit,
>
> Care to take a look at this too?
Benoit already applied this with Mark Rutlands Acked-By and Javier Martinez
Canillas Reviewed-by.
Regards,
Lars
> * Lars Poeschel [130807 04:14]:
> > F
On Monday 19 August 2013 at 21:35:22, Stephen Warren wrote:
> On 08/17/2013 03:59 AM, Tomasz Figa wrote:
> > [Ccing DT maintainers, as they may have some ideas as well]
> >
> > On Saturday 17 of August 2013 02:16:11 Linus Walleij wrote:
> >> On Thu, Aug 15, 2013 at 11:53 AM, Tomasz Figa
wrote:
tree,
check if these in turn reference the interrupt-controller, and
if they do, loop over the interrupts used by that child and
perform gpio_request() and gpio_direction_input() on these,
making them unreachable from the GPIO side.
The patch has been devised by Linus Walleij and Lars Poeschel.
C
Trivial patch to add Microchip Technology Inc. to the list
of devicetree vendor prefixes, as it is already used in
Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
Signed-off-by: Lars Poeschel
---
Documentation/devicetree/bindings/vendor-prefixes.txt |1 +
1 file changed, 1
On Wednesday 21 August 2013 at 19:40:56, Stephen Warren wrote:
> On 08/21/2013 09:19 AM, Lars Poeschel wrote:
> > Trivial patch to add Microchip Technology Inc. to the list
> > of devicetree vendor prefixes, as it is already used in
> > Documentation/devicetree/bindings/g
On Thursday 22 August 2013 at 01:10:27, Stephen Warren wrote:
> On 08/21/2013 03:49 PM, Tomasz Figa wrote:
> >> diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c
> >>
> >> +static void of_gpio_scan_irq_lines(const struct device_node *const
> >>
> >> + for (i = 0; i < int
On Thursday 22 August 2013 at 09:52:49, Florian Fainelli wrote:
> Hello,
>
> 2013/8/22 Lars Poeschel :
> > On Wednesday 21 August 2013 at 19:40:56, Stephen Warren wrote:
> >> On 08/21/2013 09:19 AM, Lars Poeschel wrote:
> >> > Trivial patch to add Microchip T
From: Lars Poeschel
The device tree property should be more descriptive.
microchip seems more reasonable than mcp. As there are no
in tree users of this property, so the rename can still be
done without pain.
Signed-off-by: Lars Poeschel
---
.../devicetree/bindings/gpio/gpio-mcp23s08.txt
From: Lars Poeschel
Trivial patch to add Microchip Technology Inc. to the list
of devicetree vendor prefixes.
Signed-off-by: Lars Poeschel
---
Documentation/devicetree/bindings/vendor-prefixes.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor
On Friday 23 August 2013 at 07:23:00, Rymarkiewicz, WaldemarX wrote:
> Hi Lars,
>
> >This adds a driver for the nxp pn532 nfc chip.
> >It is not meant for merging. Instead it is meant to show that some
> >progress has been made and what the current state is and to help
> >testing.
> >Although I c
On Thursday 22 August 2013 at 23:10:53, Stephen Warren wrote:
> On 08/21/2013 05:36 PM, Linus Walleij wrote:
> > On Thu, Aug 22, 2013 at 1:10 AM, Stephen Warren
> > wrote: [Me]
> >
> check if these in turn reference the interrupt-controller, and
> if they do, loop over the interrupts us
On Thursday 22 August 2013 at 22:53:09, Stephen Warren wrote:
> On 08/21/2013 05:27 PM, Linus Walleij wrote:
> > On Thu, Aug 22, 2013 at 1:10 AM, Stephen Warren
wrote:
> >>> On Wednesday 21 of August 2013 15:38:54 Lars Poeschel wrote:
> >>>> To solv
On Friday 23 August 2013 at 16:24:21, Mark Rutland wrote:
> On Thu, Aug 22, 2013 at 10:56:17AM +0100, Lars Poeschel wrote:
> > From: Lars Poeschel
> >
> > The device tree property should be more descriptive.
> > microchip seems more reasonable than mcp. As there are n
From: Lars Poeschel
Following commit ff5c9059 and therefore other omap platforms using
the gpio-omap driver correct the #interrupt-cells property on am33xx
too. The omap gpio binding documentaion also states that
the #interrupt-cells property should be 2.
Signed-off-by: Lars Poeschel
---
arch
On Wednesday 07 August 2013 at 16:53:09, Mark Rutland wrote:
> On Wed, Aug 07, 2013 at 12:06:32PM +0100, Lars Poeschel wrote:
> > From: Lars Poeschel
> >
> > Following commit ff5c9059 and therefore other omap platforms using
> > the gpio-omap driver correct the #
From: Lars Poeschel
In case request_threaded_irq inside adnp_irq_setup fails, the driver
segfaults. This is because irq_domain_remove is called twice with
the same pointer. First time in adnp_irq_setup and then a second time
after leaving adnp_irq_setup in the error path of adnp_i2c_probe
inside
Am Donnerstag, 8. August 2013, 15:50:18 schrieb Mark Jackson:
> Rebooting appears to have broken in 3.11 (at some point before rc1).
>
> Here is the console output:-
>
> [0.00] Booting Linux on physical CPU 0x0
> [0.00] Linux version 3.11.0-rc1-6-gf550793
> (mpfj@mpfj-nanobone
ric Balletbo i Serra
Cc: Grant Likely
Cc: Jean-Christophe PLAGNIOL-VILLARD
Cc: Santosh Shilimkar
Cc: Kevin Hilman
Cc: Balaji T K
Cc: Tony Lindgren
Cc: Jon Hunter
Signed-off-by: Linus Walleij
Signed-off-by: Lars Poeschel
diff --git a/drivers/gpio/gpiolib-of.c b/drivers/gpio/gpiolib-of.c
in
Am Mittwoch, 31. Juli 2013, 01:44:53 schrieb Linus Walleij:
> On Tue, Jul 30, 2013 at 6:30 AM, Grant Likely
wrote:
> > On Mon, Jul 29, 2013 at 6:36 AM, Linus Walleij
wrote:
> >> To solve this dilemma, perform an interrupt consistency check
> >> when adding a GPIO chip: if the chip is both gpio-
From: Lars Poeschel
This converts the mcp23s08 driver to be able to be used with device
tree.
There is a "spi-present-mask" device tree property, that allows to
use multiple of this spi chips on the same chipselect.
Signed-off-by: Lars Poeschel
---
v3:
- removed mcp,chips device tre
On Sunday 24 February 2013 at 01:14:48, Rob Landley wrote:
> On 02/19/2013 08:27:41 AM, Lars Poeschel wrote:
> > From: Lars Poeschel
> >
> > This adds a simple sysfs interface to the pwm subsystem. It is
> > heavily inspired by the gpio sysfs interface.
>
> Doc
At first: Thanks for your review!
On Monday 25 February 2013 at 05:00:25, Greg KH wrote:
> On Tue, Feb 19, 2013 at 03:27:41PM +0100, Lars Poeschel wrote:
> > +static int pwmchip_export(struct pwm_chip *chip)
> > +{
> > + int status;
> > + struct device *de
On Tuesday 05 March 2013 at 13:21:56, Axel Lin wrote:
> Set it once is enough, and it's done in vprbrd_gpiob_set() which is called
> by vprbrd_gpiob_direction_output().
>
> Signed-off-by: Axel Lin
Thank you!
Tested-and-Acked-by: Lars Poeschel
> ---
> drivers/gpio/g
ation/ABI/testing/sysfs-class-pwm new file mode 100644
> > index 000..e9be1a3
> > --- /dev/null
> > +++ b/Documentation/ABI/testing/sysfs-class-pwm
> > @@ -0,0 +1,37 @@
> > +What: /sys/class/pwm/
> > +Date: March 2013
> > +Ker
On Monday 08 April 2013 at 13:34:58, Thierry Reding wrote:
> By the way, would you mind elaborating a bit on the various use-cases
> that you have? I'm interested in what people use the PWM subsystem for
> and you seem to be the only one currently using it from userspace. I'm
> hoping I can get a b
Hi Oliver!
As you are not the first one asking for the status of the pwm sysfs
interface I post my answer to the linux-kernel list in hope others will
benefit.
On Thursday 23 May 2013 at 11:07:39, Oliver Schinagl wrote:
> Hi lars,
>
> I have trouble seeing if your patch has been applied yet to
From: Lars Poeschel
The gpmc driver is actually looking for "gpmc,num-cs" and
"gpmc,num-waitpins" properties in DT. The binding doc also states
this.
Correct the properties in the dts to provide the right values for the
gpmc driver.
Signed-off-by: Lars Poeschel
--
t; Do you think that would be acceptable?
> >
> > That would be for Thierry to decide. It does sound better to me than
> > the 1) and I don't have a better idea for 3).
> >
> > I wonder how the arbitration between in-kernel and user-space
> > consumers of t
On Friday 22 March 2013 at 09:33:10, Linus Walleij wrote:
> > +++ b/Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
> > @@ -0,0 +1,43 @@
> > +Microchip MCP2308/MCP23S08/MCP23017/MCP23S17 driver for
> > +8-/16-bit I/O expander with serial interface (I2C/SPI)
> > +
> > +Required properties:
On Monday 11 February 2013 at 22:25:51, Grant Likely wrote:
> On Mon, 11 Feb 2013 12:52:42 +0100, Lars Poeschel
wrote:
> > +Optional device specific properties:
> > +- mcp,chips : This is a table with 2 columns and up to 8 entries. The
> > first column + is a is_pre
On Wednesday 13 February 2013 at 13:51:12, Linus Walleij wrote:
> On Wed, Feb 13, 2013 at 12:13 PM, Lars Poeschel
wrote:
> > On Monday 11 February 2013 at 22:25:51, Grant Likely wrote:
> >> However, is the pullup selection per-gpio line? If so, then why not
> >> encode
From: Lars Poeschel
This adds the mfd cell to use the gpio a and gpio b part
of the Nano River Technologies viperboard.
Signed-off-by: Lars Poeschel
---
drivers/gpio/Kconfig | 13 ++
drivers/gpio/Makefile |1 +
drivers/gpio/gpio-viperboard.c | 482
From: Lars Poeschel
This adds the mfd cell to use the i2c part of the Nano River Technologies
viperboard as i2c master.
Signed-off-by: Lars Poeschel
---
drivers/i2c/busses/Kconfig | 10 +
drivers/i2c/busses/Makefile |1 +
drivers/i2c/busses/i2c-viperboard.c | 442
From: Lars Poeschel
This adds the mfd cell to use the adc part of the Nano River Technologies
viperboard.
Signed-off-by: Lars Poeschel
---
drivers/iio/adc/Kconfig |7 ++
drivers/iio/adc/Makefile |1 +
drivers/iio/adc/viperboard_adc.c | 185
From: Lars Poeschel
Add mfd driver for Nano River Technologies viperboard.
Signed-off-by: Lars Poeschel
---
drivers/mfd/Kconfig| 14
drivers/mfd/Makefile |1 +
drivers/mfd/viperboard.c | 149
include/linux/mfd
On Monday 15 October 2012 at 15:00:12, Linus Walleij wrote:
> > +#define VPRBRD_GPIOA_CLK_1 0 /* (1us = 1MHz)
> > */ +#define VPRBRD_GPIOA_CLK_101 /* (10us =
> > 100kHz) */ +#define VPRBRD_GPIOA_CLK_100 2 /* (100us
> > = 10kHz)
On Monday 15 October 2012 at 16:26:36, Lars-Peter Clausen wrote:
> Added linux-...@vger.kernel.org to Cc.
>
> On 10/12/2012 04:34 PM, Lars Poeschel wrote:
> > From: Lars Poeschel
> >
> > This adds the mfd cell to use the adc part of the Nano River Technologies
>
On Monday 15 October 2012 at 19:09:53, Peter Meerwald wrote:
> minor nitpicking below
>
> > From: Lars Poeschel
> >
> > Add mfd driver for Nano River Technologies viperboard.
> >
> > Signed-off-by: Lars Poeschel
> > ---
> >
> > drive
On Tuesday 16 October 2012 at 10:40:26, Lars-Peter Clausen wrote:
> On 10/12/2012 04:34 PM, Lars Poeschel wrote:
> > [...]
> > +static void vprbrd_dev_release(struct device *dev)
> > +{
> > + return;
>
> A empty release callback is usually a good indicator that
On Tuesday 16 October 2012 at 12:00:13, Linus Walleij wrote:
> On Tue, Oct 16, 2012 at 8:51 AM, Lars Poeschel wrote:
> > On Monday 15 October 2012 at 15:00:12, Linus Walleij wrote:
> >> > + /* if io is set to output, just return the saved value */
> >> >
From: Lars Poeschel
This driver allows to use a lcd2s 20x4 character display as
a linux console output device.
Signed-off-by: Lars Poeschel
---
drivers/video/console/Kconfig| 10 ++
drivers/video/console/Makefile |1 +
drivers/video/console/lcd2scon.c | 360
From: Lars Poeschel
The query for the viperboard version was done with memory buffer
on the stack but usb transfers need dma capable memory buffer.
This is fixed now.
Signed-off-by: Lars Poeschel
---
drivers/mfd/viperboard.c |9 -
1 file changed, 4 insertions(+), 5 deletions
Hi Matt,
On Friday 11 January 2013 at 06:48:39, Matt Porter wrote:
> diff --git a/arch/arm/common/edma.c b/arch/arm/common/edma.c
> index a3d189d..1951d63 100644
> --- a/arch/arm/common/edma.c
> +++ b/arch/arm/common/edma.c
> @@ -24,6 +24,13 @@
> #include
> #include
> #include
> +#include
From: Lars Poeschel
This driver allows to use a lcd2s 20x4 character display as
a linux console output device.
Signed-off-by: Lars Poeschel
---
drivers/video/console/Kconfig| 10 ++
drivers/video/console/Makefile |1 +
drivers/video/console/lcd2scon.c | 360
1 - 100 of 204 matches
Mail list logo
