Re: Linus being annoyed by the ARM kernel code

2011-04-04 Thread jonsm...@gmail.com
ecific DT makes them easier to write. There's nothing to be gained by adding dozens of CPU specific nodes to a board level device tree. -- Jon Smirl jonsm...@gmail.com ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org http

Schemas for device trees

2012-03-28 Thread jonsm...@gmail.com
ermine what the legal ranges were. A validating schema would contain the legal ranges. Aren't the files in Documentation/devicetree/bindings really just schemas written in English with no automated way of checking the DTS files against them? -- Jon Smirl jonsm...@gmail.com _

Re: Schemas for device trees

2012-03-28 Thread jonsm...@gmail.com
ne up to date. Piece of a simple schema: Describes data like this: Joe Bill If you feed it this, you'd get a validation error. Joe Bill -- Jon Smirl jonsm...@gmail.com ___ devicetree-discuss mailing l

Re: Schemas for device trees

2012-03-29 Thread jonsm...@gmail.com
nother pass can be made to implement a common parser. The common parser would get all of these attributes and parse them into a struct. Then we can work on making sure each driver actually implements these core attributes consistently. -- Jon Smirl jonsm...@gmail.com _

Re: Schemas for device trees

2012-04-02 Thread jonsm...@gmail.com
On Thu, Mar 29, 2012 at 9:59 PM, jonsm...@gmail.com wrote: > i2c provides an example of where a schema would be useful. > From the binding text files, I removed the common items Another reason for schemas, I just misspelled an attribute. It took me several hours to figure out why my

Re: [PATCH v2] gpio: Device tree support for LPC32xx

2012-04-07 Thread jonsm...@gmail.com
On Sat, Apr 7, 2012 at 1:45 PM, Roland Stigge wrote: > On 07/04/12 19:17, jonsm...@gmail.com wrote: >>> Please consider how the groups are specified in >>> drivers/gpio/gpio-lpc32xx.c. They each have different numbers of lines >>> and GPIO / GPI / GPO functionalit

DT support in i2c

2012-04-07 Thread jonsm...@gmail.com
Grant, moving of_i2c.c into drivers/i2c would parallel your spi/gpio patches. of_i2c_register_devices() needs to be moved up into i2c-core. Right now the ten bus drivers are individually calling it. -- Jon Smirl jonsm...@gmail.com ___ devicetree

Re: DT support in i2c

2012-04-08 Thread jonsm...@gmail.com
On Sun, Apr 8, 2012 at 9:17 PM, Rob Herring wrote: > On 04/07/2012 06:26 PM, jonsm...@gmail.com wrote: >> Grant, moving  of_i2c.c into drivers/i2c would parallel your spi/gpio >> patches. >> >> of_i2c_register_devices() needs to be moved up into i2c-core. Right >

Two different interrupt-parents

2012-04-14 Thread jonsm...@gmail.com
How do you define a device with two different interrupt parents? I have a OTG USB controller where the main usb interrupt is on the system interrupt controller and the OTG power interrupts are on a cascaded PIC. -- Jon Smirl jonsm...@gmail.com

Problem with of_irq_to_resource() and IRQ flags

2012-04-15 Thread jonsm...@gmail.com
sing them back means adding a parameter to a public API. I can't see any API to ask an irq for its current flags. That would be another way to get them and add them to the resource. Any other options? -- Jon Smirl jonsm...@gmail.com ___ devicetree-discu

Re: Two different interrupt-parents

2012-04-15 Thread jonsm...@gmail.com
Regards > Varun > >> -Original Message- >> From: devicetree-discuss- >> bounces+varun.sethi=freescale@lists.ozlabs.org [mailto:devicetree- >> discuss-bounces+varun.sethi=freescale....@lists.ozlabs.org] On Behalf Of >> jonsm...@gmail.com >> Sent:

Re: Two different interrupt-parents

2012-04-16 Thread jonsm...@gmail.com
       | I'll have my music baroque, and my code > david AT gibson.dropbear.id.au  | minimalist, thank you.  NOT _the_ _other_ >                                | _way_ _around_! > http://www.ozlabs.org/~dgibson -- Jon Smirl jonsm...@gmail.com ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
-intel-qualcomm-in-tablet-processors-in-2012 > [*1] - fex guide for SoCs up to but excluding the Allwinner A20 > http://linux-sunxi.org/Fex_Guide > [*2] http://lists.phcomp.co.uk/pipermail/arm-netbook/2013-June/007619.htmland > > http://lists.phcomp.co.uk/pipermail/arm-netbook/2013-June/007611.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Jon Smirl jonsm...@gmail.com ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
tsold-intel-qualcomm-in-tablet-processors-in-2012 > [*1] - fex guide for SoCs up to but excluding the Allwinner A20 > http://linux-sunxi.org/Fex_Guide > [*2] http://lists.phcomp.co.uk/pipermail/arm-netbook/2013-June/007619.html and > http://lists.phcomp.co.uk/pipermail/arm-netbook/2013-June/007611.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Jon Smirl jonsm...@gmail.com ___ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
l on your machine. It is called dtc. Check out scripts/dtc. So if you are in love with fex syntax write a script that converts it into device tree syntax. Then compile the DTS using dtc into a DTB. When the DTB is in memory it is a FDT (flatte

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
On Wed, Jun 5, 2013 at 7:26 PM, luke.leighton wrote: > On Thu, Jun 6, 2013 at 12:07 AM, jonsm...@gmail.com > wrote: >> On Wed, Jun 5, 2013 at 6:47 PM, luke.leighton >> wrote: >>> On Wed, Jun 5, 2013 at 10:59 PM, Henrik Nordström >>> wrote: >>> >

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread jonsm...@gmail.com
On Wed, Jun 5, 2013 at 7:26 PM, luke.leighton wrote: > On Thu, Jun 6, 2013 at 12:07 AM, jonsm...@gmail.com > wrote: >> On Wed, Jun 5, 2013 at 6:47 PM, luke.leighton >> wrote: >>> On Wed, Jun 5, 2013 at 10:59 PM, Henrik Nordström >>> wrote: >>> >

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-06 Thread jonsm...@gmail.com
eed the cost of joining. The net result will likely be a reduction in the amount they need to spend on in-house development since they will learn how to better leverage other developer's work. -- Jon Smirl jonsm...@gmail.com ___ devicetree-discuss mail