On Sat, Jul 20, 2013 at 6:10 AM, David Miller wrote:
> From: Grant Likely
> Date: Fri, 19 Jul 2013 18:15:34 -0700
>
>> What is the best way to transfer a membership list over? Can I import
>> a list, or do I need to tell everyone to register on the new list?
>
> I
On Sun, Jul 21, 2013 at 10:46 AM, Grant Likely wrote:
> On Sun, Jul 21, 2013 at 1:29 AM, Joe Perches wrote:
>> On Sat, 2013-07-20 at 17:17 -0700, Olof Johansson wrote:
>>> On Fri, Jul 19, 2013 at 8:19 PM, Grant Likely
>>> wrote:
>>> > Device tree bindings
On Sun, Jul 21, 2013 at 7:56 PM, Rob Herring wrote:
> On 07/19/2013 10:19 PM, Grant Likely wrote:
>> +OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
>> +M: Pawel Moll
>> +M: Mark Rutland
>> +M: Stephen Warren
>> +M: Ian Campbell
>
> You can a
On Sun, Jul 21, 2013 at 2:46 PM, Jon Loeliger wrote:
> Perhaps it is time to also place the official repo
> of the Device Tree Compiler on git,kernel.org as well?
I'm fine with that. I can't say I'm excited about options like github.
g.
___
devicetree-
On Sun, Jul 21, 2013 at 9:48 PM, Rob Herring wrote:
> On 07/21/2013 09:42 AM, Rob Herring wrote:
>> On 07/19/2013 01:14 PM, Sebastian Andrzej Siewior wrote:
>>> So I called of_platform_populate() on a device to get each child device
>>> probed and on rmmod and I need to reverse its doing. After a
On Sun, Jul 21, 2013 at 9:45 PM, Rob Herring wrote:
> We can debate whether the driver order matters or not, but either way
> I'm not sure this patch does the right thing. It doesn't really look
> correct to me, but I haven't dug into it.
>
> We've already tried to fix matching and reverted the fi
On Sun, Jul 21, 2013 at 1:29 AM, Joe Perches wrote:
> On Sat, 2013-07-20 at 17:17 -0700, Olof Johansson wrote:
>> On Fri, Jul 19, 2013 at 8:19 PM, Grant Likely
>> wrote:
>> > Device tree bindings require a lot more attention than they used to.
>> > We'v
On Sat, Jul 20, 2013 at 6:00 PM, Hank Leininger wrote:
> On Sat, Jul 20, 2013 at 06:28:19PM +0200, Linus Walleij wrote:
>> Hi MARC list archive folks,
>>
>> could you please start archiving the following recently addes VGER lists
>> at marc.info:
>>
>> These go into the "Linux" folder:
>> linux-gp
A number of us had a face-to-face meeting in Dublin last week to talk
about DT maintainership and the fact that it simply isn't working right
now. Neither Rob nor I can keep up with the load and there are a lot of
poorly designed bindings appearing in the tree.
Device tree binding maintainership n
On Tue, 18 Jun 2013 18:39:22 +0400, Alexander Shiyan wrote:
> Patch adds of_get_next_child and of_get_next_available_child
> stubs for non-OF builds.
>
> Signed-off-by: Alexander Shiyan
> ---
> include/linux/of.h | 16 ++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> dif
On Mon, 17 Jun 2013 13:04:59 +0800, Zhangfei Gao
wrote:
> Signed-off-by: Zhangfei Gao
Applied.
g.
> ---
> .../devicetree/bindings/vendor-prefixes.txt|1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
> b/Documentation/d
On Mon, 01 Jul 2013 16:34:26 -0500, Rob Herring wrote:
> On 07/01/2013 01:20 PM, Santosh Shilimkar wrote:
> > On some PAE architectures, the entire range of physical memory could reside
> > outside the 32-bit limit. These systems need the ability to specify the
> > initrd location using 64-bit nu
On Mon, 15 Jul 2013 19:50:27 +0100, David Woodhouse wrote:
> On Mon, 2013-07-15 at 09:56 -0700, Greg KH wrote:
> > How about a hint for subsystem maintainers as to what exactly we should
> > be looking for with these bindings? I for one have no idea what is
> > "right" vs. "wrong" with them, so a
New list on vger.kernel.org. The old list was a pain to moderate.
Signed-off-by: Grant Likely
Cc: Rob Herring
Cc: devicetree-discuss@lists.ozlabs.org
Cc: devicet...@vger.kernel.org
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
On Mon, 15 Jul 2013 23:07:36 +0200, Linus Walleij
wrote:
> On Mon, Jul 15, 2013 at 4:29 PM, Jonathan Corbet wrote:
>
> > Do we need a kernel summit discussion, or do we just need a good
> > document? Or, to phrase the question another way, are we lacking a
> > consensus among the clueful regar
On Wed, 1 May 2013 10:53:54 +0200, Gabor Juhos wrote:
> This prefix will be used in various compatible properties
> for the devices from Qualcomm Atheros, Inc.
>
> Cc: Luis R. Rodriguez
> Signed-off-by: Gabor Juhos
Applied, thanks
g.
> ---
> Documentation/devicetree/bindings/vendor-prefixe
On Mon, 1 Jul 2013 20:26:52 +0100, Mark Brown wrote:
> From: Mark Brown
>
> It is not used outside of this file so doesn't need to be in the global
> namespace.
>
> Signed-off-by: Mark Brown
Applied, thanks.
g.
___
devicetree-discuss mailing list
On Tue, 9 Jul 2013 16:10:53 +0800, Huang Shijie wrote:
> äº 2013å¹´07æ09æ¥ 15:51, Sascha Hauer åé:
> > On Tue, Jul 09, 2013 at 03:46:34PM +0800, Huang Shijie wrote:
> >> äº 2013å¹´07æ09æ¥ 15:05, Sascha Hauer åé:
> >>> Why don't you set the matching order in the driver the way you w
On Fri, 26 Apr 2013 16:17:52 -0700, Stepan Moskovchenko
wrote:
>
> Hello. I am creating a DTS file for an ARM (Qualcomm MSM) target which
> supports LPAE, meaning that the target is capable of addressing memory
> beyond the standard 4GB boundary. To account for the fact that the
> memory node
On Mon, 17 Jun 2013 16:48:13 +0200, Sebastian Andrzej Siewior
wrote:
> I am getting a few
> |warning: unused variable âpâ [-Wunused-variable]
> |warning: unused variable âpropâ [-Wunused-variable]
>
> in the case where CONFIG_OF is not defined and the parameters are only
> used in the lo
On Tue, 09 Jul 2013 14:10:58 -0600, Eric Holmberg
wrote:
> I am trying to determine if Device Tree is an appropriate use for
> configuring drivers and would like to request comments. We currently
> use Device Tree in our Shared Memory Driver (SMD) that manages up to 64
> ports (where a port c
On Tue, 21 May 2013 11:00:35 +0100, Sudeep KarkadaNagesha
wrote:
> Hi Rob, Grant,
>
> On 01/05/13 12:11, Sudeep KarkadaNagesha wrote:
> > From: Sudeep KarkadaNagesha
> >
> > These are couple of updates to existing PM/OPP library to support
> > sharing of OPPs between different device nodes.
>
On Thu, 18 Jul 2013 21:49:27 -0500, Rob Herring wrote:
> On 07/18/2013 05:24 AM, Sebastian Andrzej Siewior wrote:
> > It almost does not matter because most users use only the ->start member
> > of the struct. However if this struct is passed to a platform device
> > which is then added via platfo
On Sun, 23 Jun 2013 15:50:07 +0800, Axel Lin wrote:
> list_first_entry() expects the list is not empty, we need to check if list is
> empty before calling list_first_entry(). Thus use list_first_entry_or_null()
> instead of list_first_entry().
>
> Signed-off-by: Axel Lin
Applied, thanks.
g.
>
er. I recommend that they set up a shared
tree on git.kernel.org that they each have commit access to similar to
the tip tree or the arm-soc tree, but it is up to them.
Signed-off-by: Grant Likely
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Stephen Warren
Cc: Ian Campbell
Cc: Rob Herring
Cc: Olof Joha
Hello everyone,
The ozlabs devicetree list was requiring too much work to moderate, so
I'm closing down that list and replacing it with a list on
vger.kernel.org.
http://vger.kernel.org/vger-lists.html#devicetree
I'll be sending a patch to MAINTAINERS shortly.
g.
___
don't /think/ it was the concept of deferred probe that was considered
>> hacky, but perhaps just the first proof-of-concept implementation, and
>> any hackiness was presumably solved before the feature was merged.
>
> Well...
>
> http://lwn.net/Articles/485194/
>
On Wed, Jul 17, 2013 at 9:57 AM, Stephen Warren wrote:
> On 07/16/2013 09:02 PM, Shawn Guo wrote:
>> On Tue, Jul 16, 2013 at 09:45:43AM -0600, Stephen Warren wrote:
>>> Registering the driver earlier won't cause any bugs. However, it's not
>>> the correct approach.
>>>
>>> Deferred probe /is/ the
On Wed, Jul 10, 2013 at 6:23 PM, Florian Fainelli wrote:
> Hello Thomas,
>
> 2013/7/10 Thomas Petazzoni :
>> Dear Florian Fainelli,
>>
>> On Wed, 10 Jul 2013 17:29:44 +0100, Florian Fainelli wrote:
> [snip]
>
>>
>>> > };
>>> >
>>> > phy1: ethernet-phy@1 {
>>> >
SPI are in good hands with Linus and Mark. Rob Herring has a
really good grasp on the DT core code, and in the last week there have
been several volunteers to create and maintain a DT bindings tree. You
can expect to see an email about that hit the list shortly.
Signed-off-by: Grant Likely
---
MAINT
Hi Marek,
Thanks for working on this. Comments below...
On Wed, Jun 26, 2013 at 2:40 PM, Marek Szyprowski
wrote:
> Add device tree support for contiguous memory regions defined in device
> tree. Initialization is done in 2 steps. First, the contiguous memory is
> reserved, what happens very earl
On Wed, Jul 10, 2013 at 5:52 PM, Dmitry Torokhov
wrote:
> On Wed, Jul 10, 2013 at 04:14:57PM +0100, Grant Likely wrote:
>> On Fri, 28 Jun 2013 07:19:06 -0600, Mathieu Poirier
>> wrote:
>> > On 13-06-28 12:09 AM, Dmitry Torokhov wrote:
>> > >>>> I do
On Fri, 28 Jun 2013 07:19:06 -0600, Mathieu Poirier
wrote:
> On 13-06-28 12:09 AM, Dmitry Torokhov wrote:
> I do not agree. We want the binding to be generic and not tied
> specifically to the keyreset functionality. As such 'input-keyset' or
> 'input-keychord' are more appropria
On Fri, Jul 5, 2013 at 11:07 AM, Sascha Hauer wrote:
> Again the difference between supernodes and graphs is that the supernode
> approach does not contain information about what components are needed
> to do something useful with the device. You simply have to wait until
> *all* components are pr
On Fri, Jul 5, 2013 at 10:34 AM, Sebastian Hesselbarth
wrote:
> So for the discussion, I can see that there have been some voting for
> super-node, some for node-to-node linking. Although I initially proposed
> super-nodes, I can also happily live with node-to-node linking alone.
>
> Either someon
On Fri, Jul 5, 2013 at 9:50 AM, Russell King wrote:
> On Fri, Jul 05, 2013 at 09:37:34AM +0100, Grant Likely wrote:
>> Alternatively, you can have the same effect with a property or set of
>> properties in the controller node that contains phandles to the
>> required device
On Wed, Jul 3, 2013 at 10:02 AM, Sascha Hauer wrote:
> On Wed, Jul 03, 2013 at 05:57:18PM +0900, Inki Dae wrote:
>> > video {
>> > /* Single video card w/ multiple lcd controllers */
>> > card0 {
>> > compatible = "marvell,armada-510-display";
>> > reg = <0 0x3f
On Tue, Jul 2, 2013 at 9:25 PM, Russell King wrote:
> On Tue, Jul 02, 2013 at 09:57:32PM +0200, Sebastian Hesselbarth wrote:
>> I am against a super node which contains lcd and dcon/ire nodes. You can
>> enable those devices on a per board basis. We add them to dove.dtsi but
>> disable them by def
Hi Linus,
Please pull the following branch. Description in the signed tag.
g.
The following changes since commit 317ddd256b9c24b0d78fa8018f80f1e495481a10:
Linux 3.10-rc5 (2013-06-08 17:41:04 -0700)
are available in the git repository at:
git://git.secretlab.ca/git/linux tags/devicetree-fo
On Wed, 3 Jul 2013 15:37:56 +0100, Grant Likely wrote:
> On Wed, Jul 3, 2013 at 3:10 PM, Rob Herring wrote:
> > On 07/03/2013 01:01 AM, Benjamin Herrenschmidt wrote:
> >> Commit:
> >>
> >> e38c0a1fbc5803cbacdaac0557c70ac8ca5152e7
> >> of
On Wed, Jul 3, 2013 at 3:10 PM, Rob Herring wrote:
> On 07/03/2013 01:01 AM, Benjamin Herrenschmidt wrote:
>> Commit:
>>
>> e38c0a1fbc5803cbacdaac0557c70ac8ca5152e7
>> of/address: Handle #address-cells > 2 specially
>>
>> broke real time clock access on Bimini, js2x, and similar powerpc
>> ma
On Fri, Jun 28, 2013 at 11:38 AM, Thierry Reding
wrote:
> On Fri, Jun 28, 2013 at 10:49:15AM +0200, Hiroshi Doyu wrote:
>> Grant Likely wrote @ Wed, 26 Jun 2013 12:03:20
>> +0200:
>>
>> > On Wed, Jun 26, 2013 at 7:00 AM, Hiroshi Doyu wrote:
>> > &
On Thu, Jun 27, 2013 at 9:54 PM, Rob Herring wrote:
> On 06/21/2013 12:20 PM, Santosh Shilimkar wrote:
>> On Friday 21 June 2013 05:04 AM, Sebastian Andrzej Siewior wrote:
>>> On 06/21/2013 02:52 AM, Santosh Shilimkar wrote:
diff --git a/arch/microblaze/kernel/prom.c b/arch/microblaze/kernel/
On Thu, Jun 27, 2013 at 9:22 PM, Mr. Robert G Palmer Jr.
wrote:
> I apologize up front if this is the wrong place for these questions. I'm
> relatively new to the OF Device Tree. If this is the wrong place, would
> someone point me to the correct discussion location.
>
> 1. Is it possible to tak
On Fri, 21 Jun 2013 19:56:29 +0100, Grant Likely
wrote:
> On Fri, Jun 21, 2013 at 7:35 PM, Alexander Shiyan wrote:
> >> >> On Fri, Jun 21, 2013 at 7:17 AM, Alexander Shiyan
> >> >> wrote:
> >> >> >> On Thu, Jun 20, 2013 at 5:26 PM, Grant
On Wed, Jun 26, 2013 at 1:44 PM, Sebastian Hesselbarth
wrote:
> On 06/26/13 12:03, Grant Likely wrote:
>>
>> On Wed, Jun 26, 2013 at 7:00 AM, Hiroshi Doyu wrote:
>>>
>>> Grant Likely wrote @ Tue, 25 Jun 2013
>>> 19:52:33 +0200:
>>>
>&g
On Wed, Jun 26, 2013 at 11:31 AM, Thierry Reding
wrote:
> On Wed, Jun 26, 2013 at 11:03:20AM +0100, Grant Likely wrote:
>> On Wed, Jun 26, 2013 at 7:00 AM, Hiroshi Doyu wrote:
>> > Grant Likely wrote @ Tue, 25 Jun 2013 19:52:33
>> > +0200:
>> >
>>
On Wed, Jun 26, 2013 at 7:00 AM, Hiroshi Doyu wrote:
> Grant Likely wrote @ Tue, 25 Jun 2013 19:52:33
> +0200:
>
>> > Here's my workaround. I need to call of_detach_node() with OF_DYNAMIC
>> > to avoid duplicated device registration.
>>
>> Gah! my
On Tue, Jun 25, 2013 at 5:36 PM, Hiroshi Doyu wrote:
> Stephen Warren wrote @ Tue, 25 Jun 2013 16:56:22
> +0200:
>
>> >> How this problem is supposed to be solved in the kernel ?
>> >>
>> >> 1- drivers that are to be up and running at early_initcall time must not
>> >>rely on the device/driv
On Tue, Jun 25, 2013 at 2:29 PM, Christian Ruppert
wrote:
> On Mon, Jun 03, 2013 at 10:51:06AM +0100, Grant Likely wrote:
>> On Mon, Jun 3, 2013 at 5:05 AM, Vineet Gupta
>> wrote:
>> > On 06/01/2013 03:48 AM, Grant Likely wrote:
>> >> If I were working on
On Mon, Jun 24, 2013 at 5:33 PM, Lorenzo Pieralisi
wrote:
> Hi all,
>
> I am dealing with a lingering problem related to init and probing of platform
> devices early (before initcalls) in the kernel boot process. The problem,
> which is nothing new, is related to how platform devices are created i
tiated by device tree and supports interrupts for
> all GPIOs.
>
> Signed-off-by: James Hogan
> Cc: Grant Likely
> Cc: Rob Herring
> Cc: Rob Landley
> Cc: Linus Walleij
> Cc: linux-...@vger.kernel.org
> Cc: devicetree-discuss@lists.ozlabs.org
> ---
> Changes in
On Fri, Jun 21, 2013 at 7:35 PM, Alexander Shiyan wrote:
>> >> On Fri, Jun 21, 2013 at 7:17 AM, Alexander Shiyan
>> >> wrote:
>> >> >> On Thu, Jun 20, 2013 at 5:26 PM, Grant Likely
>> >> >> wrote:
>> >> >> > On
On Fri, Jun 21, 2013 at 6:21 PM, Alexander Shiyan wrote:
>> On Fri, Jun 21, 2013 at 7:17 AM, Alexander Shiyan wrote:
>> >> On Thu, Jun 20, 2013 at 5:26 PM, Grant Likely
>> >> wrote:
>> >> > On Thu, 20 Jun 2013 16:49:54 -0700, Bryan Wu wrote:
>
On Fri, Jun 21, 2013 at 1:36 AM, Bryan Wu wrote:
> On Thu, Jun 20, 2013 at 5:26 PM, Grant Likely wrote:
>> On Thu, 20 Jun 2013 16:49:54 -0700, Bryan Wu wrote:
>>> Hi Rob,
>>>
>>> Is this patch good for merging?
>>>
>>> In Alex's one pa
On Thu, 20 Jun 2013 16:49:54 -0700, Bryan Wu wrote:
> Hi Rob,
>
> Is this patch good for merging?
>
> In Alex's one patch to add device tree supporting for a leds driver,
> we got building errors due to miss definitions of some of_xxx api
> functions.
>
> It looks obviously to me that we need t
On Mon, Jun 17, 2013 at 5:33 PM, Linus Walleij wrote:
> On Mon, Jun 17, 2013 at 5:48 PM, Stephen Warren wrote:
>
>> This has just shown up in next-20130617, and breaks at least the
>> TPS65910 and TPS62360 drivers, since they assume that the id parameter
>> passed to probe is non-NULL. However, n
On Fri, Jun 14, 2013 at 4:55 PM, Collins, Rod
wrote:
> Grant
>
> That makes perfect sense, but I find that the DTB is included in the
> vmlinux.lds.h file which lives in source/include/asm-generic.
>
> This seems to always want to put the dtb in the init section which gets
> removed. To fix this t
On Sat, Jun 15, 2013 at 7:59 PM, Walter Goossens wrote:
> On 06/15/13 15:14, Grant Likely wrote:
>> My first recommendation would be the way it is described in
>> Documentation/arm/Booting and
>> Documentation/devicetree/booting-without-of.txt,
>> by which I mean pass
On Wed, 12 Jun 2013 15:26:42 -0600, Jason Gunthorpe
wrote:
> On Wed, Jun 12, 2013 at 06:12:22PM -0300, Ezequiel Garcia wrote:
>
> > > Actually, the best thing about this solution is that we don't even
> > > have to bother setting up the mappings when loading the mbus driver:
> > > We don't need
On Thu, 13 Jun 2013 17:28:51 +0200, Sebastian Andrzej Siewior
wrote:
> I am getting a few
> |warning: unused variable âpâ [-Wunused-variable]
> |warning: unused variable âpropâ [-Wunused-variable]
>
> in the case where CONFIG_OF is not defined and the parameters are only
> used in the lo
On Fri, 24 May 2013 17:36:30 +0800, Ley Foon Tan wrote:
> This patch adds address translation to fdt. It is needed when the early
> console is connected to a simple-bus (bridge) that has address translation
> enabled.
>
> Walter Goossens have submitted first version of patch previously. This
> pa
On Wed, 12 Jun 2013 21:12:39 +0200, Walter Goossens
wrote:
> On 06/12/13 20:23, Grant Likely wrote:
> > On Wed, Jun 12, 2013 at 6:33 PM, Collins, Rod
> > wrote:
> >> The blob is built into the zImage.initramfs.gz image which is put into
> >> flash. The zImage
On Fri, 14 Jun 2013 21:05:30 -0600, Stephen Warren
wrote:
> On 06/14/2013 07:12 PM, David Gibson wrote:
> > On Tue, Jun 11, 2013 at 11:11:25AM -0600, Stephen Warren wrote:
> >> From: Stephen Warren
> >>
> >> Many useful new features have been added to dtc since the last
> >> release. Projects t
On Thu, 30 May 2013 11:45:23 -0600, Stephen Warren
wrote:
> On 08/23/2012 12:15 PM, Yann E. MORIN wrote:
> > Hello All!
> >
> > Following advice from Jon Loeliger, I would suggest that a new release
> > of DTC be tagged and packaged.
> >
> > It is important for some projects to rely on a releas
On Mon, 3 Jun 2013 23:39:16 -0700, Mike Turquette
wrote:
> Parses OMAP clock data from DT and registers those clocks with the clock
> framework. dt_omap_clk_init must be called early during boot for timer
> initialization so it is exported and called from the existing clock code
> instead of pr
On Wed, 05 Jun 2013 10:50:02 -0600, Stephen Warren
wrote:
> On 06/03/2013 09:36 AM, Stephen Warren wrote:
> > From: Stephen Warren
> >
> > Previously, the #line parsing regex ended with ({WS}+[0-9]+)?. The {WS}
> > could match line-break characters. If the #line directive did not contain
> > th
On Wed, 05 Jun 2013 20:20:39 +0200, Tomasz Figa wrote:
> Hi,
>
> On Sunday 19 of May 2013 00:56:30 Tomasz Figa wrote:
> > Some drivers might rely on availability of trigger flags in IRQ
> > resource, for example to configure the hardware for particular interrupt
> > type. However current code cre
On Thu, Jun 13, 2013 at 11:49 PM, Collins, Rod
wrote:
> Grant
>
> What is considered the correct way to include the blob in the build so
> that it is not removed?
Don't put it in an __init section. :-p
However, I realized that the .dtb.S target does exactly that under the
assumption that multip
On Thu, Jun 13, 2013 at 11:52 PM, Benjamin Herrenschmidt
wrote:
> On Thu, 2013-06-13 at 23:22 +0100, Grant Likely wrote:
>> Grant Likely (2):
>> dtc: Update generated files to output from Bison 2.5
>> dtc: ensure #line directives don't consume data from
On Thu, Jun 13, 2013 at 11:08 PM, Stephen Warren wrote:
> On 06/13/2013 03:48 PM, Grant Likely wrote:
>> This patch merely updates the generated dtc parser and lexer files to
>> the output generated by Bison 2.5. The previous versions were generated
>> from version 2.4.1. The
x from the code generation change
caused by a different Bison version.
Benjamin Herrenschmidt (1):
of: Fix locking vs. interrupts
Grant Likely (2):
dtc: Update generated files to output from Bison 2.5
dtc: ensure #line d
. Otherwise the Bison changes would be intermingled with the
functional changes.
Signed-off-by: Grant Likely
---
scripts/dtc/dtc-parser.tab.c_shipped | 715 +++
scripts/dtc/dtc-parser.tab.h_shipped | 14 +-
2 files changed, 388 insertions(+), 341 deletions(-)
diff --git a
ommit a1ee6f068e1c8dbc62873645037a353d7852d5cc]
Reported-by: Ian Campbell
Signed-off-by: Stephen Warren
Acked-by: David Gibson
Signed-off-by: Grant Likely
---
scripts/dtc/dtc-lexer.l | 2 +-
scripts/dtc/dtc-lexer.lex.c_shipped | 232 ++--
2 files changed, 117 inser
I've cherry picked this patch from the DTC repository. I've got it in my
device tree merge branch and will be sending it to Linus shortly.
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/devicetre
On Wed, Jun 12, 2013 at 6:33 PM, Collins, Rod
wrote:
> The blob is built into the zImage.initramfs.gz image which is put into
> flash. The zImage.initramfs.gz is self copied from flash to RAM, then
> uncompressed to the running area. I will dig into the location of the
> blob in the image and repo
On Wed, Jun 12, 2013 at 3:32 PM, Collins, Rod
wrote:
>
> I have been chasing a problem where a module device driver that uses the
> device tree I install, cannot find a compatible match when I know the device
> tree has the match for my driver.
>
> So I wrote a small module device driver that du
On Mon, 10 Jun 2013 09:43:30 +0200, Linus Walleij
wrote:
> On Sun, Jun 9, 2013 at 4:21 PM, Arnd Bergmann wrote:
> > On Sunday 09 June 2013, Linus Walleij wrote:
> >> + /*
> >> +* IP AMBA bus clocks, driving the bus side of the
> >> +* peripheral cloc
On Mon, 10 Jun 2013 15:40:14 +0200, Wolfram Sang wrote:
> On Mon, Jun 10, 2013 at 02:18:17PM +0200, Linus Walleij wrote:
> > On Fri, Jun 7, 2013 at 11:32 PM, Wolfram Sang wrote:
> > > ...
> > >> I2C devices probed from device tree should subsequently be
> > >> fixed to handle the case where of_ma
On Fri, 7 Jun 2013 23:32:42 +0200, Wolfram Sang wrote:
> ...
> > I2C devices probed from device tree should subsequently be
> > fixed to handle the case where of_match_table() is
> > used (I think none of them do that today), and platforms should
> > fix their device trees to use compatible string
On Tue, 11 Jun 2013 17:29:43 +0200, Javier Martinez Canillas
wrote:
> On 06/11/2013 04:48 PM, Florian Vaussard wrote:
> > Use the MTD constants for NAND and OneNAND nodes used in OMAP3
> > DTS.
> >
> > Signed-off-by: Florian Vaussard
> > ---
> > arch/arm/boot/dts/omap3-devkit8000.dts | 10 ++
0x0800
> +#define SZ_256M 0x1000
> +#define SZ_512M 0x2000
> +
> +#define SZ_1G 0x4000
> +#define SZ_2G
On Tue, 4 Jun 2013 12:57:06 +0200, Linus Walleij
wrote:
> On Mon, Jun 3, 2013 at 3:42 PM, Lee Jones wrote:
>
> > In this patch we're populating a clk_data array, one clock per element to
> > act as a clk look-up using indexes supplied from Device Tree.
> >
> > Cc: Mike Turquette
> > Signed-off
On Wed, 12 Jun 2013 00:03:57 +0200, Laurent Pinchart
wrote:
> Document DT properties for the generic pinctrl parameters and add a
> parser function.
>
> Signed-off-by: Laurent Pinchart
> ---
> .../bindings/pinctrl/pinctrl-bindings.txt | 29 +++
> drivers/pinctrl/pinconf-generic.c
On Wed, Jun 12, 2013 at 12:43 PM, Arnd Bergmann wrote:
> On Wednesday 12 June 2013 12:07:46 Grant Likely wrote:
>>
>> It actually seems a bit silly to put the internal regs into the ranges
>> property at all. It's not like they need to be translated or provided to
>
{
> + ret = gpiochip_add_pin_range(gpio_chip, p->config.pctl_name, 0,
> + gpio_chip->base, gpio_chip->ngpio);
> + if (ret < 0)
> + dev_warn(&pdev->dev, "failed to add pin range\n");
&g
On Wed, 12 Jun 2013 15:29:38 +1000, Benjamin Herrenschmidt
wrote:
> On Wed, 2013-05-22 at 07:26 -0500, Rob Herring wrote:
> > > git://sources.calxeda.com/kernel/linux.git of-platform-removal
> >
> > Ben,
> >
> > Did you have a chance to test this? I want to get this into -next.
>
> I tested th
r touchscreen.
> - Updated commit message.
>
> :100755 100755 8fffa3c... 65ee2cd... M
> Documentation/devicetree/bindings/mfd/tps6507x.txt
> :100644 100644 65e0f9a... 89232ee... M
> drivers/input/touchscreen/tps6507x-ts.c
> Documentation/devicetree/bindings/mf
On Wed, 12 Jun 2013 00:34:14 +0200, Arnd Bergmann wrote:
> On Tuesday 11 June 2013 15:50:23 Jason Gunthorpe wrote:
> > So, I think we can/have agree that the ranges in the FDT should
> > reflect the bootloader's settings, and if the ranges is missing an
> > element it means the bootloader didn't s
On Tue, 11 Jun 2013 17:26:47 +0200, Arnd Bergmann wrote:
> On Tuesday 11 June 2013 10:57:38 Ezequiel Garcia wrote:
> > Jason, Arnd:
> >
> > On Sat, Jun 08, 2013 at 07:45:06PM -0600, Jason Gunthorpe wrote:
> > [...]
> > >
> > > This is the mangling I was referring to. It needs to be the offset
>
On Sat, 8 Jun 2013 19:45:06 -0600, Jason Gunthorpe
wrote:
> On Sat, Jun 08, 2013 at 03:38:52PM -0300, Ezequiel Garcia wrote:
>
> > > mbus {
> > >ranges = <0x012f 0 0xe800 0x800>
> > >devbus-bootcs {
> > >ranges = <0 0x012f 0 0x800>
> > >}
> > > }
> > >
On Sat, 8 Jun 2013 15:38:52 -0300, Ezequiel Garcia
wrote:
> Hi Jason, Arnd:
>
> Thanks for your reviews!
>
> I agree with most of your suggestions so far. However, I'd like to discuss
> one point before we move forward with the other (imo, less importants)
> issues. See below.
>
> On Fri, Jun
On Fri, 7 Jun 2013 13:47:42 -0300, Ezequiel Garcia
wrote:
> Ideally 'ranges' entry should be added in device tree source files.
> However, since those properties do not inherit the entries from included
> files it would be a duplication hell, which means a nightmare to
> maintain.
>
> So, inste
On Wed, 12 Jun 2013 08:24:26 +, "J, KEERTHY" wrote:
> Hello Grant,
>
> > -Original Message-
> > From: Lee Jones [mailto:lee.jo...@linaro.org]
> > > > >
> > > > > Applied, thanks.
> > > >
> > > > Ah wait. It appears Grant wants to take this.
> > > >
> > > > Unapplied, thanks. :)
> > >
On Wed, Jun 12, 2013 at 7:30 AM, Michal Simek wrote:
> On 06/12/2013 12:22 AM, Grant Likely wrote:
>> On Tue, 11 Jun 2013 16:08:11 +0200, Michal Simek wrote:
>> It would mean every device driver needs to be polled. As long as the
>> polling frequency is high enough for
On Wed, 12 Jun 2013 10:25:56 +0200 (CEST), Thomas Gleixner
wrote:
> On Wed, 12 Jun 2013, Benjamin Herrenschmidt wrote:
>
> > The OF code uses irqsafe locks everywhere except in a handful of functions
> > for no obvious reasons. Since the conversion from the old rwlocks, this
> > now triggers loc
On Mon, 10 Jun 2013 19:34:45 +0100, Will Deacon wrote:
> Add myself as maintainer for the ARM system MMU driver.
>
> Signed-off-by: Will Deacon
Acked-by: Grant Likely
> ---
> MAINTAINERS | 6 ++
> 1 file changed, 6 insertions(+)
>
> diff --git a/MAINTAINE
On Mon, 10 Jun 2013 19:34:43 +0100, Will Deacon wrote:
> This patch adds a description of the device tree binding for the ARM
> System MMU architecture.
>
> Cc: Rob Herring
> Cc: Andreas Herrmann
> Cc: Joerg Roedel
> Signed-off-by: Will Deacon
A
Cc: Jassi Brar
> Cc: Vinod Koul
> Signed-off-by: Will Deacon
Acked-by: Grant Likely
> ---
> drivers/dma/pl330.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
> index 22e2a8f..f1bc593 100644
> ---
Vinod Koul
> Signed-off-by: Will Deacon
Right, device drivers shouldn't be cosing their own primecell ID parser.
Acked-by: Grant Likely
> ---
> drivers/dma/pl330.c | 27 +++
> 1 file changed, 3 insertions(+), 24 deletions(-)
>
> diff --git a/d
1 - 100 of 2897 matches
Mail list logo
