[linux-sunxi] SUN4i CSI

Hi everyone I'm working on the CSI driver.I failed to understand ( lack of documentation) which DMA is used to transfer from the CSI. I can only find a reference in the bsp driver for the DRAM CPU_DRAM_PADDR_ORG = 0x4000 HW_DMA_OFFSET= 0x dma_addr_t addr_org =

Re: [linux-sunxi] Re: [PATCH 0/4] Add AXP209 GPIO driver

Hi, On 09-03-16 16:28, Maxime Ripard wrote: Hi, On Wed, Mar 09, 2016 at 01:17:50PM +0100, Hans de Goede wrote: Hi, On 09-03-16 11:50, Maxime Ripard wrote: Hi, The axp209 PMIC used in combination to some Allwinner SoCs has a bunch of GPIOs accessible. Some boards use these to control their

[linux-sunxi] Re: [PATCH 0/4] Add AXP209 GPIO driver

Hi, On Wed, Mar 09, 2016 at 01:17:50PM +0100, Hans de Goede wrote: > Hi, > > On 09-03-16 11:50, Maxime Ripard wrote: > >Hi, > > > >The axp209 PMIC used in combination to some Allwinner SoCs has a bunch > >of GPIOs accessible. Some boards use these to control their backlight > >or a few LEDs. >

Re: [linux-sunxi] [PATCH 1/4] gpio: Add AXP209 GPIO driver

> "Maxime" == Maxime Ripard writes: > The AXP209 PMIC has a bunch of GPIOs accessible, that are usually used to > control LEDs or backlight. Do you find 3 'a bunch'? ;) > +static int axp20x_gpio_probe(struct platform_device *pdev) > +{ > +struct

[linux-sunxi] Re: [PATCH 1/4] gpio: Add AXP209 GPIO driver

Hi Maxime, [auto build test ERROR on gpio/for-next] [also build test ERROR on next-20160309] [cannot apply to v4.5-rc7] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Maxime-Ripard/Add-AXP209

[linux-sunxi] Re: [PATCH 0/4] Add AXP209 GPIO driver

Hi, On 09-03-16 11:50, Maxime Ripard wrote: Hi, The axp209 PMIC used in combination to some Allwinner SoCs has a bunch of GPIOs accessible. Some boards use these to control their backlight or a few LEDs. Thanks for working on this, but IMHO this cannot go upstream like this, the gpio pins on

[linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users

On Tue, 8 Mar 2016 08:25:47 +0530 Vinod Koul wrote: > > Why does dmaengine need to wait? Can you explain that I don't have an answer for that one, but when I set WAIT_CYCLES to 1 for the NAND use case it does not work. So I guess it is somehow related to how the DRQ line

Re: [linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users

On Tue, Mar 08, 2016 at 03:35:38PM +0530, Vinod Koul wrote: > On Tue, Mar 08, 2016 at 09:42:31AM +0100, Hans de Goede wrote: > > > > > > I see 2 possible reasons why waiting till checking for drq can help: > > > > 1) A lot of devices have an internal fifo hooked up to a single mmio data > >

[linux-sunxi] [PATCH 2/4] mfd: axp20x: Add AXP209 GPIO driver to the mfd

Now that we have a GPIO driver for the AXP209, we can add it to our MFD. Signed-off-by: Maxime Ripard --- drivers/mfd/axp20x.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/mfd/axp20x.c b/drivers/mfd/axp20x.c index a57d6e940610..89518ee3be33

[linux-sunxi] [PATCH 0/4] Add AXP209 GPIO driver

Hi, The axp209 PMIC used in combination to some Allwinner SoCs has a bunch of GPIOs accessible. Some boards use these to control their backlight or a few LEDs. There's supposed to be 4 of them, but the fourth one has a different configuration register scheme, and I couldn't find any board that

[linux-sunxi] [PATCH 1/4] gpio: Add AXP209 GPIO driver

The AXP209 PMIC has a bunch of GPIOs accessible, that are usually used to control LEDs or backlight. Add a driver for them Signed-off-by: Maxime Ripard --- .../devicetree/bindings/gpio/gpio-axp209.txt | 30 drivers/gpio/Kconfig

[linux-sunxi] [PATCH 4/4] ARM: sun5i: chip: Add status LED

The CHIP has a status LED connected to one of the AXP GPIOs. Add the gpio-leds node to be able to use the proper LED framework to control it. Signed-off-by: Maxime Ripard --- arch/arm/boot/dts/sun5i-r8-chip.dts | 10 ++ 1 file changed, 10 insertions(+)

Re: [linux-sunxi] Re: [PATCH] dma: sun4i: expose block size and wait cycle configuration to DMA users

> > > > It doesn't really makes sense to us, but it does have a significant > > impact on the throughput. > > I wouldn't say significant impact, but tweaking those parameters has > some impact on the performances, and since it's not that complicated to > implement, I thought it was worth a try,