On 24 January 2014 18:58, Lorenzo Pieralisi lorenzo.pieral...@arm.com wrote:
Hi Vincent,
On Fri, Jan 24, 2014 at 08:40:40AM +, Vincent Guittot wrote:
[...]
Hi Lorenzo,
Sorry for the late reply,
I had an idea. To simplify things, I think that one possibility is to
add a parameter
On Tue, Jan 28, 2014 at 1:16 AM, Sergei Shtylyov
sergei.shtyl...@cogentembedded.com wrote:
--- /dev/null
+++ net-next/Documentation/devicetree/bindings/net/ethernet.txt
@@ -0,0 +1,23 @@
+The following properties are common to the Ethernet controllers:
+
+- local-mac-address: array of 6
On Wed, Jan 15, 2014 at 05:32:12PM +0100, Denis Carikli wrote:
diff --git a/arch/arm/boot/dts/imx35-eukrea-cpuimx35.dtsi
b/arch/arm/boot/dts/imx35-eukrea-cpuimx35.dtsi
new file mode 100644
index 000..303f789
--- /dev/null
+++ b/arch/arm/boot/dts/imx35-eukrea-cpuimx35.dtsi
@@ -0,0 +1,59
From: Geert Uytterhoeven geert+rene...@linux-m68k.org
Signed-off-by: Geert Uytterhoeven geert+rene...@linux-m68k.org
---
v5:
- Define interrupts in terms of interrupt-names in bindings
- No code changes
v4:
- Clarify SoCtype and interrupts
- Add clock property
- Add QSPI example
- Add
On Mon, Jan 27, 2014 at 06:17:07PM +, Mark Brown wrote:
On Mon, Jan 27, 2014 at 01:03:09PM +0100, Markus Pargmann wrote:
case SND_SOC_BIAS_STANDBY:
+ /* Switch off master clock */
+ if (!IS_ERR(aic32x4-mclk))
+
On 01/27/2014 11:12 AM, Tomasz Figa wrote:
The brcmfmac driver that consumes these DT nodes will have a closer look
at the device obtaining the chipid during the probe and determine if it
can support it. So the compatible string indicates that the device needs
a so-called fullmac wireless
Hi Shawn,
On Sunday, 26. January 2014 00:43:04 Shawn Guo wrote:
We created the pingrp macros in imx6sl-pingrp.h for purpose of less LOC
when same pin group is used by multiple boards. However, DT maintainers
take it as an abuse of DTC macro support. So let's get rid of it to
make the pins
On Mon, Jan 27, 2014 at 05:36:24PM +, Russell King - ARM Linux wrote:
[..]
+static int armadaxp_wdt_clock_init(struct platform_device *pdev,
+ struct orion_watchdog *dev)
+{
+ int ret;
+
+ dev-clk = of_clk_get_by_name(pdev-dev.of_node, fixed);
+
On Mon, Jan 27, 2014 at 02:37:45PM +, Russell King - ARM Linux wrote:
On Sun, Jan 26, 2014 at 12:43:03AM +0800, Shawn Guo wrote:
arch/arm/boot/dts/imx6dl-hummingboard.dts |5 +-
arch/arm/boot/dts/imx6qdl-microsom.dtsi|5 +-
I've merged your changes here into my local copy
Hi,
On 01/28/2014 11:11 AM, Arend van Spriel wrote:
On 01/27/2014 11:12 AM, Tomasz Figa wrote:
The brcmfmac driver that consumes these DT nodes will have a closer look
at the device obtaining the chipid during the probe and determine if it
can support it. So the compatible string indicates
On Tuesday 28 January 2014, Ulf Hansson wrote:
On 28 January 2014 01:59, Tomasz Figa tomasz.f...@gmail.com wrote:
On 27.01.2014 11:19, Ulf Hansson wrote:
There is already a host capability that I think we could use to handle
this. MMC_CAP_NONREMOVABLE, the corresponding DT binding string is
clock-specifier to DT binding description
2. remove local variable rate
3. add local variable parent_name
4. use clk_register_fixed_factor() instead of clk_register_fixed_rate()
5. remove flag CLK_IS_ROOT
Applies to next-20140128
.../bindings/clock/moxa,moxart-clock.txt
On Tue, Jan 28, 2014 at 11:17:57AM +, Russell King - ARM Linux wrote:
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
Why does the direction needs to be specified in specifier? I see two
options, either the
On Tuesday 28 January 2014 17:02:42 Vinod Koul wrote:
On Tue, Jan 28, 2014 at 11:17:57AM +, Russell King - ARM Linux wrote:
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
On Tuesday 28 January 2014 10:05:35 Lars-Peter Clausen wrote:
Why does the direction needs to be
On Tuesday 28 January 2014 13:05:10 Arnd Bergmann wrote:
On Tuesday 28 January 2014 17:02:42 Vinod Koul wrote:
On Tue, Jan 28, 2014 at 11:17:57AM +, Russell King - ARM Linux wrote:
On Tue, Jan 28, 2014 at 10:16:53AM +0100, Arnd Bergmann wrote:
On Tuesday 28 January 2014 10:05:35
On Tue, Jan 28, 2014 at 01:08:47PM +0100, Arnd Bergmann wrote:
On a related note, should we try to remove the slave_id field from
the slave config structure as well? I believe it is still used by
the shmobile dma engine in non-DT mode, but that is inconsistent with
how all the others work, and
Add document describing device tree bindings for MAX14577 MFD driver
(for both MAX14577 and MAX77836 chipsets).
Signed-off-by: Krzysztof Kozlowski k.kozlow...@samsung.com
Cc: Kyungmin Park kyungmin.p...@samsung.com
Cc: Tomasz Figa t.f...@samsung.com
Cc: Marek Szyprowski m.szyprow...@samsung.com
On Tue, Jan 28, 2014 at 01:05:10PM +0100, Arnd Bergmann wrote:
Ok, thanks for clearing up my mistake. However, the argument remains:
the direction doesn't need to be in the DT DMA descriptor since it
gets set by software anyway.
Yes - for full-duplex, it's implied, since you have one DMA
On Mon, Jan 27, 2014 at 4:50 PM, Sergei Shtylyov
sergei.shtyl...@cogentembedded.com wrote:
This patch is an attempt to gather the Ethernet related bindings in one file,
like it's done in the MMC and some other subsystems. It should save some of
the trouble of documenting several properties over
Some random thoughts ahead of meeting today...
On Fri, 18 Oct 2013 16:57:36 +0200, Tomasz Figa t.f...@samsung.com wrote:
/*
* schema.dtss - Sample Device Tree schema file.
*
* Copyright (C) 2013 Samsung Electronics Co., Ltd.
* Author: Tomasz Figa t.f...@samsung.com
*
* This program
On 01/28/2014 04:38 PM, Rob Herring wrote:
This patch is an attempt to gather the Ethernet related bindings in one file,
like it's done in the MMC and some other subsystems. It should save some of
the trouble of documenting several properties over and over in each binding
document, instead only
Hi,
On Mon, Jan 27, 2014 at 10:05:20AM -0600, Felipe Balbi wrote:
Why would you need to know if the PHY drivers are needed or not
explicitly in your controller driver?
because, one way or another, they all do need it. Except for quirky ones
like AM437x where a USB3 IP was hardwired into
Sehr geehrter Nutzer
Ihre beiden eingehenden E-Mails wurden am ungeklarten Status aufgrund der
jungsten Upgrade auf unserer Datenbank gespeichert, Um erhalten die Nachrichten
bestatigen Konto.
Um neu bestatigen Ihre Mailbox, auf diese E-Mail antworten sofort.
Durch das Ausfullen der unten
2014/1/27 Rob Herring robherri...@gmail.com:
On Mon, Jan 27, 2014 at 5:51 AM, Alexey Charkov alch...@gmail.com wrote:
This should make the driver usable with VIA/WonderMedia ARM-based
Systems-on-Chip integrated Rhine III adapters. Note that these
are always in MMIO mode, and don't have any
2014/1/28 Ben Hutchings b...@decadent.org.uk:
On Mon, 2014-01-27 at 19:34 +0400, Alexey Charkov wrote:
2014/1/27 Ben Hutchings b...@decadent.org.uk:
On Mon, 2014-01-27 at 15:51 +0400, Alexey Charkov wrote:
This should make the driver usable with VIA/WonderMedia ARM-based
Systems-on-Chip
On Tue, Jan 28, 2014 at 10:05:35AM +0100, Lars-Peter Clausen wrote:
On 01/28/2014 07:27 AM, Andy Gross wrote:
Add device tree binding support for the QCOM BAM DMA driver.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 52
Hi Hans,
El 22/01/14 18:36, Hans de Goede escribió:
The usb-clk register is special in that it not only contains clk gate bits,
but also has a few reset bits. This commit adds support for this by allowing
gates type sunxi clks to also register a reset controller.
Signed-off-by: Hans de Goede
Hi,
On Monday 27 January 2014 07:49 PM, Yuvaraj Kumar C D wrote:
This patch adds the SATA PHY driver for Exynos5250.Exynos5250 SATA
PHY comprises of CMU and TRSV blocks which are of I2C register Map.
So this patch also adds a i2c client driver, which is used configure
the CMU and TRSV block
28 matches
Mail list logo
