Hi,
On Fri, Dec 7, 2012 at 7:21 PM, Grant Likely wrote:
> On Thu, 6 Dec 2012 13:11:42 +0900, Mark Brown
> wrote:
>> On Thu, Dec 06, 2012 at 09:31:40AM +0530, Padma Venkat wrote:
>> > On Wed, Nov 28, 2012 at 4:17 PM, Padmavathi Venna
>> > wrote:
>>
>> > > Padmavathi Venna (2):
>> > > ASoC: S
On Friday 07 December 2012, Michal Simek wrote:
> On 12/06/2012 10:27 PM, Bjorn Helgaas wrote:
> > [+cc linux-pci]
> >
> > On Thu, Dec 6, 2012 at 7:23 AM, Michal Simek
> > wrote:
> >> Hi guys,
> >>
> >> I have a question regarding to sharing generic OF pcie driver between
> >> two architectures M
On 12/07/2012 02:17 PM, Grant Likely wrote:
On Thu, 6 Dec 2012 15:23:14 +0100, Michal Simek wrote:
Hi guys,
I have a question regarding to sharing generic OF pcie driver between
two architectures MB and ARM Zynq.
Is drivers/pci/pcie location good for it?
Make no sense to have the same driver i
From: Grant Likely
Date: Tue, 4 Dec 2012 21:49:26 +
> On Tue, Dec 4, 2012 at 9:10 PM, David Miller wrote:
>> From: Grant Likely
>> Date: Tue, 4 Dec 2012 14:44:57 +
>>
>>> On Tue, Dec 4, 2012 at 2:09 PM, Andreas Larsson wrote:
This series removes the dependency on !SPARC for OF_I2C
From: Andreas Larsson
Date: Tue, 4 Dec 2012 15:09:37 +0100
> Signed-off-by: Andreas Larsson
Applied.
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetree-discuss
From: Vipul Kumar Samar
This patch extends existing DT support for stmpe devices. This updates:
- missing header files in stmpe.c
- stmpe_of_probe() with pwm, rotator and new bindings.
- Bindings are updated in binding document.
Acked-by: Lee Jones
Acked-by: Linus Walleij
Signed-off-by: Vipul
Hi,
Am Montag, den 26.11.2012, 18:56 +0200 schrieb Tomi Valkeinen:
> On 2012-11-26 18:10, Steffen Trumtrar wrote:
> > Hi,
> >
> > On Mon, Nov 26, 2012 at 04:38:36PM +0200, Tomi Valkeinen wrote:
>
> >>> +optional properties:
> >>> + - hsync-active: hsync pulse is active low/high/ignored
> >>> + -
On Fri, 07 Dec 2012 10:45:01 +0100, Michal Simek wrote:
> On 12/06/2012 10:27 PM, Bjorn Helgaas wrote:
> > [+cc linux-pci]
> >
> > On Thu, Dec 6, 2012 at 7:23 AM, Michal Simek
> > wrote:
> >> Hi guys,
> >>
> >> I have a question regarding to sharing generic OF pcie driver between
> >> two archit
Add NAND driver entries to export NAND functionality on da850 EVM and
NAND pinctrl node to do pin mux according to pinctrl-single driver.
Signed-off-by: Kumar, Anil
---
Depend on link:
http://www.spinics.net/lists/linux-doc/msg07535.html
:100644 100644 8cac9d2... 05b558a... M arch/arm/boot/dts
This set of patches adds:
* Add pinctrl-single for handling Padconf registers.
* Add NAND node to export NAND functionality on da850 EVM.
* Add NAND pinctrl node to do pin mux according to pinctrl-single driver.
Kumar, Anil (2):
ARM: davinci: da850: add pinctrl driver entries
ARM: davinci: da
For DT, DaVinci platform can use pinctrl-single driver for handling
padconf registers.
Enable PINCTRL Kconfig for all DaVinci platform. Add required
pinctrl DT entries in da850 dts file.
Test procedure
1)Populate DT file with NAND node information.
2)Populate board DT file with pinmux informati
tree: git://git.secretlab.ca/git/linux-2.6.git spi/next
head: b15d5d7004e25716c8b8dfe4e322a64551e2e6cc
commit: b3a223ee2d1a4635b0643c547bc0096a37334ed1 [9/12] spi: Remove SPI_BUFSIZ
restriction on spi_write_then_read()
sparse warnings:
+ drivers/spi/spi.c:1554:37: sparse: incompatible types
tree: git://git.secretlab.ca/git/linux-2.6.git spi/next
head: b15d5d7004e25716c8b8dfe4e322a64551e2e6cc
commit: b3a223ee2d1a4635b0643c547bc0096a37334ed1 [9/12] spi: Remove SPI_BUFSIZ
restriction on spi_write_then_read()
config: make ARCH=x86_64 allyesconfig
All warnings:
drivers/spi/spi.c: In
From: "R. Chandrasekar"
Adding driver for the Mobile Image Enhancement (MIE)
module of exynos SoC. This cl scope is limited to dithereing.
mie dithering function is enabled from fimd
Signed-off-by: R. Chandrasekar
Change-Id: I05be2a2a5484719ff7bdeff722d95223191b077f
---
drivers/gpu/drm/exynos
Since the aemif driver conversion to DT along with
its movement to drivers/ folder is not yet done,
fix NAND binding documentation to have NAND specific
DT details only.
Signed-off-by: Kumar, Anil
---
:100644 100644 e37241f... 49fc7ad... M
Documentation/devicetree/bindings/arm/davinci/nand.txt
This reverts commit a2c0911c09190125f52c9941b9d187f601c2f7be.
Signed-off-by: Vakul Garg
---
Instead of adding SEC era information in crypto node's compatible, a new
property 'fsl,sec-era' is being introduced into crypto node.
.../devicetree/bindings/crypto/fsl-sec4.txt|5 ++---
1 fi
From: "R. Chandrasekar"
mie provides the dithereing functionality, fimd need to call the
mie dithering function is required when panel uses lesser
bits per pixel (bpp) of fimd.
This cl adds the functions to add the mie plugin, and calls the
mie dithereing function.
Signed-off-by: R. Chandraseka
From: "R. Chandrasekar"
adding device tree support for mobile image enhancement (mie)
module of exynos SoC. driver fetches the base address of mie
from the device tree.
Signed-off-by: R. Chandrasekar
---
arch/arm/boot/dts/exynos5250.dtsi |7 ++-
1 file changed, 6 insertions(+), 1 delet
From: "R. Chandrasekar"
this patch set adds the driver support for the dithering functionality of the
mobile image enhancement (mie) module.
device tree support is added for mie.
fimd adds the mie module as plugin and calls the dithering function. dithere is
required when the panels bpp is les
Hi Mark,
On Thu, Dec 6, 2012 at 11:58 AM, Mark Brown
wrote:
> On Thu, Dec 06, 2012 at 11:55:11AM +0530, Abhilash Kesavan wrote:
>
>> As of now there is no support in the regulator core to specify the suspend
>> state
>> (mode, enabled/disabled) using dt. I can add new properties specifying
>> th
Hi,
Max77686 PMIC has dt support and I wanted to specify the suspend state of the
regulator via dt. set_suspend_disable and set_suspend_mode call-backs are
already implemented in drivers/regulator/max77686.c.
As of now there is no support in the regulator core to specify the suspend state
(mode,
On 12/07/2012 02:34 PM, Grant Likely wrote:
> It really needs to look like this:
>
> pwmleds {
> compatible = "pwm-leds";
> kpad {
> label = "omap4::keypad";
> max-brightness = <127>;
> pwms = <&twl_pwm 0 7812500>;
> };
> charging {
On Thu, 6 Dec 2012 13:11:42 +0900, Mark Brown
wrote:
> On Thu, Dec 06, 2012 at 09:31:40AM +0530, Padma Venkat wrote:
> > On Wed, Nov 28, 2012 at 4:17 PM, Padmavathi Venna
> > wrote:
>
> > > Padmavathi Venna (2):
> > > ASoC: Samsung: Get I2S src_clk from clock alias id.
> > > ASoC: SAMSUNG:
On Thu, 6 Dec 2012 08:06:20 +0530, Viresh Kumar wrote:
> On 6 December 2012 04:12, Grant Likely wrote:
> > On Sat, 1 Dec 2012 00:33:46 +0530, Viresh Kumar
> > wrote:
> >> This first tries to match the table my patch added, _BUT_ the string will
> >> never match as we had "st,stmpe810" in table
On Thu, 6 Dec 2012 07:28:22 +0530, Viresh Kumar wrote:
> First of all, thanks for explaining :)
>
> On 6 December 2012 04:12, Grant Likely wrote:
> > On Sat, 1 Dec 2012 00:33:46 +0530, Viresh Kumar
> > wrote:
> >> This first tries to match the table my patch added, _BUT_ the string will
> >> n
On Thu, 6 Dec 2012 13:36:11 +0100, Peter Ujfalusi wrote:
> Hi Grant,
>
> On 12/06/2012 11:00 AM, Grant Likely wrote:
> > On Mon, 12 Nov 2012 15:41:10 +0100, Peter Ujfalusi
> > wrote:
> >> Support for device tree booted kernel.
> >> When the kernel is booted with DeviceTree blob we support one l
On Thu, 6 Dec 2012 15:23:14 +0100, Michal Simek wrote:
> Hi guys,
>
> I have a question regarding to sharing generic OF pcie driver between
> two architectures MB and ARM Zynq.
> Is drivers/pci/pcie location good for it?
> Make no sense to have the same driver in two locations.
> Is using readl/w
On Thu, 6 Dec 2012 16:55:33 +0100, Lars-Peter Clausen wrote:
> This patch allows to specify that a SPI device is connected in 3-wire mode via
> device tree.
>
> Signed-off-by: Lars-Peter Clausen
> Acked-by: Rob Herring
Applied, thanks.
g.
> ---
> Documentation/devicetree/bindings/spi/spi-b
Hi Stefan,
On 12/07/2012 08:22 AM, Stefan Roese wrote:
> Currently cfi_cmdset_0002.c does not support PPB locking of sectors. This
> patch adds support for this locking/unlocking mechanism. It is needed on
> some platforms, since newer U-Boot versions do support this PPB locking
> and protect for
On 12/5/2012 6:13 PM, Philip, Avinash wrote:
> On Wed, Dec 05, 2012 at 17:33:37, Nori, Sekhar wrote:
>> Hi Avinash,
>>
>> On 11/29/2012 5:16 PM, Philip, Avinash wrote:
>>> Update number of errors using nand ecc strength.
>>> Also add macro definitions BCH8_ERROR_MAX & BCH4_ERROR_MAX
>>
>> Can you p
On Fri, Dec 07, 2012 at 01:59:21PM +0530, Padmavathi Venna wrote:
> Previously, the ASoC 'platform' (PCM/DMA) object was instantiated via a
> platform_device. This didn't represent the hardware well, since there
> was no separate hardware associated with this platform_device; it was a
> virtual dev
On 11/29/2012 5:16 PM, Philip, Avinash wrote:
> The ELM hardware module can be used to speedup BCH 4/8/16 ECC scheme
> error correction.
> For now only 4 & 8 bit support is added
>
> Signed-off-by: Philip, Avinash
> Cc: Grant Likely
> Cc: Rob Herring
> Cc: Rob Landley
> ---
> Changes since v2:
On 12/06/2012 10:27 PM, Bjorn Helgaas wrote:
[+cc linux-pci]
On Thu, Dec 6, 2012 at 7:23 AM, Michal Simek wrote:
Hi guys,
I have a question regarding to sharing generic OF pcie driver between
two architectures MB and ARM Zynq.
Is drivers/pci/pcie location good for it?
Make no sense to have th
On 2012-12-06 12:07, Grant Likely wrote:
> On Mon, 26 Nov 2012 16:39:58 +0100, Steffen Trumtrar
> wrote:
>> On Mon, Nov 26, 2012 at 02:37:26PM +0200, Tomi Valkeinen wrote:
>>> On 2012-11-26 11:07, Steffen Trumtrar wrote:
>>>
+/*
+ * Subsystem independent description of a videomode.
Add the basic device tree based lookup.
Signed-off-by: Padmavathi Venna
---
.../bindings/sound/samsung,smdk-wm8994.txt | 14 ++
arch/arm/boot/dts/exynos5250-smdk5250.dts | 12 +
sound/soc/samsung/smdk_wm8994.c| 26
3
Previously, the ASoC 'platform' (PCM/DMA) object was instantiated via a
platform_device. This didn't represent the hardware well, since there
was no separate hardware associated with this platform_device; it was a
virtual device with sole purpose to call snd_soc_register_platform().
This change re
Changes since V1:
- Renamed all samsung based audio platform names with the corresponding
cpu dai name
- Register the dma device in the corresponding samsung cpu dai driver
- Deleted "samsung_asoc_dma" platform device from devs.c
- Deleted the "samsung_asoc
Hi Mark,
On Fri, Dec 7, 2012 at 12:16 PM, Mark Brown
wrote:
> On Thu, Dec 06, 2012 at 09:20:36AM +0530, Padmavathi Venna wrote:
>> Previously, the ASoC 'platform' (PCM/DMA) object was instantiated via a
>> platform_device. This didn't represent the hardware well, since there
>> was no separate ha
38 matches
Mail list logo
