Exynos SoCs use pinctrl to configure GPIOs. Update the document
to reflect this change.
Signed-off-by: Sachin Kamat
Cc: Rahul Sharma
---
.../devicetree/bindings/video/exynos_hdmi.txt |6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindi
Hi Jean-Christophe,
On 5/17/2013 22:42, Jean-Christophe PLAGNIOL-VILLARD wrote:
Allow to compile the driver all the time if AT91 enabled.
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
Cc: Nicolas Ferre
Cc: linux-...@vger.kernel.org
---
.../devicetree/bindings/usb/atmel-usb.txt |
On Thu, May 16, 2013 at 05:55:24PM +0200, Thomas Petazzoni wrote:
> Now that we have the necessary drivers and Device Tree informations to
> support PCIe on Armada 370 and Armada XP, enable the CONFIG_PCI
> option.
>
> Also, since the Armada 370 Mirabox has a built-in USB XHCI controller
> connect
On Thu, May 16, 2013 at 05:55:20PM +0200, Thomas Petazzoni wrote:
> The Armada 370 has two gatable clocks for each PCIe interface, and we
> want both of them to be enabled. We therefore make one of the two
> clocks a child of the other, as we did for the sataX and sataXlnk
> clocks on Armada XP.
>
On Thu, May 16, 2013 at 05:55:17PM +0200, Thomas Petazzoni wrote:
> From: Andrew Murray
>
> This patch factors out common implementation patterns to reduce overall kernel
> code and provide a means for host bridge drivers to directly obtain struct
> resources from the DT's ranges property without
On Thu, May 16, 2013 at 05:55:16PM +0200, Thomas Petazzoni wrote:
> Since 82a682676 ('ARM: dts: mvebu: Convert all the mvebu files to use
> the range property') all the device nodes of Armada 370/XP are under a
> common 'ranges' property that translates the device register addresses
> into their ab
On 05/19/2013 03:41 PM, Tomasz Figa wrote:
+static struct dm9000_plat_data *dm9000_parse_dt(struct device *dev)
> > +{
> > + struct dm9000_plat_data *pdata;
> > + struct device_node *np = dev->of_node;
> > + const void *mac_addr;
> > +
> > + if (!IS_ENABLED(CONFIG_OF) || !np)
Hi Sylwester,
On Sunday 19 of May 2013 15:27:53 Sylwester Nawrocki wrote:
> Hi,
>
> On 05/19/2013 01:16 PM, Tomasz Figa wrote:
> > +++ b/Documentation/devicetree/bindings/net/davicom-dm9000.txt
> > @@ -0,0 +1,26 @@
> > +Davicom DM9000 Fast Ethernet controller
> > +
> > +Required properties:
> > +
Hi,
On 05/19/2013 01:16 PM, Tomasz Figa wrote:
+++ b/Documentation/devicetree/bindings/net/davicom-dm9000.txt
@@ -0,0 +1,26 @@
+Davicom DM9000 Fast Ethernet controller
+
+Required properties:
+- compatible = "davicom,dm9000";
+- reg : physical addresses and sizes of registers, must contain 2 ent
This patch adds Device Tree support to dm9000 driver.
Signed-off-by: Tomasz Figa
---
Changes since v1:
- dropped davicom,simple-phy property as it seems to be of no use
- used of_get_mac_address() to get MAC address from device tree
- replaced #ifdef CONFIG_OF around dm9000_parse_dt() with IS
On Sunday 19 of May 2013 12:35:44 Sascha Hauer wrote:
> On Sun, May 19, 2013 at 10:54:53AM +0200, Tomasz Figa wrote:
> > Hi Sascha,
> >
> > On Sunday 19 of May 2013 09:05:38 Sascha Hauer wrote:
> > > Hi Tomasz,
> > >
> > > On Sun, May 19, 2013 at 01:03:14AM +0200, Tomasz Figa wrote:
> > > > This
On Sunday 19 of May 2013 12:39:26 Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 11:46 Sun 19 May , Tomasz Figa wrote:
> > On Sunday 19 of May 2013 11:17:36 Jean-Christophe PLAGNIOL-VILLARD
wrote:
> > > > > > > PULL_UP (1 << 0): indicate this pin need a pull up.
> > > > > > > MULTIDRIVE
On 11:46 Sun 19 May , Tomasz Figa wrote:
> On Sunday 19 of May 2013 11:17:36 Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > > > PULL_UP (1 << 0): indicate this pin need a pull up.
> > > > > > MULTIDRIVE (1 << 1): indicate this pin need to be
> > > > > > configured as
> > > > > > m
On Sun, May 19, 2013 at 10:54:53AM +0200, Tomasz Figa wrote:
> Hi Sascha,
>
> On Sunday 19 of May 2013 09:05:38 Sascha Hauer wrote:
> > Hi Tomasz,
> >
> > On Sun, May 19, 2013 at 01:03:14AM +0200, Tomasz Figa wrote:
> > > This patch adds Device Tree support to dm9000 driver.
> > >
> > > Signed-o
On Sunday 19 of May 2013 11:17:36 Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > > PULL_UP (1 << 0): indicate this pin need a pull up.
> > > > > MULTIDRIVE (1 << 1): indicate this pin need to be
> > > > > configured as
> > > > > multidrive. DEGLITCH(1 << 2): indicate this pin
> > > > PULL_UP (1 << 0): indicate this pin need a pull up.
> > > > MULTIDRIVE (1 << 1): indicate this pin need to be configured as
> > > > multidrive. DEGLITCH(1 << 2): indicate this pin need
> > > > deglitch.
> > > > PULL_DOWN (1 << 3): indicate this pin need a pull dow
Hi Sascha,
On Sunday 19 of May 2013 09:05:38 Sascha Hauer wrote:
> Hi Tomasz,
>
> On Sun, May 19, 2013 at 01:03:14AM +0200, Tomasz Figa wrote:
> > This patch adds Device Tree support to dm9000 driver.
> >
> > Signed-off-by: Tomasz Figa
> > ---
> >
> > .../devicetree/bindings/net/davicom-dm900
Hi Tomasz,
On Sun, May 19, 2013 at 01:03:14AM +0200, Tomasz Figa wrote:
> This patch adds Device Tree support to dm9000 driver.
>
> Signed-off-by: Tomasz Figa
> ---
> .../devicetree/bindings/net/davicom-dm9000.txt | 27 ++
> .../devicetree/bindings/vendor-prefixes.txt| 1 +
18 matches
Mail list logo
