Hi Kuninori,
On 25.02.2013 09:49, Kuninori Morimoto wrote:
>
> Hi Mark, Stephen, Lars
>
> These are v7 of simple-card DT support.
> I well considered your comments/advices.
> Then, I noticed that creating snd_soc_register_cpu() is better solution.
> It is very basic/simple version at this point,
Hi Arnd,
On 04.07.2013 23:34, Arnd Bergmann wrote:
> On Thursday 04 July 2013, Mark Brown wrote:
>> Another way of skinning this would be for either the kernel to contain
>> a set of machine ID to compatible string mappings or for the device
>> trees for the boards to have an additional propertie
Hi Nicolas,
On 04.07.2013 19:28, Nicolas Pitre wrote:
> On Thu, 4 Jul 2013, Daniel Mack wrote:
>> I'm open to opinion and sugesstions :)
>
> What you describe above more or less fits the definition of what I
> called the "impedance matcher". However it doesn&#
Hi,
I'm facing a problem with a transition from legacy board-file driven ARM
machines to DTB, and I'm under the impression that a solution for it
could be of broader interest.
In short, devices that have been deployed in quantities come in three
hardware variants, which all boot with a unique mac
On 26.06.2013 15:46, Marek Belisko wrote:
> Hi Daniel,
> On 06/26/2013 03:16 PM, Daniel Mack wrote:
>> Hi Marek,
>>
>> On 26.06.2013 15:05, Marek Belisko wrote:
>>> PCM1681 can be controlled via I2C, SPI or in bootstrap mode. This code add
>>> suppor
Hi Marek,
On 26.06.2013 15:05, Marek Belisko wrote:
> PCM1681 can be controlled via I2C, SPI or in bootstrap mode. This code add
> support only for I2C mode.
>
> Signed-off-by: Marek Belisko
> ---
> .../devicetree/bindings/sound/ti,pcm1681.txt | 15 +
> sound/soc/codecs/Kconfig
Hi Michal,
On 19.04.2013 15:38, Michal Bachraty wrote:
> Add devicetree support for this dummy audio soc driver.
I think Mark wants to see only "ASoC:" in the patch subjects now.
>
> Signed-off-by: Michal Bachraty
> ---
> sound/soc/codecs/spdif_transciever.c | 10 ++
> 1 file change
Hi Michal,
On 20.03.2013 14:55, michal.bachr...@gmail.com wrote:
> Thanks for writing this driver! I have tested your si5351 clock
> driver and his tuning capabilities. It works well, it generates
> proper clock frequency, but when new frequency is generated, little
> clock gap (1ms) is generat
On Wed, Mar 20, 2013 at 4:19 PM, Rob Herring wrote:
> On 03/20/2013 09:51 AM, Grant Likely wrote:
>> The same data is now available in sysfs, so we can remove the code
>> that exports it in /proc and replace it with a symlink to the sysfs
>> version.
>>
>> Tested on versatile qemu model and mpc520
to overwrite stored Si5351 configuration
> which is very helpful for clock generators with empty eeprom
> configuration. Corresponding device tree binding documentation is
> also added.
>
> Signed-off-by: Sebastian Hesselbarth
Tested-by: Daniel Mack
Thanks!
Daniel
> ---
&g
remove .is_enabled functions as they read from i2c
> (Reported by Daniel Mack)
> - add CLK_SET_RATE_PARENT on clkout reparent if clkout uses
> its own multisync
>
> Cc: Grant Likely
> Cc: Rob Herring
> Cc: Rob Landley
> Cc: Mike Turquette
> Cc: Stephen Warren
&g
On 13.03.2013 06:32, Dan Carpenter wrote:
> "val" has to be signed for the error handling to work.
Absolutely.
> Signed-off-by: Dan Carpenter
Acked-by: Daniel Mack
>
> diff --git a/sound/soc/codecs/tas5086.c b/sound/soc/codecs/tas5086.c
> index 008bea4..41d03ae
On 12.03.2013 14:36, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Use the module_i2c_driver() macro to make the code smaller
> and a bit simpler.
Thanks for catching this!
> Signed-off-by: Wei Yongjun
Acked-by: Daniel Mack
> ---
> sound/soc/codecs/tas5086.c | 12 +
Hi Sebastian,
On 27.02.2013 11:01, Sebastian Hesselbarth wrote:
> first of all sorry for the late answer but thanks for testing the driver.
>
> On 2/19/13, Daniel Mack wrote:
>> Hi Sebastian,
>>
>> I did some more tests today and it took me a while to dig for the ro
Hi Sebastian,
I did some more tests today and it took me a while to dig for the root
cause why things were not working for me in the first place - see below.
On 09.02.2013 13:59, Sebastian Hesselbarth wrote:
> +==Example==
> +
> +/* 25MHz reference crystal */
> +ref25: ref25M {
> + compatib
On 10.01.2013 21:22, Tony Lindgren wrote:
> * Andreas Fenkart [121220 14:15]:
>> Without functional clock the omap_hsmmc module can't forward
>> SDIO IRQs to the system. This patch reconfigures dat1 line
>> as a gpio while the fclk is off. And uses SDIO IRQ detection of
>> the module, while fclk i
Hi Sebastian,
On 09.02.2013 13:59, Sebastian Hesselbarth wrote:
> This patch adds a common clock driver for Silicon Labs Si5351a/b/c
> i2c programmable clock generators. Currently, the driver supports
> DT kernels only and VXCO feature of si5351b is not implemented. DT
> bindings selectively allow
Hi Tony, Mark, Ezequiel,
Tony Lindgren wrote:
>* Ezequiel Garcia [130121 09:00]:
>> Hi Mark,
>>
>> On Mon, Jan 21, 2013 at 9:30 AM, Mark Rutland
>wrote:
>> > [...]
>> >
>> >> diff --git a/arch/arm/mach-omap2/gpmc.c
>b/arch/arm/mach-omap2/gpmc.c
>> >> index 01ce462..f7de9eb 100644
>> >> --- a/
On Jan 15, 2013 2:06 AM, "Tony Lindgren" wrote:
>
> * Ezequiel Garcia [121223 13:49]:
> > On Fri, Dec 14, 2012 at 7:36 AM, Daniel Mack wrote:
> > > +
> > > +Example for an AM33xx board:
> > > +
> > > + gpmc: gpmc@500
On 12/15/2012 03:27 PM, Grant Likely wrote:
> On Fri, 14 Dec 2012 11:36:44 +0100, Daniel Mack wrote:
>> This patch adds basic DT bindings for OMAP GPMC.
>>
>> The actual peripherals are instantiated from child nodes within the GPMC
>> node, and the only type of device
to use them.
Successfully tested on an AM33xx board.
Signed-off-by: Daniel Mack
---
Documentation/devicetree/bindings/bus/ti-gpmc.txt | 84 ++
.../devicetree/bindings/mtd/gpmc-nand.txt | 76 +
arch/arm/mach-omap2/gpmc.c | 173
The am33xx is capable of handling bch error correction modes, so
enable that feature in the driver.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2
;
- make reg sizes consistent
- AM335x only has 2 wait-pins
Version 8: comments from Grant, thanks to Jon for the summary of all
the derivates:
- Added specific compatible strings for different derivates of OMAPs
- Renamed num-cs to gpmc,num-cs
- Renamed num-waitpins to gpmc,num-waitpins
D
On DT driven boards, the gpmc node will match the driver. Hence, there's
no need to do that unconditionally from the initcall.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-
: Daniel Mack
---
drivers/mtd/nand/omap2.c | 4 +++-
include/linux/platform_data/mtd-nand-omap2.h | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index 0002d5e..1d333497c 100644
--- a/drivers/mtd/nand
gpmc_nand_init() will be called from another driver's probe() function,
so the easiest way to prevent section mismatches is to drop the
annotation here.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a
On 06.12.2012 17:19, Jon Hunter wrote:
>
> On 12/05/2012 05:24 PM, Grant Likely wrote:
>> On Wed, 5 Dec 2012 16:33:48 -0600, Jon Hunter wrote:
>>> Hi Grant,
>>>
>>> On 12/05/2012 04:22 PM, Grant Likely wrote:
>>>> On Wed, 5 Dec 2012 20:09:
Hi Jon,
On 06.12.2012 17:19, Jon Hunter wrote:
>
> On 12/05/2012 05:24 PM, Grant Likely wrote:
>> On Wed, 5 Dec 2012 16:33:48 -0600, Jon Hunter wrote:
>>> Hi Grant,
>>>
>>> On 12/05/2012 04:22 PM, Grant Likely wrote:
>>>> On Wed, 5 Dec 2012 2
On 06.12.2012 17:22, Jon Hunter wrote:
>
> On 12/05/2012 06:03 PM, Tony Lindgren wrote:
>> * Grant Likely [121205 15:26]:
>>> On Wed, 5 Dec 2012 16:33:48 -0600, Jon Hunter wrote:
On 12/05/2012 04:22 PM, Grant Likely wrote:
>
> Please, be specific. Use something like "ti,am3340-gpmc"
On 05.12.2012 20:22, Jon Hunter wrote:
>
> On 12/05/2012 01:09 PM, Daniel Mack wrote:
>> This is a series of patches to support GPMC peripherals on OMAP boards.
>>
>> Grant, Rob, could you have a look and give your Acked-by if
>> appropriate?
>>
>>
>&
to use them.
Successfully tested on an AM33xx board.
Signed-off-by: Daniel Mack
---
Documentation/devicetree/bindings/bus/ti-gpmc.txt | 77 ++
.../devicetree/bindings/mtd/gpmc-nand.txt | 76 +
arch/arm/mach-omap2/gpmc.c | 171
affecting the documentation:
- add num-wait pins properties as they are marked 'required'
- make reg sizes consistent
- AM335x only has 2 wait-pins
Again, many thanks to everybody, in particular Avinash, for the long
disussion about how to the these details right in the first place.
gpmc_nand_init() will be called from another driver's probe() function,
so the easiest way to prevent section mismatches is to drop the
annotation here.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a
The am33xx is capable of handling bch error correction modes, so
enable that feature in the driver.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2
: Daniel Mack
---
drivers/mtd/nand/omap2.c | 4 +++-
include/linux/platform_data/mtd-nand-omap2.h | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index 0002d5e..1d333497c 100644
--- a/drivers/mtd/nand
On DT driven boards, the gpmc node will match the driver. Hence, there's
no need to do that unconditionally from the initcall.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-
On 05.12.2012 18:41, Tony Lindgren wrote:
> * Daniel Mack [121205 09:29]:
>> On 05.12.2012 18:19, Tony Lindgren wrote:
>>>
>>> The plat/cpu.h file will disappear after the merge window, which means
>>> omap2+ related drivers cannot use cpu_is_omap macros.
>
On 05.12.2012 19:33, Tony Lindgren wrote:
> * Jon Hunter [121205 10:22]:
>>
>> On 12/05/2012 11:41 AM, Tony Lindgren wrote:
>>> * Daniel Mack [121205 09:29]:
>>>> On 05.12.2012 18:19, Tony Lindgren wrote:
>>>>>
>>>>> The
Hi Tony,
On 05.12.2012 18:19, Tony Lindgren wrote:
> * Daniel Mack [121205 05:07]:
>> On 29.11.2012 21:59, Jon Hunter wrote:
>>> On 11/29/2012 02:42 PM, Daniel Mack wrote:
>>>> On 29.11.2012 21:32, Jon Hunter wrote:
>>>>>
>>>>> On 1
On 29.11.2012 21:59, Jon Hunter wrote:
> On 11/29/2012 02:42 PM, Daniel Mack wrote:
>> On 29.11.2012 21:32, Jon Hunter wrote:
>>>
>>> On 11/29/2012 01:59 PM, Jon Hunter wrote:
>>>>
>>>> On 11/29/2012 10:01 AM, Daniel Mack wrote:
>>>>
Hi Tony,
Hi Andreas,
On 30.11.2012 18:40, Tony Lindgren wrote:
> * Andreas Fenkart [121130 03:21]:
>>
>> The alternative was to configure dat1 line as a GPIO, while
>> waiting for an IRQ. Then configuring it back as dat1 when the
>> SDIO card is signalling an IRQ. Or the host starts a transfer. I
On 29.11.2012 21:28, Jon Hunter wrote:
>
> On 11/29/2012 10:01 AM, Daniel Mack wrote:
>> This patch adds basic DT bindings for OMAP GPMC.
>>
>> The actual peripherals are instantiated from child nodes within the GPMC
>> node, and the only type of device that
On 29.11.2012 21:32, Jon Hunter wrote:
>
> On 11/29/2012 01:59 PM, Jon Hunter wrote:
>>
>> On 11/29/2012 10:01 AM, Daniel Mack wrote:
>>> The am33xx is capable of handling bch error correction modes, so
>>> enable that feature in the driver.
>>>
>
to use them.
Successfully tested on an AM33xx board.
Signed-off-by: Daniel Mack
---
Documentation/devicetree/bindings/bus/ti-gpmc.txt | 76 +
.../devicetree/bindings/mtd/gpmc-nand.txt | 76 +
arch/arm/mach-omap2/gpmc.c | 171
The am33xx is capable of handling bch error correction modes, so
enable that feature in the driver.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2
-added the "of_node" addition in mtd_nand_omap2.h in 2/5
Again, many thanks to everybody, in particular Avinash, for the long
disussion about how to the these details right in the first place.
Daniel
Daniel Mack (5):
ARM: OMAP: gpmc: don't create devices from initcall on DT
mtd:
gpmc_nand_init() will be called from another driver's probe() function,
so the easiest way to prevent section mismatches is to drop the
annotation here.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a
: Daniel Mack
---
drivers/mtd/nand/omap2.c | 4 +++-
include/linux/platform_data/mtd-nand-omap2.h | 4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index 3282b15..a733f15 100644
--- a/drivers/mtd/nand/omap2
On DT driven boards, the gpmc node will match the driver. Hence, there's
no need to do that unconditionally from the initcall.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-
On 29.11.2012 16:08, Philip, Avinash wrote:
> On Thu, Nov 29, 2012 at 17:28:04, Daniel Mack wrote:
>> Hi Avinash,
>>
>> On 29.11.2012 06:24, Philip, Avinash wrote:
>>> On Wed, Nov 28, 2012 at 22:28:55, Daniel Mack wrote:
>>>> [Resending +devicetree-discu
On 29.11.2012 15:59, Philip, Avinash wrote:
> On Thu, Nov 29, 2012 at 18:11:42, Daniel Mack wrote:
>> On 29.11.2012 13:36, Philip, Avinash wrote:
>>> On Wed, Nov 28, 2012 at 22:28:59, Daniel Mack wrote:
>>> [...]
>>>> + if (!of_property_r
On 29.11.2012 13:36, Philip, Avinash wrote:
> On Wed, Nov 28, 2012 at 22:28:59, Daniel Mack wrote:
> [...]
>> +if (!of_property_read_string(child, "ti,nand-ecc-opt", &s)) {
>> +for (val = 0; val < ARRAY_SIZE(nand_ecc_opts); val++)
>&g
Hi Avinash,
On 29.11.2012 06:24, Philip, Avinash wrote:
> On Wed, Nov 28, 2012 at 22:28:55, Daniel Mack wrote:
>> [Resending +devicetree-discuss, +Rob, +Grant]
>>
>>
>> This is a series of patches to support GPMC peripherals on OMAP boards.
>>
>> Depends
to use them.
Successfully tested on an AM33xx board.
Signed-off-by: Daniel Mack
---
Documentation/devicetree/bindings/bus/ti-gpmc.txt | 76 +
.../devicetree/bindings/mtd/gpmc-nand.txt | 81 +
arch/arm/mach-omap2/gpmc.c | 181
Re-add accidentially forgotten
Documentation/devicetree/bindings/bus/ti-gpmc.txt
- Rename "software" ecc mode to "sw"
- Initialize gpmc_nand_data->is_elm_used to 'true' rather than 1
- Drop ti,nand-ecc-use-elm binding in favor of a new ecc mode
named &quo
The am33xx is capable of handling bch error correction modes, so
enable that feature in the driver.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2
: Daniel Mack
---
drivers/mtd/nand/omap2.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index 3282b15..a733f15 100644
--- a/drivers/mtd/nand/omap2.c
+++ b/drivers/mtd/nand/omap2.c
@@ -1331,6 +1331,7 @@ static int __devinit
gpmc_nand_init() will be called from another driver's probe() function,
so the easiest way to prevent section mismatches is to drop the
annotation here.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a
Hi Avinash,
Hi Peter,
On 23.11.2012 11:43, Philip, Avinash wrote:
> On Wed, Nov 21, 2012 at 15:45:23, Daniel Mack wrote:
>> On 20.11.2012 16:59, Peter Korsgaard wrote:
>>>>>>>> "Daniel" == Daniel Mack writes:
> Peter,
>
> In patch [1], mtd: n
On 20.11.2012 16:59, Peter Korsgaard wrote:
>>>>>> "Daniel" == Daniel Mack writes:
>
> Hi,
>
> >>>> In omap2 driver NAND_ECC_HW ecc mode supports 3 ecc layout
> >>>> OMAP_ECC_HAMMING_CODE_HW_ROMCODE
> >>>> OM
On 11.11.2012 02:56, Daniel Mack wrote:
> On 07.11.2012 16:37, Philip, Avinash wrote:
>> On Wed, Nov 07, 2012 at 15:18:37, Daniel Mack wrote:
>>> On 05.11.2012 14:29, Philip, Avinash wrote:
>>>> On Mon, Nov 05, 2012 at 18:28:22, Daniel Mack wrote:
>>>>&g
On 07.11.2012 16:37, Philip, Avinash wrote:
> On Wed, Nov 07, 2012 at 15:18:37, Daniel Mack wrote:
>> On 05.11.2012 14:29, Philip, Avinash wrote:
>>> On Mon, Nov 05, 2012 at 18:28:22, Daniel Mack wrote:
>>>> On 05.11.2012 12:03, Philip, Avinash wrote:
>>>>
On 05.11.2012 14:29, Philip, Avinash wrote:
> On Mon, Nov 05, 2012 at 18:28:22, Daniel Mack wrote:
>> On 05.11.2012 12:03, Philip, Avinash wrote:
>>> On Fri, Nov 02, 2012 at 20:55:56, Daniel Mack wrote:
>>>> This patch adds basic DT bindings for OMAP GPMC.
>&g
On 05.11.2012 22:46, Jon Hunter wrote:
>
> On 11/02/2012 03:23 PM, Daniel Mack wrote:
>> On 02.11.2012 20:57, Jon Hunter wrote:
>>> On 11/02/2012 02:23 PM, Daniel Mack wrote:
>>>> On 02.11.2012 20:18, Jon Hunter wrote:
>>>>> On 11/02/2012 06:14
On 05.11.2012 12:03, Philip, Avinash wrote:
> On Fri, Nov 02, 2012 at 20:55:56, Daniel Mack wrote:
>> This patch adds basic DT bindings for OMAP GPMC.
>>
>> The actual peripherals are instanciated from child nodes within the GPMC
>> node, and the only type of device tha
On 02.11.2012 20:57, Jon Hunter wrote:
> On 11/02/2012 02:23 PM, Daniel Mack wrote:
>> On 02.11.2012 20:18, Jon Hunter wrote:
>>> On 11/02/2012 06:14 AM, Daniel Mack wrote:
>>>>>> diff --git a/Documentation/devicetree/bindings/bus/ti-gpmc.txt
>>>&
Hi Afzal,
On 02.11.2012 17:31, Afzal Mohammed wrote:
> This series adds usb support to am335x SoC's found on boards like
> Beagle Bone. Here only first instance is supported, as currently
> multiple phy's of same type is not supported (am335x has two USB2
> phy's).
I'm testing these patches with
Hi Jon,
On 02.11.2012 20:18, Jon Hunter wrote:
> On 11/02/2012 06:14 AM, Daniel Mack wrote:
>> Hi Jon,
>>
>> as all comments so far focussed on patch 4/4, could we agree to merge
>> 1-3 of this series already? These are all small and straight-forward
>> things t
to use them.
Successfully tested on an AM33xx board.
Signed-off-by: Daniel Mack
---
Documentation/devicetree/bindings/bus/ti-gpmc.txt | 76 +++
.../devicetree/bindings/mtd/gpmc-nand.txt | 60 +
arch/arm/mach-omap2/gpmc.c | 141
: Daniel Mack
---
drivers/mtd/nand/omap2.c | 4 +++-
include/linux/platform_data/mtd-nand-omap2.h | 2 ++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index 3282b15..a733f15 100644
--- a/drivers/mtd/nand/omap2.c
On DT driven boards, the gpmc node will match the driver. Hence, there's
no need to do that unconditionally from the initcall.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2/gpmc-nand.c
index 8607735..c3616c6 100644
--- a/arch/arm/mach-omap2/gpmc-nand.c
+++ b/arch/arm/mach-omap2/gpmc
interrupt-parent from example bindings
- add of_node_put() at the end of the child iteration
Daniel Mack (4):
mtd: omap-nand: pass device_node in platform data
ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs
ARM: OMAP: gpmc: don't create devices from initcall on DT
ARM: OMAP: gpmc:
i Daniel,
>
> On 11/01/2012 01:36 PM, Daniel Mack wrote:
>> This patch adds basic DT bindings for OMAP GPMC.
>>
>> The actual peripherals are instanciated from child nodes within the GPMC
>> node, and the only type of device that is currently supported is NAND.
>>
to use them.
Successfully tested on an AM33xx board.
Signed-off-by: Daniel Mack
---
Documentation/devicetree/bindings/bus/ti-gpmc.txt | 73 +++
.../devicetree/bindings/mtd/gpmc-nand.txt | 61 +
arch/arm/mach-omap2/gpmc.c | 139
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc-nand.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/gpmc-nand.c b/arch/arm/mach-omap2/gpmc-nand.c
index 8607735..c3616c6 100644
--- a/arch/arm/mach-omap2/gpmc-nand.c
+++ b/arch/arm/mach-omap2/gpmc
y allowing us to
switch the implementation with less pain.
Thanks,
Daniel
Daniel Mack (4):
mtd: omap-nand: pass device_node in platform data
ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs
ARM: OMAP: gpmc: don't create devices from initcall on DT
ARM: OMAP: gpmc: add DT bindings fo
On DT driven boards, the gpmc node will match the driver. Hence, there's
no need to do that unconditionally from the initcall.
Signed-off-by: Daniel Mack
---
arch/arm/mach-omap2/gpmc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/gpmc.c b/arch/arm/mach-
: Daniel Mack
---
drivers/mtd/nand/omap2.c | 4 +++-
include/linux/platform_data/mtd-nand-omap2.h | 2 ++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index 3282b15..a733f15 100644
--- a/drivers/mtd/nand/omap2.c
On 30.10.2012 11:50, Afzal Mohammed wrote:
> Hi Daniel,
>
> On Monday 29 October 2012 10:52 PM, Daniel Mack wrote:
>> On 29.10.2012 16:09, Rob Herring wrote:
>
>>> You may want a CS0 node with nand as a child node of that.
>
>> Hmm, I don't see what tha
On 01.11.2012 00:13, Stephen Warren wrote:
> On 10/31/2012 05:00 PM, Daniel Mack wrote:
>> cc devicetree-discuss. Here's a reference to the full thread:
>>
>> http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/145221/
>>
>> On 26.10.2012 20:39, Stephen
cc devicetree-discuss. Here's a reference to the full thread:
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/145221/
On 26.10.2012 20:39, Stephen Warren wrote:
> On 10/24/2012 03:47 AM, Daniel Mack wrote:
>> Hi,
>>
>> a project I'm involved in use
Hi Rob,
On Oct 29, 2012 10:49 PM, "Rob Herring" wrote:
>
> On 10/29/2012 12:22 PM, Daniel Mack wrote:
> > On 29.10.2012 16:09, Rob Herring wrote:
> >> On 10/29/2012 09:39 AM, Daniel Mack wrote:
> >>> Hi,
> >>>
> >>> we're c
On 29.10.2012 16:09, Rob Herring wrote:
> On 10/29/2012 09:39 AM, Daniel Mack wrote:
>> Hi,
>>
>> we're currently working on a DT binding for the GPMC bus that is found
>> on SoCs by TI. The implementation is based on CS lines and an 8, 16 or
>> 32 bit paralle
Hi,
we're currently working on a DT binding for the GPMC bus that is found
on SoCs by TI. The implementation is based on CS lines and an 8, 16 or
32 bit parallel interface. That IP is quite flexible, and it can for
example be used for physmap flash, external peripherals or even NAND.
Depending on
On 19.10.2012 11:59, Afzal Mohammed wrote:
> enhance rtc-omap driver with DT capability
>
> Signed-off-by: Afzal Mohammed
> Acked-by: Sekhar Nori
> ---
>
> v4:
> Proper devicetree documentation
>
> v2:
> Use compatible as ti,da830-rtc instead of ti,am1808-rtc
>
> Documentation/devicetree/b
Hi,
On 14.10.2012 12:59, Sebastian Hesselbarth wrote:
> Adding LAKML and devtree as there might be people willing to comment about
> DT representation of i2c-attached clock generators, too.
>
> On 10/12/2012 08:17 PM, Daniel Mack wrote:
>> On 11.10.2012 18:00, Sebastian
On 01.10.2012 23:11, David Miller wrote:
> From: Daniel Mack
> Date: Wed, 26 Sep 2012 19:24:27 +0200
>
>> Allow users to specify the phy interface of the CPSW slaves. The new
>> node parameter is called "phy_if_mode" and is optional. The original
>> behaviou
Apart from pure matching, the bindings also support setting the the
reset gpio line.
Signed-off-by: Daniel Mack
Cc: Alexander Sverdlin
---
Documentation/devicetree/bindings/sound/cs4271.txt | 36 ++
sound/soc/codecs/cs4271.c | 24 +--
2
On 26.09.2012 20:50, N, Mugunthan V wrote:
>> For RMII mode operation in 100Mbps, the CPSW needs to set the
>> IFCTL_A / IFCTL_B bits in the MACCONTROL register.
>>
>> Signed-off-by: Daniel Mack
>> Cc: Mugunthan V N
>> Cc: Vaibhav Hiremath
>> Cc: David
For RMII mode operation in 100Mbps, the CPSW needs to set the
IFCTL_A / IFCTL_B bits in the MACCONTROL register.
Signed-off-by: Daniel Mack
Cc: Mugunthan V N
Cc: Vaibhav Hiremath
Cc: David S. Miller
---
drivers/net/ethernet/ti/cpsw.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a
Allow users to specify the phy interface of the CPSW slaves. The new
node parameter is called "phy_if_mode" and is optional. The original
behaviour of the driver is preserved when not given.
Signed-off-by: Daniel Mack
Cc: Mugunthan V N
Cc: Vaibhav Hiremath
Cc: David
Hi Stephen,
On 10.09.2012 21:40, Stephen Warren wrote:
> On 09/10/2012 09:03 AM, Daniel Mack wrote:
>> Add DT bindings for the gpio-regulator driver and some documentation on
>> how to use it.
>
>> +++ b/Documentation/devicetree/bindings/regulator/gpio-regula
Add DT bindings for the gpio-regulator driver and some documentation on
how to use it.
Signed-off-by: Daniel Mack
---
v1 -> v2
Fixed wrong kzalloc() size.
.../bindings/regulator/gpio-regulator.txt | 58 ++
drivers/regulator/gpio-regulator.c |
Add DT bindings for the gpio-regulator driver and some documentation on
how to use it.
Signed-off-by: Daniel Mack
---
.../bindings/regulator/gpio-regulator.txt | 58 ++
drivers/regulator/gpio-regulator.c | 118 -
2 files changed, 175
roller's private data so
the DT bindings can easily build upon the driver.
Signed-off-by: Daniel Mack
---
drivers/spi/spi-gpio.c | 34 --
1 file changed, 24 insertions(+), 10 deletions(-)
diff --git a/drivers/spi/spi-gpio.c b/drivers/spi/spi-gpio.c
index 0b5
This patch adds DT bindings to the spi-gpio driver and some
documentation about how to use it.
Signed-off-by: Daniel Mack
---
Documentation/devicetree/bindings/spi/spi-gpio.txt | 29 +++
drivers/spi/spi-gpio.c | 99 +-
2 files changed, 125
On 05.09.2012 05:24, Mark Brown wrote:
> On Mon, Sep 03, 2012 at 01:50:34PM +0200, Linus Walleij wrote:
>> On Sun, Sep 2, 2012 at 10:17 PM, Daniel Mack wrote:
>
>>> Hmm, I don't know whether anyone took those patches yet? Mark?
>
>> Mark better take them,
On 05.08.2012 21:12, Linus Walleij wrote:
> On Sun, Aug 5, 2012 at 1:57 PM, Daniel Mack wrote:
>
>>> Acked-by: Linus Walleij
>>
>> Ok, thanks. Mark, did the patches reach you this time? I think they
>> should go thru the SPI tree.
>
> Yeah no problem, Ma
On 15.08.2012 09:13, Éric Piel wrote:
> On 07-08-12 20:49, Daniel Mack wrote:
> :
>>
>> I fixed all these issues now and attached a v4.
>>
> Sorry for the late reply, I had read the v3 but didn't find time to send
> comments. They are all addressed in v4.
>
1 - 100 of 118 matches
Mail list logo
