On 07/10/2013 03:15 PM, Laxman Dewangan wrote:
> This patch series does following:
> - Remove unused member from extcon palmas structure.
> - Fix to support of detecting cable properly with multiple insert/removal.
> - Add support for suspend/resume functionlaity and wakup from suspend.
> - Option
Hi Laxman,
On 07/10/2013 03:15 PM, Laxman Dewangan wrote:
> Based on system design, platform needs to detect the VBUS or ID or
> both. Provide option to select this through platform data to
> disable part of cable detection through palmas-usb.
>
> Signed-off-by: Laxman Dewangan
> Acked-by: Grae
Hi Richard,
On 7/9/2013 22:25, Richard Genoud wrote:
[snip]
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+#include
+
+#include
+
+#include
+#include
+#include
+#include
+
+#include
+#include
+#include
+
+#include "../codecs/wm8731.h"
+#include "atmel-pcm
Based on system design, platform needs to detect the VBUS or ID or
both. Provide option to select this through platform data to
disable part of cable detection through palmas-usb.
Signed-off-by: Laxman Dewangan
Acked-by: Graeme Gregory
---
No changes from V1.
.../devicetree/bindings/extcon/ext
Add suspend/resume callbacks and support for wakeup from
suspend on USB HOST or USB Device cable insertion or removal.
Signed-off-by: Laxman Dewangan
Acked-by: Graeme Gregory
---
No changes from V1.
drivers/extcon/extcon-palmas.c | 38 +++---
1 files changed,
When integrating driver with Tegra platform, it is found that
the ID pins get detected only once after booting system and
further removal and re-insert does not detect the ID pin.
Fixing this issue with enabling interrupt on ID_GND and ID_FLOAT
always and clearing the status on LATCH register whi
This patch series does following:
- Remove unused member from extcon palmas structure.
- Fix to support of detecting cable properly with multiple insert/removal.
- Add support for suspend/resume functionlaity and wakup from suspend.
- Option to select/de-select the ID or VBUS detection.
Changes fr
Remove unused member vbus_enable and set_vbus_work from palmas_usb
as these members are not used in drivers.
Signed-off-by: Laxman Dewangan
Acked-by: Graeme Gregory
---
No changes from V1.
include/linux/mfd/palmas.h |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/i
On Wed, Jul 10, 2013 at 5:16 AM, Arnd Bergmann wrote:
> On Tuesday 09 July 2013, Thomas Petazzoni wrote:
>> Dear Neil Zhang,
>>
>> On Tue, 9 Jul 2013 14:42:45 +0800, Neil Zhang wrote:
>> > support CLOCKSOURCE OF DECLARE for mmp timer.
>> >
>> > Signed-off-by: Neil Zhang
>> > ---
>> > arch/arm/ma
On Tue, Jul 09, 2013 at 05:34:15PM -0700, Julius Werner wrote:
> This patch adds support for a new 'samsung,hsic-reset-gpio' in the
> device tree, which will be interpreted as an active-low reset pin during
> PHY initialization when it exists. Useful for intergrated HSIC devices
> like an SMSC 3503
于 2013年07月09日 20:03, Rob Herring 写道:
> the same and that is the assumption. Matching is not just based on
> compatible properties and your patch does not handle the other cases.
Could you show a example of "the other cases"?
After this patch,
[1] the matching will first check the @match->type and
Hi Laxman,
On 07/09/2013 10:04 PM, Laxman Dewangan wrote:
> When integrating driver with Tegra platform, it is found that
> the ID pins get detected only once after booting system and
> further removal and re-insert does not detect the ID pin.
>
> Fixing this issue with enabling interrupt on ID_G
From: Dinh Nguyen
Add device tree support to the DW watchdog timer.
Signed-off-by: Dinh Nguyen
Cc: Jamie Iles
Cc: Viresh Kumar
Cc: Grant Likely
Cc: Rob Herring
Cc: Wim Van Sebroeck
Cc: Pavel Machek
---
.../devicetree/bindings/watchdog/dw_wdt.txt| 16
drivers/wa
On Tuesday 09 July 2013, Neil Zhang wrote:
> + soc {
> + compatible = "simple-bus";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + interrupt-parent = <&gic>;
> + ranges;
> +
> + gic: interrupt-controller@d1dfe100 {
>
On Tuesday 09 July 2013, Thomas Petazzoni wrote:
> Dear Neil Zhang,
>
> On Tue, 9 Jul 2013 14:42:45 +0800, Neil Zhang wrote:
> > support CLOCKSOURCE OF DECLARE for mmp timer.
> >
> > Signed-off-by: Neil Zhang
> > ---
> > arch/arm/mach-mmp/mmp-dt.c |5 ++---
> > arch/arm/mach-mmp/mmp2-dt.c
On Tue, Jul 09, 2013 at 12:50:47PM -0600, Bjorn Helgaas wrote:
> On Tue, Jul 9, 2013 at 12:20 PM, Jason Cooper wrote:
> > On Tue, Jul 09, 2013 at 01:41:13PM -0300, Ezequiel Garcia wrote:
> >> From: Thomas Petazzoni
> >>
> >> The new device tree layout encodes the window's target ID and attribute
I am trying to determine if Device Tree is an appropriate use for
configuring drivers and would like to request comments. We currently
use Device Tree in our Shared Memory Driver (SMD) that manages up to 64
ports (where a port consists of an RX FIFO and a TX FIFO) between any
two processors an
On 07/09/2013 12:20 PM, Jason Cooper wrote:
> Bjorn,
>
> On Tue, Jul 09, 2013 at 01:41:13PM -0300, Ezequiel Garcia wrote:
>> From: Thomas Petazzoni
>>
>> The new device tree layout encodes the window's target ID and attribute
>> in the PCIe controller node's ranges property. This allows to parse
On Tue, Jul 09, 2013 at 12:50:47PM -0600, Bjorn Helgaas wrote:
> On Tue, Jul 9, 2013 at 12:20 PM, Jason Cooper wrote:
> > Bjorn,
> >
> > On Tue, Jul 09, 2013 at 01:41:13PM -0300, Ezequiel Garcia wrote:
> >> From: Thomas Petazzoni
> >>
> >> The new device tree layout encodes the window's target ID
On Tue, Jul 9, 2013 at 12:20 PM, Jason Cooper wrote:
> Bjorn,
>
> On Tue, Jul 09, 2013 at 01:41:13PM -0300, Ezequiel Garcia wrote:
>> From: Thomas Petazzoni
>>
>> The new device tree layout encodes the window's target ID and attribute
>> in the PCIe controller node's ranges property. This allows
Bjorn,
On Tue, Jul 09, 2013 at 01:41:13PM -0300, Ezequiel Garcia wrote:
> From: Thomas Petazzoni
>
> The new device tree layout encodes the window's target ID and attribute
> in the PCIe controller node's ranges property. This allows to parse
> such entries to obtain such information and use the
Widening audience
FlorianLe mardi 9 juillet 2013 17:44:55 Fainelli a écrit :
> Hello Thomas,
>
> 2013/7/9 Thomas Petazzoni :
> > Hello,
> >
> > We have a case of an hardware platform that uses the mvneta network
> > driver, but instead of the SoC being connected to a PHY, it's connected
> > dir
Sorry, looks like I forgot to push the tree out.
Anyhow should be there shortly.
On 07/09/2013 03:04 PM, Alexandre Belloni wrote:
> Hi Jonathan,
>
> I don't actually see it in iio.git on kernel.org, am I doing something
> wrong ?
>
> On 06/07/2013 12:24, Jonathan Cameron wrote:
>> On 07/04/2013
Hi,
On Tue, Jul 09, 2013 at 02:33:58PM +0200, Patel, Satish wrote:
> > > Operation:
> > >
> > > Once the card gets inserted into the slot, user application can
> > > initiate activate sequence anytime, it is not mandatory that
> > > activation has to be called Immediately. It all depends whether
>
Now that the mbus device tree binding has been introduced, we can
switch over to it.
Also, and since the initialization of the mbus driver is quite
fundamental for the system to work properly, this patch adds a BUG()
in case mbus fails to initialize.
Signed-off-by: Ezequiel Garcia
---
arch/arm/
From: Thomas Petazzoni
We add an API to create MBus address decoding windows from the target
ID and attribute. This function will be used later and deprecate the
current name based scheme.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 33 +
incl
From: Thomas Petazzoni
Now that every user of the deprecated name-based API has been
converted to using the ID-based API, let's remove the former one.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 38 --
include/linux/mbus.h | 5 -
We introduce a common initialization function mvebu_mbus_common_init()
that will be used by both legacy and device-tree initialization code.
This patch is an intermediate step, which will allow to introduce the
DT binding for this driver in a less intrusive way.
Signed-off-by: Thomas Petazzoni
Si
From: Thomas Petazzoni
These structures were only different in the mapping tables.
Now that those tables have been removed, it doesn't make any sense
to keep different structures.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 14 +++---
1 file changed, 3 insertions(+),
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-db.dts | 2 +-
arch/arm/boot/dts/armada-370-mirabox.dts | 2 +-
arch/arm/boot/dts/armada-370-rd.dts | 2 +-
arch/arm/boot/dts/armada-370.dtsi| 2 +-
arch/arm/boot/dts/armada-xp-db.dts
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-mv78xx0/pcie.c | 23 +
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-orion5x/common.c
This patch adds static window allocation to the device tree binding.
Each first-child of the mbus-compatible node, with a suitable 'ranges'
property, declaring an address translation, will trigger an address
decoding window allocation.
Signed-off-by: Ezequiel Garcia
---
.../devicetree/bindings/b
Here's the new MBus DT binding, implementing the changes proposed
by Thomas when we discussed the previous patchset:
http://www.spinics.net/lists/arm-kernel/msg257170.html
As far as I know, this round fixes *all* the concerns raised in the past
and therefore I'd like to get Acked-by's from all
On 07/05/2013 01:27:05 AM, hongbo.zh...@freescale.com wrote:
From: Hongbo Zhang
Freescale QorIQ T4 and B4 introduce new 8-channel DMA engines, this
patch add
the device tree nodes for them.
Signed-off-by: Hongbo Zhang
---
arch/powerpc/boot/dts/fsl/elo3-dma-0.dtsi | 90
++
Now that mbus has been added to the device tree, it's possible to
move the DeviceBus out of internal registers, placing it directly
below the mbus. This is a more accurate representation of the hardware.
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-xp.dtsi | 94 +++
Now that mbus has been added to the device tree, it's possible to
move the PCIe nodes out of internal registers, placing it directly
below the mbus. This is a more accurate representation of the
hardware.
Moving the PCIe nodes, we now need to introduce an extra cell to
encode the window target ID
In order to access the SoC BootROM, we need to declare a mapping
(through a ranges property). The mbus driver will use this property
to allocate a suitable address decoding window.
Signed-off-by: Ezequiel Garcia
---
arch/arm/boot/dts/armada-370-db.dts | 3 ++-
arch/arm/boot/dts/arma
The Armada 370/XP SoC family has a completely configurable address
space handled by the MBus controller.
This patch introduces the device tree layout of MBus, making the
'soc' node as mbus-compatible.
Since every peripheral/controller is a child of this 'soc' node,
this makes all of them sit behin
From: Thomas Petazzoni
After replacing the MBus name-based by the new ID-based API
let's fix the general description of the driver at the beginning
of the file.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 10 +++---
1 file changed, 3 insertions(+), 7 deletions(-)
diff -
The address decoding window to access the BootROM should not be
allocated programatically, but instead declared in the device tree.
Signed-off-by: Ezequiel Garcia
---
arch/arm/mach-mvebu/platsmp.c | 25 -
1 file changed, 24 insertions(+), 1 deletion(-)
diff --git a/arch/
We add two optional properties to the MBus DT binding, to encode
the PCIe memory and IO aperture. This allows such information to
be retrieved by -for instance- the pci driver to allocate the
MBus decoding windows.
Correspondingly, and in order to retrieve this information,
we add two new APIs.
S
From: Thomas Petazzoni
This tables were used together with the name-based MBus window
creation API. Since that's has been removed, we can also remove
the tables.
Signed-off-by: Thomas Petazzoni
---
drivers/bus/mvebu-mbus.c | 150 +++
1 file changed,
From: Thomas Petazzoni
The new device tree layout encodes the window's target ID and attribute
in the PCIe controller node's ranges property. This allows to parse
such entries to obtain such information and use the recently introduced
MBus API to create the windows, instead of using the current n
This patch adds the most fundamental device-tree initialization.
We only introduce what's required to be able to probe the mvebu-mbus
driver from the DT. Follow-up patches will extend the device tree binding,
allowing to describe static address decoding windows.
Signed-off-by: Thomas Petazzoni
Si
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-dove/common.c | 68 ++
Now that mbus device tree binding has been introduced, remove the address
decoding window management from this driver.
A suitable 'ranges' entry should be added to the devbus-compatible node in
the device tree, as described by the mbus binding documentation.
Acked-by: Greg Kroah-Hartman
Signed-of
From: Thomas Petazzoni
With the introduction of the ID based MBus API, it's better
to switch to use it instead of the current name based scheme.
This will allow to deprecate the name based API, once every
user is removed.
Signed-off-by: Thomas Petazzoni
---
arch/arm/mach-kirkwood/common.c | 1
Dear Neil Zhang,
On Tue, 9 Jul 2013 14:42:45 +0800, Neil Zhang wrote:
> support CLOCKSOURCE OF DECLARE for mmp timer.
>
> Signed-off-by: Neil Zhang
> ---
> arch/arm/mach-mmp/mmp-dt.c |5 ++---
> arch/arm/mach-mmp/mmp2-dt.c |3 +--
> arch/arm/mach-mmp/time.c| 15 ++-
>
On 07/09/2013 10:29 AM, Mark Brown wrote:
On Mon, Jul 08, 2013 at 12:22:36PM -0500, Nishanth Menon wrote:
case #1 - TPS62361 has a single SMPS and a single generic i2c bus,
one can talk on. In this case, you'd associate the regulator device
in one place - i2cX or on custom SoC hardware interfac
On Mon, Jul 08, 2013 at 12:22:36PM -0500, Nishanth Menon wrote:
> case #1 - TPS62361 has a single SMPS and a single generic i2c bus,
> one can talk on. In this case, you'd associate the regulator device
> in one place - i2cX or on custom SoC hardware interface.
> When used with custom SoC hardwar
On Tue, Jul 09, 2013 at 04:25:29PM +0200, Richard Genoud wrote:
> - reg: Should contain SSC registers location and length
> - interrupts: Should contain SSC interrupt
> +For dma transfer:
> +- dmas: DMA specifier, consisting of a phandle to DMA controller node,
> + the memory interface and SSC
On Tue, Jul 09, 2013 at 04:25:28PM +0200, Richard Genoud wrote:
> This add the sound DT binding for sam9x5ek-wm8731 machine driver
>
> Signed-off-by: Richard Genoud
> ---
> .../bindings/sound/atmel-sam9x5-wm8731-audio.txt | 30
>
Put new binding documents in the same pa
On 09:09 Fri 05 Jul , Fabio Estevam wrote:
> Hi Jean-Christophe,
>
> On Tue, May 28, 2013 at 8:09 AM, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> > On 12:35 Sun 26 May , Markus Pargmann wrote:
> >> Add devicetree support for imx framebuffer driver. It uses the generic
> >> display binding
On Tue, Jul 09, 2013 at 04:25:27PM +0200, Richard Genoud wrote:
> +/*
> + * Authorized rates are:
> + * Rate = MCLK_RATE / (n * 2)
> + * Where n is in [1..4095]
> + * (cf register SSC_CMR)
> + */
> +static unsigned int rates[] = {
> + 8000,
> + 16000,
> + 32000,
> + 48000,
> +
2013/7/9 Mark Brown :
> On Tue, Jul 09, 2013 at 04:25:26PM +0200, Richard Genoud wrote:
>> [I've just seen that I forgot to cc Uwe to the cover letter, sorry for that.]
>
> This is the second or third copy of this patch set I've been sent
> *today*. Worse, everything seems to be being sent in repl
On Tue, Jul 09, 2013 at 04:25:26PM +0200, Richard Genoud wrote:
> [I've just seen that I forgot to cc Uwe to the cover letter, sorry for that.]
This is the second or third copy of this patch set I've been sent
*today*. Worse, everything seems to be being sent in reply to the same
thread increasin
On 07/09/2013 06:03 AM, Rob Herring wrote:
> On Tue, Jul 9, 2013 at 3:10 AM, Huang Shijie wrote:
>> 于 2013年07月09日 15:51, Sascha Hauer 写道:
>>
>>> On Tue, Jul 09, 2013 at 03:46:34PM +0800, Huang Shijie wrote:
于 2013年07月09日 15:05, Sascha Hauer 写道:
>
> Why don't you set the matching
On 07/09/2013 01:05 AM, Sascha Hauer wrote:
> On Fri, Jul 05, 2013 at 04:43:38PM +0800, Huang Shijie wrote:
>> If we set the uart compatible in the dts file like this:
>>--
>> compatible = "fsl,imx6q-uart", "fsl,imx21-uart";
>>
Enable the SSC needed for the WM8731 codec
Signed-off-by: Richard Genoud
---
arch/arm/boot/dts/at91sam9x5ek.dtsi |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9x5ek.dtsi
b/arch/arm/boot/dts/at91sam9x5ek.dtsi
index 2bf51cc..0534c58 100644
--- a/arch/arm/boot
Signed-off-by: Richard Genoud
---
arch/arm/boot/dts/at91sam9x5.dtsi |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9x5.dtsi
b/arch/arm/boot/dts/at91sam9x5.dtsi
index 57d45f5..cf78ac0 100644
--- a/arch/arm/boot/dts/at91sam9x5.dtsi
+++ b/arch/arm/boot/dts/at91sa
The sam9x5ek board has 2 jacks:
headphone wired on RHPOUT/LHPOUT of the wm8731
line in wired on LLINEIN/RLINEIN of the wm8731
Signed-off-by: Richard Genoud
---
arch/arm/boot/dts/at91sam9x5ek.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9
The WM8731 codec on sam9x5ek board is on i2c, address 1A
Signed-off-by: Richard Genoud
Acked-by: Mark Brown
---
arch/arm/boot/dts/at91sam9x5ek.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9x5ek.dtsi
b/arch/arm/boot/dts/at91sam9x5ek.dtsi
index d10724
This add the sound DT binding for sam9x5ek-wm8731 machine driver
Signed-off-by: Richard Genoud
---
.../bindings/sound/atmel-sam9x5-wm8731-audio.txt | 30
1 file changed, 30 insertions(+)
create mode 100644
Documentation/devicetree/bindings/sound/atmel-sam9x5-wm8731-aud
From: Nicolas Ferre
Description of the Asoc machine driver for an at91sam9x5 based board
with a wm8731 audio DAC. Wm8731 is clocked by a crystal and used as a
master on the SSC/I2S interface. Its connections are a headphone jack
and an Line input jack.
[Richard: this is based on an old patch fro
As atmel-ssc can be used with DMA, the documentation should be updated.
Also, a configuration DMA example is given.
Signed-off-by: Richard Genoud
---
.../devicetree/bindings/misc/atmel-ssc.txt | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
diff --git a/Docu
[I've just seen that I forgot to cc Uwe to the cover letter, sorry for that.]
Hi,
This patchset add sound on the at91sam9x5ek board.
It's based on Nicolas Ferre's work in the 2.6.39 atmel patch for sam9x5:
https://github.com/linux4sam/linux-at91/commit/0aa157c9e71f3abc30fa37eb5c95b392978d
It
Quoting Mark Rutland (2013-06-26 01:40:58)
> Hi,
>
> I have a couple of minor comments.
>
> On Fri, Jun 21, 2013 at 07:14:14AM +0100, Mike Turquette wrote:
> > Device Tree binding for the basic clock multiplexer, plus the setup
> > function to register the clock. Based on the existing fixed-cloc
2013/7/9 Nicolas Ferre :
> On 09/07/2013 15:19, Richard Genoud :
>
>> 2013/7/9 Richard Genoud :
>>>
>>> As atmel-ssc can be used with DMA, the documentation should be updated.
>>> Also, a configuration DMA example is given.
>>>
>>> Signed-off-by: Richard Genoud
>>> ---
>>> .../devicetree/binding
On 09/07/2013 15:19, Richard Genoud :
2013/7/9 Richard Genoud :
As atmel-ssc can be used with DMA, the documentation should be updated.
Also, a configuration DMA example is given.
Signed-off-by: Richard Genoud
---
.../devicetree/bindings/misc/atmel-ssc.txt | 24 ++--
2013/7/9 Richard Genoud :
> As atmel-ssc can be used with DMA, the documentation should be updated.
> Also, a configuration DMA example is given.
>
> Signed-off-by: Richard Genoud
> ---
> .../devicetree/bindings/misc/atmel-ssc.txt | 24
> ++--
> 1 file changed, 22 inser
Based on system design, platform needs to detect the VBUS or ID or
both. Provide option to select this through platform data to
disable part of cable detection through palmas-usb.
Signed-off-by: Laxman Dewangan
---
.../devicetree/bindings/extcon/extcon-palmas.txt |2 +
drivers/extcon/extco
Add suspend/resume callbacks and support for wakeup from
suspend on USB HOST or USB Device cable insertion or removal.
Signed-off-by: Laxman Dewangan
---
drivers/extcon/extcon-palmas.c | 38 +++---
1 files changed, 35 insertions(+), 3 deletions(-)
diff --git a/
Remove unused member vbus_enable and set_vbus_work from palmas_usb
as these members are not used in drivers.
Signed-off-by: Laxman Dewangan
---
include/linux/mfd/palmas.h |5 -
1 files changed, 0 insertions(+), 5 deletions(-)
diff --git a/include/linux/mfd/palmas.h b/include/linux/mfd/p
When integrating driver with Tegra platform, it is found that
the ID pins get detected only once after booting system and
further removal and re-insert does not detect the ID pin.
Fixing this issue with enabling interrupt on ID_GND and ID_FLOAT
always and clearing the status on LATCH register whi
This patch series does following:
- Remove unused member from extcon palmas structure.
- Fix to support of detecting cable properly with multiple insert/removal.
- Add support for suspend/resume functionlaity and wakup from suspend.
- Option to select/de-select the ID or VBUS detection.
Laxman Dew
Neil,
On Tue, Jul 09, 2013 at 02:42:44PM +0800, Neil Zhang wrote:
> The documented vendor prefix for Marvell is 'marvell', not 'mrvl', so
> let's change it.
>
> Signed-off-by: Neil Zhang
> ---
> .../devicetree/bindings/arm/mrvl/intc.txt | 16 +++---
> .../devicetree/bindings/arm/mrvl
The sam9x5ek board has 2 jacks:
headphone wired on RHPOUT/LHPOUT of the wm8731
line in wired on LLINEIN/RLINEIN of the wm8731
Signed-off-by: Richard Genoud
---
arch/arm/boot/dts/at91sam9x5ek.dtsi | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9
Signed-off-by: Richard Genoud
---
arch/arm/boot/dts/at91sam9x5.dtsi |3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9x5.dtsi
b/arch/arm/boot/dts/at91sam9x5.dtsi
index 57d45f5..cf78ac0 100644
--- a/arch/arm/boot/dts/at91sam9x5.dtsi
+++ b/arch/arm/boot/dts/at91sa
The WM8731 codec on sam9x5ek board is on i2c, address 1A
Signed-off-by: Richard Genoud
Acked-by: Mark Brown
---
arch/arm/boot/dts/at91sam9x5ek.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9x5ek.dtsi
b/arch/arm/boot/dts/at91sam9x5ek.dtsi
index d10724
Enable the SSC needed for the WM8731 codec
Signed-off-by: Richard Genoud
---
arch/arm/boot/dts/at91sam9x5ek.dtsi |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9x5ek.dtsi
b/arch/arm/boot/dts/at91sam9x5ek.dtsi
index 2bf51cc..0534c58 100644
--- a/arch/arm/boot
As atmel-ssc can be used with DMA, the documentation should be updated.
Also, a configuration DMA example is given.
Signed-off-by: Richard Genoud
---
.../devicetree/bindings/misc/atmel-ssc.txt | 24 ++--
1 file changed, 22 insertions(+), 2 deletions(-)
diff --git a/Doc
From: Nicolas Ferre
Description of the Asoc machine driver for an at91sam9x5 based board
with a wm8731 audio DAC. Wm8731 is clocked by a crystal and used as a
master on the SSC/I2S interface. Its connections are a headphone jack
and an Line input jack.
[Richard: this is based on an old patch fro
This add the sound DT binding for sam9x5ek-wm8731 machine driver
Signed-off-by: Richard Genoud
---
.../bindings/sound/atmel-sam9x5-wm8731-audio.txt | 30
1 file changed, 30 insertions(+)
create mode 100644
Documentation/devicetree/bindings/sound/atmel-sam9x5-wm8731-aud
Hi,
This patchset add sound on the at91sam9x5ek board.
It's based on Nicolas Ferre's work in the 2.6.39 atmel patch for sam9x5:
https://github.com/linux4sam/linux-at91/commit/0aa157c9e71f3abc30fa37eb5c95b392978d
It needs Bo Chen's patchset on the generic dmaengine (topic/atmel branch
on Mark'
On Tue, Jul 9, 2013 at 3:10 AM, Huang Shijie wrote:
> 于 2013年07月09日 15:51, Sascha Hauer 写道:
>
>> On Tue, Jul 09, 2013 at 03:46:34PM +0800, Huang Shijie wrote:
>>>
>>> 于 2013年07月09日 15:05, Sascha Hauer 写道:
Why don't you set the matching order in the driver the way you want it
to be,
Hi,
On Tue, Jul 09, 2013 at 04:23:29AM +0200, Patel, Satish wrote:
> > > We have two options over here
> > >
> > > Option 1:
> > >
> > > Defining generic api to which can be mapped over multiple phys
> > > For smartcard case, I have can thought of following mapping with new
> > > generic apis as s
2013/7/9 Mark Brown :
> On Tue, Jul 09, 2013 at 10:19:45AM +0200, Richard Genoud wrote:
>> 2013/7/8 Mark Brown :
>
>> > The obvious question here is of course if we can use the same driver for
>> > both of them.
>
>> I haven't got a g20 to test that, but that's the goal.
>
> I think I do somewhere.
2013/7/9 Mark Brown :
> On Tue, Jul 09, 2013 at 10:27:53AM +0200, Richard Genoud wrote:
>
>> The dma binding is documented here
>> Documentation/devicetree/bindings/dma/atmel-dma.txt
>> But you're right, I shoud update
>> Documentation/devicetree/bindings/misc/atmel-ssc.txt.
>
> No, you need to wri
On Tue, Jul 09, 2013 at 10:27:53AM +0200, Richard Genoud wrote:
> The dma binding is documented here
> Documentation/devicetree/bindings/dma/atmel-dma.txt
> But you're right, I shoud update
> Documentation/devicetree/bindings/misc/atmel-ssc.txt.
No, you need to write a binding for this machine dr
On Tue, Jul 09, 2013 at 10:19:45AM +0200, Richard Genoud wrote:
> 2013/7/8 Mark Brown :
> > The obvious question here is of course if we can use the same driver for
> > both of them.
> I haven't got a g20 to test that, but that's the goal.
I think I do somewhere.
> For now, g20 is still non-DT,
On Tue, Jul 09, 2013 at 07:26:27AM +0200, Michal Simek wrote:
> On 07/08/2013 04:51 PM, Mark Brown wrote:
> > Applied, thanks.
> have you applied this patch?
Yes, network is spotty here so pushes aren't working so well.
signature.asc
Description: Digital signature
_
On 07/09/2013 10:03 AM, Jingoo Han wrote:
> This patch series adds a simple driver for the Samsung Exynos SoC
> series DP transmitter PHY, using the generic PHY framework [1].
> Previously the DP PHY used an internal DT node to control the PHY
> power enable bit.
>
> These patches was tested on Ex
Hi Richard,
On 7/9/2013 16:19, Richard Genoud wrote:
2013/7/8 Mark Brown :
On Mon, Jul 08, 2013 at 03:29:49PM +0200, Richard Genoud wrote:
+ * Nicolas Ferre
+ *
+ * Based on sam9g20_wm8731.c by:
+ * Sedji Gaouaou
The obvious question here is of course if we can use the same dr
2013/7/8 Mark Brown :
> On Mon, Jul 08, 2013 at 03:29:50PM +0200, Richard Genoud wrote:
>> Signed-off-by: Richard Genoud
>> ---
>> arch/arm/boot/dts/at91sam9x5.dtsi |3 +++
>
> There was no binding document in your first patch - there should be one
> for any new DT bindings.
The dma binding is
2013/7/8 Mark Brown :
> On Mon, Jul 08, 2013 at 03:29:49PM +0200, Richard Genoud wrote:
>
>> + * Nicolas Ferre
>> + *
>> + * Based on sam9g20_wm8731.c by:
>> + * Sedji Gaouaou
>
> The obvious question here is of course if we can use the same driver for
> both of them.
I haven't got a
Use the generic PHY API to control the DP PHY.
Signed-off-by: Jingoo Han
Reviewed-by: Tomasz Figa
---
.../devicetree/bindings/video/exynos_dp.txt | 18 +-
drivers/video/exynos/exynos_dp_core.c| 16
drivers/video/exynos/exynos_dp_core
Exynos Display Port can be used only for Exynos SoCs. In addition,
non-DT for EXYNOS SoCs is not supported from v3.11; thus, there is
no need to support non-DT for Exynos Display Port.
The 'include/video/exynos_dp.h' file has been used for non-DT
support and the content of file include/video/exyno
于 2013年07月09日 15:51, Sascha Hauer 写道:
On Tue, Jul 09, 2013 at 03:46:34PM +0800, Huang Shijie wrote:
于 2013年07月09日 15:05, Sascha Hauer 写道:
Why don't you set the matching order in the driver the way you want it
to be, i.e.:
{ .compatible = "fsl,imx6q-uart", ... },
{ .compatible =
Add a PHY provider driver for the Samsung Exynos SoC Display Port PHY.
Signed-off-by: Jingoo Han
Reviewed-by: Tomasz Figa
Cc: Sylwester Nawrocki
Acked-by: Felipe Balbi
---
.../devicetree/bindings/phy/samsung-phy.txt|8 ++
drivers/phy/Kconfig|6 +
1 - 100 of 106 matches
Mail list logo
