On Wed, Apr 10, 2013 at 10:33:37AM -0700, Christian Daudt wrote:
> Hi Arnd, Olof,
> Please pull the branch below - it contains the BCM281xx l2 cache
> enabling code.
>
> Thanks,
>csd
>
>
> The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
>
> Linux 3.9-rc5 (20
On Wed, Apr 10, 2013 at 02:29:14PM -0400, Mike Frysinger wrote:
> I want to use this in more places, so put it in util.h rather than
> copying & pasting it into another file.
>
> Signed-off-by: Mike Frysinger
Acked-by: David Gibson
--
David Gibson| I'll have my music baroq
On Wed, Apr 10, 2013 at 02:29:11PM -0400, Mike Frysinger wrote:
> Often times, fdts get embedded in other larger files. Rather than force
> people to `dd` the blob out themselves, make the fdtdump file smarter.
>
> It can now scan the blob looking for the fdt magic. Once locate, it does
> a litt
On Wed, Apr 10, 2013 at 02:29:10PM -0400, Mike Frysinger wrote:
> This starts a new usage framework and then cuts fdtdump over to it.
> Now we can do `fdtdump -h` and get something useful back.
Hrm. The problem is that the new scheme relies on getopt_long(),
which is a GNU extension. I'd like to
From: Sebastian Hesselbarth
Date: Wed, 10 Apr 2013 19:36:29 +0200
> Patch "net: mvmdio: get and enable optional clock" was missing an
> update of the corresponding device tree binding documentation. This
> patch adds the clocks property to mvmdio binding documentation.
>
> Signed-off-by: Sebasti
On 04/10/13 03:13, Mark Rutland wrote:
+
+- #size-cells : Must be 1.
+
+- ranges : Indicates parent and child bus address space are the same.
+
>>> Similarly, what if someone wants to write a more complex mapping for some
>>> reason?
>>>
>>> We should be able to handle it i
On Wed, Apr 10, 2013 at 03:31:18PM +0100, Srinivas KANDAGATLA wrote:
> If you try to insert a new node or extend a property with large value,
> using fdtput you will notice that it always fails.
>
> example:
> fdtput -v -p -ts ./tst.dtb "/node-1" "property-1" "str10"
> Error at 'node-1': FDT_ERR_
On Wed, Apr 10, 2013 at 03:33:18PM +0100, Srinivas KANDAGATLA wrote:
> libfdt has code to add new property or node or extend a property to an
> arbitary value, however it cannot be used because all the library
> functions take preallocated fdt pointer limted to a size.
>
> Adding realloc function
On 04/05/2013 01:37 AM, Thierry Reding wrote:
> On Thu, Apr 04, 2013 at 03:28:54PM -0600, Stephen Warren wrote:
> [...]
>>> diff --git
>>> a/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
>>> b/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
>>
>>>
>>>
+Required prope
On 04/05/2013 12:03 AM, Thierry Reding wrote:
> On Thu, Apr 04, 2013 at 03:30:01PM -0600, Stephen Warren wrote:
>> On 04/04/2013 03:28 PM, Stephen Warren wrote:
>>> On 04/03/2013 08:45 AM, Thierry Reding wrote:
Move the PCIe driver from arch/arm/mach-tegra into the
drivers/pci/host direct
On Monday 08 April 2013, Tomasz Figa wrote:
> On Saturday 06 of April 2013 00:24:18 Tomasz Figa wrote:
> > On Friday 05 of April 2013 21:54:21 Arnd Bergmann wrote:
> > > On Friday 05 April 2013, Tomasz Figa wrote:
> >
> > I'm not sure what you mean by a register-level interface. Something like
> >
On 04/10/2013 11:36 PM, Randy Dunlap wrote:
On 04/10/13 01:48, Stephen Rothwell wrote:
Hi all,
Changes since 20130409:
on i386:
ERROR: "of_get_next_parent" [drivers/media/v4l2-core/videodev.ko] undefined!
'of_get_next_parent()' should be exported for use by modules...?
Yes, there was a
On Wednesday 10 April 2013 14:29:17 Stephen Warren wrote:
>
> > If the information is there, whether to convert from IRQ to GPIO
> > or from GPIO to IRQ is a technicality and any order should be
> > feasible in some way?
>
> There isn't always a unique 1:1 mapping between GPIOs and IRQs. Put
> an
On 04/10/13 01:48, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130409:
>
on i386:
ERROR: "of_get_next_parent" [drivers/media/v4l2-core/videodev.ko] undefined!
'of_get_next_parent()' should be exported for use by modules...?
--
~Randy
_
Dear Andrew Murray,
On Wed, 10 Apr 2013 08:29:26 +0100, Andrew Murray wrote:
> diff --git a/include/linux/of_pci.h b/include/linux/of_pci.h
> index bb115de..6852481 100644
> --- a/include/linux/of_pci.h
> +++ b/include/linux/of_pci.h
> @@ -11,4 +11,7 @@ struct device_node;
> struct device_node *
Ben, Michal,
On Wed, 10 Apr 2013 08:13:54 -0500, Rob Herring wrote:
> Adding Ben H and Michal...
>
> On 04/10/2013 02:29 AM, Andrew Murray wrote:
> > The pci_process_bridge_OF_ranges function, used to parse the
> > "ranges" property of a PCI host device, is found in both Microblaze
> > and PowerP
On Wed, Apr 10, 2013 at 10:29 PM, Stephen Warren wrote:
> On 04/10/2013 12:12 PM, Linus Walleij wrote:
>> If the information is there, whether to convert from IRQ to GPIO
>> or from GPIO to IRQ is a technicality and any order should be
>> feasible in some way?
>
> There isn't always a unique 1:1
On Wed, Apr 10, 2013 at 9:50 PM, Jon Hunter wrote:
> On 04/10/2013 02:44 PM, Linus Walleij wrote:
>> All patches applied with Kevin's and Santosh's tags!
>
> Thanks. Sorry for the confusion!
>
> By the way, I am hoping you only took 1-4,
Yeah I only took 1-4, no problem...
Yours,
Linus Walleij
* Stephen Warren [130410 10:37]:
> On 04/10/2013 02:12 AM, Prabhakar Lad wrote:
> ...
> > Following is the proposed fix/hack let me know if its OK.
> >
> > Regards,
> > --Prabhakar
> >
> > ->>>
> >
> > diff --git a/drivers/pinctrl/core.h b/drivers/pinctrl/core.h
> > index ee72f1
On 04/10/2013 12:12 PM, Linus Walleij wrote:
> On Fri, Mar 29, 2013 at 6:01 PM, Stephen Warren wrote:
>> On 03/27/2013 02:55 PM, Linus Walleij wrote:
>>> On Wed, Mar 27, 2013 at 5:09 PM, Stephen Warren
>>> wrote:
>>>
>>> This is the case for some SMSC911x clients like the snowball
>>> routing it
* Nishanth Menon [130410 12:23]:
> On Wed, Apr 10, 2013 at 1:49 PM, Tony Lindgren wrote:
> >
> > We can avoid the concern of storing the struct clk * and do the
> > look up lazily on consumer driver probe by setting a dummy struct
> > clk * here. Then replace of_clk_src_simple_get() with a custom
On 04/10/2013 02:44 PM, Linus Walleij wrote:
> On Wed, Apr 10, 2013 at 9:41 PM, Jon Hunter wrote:
>> On 04/10/2013 02:39 PM, Linus Walleij wrote:
>>> On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter wrote:
>>>
When booting with device-tree the function pointer for detecting context
loss is
On 04/10/2013 02:33 PM, Linus Walleij wrote:
> On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter wrote:
>
>> Currently the IRQ domain is not freed once allocated, in the case where
>> omap_gpio_probe() fails. Therefore, ensure we free the domain if the
>> probe does fail. Furthermore, the local variab
On Wed, Apr 10, 2013 at 9:41 PM, Jon Hunter wrote:
> On 04/10/2013 02:39 PM, Linus Walleij wrote:
>> On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter wrote:
>>
>>> When booting with device-tree the function pointer for detecting context
>>> loss is not populated. Ideally, the pm_runtime framework shou
On Thu, Apr 4, 2013 at 12:02 PM, Lars Poeschel wrote:
> From: Lars Poeschel
>
> This converts the mcp23s08 driver to be able to be used with device
> tree.
> There is a "spi-present-mask" device tree property, that allows to
> use multiple of this spi chips on the same chipselect.
>
> Signed-off
On 04/10/2013 02:39 PM, Linus Walleij wrote:
> On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter wrote:
>
>> When booting with device-tree the function pointer for detecting context
>> loss is not populated. Ideally, the pm_runtime framework should be
>> enhanced to allow a means for reporting context
On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter wrote:
> When booting with device-tree the function pointer for detecting context
> loss is not populated. Ideally, the pm_runtime framework should be
> enhanced to allow a means for reporting context/state loss and we could
> avoid populating such func
On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter wrote:
> The OMAP GPIO interrupt service routine is checking each bit in the
> GPIO interrupt status register to see which bits are set. It is not
> efficient to check every bit especially if only a few bits are set.
> Therefore, instead of checking eve
On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter wrote:
> From: Tarun Kanti DebBarma
>
> 68942edb09f69b6e09522d1d346665eb3aadde49 (gpio/omap: fix wakeups
> on level-triggered GPIOs) already restores the fallingdetect and
> risingdetect contexts in *_runtime_resume(). These registers were
> modified i
On Thu, Apr 4, 2013 at 10:16 PM, Jon Hunter wrote:
> Currently the IRQ domain is not freed once allocated, in the case where
> omap_gpio_probe() fails. Therefore, ensure we free the domain if the
> probe does fail. Furthermore, the local variable "ret" is not needed
> and so remove this.
>
> Sign
On Fri, Mar 15, 2013 at 2:45 PM, Andreas Larsson wrote:
> The drivers sets up an irq domain and hands out unique virqs to irq
> capable gpio lines regardless of which underlying irqs maps to which gpio
> line.
>
> Signed-off-by: Andreas Larsson
(...)
> +- irqmap : An array with an index for each
Hi Tony,
On Wed, Apr 10, 2013 at 1:49 PM, Tony Lindgren wrote:
> * Nishanth Menon [130410 10:44]:
>> Details in the patch below (Tony, I have added you as collaborator for
>> helping in getting this working-clk_add_alias was'nt needed in the
>> internal patch discussion we had - I have taken a bi
On Fri, Mar 15, 2013 at 2:45 PM, Andreas Larsson wrote:
> This driver supports GRGPIO gpio cores available in the GRLIB VHDL IP
> core library from Aeroflex Gaisler.
>
> Signed-off-by: Andreas Larsson
> ---
> .../devicetree/bindings/gpio/gpio-grgpio.txt | 24 +++
> drivers/gpio/Kconfig
* Nishanth Menon [130410 10:44]:
> Details in the patch below (Tony, I have added you as collaborator for
> helping in getting this working-clk_add_alias was'nt needed in the
> internal patch discussion we had - I have taken a bit of freedom in
> adding your contributions to the patch below)
OK t
On 04/09/2013 04:06 PM, Thomas Petazzoni wrote:
> From: Thierry Reding
>
> This function can be used to parse a bus-range property as specified by
> device nodes representing PCI bridges.
>
> Signed-off-by: Thierry Reding
Reviewed-by: Rob Herring
> ---
> drivers/of/of_pci.c| 25 ++
On 04/09/2013 04:06 PM, Thomas Petazzoni wrote:
> From: Thierry Reding
>
> This function can be used to parse the device and function number from a
> standard 5-cell PCI resource. PCI_SLOT() and PCI_FUNC() can be used on
> the returned value obtain the device and function numbers respectively.
>
On 04/10/2013 02:29 AM, Andrew Murray wrote:
> This patch converts the pci_load_of_ranges function to use the new common
> of_pci_range_parser.
>
> Signed-off-by: Andrew Murray
> Signed-off-by: Liviu Dudau
Reviewed-by: Rob Herring
> ---
> arch/mips/pci/pci.c | 50 -
When hacking raw fdt files, it's useful to know the actual offsets into
the file each node appears. Add a --debug mode that includes this.
Signed-off-by: Mike Frysinger
---
fdtdump.c | 40
1 file changed, 36 insertions(+), 4 deletions(-)
diff --git a/fd
I want to use this in more places, so put it in util.h rather than
copying & pasting it into another file.
Signed-off-by: Mike Frysinger
---
convert-dtsv0-lexer.l | 2 --
dtc.h | 1 -
util.h| 2 ++
3 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/con
Now that all utils have converted to the new usage framework, we can
rename to just plain "usage()" and avoid naming conflicts.
Signed-off-by: Mike Frysinger
---
convert-dtsv0-lexer.l | 2 +-
dtc.c | 6 +++---
fdtdump.c | 2 +-
fdtget.c | 6 +++---
fd
This helps standardize the flag processing and the usage screens.
Only lightly tested; would be great if someone who uses these utils
could double check.
Signed-off-by: Mike Frysinger
---
convert-dtsv0-lexer.l | 22 +++---
dtc.c | 111 ++-
This starts a new usage framework and then cuts fdtdump over to it.
Now we can do `fdtdump -h` and get something useful back.
Signed-off-by: Mike Frysinger
---
fdtdump.c | 31 +++
util.c| 54 ++
util.h| 61 ++
Often times, fdts get embedded in other larger files. Rather than force
people to `dd` the blob out themselves, make the fdtdump file smarter.
It can now scan the blob looking for the fdt magic. Once locate, it does
a little validation on the main struct to make sure we didn't hit random
binary
We only display this string, so there's no need for it to be writable.
Constify away!
Acked-by: David Gibson
Signed-off-by: Mike Frysinger
---
util.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/util.h b/util.h
index 3c20b15..d856eb9 100644
--- a/util.h
+++ b/util.h
@@ -2
We've got these handy helpers, so let's use them.
Acked-by: David Gibson
Signed-off-by: Mike Frysinger
---
util.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/util.c b/util.c
index b081fa8..12f0614 100644
--- a/util.c
+++ b/util.c
@@ -212,12 +212,12 @@ int utilfdt_rea
This is so all utilities can have this flag and not just dtc.
Acked-by: David Gibson
Signed-off-by: Mike Frysinger
---
dtc.c | 5 +
util.c | 7 +++
util.h | 5 +
3 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/dtc.c b/dtc.c
index d40e220..e4e1b84 100644
--- a/dtc.c
For a follow up commit, we want to be able to scan the buffer that was
returned to us. In order to do that safely, we need to know how big
the buffer actually is, so pass that back if requested.
Signed-off-by: Mike Frysinger
---
fdtget.c | 2 +-
fdtput.c | 2 +-
tests/testutil
Each utility currently open codes how they process options and
implement usage(). This leads to inconsistent behavior and output
which sucks. A bunch also get common things wrong (like sending
--help to stderr).
Rather than go through them one by one and fix their bugs, start
a new mini framewor
On Wed, Apr 3, 2013 at 9:49 AM, Andreas Larson wrote:
> On 2013-03-27 09:58, Linus Walleij wrote:
>>
>> On Tue, Mar 19, 2013 at 1:40 AM, Anton Vorontsov wrote:
>>>
>>> On Fri, Mar 15, 2013 at 02:45:38PM +0100, Andreas Larsson wrote:
There is no general support for 64-bit big endian acce
On 04/10/2013 02:29 AM, Andrew Murray wrote:
> 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 relying on architecture
> specific
> DT handl
On Fri, Mar 29, 2013 at 6:01 PM, Stephen Warren wrote:
> On 03/27/2013 02:55 PM, Linus Walleij wrote:
>> On Wed, Mar 27, 2013 at 5:09 PM, Stephen Warren
>> wrote:
>>
>> This is the case for some SMSC911x clients like the snowball
>> routing it to a GPIO, whereas I think the RealView and Integrat
On 13:55-20130410, Roger Quadros wrote:
> On 04/10/2013 11:06 AM, Mike Turquette wrote:
> > Quoting Nishanth Menon (2013-04-09 13:49:00)
> >> On 10:43-20130409, Tony Lindgren wrote:
> >>> * Tony Lindgren [130409 09:54]:
> >>>> * Roger Quadros [130409
On Mon, Apr 08, 2013 at 06:03:54PM +0100, Olav Haugan wrote:
> Hi Will,
Hello,
> > Generally, the StreamIDs are fixed in hardware (as a function of various AXI
> > bits -- see the SMMU integration guide) and cannot be set by software.
> > Furthermore, when the StreamIDs have an implicit effect on
This patch adds an optional shared block clock to avoid lockups on
clock gated controllers. Besides the new clock, clock handling for
existing clocks is cleaned up and moved to devm_clk_get. Device
tree binding documentation is updated for the new clocks property.
Signed-off-by: Sebastian Hesselba
Patch "net: mvmdio: get and enable optional clock" was missing an
update of the corresponding device tree binding documentation. This
patch adds the clocks property to mvmdio binding documentation.
Signed-off-by: Sebastian Hesselbarth
---
Cc: Grant Likely
Cc: Rob Herring
Cc: Rob Landley
Cc: "D
On 04/10/2013 02:12 AM, Prabhakar Lad wrote:
...
> Following is the proposed fix/hack let me know if its OK.
>
> Regards,
> --Prabhakar
>
> ->>>
>
> diff --git a/drivers/pinctrl/core.h b/drivers/pinctrl/core.h
> index ee72f1f..78fb42d 100644
> --- a/drivers/pinctrl/core.h
> +++ b
Hooray Google!
Thanks for removing plain text sending from gmail web-frontend.. *sigh*
Sorry for resending this, but HTML mails get rejected by linux mailing lists.
On 04/10/2013 04:48 PM, Michal Bachraty wrote:
Hi Sebastian,
This driver doesn't work for me. In my case, u-boot initializes si-53
On Wed, Apr 10, 2013 at 4:48 PM, Michal Bachraty <
michal.bachr...@streamunlimited.com> wrote:
> Hi Sebastian,
> This driver doesn't work for me. In my case, u-boot initializes si-5351 and
> power down unused clocks while booting kernel. there is need for power up
> clocks as was in previous vers
Hi Christian,
On 04/10/2013 05:40 PM, Christian Ruppert wrote:
> This patch adds a device tree binding for the simple fixed factor clock
> divider/multiplier of the common clock tree binding.
This patch remind me of something :
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-August/116
libfdt has code to add new property or node or extend a property to an
arbitary value, however it cannot be used because all the library
functions take preallocated fdt pointer limted to a size.
Adding realloc function into libfdt can help tools like fdtput to insert
nodes or properties or extend
If you try to insert a new node or extend a property with large value,
using fdtput you will notice that it always fails.
example:
fdtput -v -p -ts ./tst.dtb "/node-1" "property-1" "str10"
Error at 'node-1': FDT_ERR_NOSPACE
or
fdtput -v -c ./tst.dtb "/node-1"
Error at 'node-1': FDT_ERR_NOSPACE
This patch makes use of realloc functions added to libfdt.
Now the tool can insert a new node or property or extend a property with
new value greater than original size.
Without this patch fdtput tool complains with FDT_ERR_NOSPACE when we
try to add a node/property or extend the value of a proper
2013/4/10 Guennadi Liakhovetski :
> On Wed, 10 Apr 2013, Barry Song wrote:
>
>> 2013/4/10 Guennadi Liakhovetski :
>> > On Wed, 10 Apr 2013, Barry Song wrote:
>
> [snip]
>
>> >> > This cannot work, because some I2C devices, e.g. sensors, need a clock
>> >> > signal from the camera interface to probe
Hi Sebastian,
This driver doesn't work for me. In my case, u-boot initializes si-5351 and
power down unused clocks while booting kernel. there is need for power up
clocks as was in previous versions of your driver.
See patch, whre the problem is fixed:
@@ -992,6 +992,10 @@ static long si5351_
On Wed, 10 Apr 2013, Barry Song wrote:
> 2013/4/10 Guennadi Liakhovetski :
> > On Wed, 10 Apr 2013, Barry Song wrote:
[snip]
> >> > This cannot work, because some I2C devices, e.g. sensors, need a clock
> >> > signal from the camera interface to probe. Before the bridge driver has
> >> > complet
Add properties for some of the more important bits of platform data and
fill out the binding document.
Not all of the current platform data is suitable for the sort of fixed
configuration that is done using DT, some of it should have runtime
mechanisms added instead and some is unlikely to ever be
We can actually read this back from the device but we use this when
registered using standard I2C board data registration so make sure
it's there for OF too.
Signed-off-by: Mark Brown
---
Untested at present.
drivers/mfd/wm8994-core.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions
2013/4/10 Guennadi Liakhovetski :
> On Wed, 10 Apr 2013, Barry Song wrote:
>
>> Hi Guennadi,
>
> There's a typo above.
sorry for the typo.
>
>> Thanks!
>>
>> 2013/4/10 Guennadi Liakhovetski :
>> > Hi Barry
>> >
>> > On Wed, 10 Apr 2013, Barry Song wrote:
>> >
>> >> Hi Guennadia,
>> >>
>> >> 2012/
On Wed, 10 Apr 2013, Barry Song wrote:
> Hi Guennadia,
There's a typo above.
> Thanks!
>
> 2013/4/10 Guennadi Liakhovetski :
> > Hi Barry
> >
> > On Wed, 10 Apr 2013, Barry Song wrote:
> >
> >> Hi Guennadia,
> >>
> >> 2012/9/27 Guennadi Liakhovetski :
> >> > Currently soc-camera doesn't work wi
2013/4/10 Mark Brown :
> On Wed, Apr 10, 2013 at 09:53:20PM +0800, Barry Song wrote:
>> 2013/4/10 Guennadi Liakhovetski :
>
>> >> what about another possible way:
>> >> we let all host and i2c client driver probed in any order,
>
>> > This cannot work, because some I2C devices, e.g. sensors, need a
On Wed, Apr 10, 2013 at 09:53:20PM +0800, Barry Song wrote:
> 2013/4/10 Guennadi Liakhovetski :
> >> what about another possible way:
> >> we let all host and i2c client driver probed in any order,
> > This cannot work, because some I2C devices, e.g. sensors, need a clock
> > signal from the came
Hi Guennadia,
Thanks!
2013/4/10 Guennadi Liakhovetski :
> Hi Barry
>
> On Wed, 10 Apr 2013, Barry Song wrote:
>
>> Hi Guennadia,
>>
>> 2012/9/27 Guennadi Liakhovetski :
>> > Currently soc-camera doesn't work with independently registered I2C client
>> > devices, it has to register them itself. Thi
On Wed, Apr 10, 2013 at 06:33:51AM -0700, Guenter Roeck wrote:
> On Wed, Apr 10, 2013 at 02:36:22PM +0200, Nicolas Ferre wrote:
> > Compiling the at91rm9200_wdt.c driver without at91rm9200
> > support was leading to several errors:
> >
> > drivers/built-in.o: In function `at91_wdt_close':
> > at91
On Wed, Apr 10, 2013 at 02:36:22PM +0200, Nicolas Ferre wrote:
> Compiling the at91rm9200_wdt.c driver without at91rm9200
> support was leading to several errors:
>
> drivers/built-in.o: In function `at91_wdt_close':
> at91_adc.c:(.text+0xc9fe4): undefined reference to `at91_st_base'
> drivers/bui
Adding Ben H and Michal...
On 04/10/2013 02:29 AM, Andrew Murray wrote:
> The pci_process_bridge_OF_ranges function, used to parse the "ranges"
> property of a PCI host device, is found in both Microblaze and PowerPC
> architectures. These implementations are nearly identical. This patch
> moves t
Compiling the at91rm9200_wdt.c driver without at91rm9200
support was leading to several errors:
drivers/built-in.o: In function `at91_wdt_close':
at91_adc.c:(.text+0xc9fe4): undefined reference to `at91_st_base'
drivers/built-in.o: In function `at91_wdt_write':
at91_adc.c:(.text+0xca004): undefine
Hi Barry
On Wed, 10 Apr 2013, Barry Song wrote:
> Hi Guennadia,
>
> 2012/9/27 Guennadi Liakhovetski :
> > Currently soc-camera doesn't work with independently registered I2C client
> > devices, it has to register them itself. This patch adds support for such
> > configurations, in which case cli
On Sun, Apr 07, 2013 at 09:49:03PM -0500, Timur Tabi wrote:
> Markus Pargmann wrote:
> >This patch copies some parts from imx-ssi to support AC97 on
> >imx27-pca100 and imx27-pcm043. It is activated with a new fsl,imx-ac97
> >bool property. It was tested on imx27-pca100.
>
> I'm not crazy about th
Hi,
On Wed, 10 Apr 2013 09:06:11 + Tang Yuantian-B29983
wrote:
>
> Yes, I already sent out the v2 patch.
> Please see: http://patchwork.ozlabs.org/patch/235288/
Thanks. I should read all my email before replying to it :-)
--
Cheers,
Stephen Rothwells...@canb.auug.org.
On 04/10/2013 12:54 AM, Nishanth Menon wrote:
> On 15:49-20130409, Nishanth Menon wrote:
>> On 10:43-20130409, Tony Lindgren wrote:
>>> * Tony Lindgren [130409 09:54]:
* Roger Quadros [130409 03:00]:
> On 04/05/2013 06:58 PM, Tony Lindgren wrote:
>>
>> Can't you just use the cloc
On Sun, Apr 07, 2013 at 09:52:17PM -0500, Timur Tabi wrote:
> Markus Pargmann wrote:
> >Notes:
> >Changes in v2:
> > - Simplify the driver, by combining audmux port configurations. The
> > audmux driver actually knows on which platform he is running and
> > will return the appro
On 04/10/2013 11:06 AM, Mike Turquette wrote:
> Quoting Nishanth Menon (2013-04-09 13:49:00)
>> On 10:43-20130409, Tony Lindgren wrote:
>>> * Tony Lindgren [130409 09:54]:
* Roger Quadros [130409 03:00]:
> On 04/05/2013 06:58 PM, Tony Lindgren wrote:
>>
>> Can't you just use the
Hi Guennadia,
2012/9/27 Guennadi Liakhovetski :
> Currently soc-camera doesn't work with independently registered I2C client
> devices, it has to register them itself. This patch adds support for such
> configurations, in which case client drivers have to request deferred
> probing until their hos
Vivek Gautam wrote:
>
> This patch-set is in continuation with patch-series:
> [PATCH v4 0/4] Enable ehci, ohci and dwc3 devices on exynos5250
> out of which follwowing patches have been picked up:
> ARM: Exynos5250: Enabling ehci-s5p driver
> ARM: Exynos5250: Enabling ohci-exynos driver
>
> Base
Am Mittwoch, 10. April 2013, 12:15:48 schrieb Kukjin Kim:
> Heiko Stübner wrote:
> > This is the second installment of beginning devicetree support the
> > Samsung S3C24xx architectures and focuses on the s3c2416 for now.
> >
> > Included is the devicetree support for the s3c24xx irq controller an
Vivek Gautam wrote:
>
> Based on 'for-next' of linux-samsung tree with following patches
> from Doug on top:
> usb: Document clocks in samsung, exynos4210-ehci/ohci bindings
> ARM: dts: add usb 2.0 clock references to exynos5250 device tree
>
> Also depending upon following patch-series for Samsu
Heiko Stübner wrote:
>
> This is the second installment of beginning devicetree support the
> Samsung S3C24xx architectures and focuses on the s3c2416 for now.
>
> Included is the devicetree support for the s3c24xx irq controller and
> basic support for smdk2416 boards, which can sucessfully boot
On Tue, Apr 09, 2013 at 05:42:38PM +0100, Stephen Boyd wrote:
> On 04/09/13 02:08, Mark Rutland wrote:
> > On Tue, Apr 09, 2013 at 03:30:20AM +0100, Stephen Boyd wrote:
> >>
> >> -** Timer node properties:
> >> +** CP15 Timer node properties:
> >>
> >> - compatible : Should at least contain on
Sachin Kamat wrote:
>
> Added MFC related clock entries in exynos4.dtsi file.
>
> Signed-off-by: Sachin Kamat
> Reviewed-by: Sylwester Nawrocki
Applied this series.
Thanks.
- Kukjin
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozla
Hi,
On Tue, 9 Apr 2013 14:56:09 +0800 wrote:
>
> From: Tang Yuantian
>
> As the function itself says it is caller's responsibility to call the
> of_node_put(). So, remove it on success to keep the reference count
> correct.
>
> Signed-off-by: Tang Yuantian
> ---
> drivers/of/base.c | 3 ---
Hi Stephen,Peter,
On Mon, Apr 8, 2013 at 10:54 PM, Stephen Warren wrote:
> On 04/08/2013 07:12 AM, Prabhakar Lad wrote:
>> On Wed, Apr 3, 2013 at 10:14 PM, Stephen Warren
>> wrote:
>>> On 04/03/2013 03:16 AM, Prabhakar Lad wrote:
Hi Linus/Stephen,
I am working adding DT nodes fo
Quoting Thomas Petazzoni (2013-03-27 07:40:23)
> 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.
>
> Signed-off-by: T
Quoting Thomas Petazzoni (2013-03-27 07:40:24)
> The current revision of the datasheet only mentions the gatable clocks
> for the PCIe 0.0, 0.1, 0.2 and 0.3 interfaces, and forgot to mention
> the ones for the PCIe 1.0, 1.1, 1.2, 1.3, 2.0 and 3.0
> interfaces. After confirmation with Marvell engine
Quoting Nishanth Menon (2013-04-09 13:49:00)
> On 10:43-20130409, Tony Lindgren wrote:
> > * Tony Lindgren [130409 09:54]:
> > > * Roger Quadros [130409 03:00]:
> > > > On 04/05/2013 06:58 PM, Tony Lindgren wrote:
> > > > >
> > > > > Can't you just use the clock name there to get it?
> > > >
>
The pci_process_bridge_OF_ranges function, used to parse the "ranges"
property of a PCI host device, is found in both Microblaze and PowerPC
architectures. These implementations are nearly identical. This patch
moves this common code to a common place.
Signed-off-by: Andrew Murray
Signed-off-by:
This patch converts the pci_load_of_ranges function to use the new common
of_pci_range_parser.
Signed-off-by: Andrew Murray
Signed-off-by: Liviu Dudau
---
arch/mips/pci/pci.c | 50 --
1 files changed, 16 insertions(+), 34 deletions(-)
diff --gi
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 relying on architecture specific
DT handling. This will make it easier to write archiecture indep
This patchset factors out duplicated code associated with parsing PCI
DT "ranges" properties across the architectures and introduces a
"ranges" parser. This parser "of_pci_range_parser" can be used directly
by ARM host bridge drivers enabling them to obtain ranges from device
trees.
Compared to th
98 matches
Mail list logo
