Instead of supplying platform data to the shdma dmaengine driver via
AUXDATA in the DT case, we now support platform data via an OF match table.
Make platform data optional.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/shdma-of.c |3 ---
1 files changed, 0 insertions(+), 3
This configuration data will be re-used, when DMAC DT support is added to
r8a73a4.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/Kconfig |4 ++
drivers/dma/sh/Makefile|1 +
drivers/dma/sh/shdma-r8a73a4.c | 75
drivers
This configuration data will be re-used, when DMAC DT support is added to
sh73a0, DMAC platform data in setup-sh73a0.c will be removed.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/Kconfig|4 +
drivers/dma/sh/Makefile |1 +
drivers/dma/sh/shdma-sh73a0.c | 181
Platform data shouldn't be changed at run-time, so, pointers to it should
be const.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/shdma.h |2 +-
drivers/dma/sh/shdmac.c | 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/dma/sh/shdma.h b
Similar to the non-DT case, this patch passes SoC-specific configuration
to the driver via device ID matching, instead of platform data.
Signed-off-by: Guennadi Liakhovetski
---
v2: adjust spacing within array definitions to keep a uniform style.
Documentation/devicetree/bindings/dma
of them.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/Makefile |2 ++
drivers/dma/sh/{shdma.c => shdmac.c} | 11 ++-
2 files changed, 12 insertions(+), 1 deletions(-)
rename drivers/dma/sh/{shdma.c => shdmac.c} (98%)
diff --git a/drivers/dma/sh/Make
of them.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/Makefile |2 ++
drivers/dma/sh/{shdma.c = shdmac.c} | 11 ++-
2 files changed, 12 insertions(+), 1 deletions(-)
rename drivers/dma/sh/{shdma.c = shdmac.c} (98%)
diff --git
Similar to the non-DT case, this patch passes SoC-specific configuration
to the driver via device ID matching, instead of platform data.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
v2: adjust spacing within array definitions to keep a uniform style.
Documentation
This configuration data will be re-used, when DMAC DT support is added to
sh73a0, DMAC platform data in setup-sh73a0.c will be removed.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/Kconfig|4 +
drivers/dma/sh/Makefile |1
Platform data shouldn't be changed at run-time, so, pointers to it should
be const.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/shdma.h |2 +-
drivers/dma/sh/shdmac.c | 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git
This configuration data will be re-used, when DMAC DT support is added to
r8a73a4.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/Kconfig |4 ++
drivers/dma/sh/Makefile|1 +
drivers/dma/sh/shdma-r8a73a4.c | 75
Instead of supplying platform data to the shdma dmaengine driver via
AUXDATA in the DT case, we now support platform data via an OF match table.
Make platform data optional.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/shdma-of.c |3 ---
1 files
This configuration data will be re-used, when DMAC DT support is added to
r8a7740, DMAC platform data in setup-r8a7740.c will be removed.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/Kconfig |4 ++
drivers/dma/sh/Makefile|1
.
Otherwise the ARM patches will have to wait for 1 cycle.
Guennadi Liakhovetski (15):
DMA: shdma: add support for DMAC configuration data, supplied via
device ID
DMA: shdma: add r8a7740 DMAC data to the device ID table
DMA: shdma: add r8a73a4 DMAC data to the device ID table
DMA: shdma: make
Move two generic pointer-conversion macros to a header for common shdma use.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/shdma-base.c |3 ---
drivers/dma/sh/shdma-of.c |2 --
include/linux/shdma-base.h |3 +++
3 files changed, 3
this option a #dma-cells property also must be
added to the respective DMAC DT node.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
Documentation/devicetree/bindings/dma/shdma.txt | 16 ++
drivers/dma/sh/shdma.h |7 +++
drivers/dma/sh/shdmac.c
In addition to 3 SYS-DMACs, r817740 SoCs also have 2 RT-DMACs. This patch
adds support for them in both DT- amd non-DT-modes.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
arch/arm/boot/dts/r8a7740.dtsi | 34 +++
arch/arm/mach-shmobile/clock
This patch removes DMAC platform data on r8a7740 and switches to using
device ID data.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
arch/arm/mach-shmobile/clock-r8a7740.c |6 +-
arch/arm/mach-shmobile/setup-r8a7740.c | 106 +---
2
Add a DMAC platform device and clock definitions for it on r8a73a4.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
arch/arm/mach-shmobile/clock-r8a73a4.c|4 +++-
arch/arm/mach-shmobile/include/mach/r8a73a4.h |9 +
arch/arm/mach-shmobile/setup
This patch removes DMAC platform data on sh73a0 and switches to using
device ID data.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
arch/arm/mach-shmobile/clock-sh73a0.c |2 +-
arch/arm/mach-shmobile/setup-sh73a0.c | 182 +
2 files
Add a DT node for the only system DMAC instance on r8a73a4. The RT DMAC
can be added later under the same multiplexer, because they can serve the
same slaves and use the same MID-RID values. Configuration data is
supplied to the driver, using a compatibility match string.
Signed-off-by: Guennadi
This patch adds Device Tree support for the three generic DMA controller
instances on r8a7740 in a DMA multiplexer node.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
v2: Use dma-controller for DMA controller DT nodes
arch/arm/boot/dts/r8a7740.dtsi | 61
This patch adds Device Tree support for the three generic DMA controller
instances on r8a7740 in a DMA multiplexer node.
Signed-off-by: Guennadi Liakhovetski
---
arch/arm/boot/dts/r8a7740.dtsi | 61
arch/arm/mach-shmobile/clock-r8a7740.c |3 ++
2
This patch removes DMAC platform data on r8a7740 and switches to using
device ID data.
Signed-off-by: Guennadi Liakhovetski
---
Simon: this patch should only be applied after DMA driver changes,
otherwise DMA on r8a7740 will be broken. We can delay this patch
for one more kernel version
This configuration data will be re-used, when DMAC DT support is added to
r8a73a4.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/Kconfig |4 ++
drivers/dma/sh/Makefile|1 +
drivers/dma/sh/shdma-r8a73a4.c | 75
drivers
Add a DMAC platform device and clock definitions for it on r8a73a4.
Signed-off-by: Guennadi Liakhovetski
---
Simon: this patch supersedes my earlier patch "ARM: shmobile: r8a73a4: add
a DMAC platform device and clock for it". With this approach we also don't
have a build dependency
Similar to the non-DT case, this patch passes SoC-specific configuration
to the driver via device ID matching, instead of platform data.
Signed-off-by: Guennadi Liakhovetski
---
Documentation/devicetree/bindings/dma/shdma.txt |7 +--
drivers/dma/sh/shdmac.c
This configuration data will be re-used, when DMAC DT support is added to
r8a7740, DMAC platform data in setup-r8a7740.c will be removed.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/Kconfig |4 ++
drivers/dma/sh/Makefile|1 +
drivers/dma/sh/shdma-r8a7740.c
's renesas.git devel branch.
Cc: Guennadi Liakhovetski
Guennadi Liakhovetski (8):
DMA: shdma: add support for DMAC configuration data, supplied via
device ID
DMA: shdma: add r8a7740 DMAC data to the device ID table
DMA: shdma: add r8a73a4 DMAC data to the device ID table
ARM: shmobile:
of them.
Signed-off-by: Guennadi Liakhovetski
---
A file has to be renamed to preserve the driver module name.
drivers/dma/sh/Makefile |2 ++
drivers/dma/sh/{shdma.c => shdmac.c} | 11 ++-
2 files changed, 12 insertions(+), 1 deletions(-)
rename drivers/dma/sh/{shdm
Instead of supplying platform data to the shdma dmaengine driver via
AUXDATA in the DT case, we now support platform data via an OF match table.
Make platform data optional.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/shdma-of.c |3 ---
1 files changed, 0 insertions(+), 3
of them.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
A file has to be renamed to preserve the driver module name.
drivers/dma/sh/Makefile |2 ++
drivers/dma/sh/{shdma.c = shdmac.c} | 11 ++-
2 files changed, 12 insertions(+), 1 deletions
Instead of supplying platform data to the shdma dmaengine driver via
AUXDATA in the DT case, we now support platform data via an OF match table.
Make platform data optional.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/shdma-of.c |3 ---
1 files
This configuration data will be re-used, when DMAC DT support is added to
r8a7740, DMAC platform data in setup-r8a7740.c will be removed.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/Kconfig |4 ++
drivers/dma/sh/Makefile|1
.
Cc: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
Guennadi Liakhovetski (8):
DMA: shdma: add support for DMAC configuration data, supplied via
device ID
DMA: shdma: add r8a7740 DMAC data to the device ID table
DMA: shdma: add r8a73a4 DMAC data to the device ID table
ARM
Add a DMAC platform device and clock definitions for it on r8a73a4.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
Simon: this patch supersedes my earlier patch ARM: shmobile: r8a73a4: add
a DMAC platform device and clock for it. With this approach we also don't
have
Similar to the non-DT case, this patch passes SoC-specific configuration
to the driver via device ID matching, instead of platform data.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
Documentation/devicetree/bindings/dma/shdma.txt |7 +--
drivers/dma/sh
This configuration data will be re-used, when DMAC DT support is added to
r8a73a4.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/Kconfig |4 ++
drivers/dma/sh/Makefile|1 +
drivers/dma/sh/shdma-r8a73a4.c | 75
This patch removes DMAC platform data on r8a7740 and switches to using
device ID data.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
Simon: this patch should only be applied after DMA driver changes,
otherwise DMA on r8a7740 will be broken. We can delay this patch
This patch adds Device Tree support for the three generic DMA controller
instances on r8a7740 in a DMA multiplexer node.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
arch/arm/boot/dts/r8a7740.dtsi | 61
arch/arm/mach
layout.
Signed-off-by: Guennadi Liakhovetski
---
v2: remove merge order dependency. This version can be merged without
requiring platforms to adjust their platform data. Only new SoCs with
bitwise CHCLR layouts will have to use new platform data fields.
drivers/dma/sh/shdma.c | 14
layout.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
v2: remove merge order dependency. This version can be merged without
requiring platforms to adjust their platform data. Only new SoCs with
bitwise CHCLR layouts will have to use new platform data fields.
drivers/dma
Hi
The first two patches in this small series improve driver internals a bit
by using preferred APIs, the 3rd patch adds support for new DMAC versions,
present on AG5, APE6, H2.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open
Switch shdma to using devm_* managed functions for allocation of memory,
requesting IRQs, mapping IO resources etc.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/shdma-base.c | 11 +-
drivers/dma/sh/shdma.c | 71 ---
drivers/dma/sh
ich avoids this clumsiness.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/shdma.c | 22 +++---
drivers/dma/sh/shdma.h |6 +++---
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/dma/sh/shdma.c b/drivers/dma/sh/shdma.c
index 3083d62..64eb
layout.
Signed-off-by: Guennadi Liakhovetski
---
drivers/dma/sh/shdma.c |6 --
include/linux/sh_dma.h | 12 +++-
2 files changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/sh/shdma.c b/drivers/dma/sh/shdma.c
index 64eb7fb..883a4de 100644
--- a/drivers/dma/sh/shdma.c
struct sh_dmae_device::chan_reg is a pointer to u32, therefore when adding
offsets to it care should be taken to add offsets in sizeof(u32) units, not
in bytes. This patch corrects such a bug. While at it we also remove the
redundant parameter of the affected function.
Signed-off-by: Guennadi
struct sh_dmae_device::chan_reg is a pointer to u32, therefore when adding
offsets to it care should be taken to add offsets in sizeof(u32) units, not
in bytes. This patch corrects such a bug. While at it we also remove the
redundant parameter of the affected function.
Signed-off-by: Guennadi
Switch shdma to using devm_* managed functions for allocation of memory,
requesting IRQs, mapping IO resources etc.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/shdma-base.c | 11 +-
drivers/dma/sh/shdma.c | 71
this clumsiness.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/shdma.c | 22 +++---
drivers/dma/sh/shdma.h |6 +++---
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/dma/sh/shdma.c b/drivers/dma/sh/shdma.c
index
Hi
The first two patches in this small series improve driver internals a bit
by using preferred APIs, the 3rd patch adds support for new DMAC versions,
present on AG5, APE6, H2.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open
layout.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/dma/sh/shdma.c |6 --
include/linux/sh_dma.h | 12 +++-
2 files changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/sh/shdma.c b/drivers/dma/sh/shdma.c
index 64eb7fb..883a4de
859/
a patch series has been submitted by your employer to support the da9063
PMIC. Are there plans to continue that work and update the driver? Any
specific dates when a new submission can be expected?
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
h
/
a patch series has been submitted by your employer to support the da9063
PMIC. Are there plans to continue that work and update the driver? Any
specific dates when a new submission can be expected?
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http
Fix a s/maxium/maxim/ typo in DT binding documentation.
Reported-by: Sergei Shtylyov
Signed-off-by: Guennadi Liakhovetski
---
Mark, if still possible, feel free to merge this with the original patch.
Thanks
Guennadi
.../bindings/regulator/max8973-regulator.txt |4 ++--
1 files
Fix a s/maxium/maxim/ typo in DT binding documentation.
Reported-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
Mark, if still possible, feel free to merge this with the original patch.
Thanks
Guennadi
On Mon, 24 Jun 2013, Sergei Shtylyov wrote:
> Hello.
>
> On 06/24/2013 02:50 PM, Guennadi Liakhovetski wrote:
>
> > This patch adds primitive DT support to the max8973 regulator driver. None
> > of the configuration parameters, supported in the platform data are
, where no run-time configuration of the chip is required. In such
cases the driver can be used to scale its output voltage. In the future
support for configuration parameters should be added.
Signed-off-by: Guennadi Liakhovetski
---
v2: as suggested by Mark, regulator bindings are now directly
, where no run-time configuration of the chip is required. In such
cases the driver can be used to scale its output voltage. In the future
support for configuration parameters should be added.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
v2: as suggested by Mark
On Mon, 24 Jun 2013, Sergei Shtylyov wrote:
Hello.
On 06/24/2013 02:50 PM, Guennadi Liakhovetski wrote:
This patch adds primitive DT support to the max8973 regulator driver. None
of the configuration parameters, supported in the platform data are yet
available in DT, therefore
On Sat, 22 Jun 2013, Prabhakar Lad wrote:
> From: "Lad, Prabhakar"
>
> Both synchronous and asynchronous tvp514x subdevice probing is supported by
> this patch.
>
> Signed-off-by: Prabhakar Lad
> Cc: Guennadi Liakhovetski
> Cc: Laurent Pinchart
> Cc: H
On Sun, 23 Jun 2013, Guennadi Liakhovetski wrote:
> On Sat, 22 Jun 2013, Prabhakar Lad wrote:
>
> > From: "Lad, Prabhakar"
> >
> > Both synchronous and asynchronous adv7343 subdevice probing is supported by
> > this patch.
> >
> > Signed-o
On Sat, 22 Jun 2013, Prabhakar Lad wrote:
> From: "Lad, Prabhakar"
>
> Both synchronous and asynchronous adv7343 subdevice probing is supported by
> this patch.
>
> Signed-off-by: Lad, Prabhakar
> Cc: Guennadi Liakhovetski
> Cc: Laurent Pinchart
> Cc: H
On Sat, 22 Jun 2013, Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
Both synchronous and asynchronous adv7343 subdevice probing is supported by
this patch.
Signed-off-by: Lad, Prabhakar prabhakar.cse...@gmail.com
Cc: Guennadi Liakhovetski g.liakhovet...@gmx.de
Cc
On Sun, 23 Jun 2013, Guennadi Liakhovetski wrote:
On Sat, 22 Jun 2013, Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
Both synchronous and asynchronous adv7343 subdevice probing is supported by
this patch.
Signed-off-by: Lad, Prabhakar prabhakar.cse
On Sat, 22 Jun 2013, Prabhakar Lad wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
Both synchronous and asynchronous tvp514x subdevice probing is supported by
this patch.
Signed-off-by: Prabhakar Lad prabhakar.cse...@gmail.com
Cc: Guennadi Liakhovetski g.liakhovet...@gmx.de
Cc
Hi Mark
Thanks for the review
On Fri, 21 Jun 2013, Mark Brown wrote:
> On Fri, Jun 21, 2013 at 08:30:26AM +0200, Guennadi Liakhovetski wrote:
>
> > +Required properties:
> > +
> > +- compatible: must be "maxium,max8973"
> > +- reg:
DA9210_DVC_CTRL_EN 0x80
> +
> +/* DA9210_REG_BUCK_ILIM (addr=0xD0) */
> +#define DA9210_BUCK_ILIM_SHIFT 0
> +#define DA9210_BUCK_ILIM_MASK 0x0F
> +#define DA9210_BUCK_IALARM 0x10
> +
> +/* DA9210_REG_B
, where no run-time configuration of the chip is required. In such
cases the driver can be used to scale its output voltage. In the future
support for configuration parameters should be added.
Signed-off-by: Guennadi Liakhovetski
---
.../bindings/regulator/max8973-regulator.txt | 25
of the struct for each chip instance.
Signed-off-by: Guennadi Liakhovetski
---
drivers/regulator/max8973-regulator.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/regulator/max8973-regulator.c
b/drivers/regulator/max8973-regulator.c
index adb1414
of the struct for each chip instance.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
drivers/regulator/max8973-regulator.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/regulator/max8973-regulator.c
b/drivers/regulator
, where no run-time configuration of the chip is required. In such
cases the driver can be used to scale its output voltage. In the future
support for configuration parameters should be added.
Signed-off-by: Guennadi Liakhovetski g.liakhovetski+rene...@gmail.com
---
.../bindings/regulator/max8973
) */
+#define DA9210_IF_BASE_ADDR_SHIFT4
+#define DA9210_IF_BASE_ADDR_MASK 0xF0
+
+/* DA9210_REG_CONFIG_E (addr=0x147) */
+#define DA9210_STAND_ALONE 0x01
+
+#endif /* __DA9210_REGISTERS_H__ */
+
--
end-of-patch for RFC V1
---
Guennadi
Hi Mark
Thanks for the review
On Fri, 21 Jun 2013, Mark Brown wrote:
On Fri, Jun 21, 2013 at 08:30:26AM +0200, Guennadi Liakhovetski wrote:
+Required properties:
+
+- compatible: must be maxium,max8973
+- reg: the i2c slave address of the regulator. It should
media and Video Capture.
>
> Any Discussion?
>
> Is the response to this question something to the effect
> of "sure... Start writing a driver any time you want..."
>
> Thanks.
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://
Capture.
Any Discussion?
Is the response to this question something to the effect
of sure... Start writing a driver any time you want...
Thanks.
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send
Hi
On Tue, 30 Apr 2013, Guennadi Liakhovetski wrote:
> of_parse_phandle_with_args() and of_count_phandle_with_args() functions
> are declared with their first parameter as const. However, their
> respective stubs, used when CONFIG_OF isn't defined, don't have the "const"
>
Hi
On Tue, 30 Apr 2013, Guennadi Liakhovetski wrote:
of_parse_phandle_with_args() and of_count_phandle_with_args() functions
are declared with their first parameter as const. However, their
respective stubs, used when CONFIG_OF isn't defined, don't have the const
modifier. This patch adds
On Wed, 5 Jun 2013, Will Deacon wrote:
> On Mon, May 27, 2013 at 08:11:07AM +0100, Andy Shevchenko wrote:
> > On Fri, 2013-05-24 at 23:55 +0200, Guennadi Liakhovetski wrote:
> > > On Thu, 23 May 2013, Andy Shevchenko wrote:
> > >
> > > > When user inter
Hi Rafael
On Wed, 22 May 2013, Rafael J. Wysocki wrote:
> On Wednesday, May 22, 2013 08:12:22 PM Guennadi Liakhovetski wrote:
> > Hi Rafael
> >
> > I don't see this patch in your cpufreq branch nor in next or Linus' trees,
> > has it been pulled yet?
>
> No, I
Hi Rafael
On Wed, 22 May 2013, Rafael J. Wysocki wrote:
On Wednesday, May 22, 2013 08:12:22 PM Guennadi Liakhovetski wrote:
Hi Rafael
I don't see this patch in your cpufreq branch nor in next or Linus' trees,
has it been pulled yet?
No, I haven't applied it yet, not sure why
On Wed, 5 Jun 2013, Will Deacon wrote:
On Mon, May 27, 2013 at 08:11:07AM +0100, Andy Shevchenko wrote:
On Fri, 2013-05-24 at 23:55 +0200, Guennadi Liakhovetski wrote:
On Thu, 23 May 2013, Andy Shevchenko wrote:
When user interrupts ongoing transfers the dmatest may end up
ed_test(info, bv);
> +
> + if (__is_threaded_test_run(info))
> + ret = -EBUSY;
> + else
> + ret = __restart_threaded_test(info, bv);
> +
> mutex_unlock(>lock);
> }
>
> --
>
-info.html
Please read the FAQ at http://www.tux.org/lkml/
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
On Wed, 22 May 2013, Felipe Ferreri Tonello wrote:
> Hi Guennadi,
>
> On Wednesday, May 22, 2013 10:30:40 PM Guennadi Liakhovetski wrote:
> > On Wed, 22 May 2013, Felipe F. Tonello wrote:
> > > From: "Felipe F. Tonello"
> > >
> > > This is
On Wed, 22 May 2013, Felipe Ferreri Tonello wrote:
Hi Guennadi,
On Wednesday, May 22, 2013 10:30:40 PM Guennadi Liakhovetski wrote:
On Wed, 22 May 2013, Felipe F. Tonello wrote:
From: Felipe F. Tonello e...@felipetonello.com
This is useful for power managment purposes if a sdhci
_MMC_SDHCI_IO_ACCESSORS
> --
> 1.8.1.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
---
Guennadi Liakhovets
Hi Rafael
I don't see this patch in your cpufreq branch nor in next or Linus' trees,
has it been pulled yet?
Thanks
Guennadi
On Thu, 28 Mar 2013, Shawn Guo wrote:
> On Wed, Mar 27, 2013 at 11:46:38PM +0100, Guennadi Liakhovetski wrote:
> > Hi Shawn
> >
> > On Mon,
Hi Rafael
I don't see this patch in your cpufreq branch nor in next or Linus' trees,
has it been pulled yet?
Thanks
Guennadi
On Thu, 28 Mar 2013, Shawn Guo wrote:
On Wed, Mar 27, 2013 at 11:46:38PM +0100, Guennadi Liakhovetski wrote:
Hi Shawn
On Mon, 25 Feb 2013, Guennadi Liakhovetski
/majordomo-info.html
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
, my task description says "a da9210 PMIC." I think this one is meant:
http://www.dialog-semiconductor.com/products/power-management/DA9210
Thanks
Guennadi
> Best regards,
>
> Tony Olech
>
>
> > -Original Message-
> > From: Guennadi Liakhovetski
Hi Tony
On Thu, 9 May 2013, Anthony Olech wrote:
> Hi Guennadi Liakhovetski,
>
> Now that Krystian no longer works for Dialog I think that I might be
> your best contact.
> As far as I am aware without doing any checking, the DA906x driver
> should possibly cover the DA9063
; this out.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/
of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
To unsubscribe from this list: send
Hi Tony
On Thu, 9 May 2013, Anthony Olech wrote:
Hi Guennadi Liakhovetski,
Now that Krystian no longer works for Dialog I think that I might be
your best contact.
As far as I am aware without doing any checking, the DA906x driver
should possibly cover the DA9063.
Good!
If you need
://www.dialog-semiconductor.com/products/power-management/DA9210
Thanks
Guennadi
Best regards,
Tony Olech
-Original Message-
From: Guennadi Liakhovetski [mailto:g.liakhovet...@gmx.de]
Sent: 09 May 2013 15:29
To: Anthony Olech
Cc: Krystian Garbaciak; Mark Brown; linux
On Wed, 8 May 2013, Guennadi Liakhovetski wrote:
> Hi
>
> Based on an old (2.6.35) configuration for my PC I updated to 3.9.1 and
> went through make config, automatically called by make bzImage, the
> resulted configuration couldn't be built:
A "make distclean" f
On Wed, 8 May 2013, Guennadi Liakhovetski wrote:
Hi
Based on an old (2.6.35) configuration for my PC I updated to 3.9.1 and
went through make config, automatically called by make bzImage, the
resulted configuration couldn't be built:
A make distclean fixed it.
Thanks
Guennadi
scripts
On Thu, 2 May 2013, Vinod Koul wrote:
> On Tue, Apr 30, 2013 at 02:17:13PM +0200, Guennadi Liakhovetski wrote:
> > (added Russell to CC, sorry for not including initially)
> >
> > Hi Vinod
> >
> > On Tue, 30 Apr 2013, Vinod Koul wrote:
> >
> &g
Hi Chris, Simon, Vinod (in alphabetical order :-) )
On Thu, 11 Apr 2013, Guennadi Liakhovetski wrote:
> This patch series adds Device Tree support to the shdma dmaengine driver
> and illustraits its use with the kzm9g-reference board's MMCIF interface.
Formally patches in this series
401 - 500 of 1041 matches
Mail list logo
