On Mon, Jun 10, 2013 at 8:23 PM, Stephen Warren wrote:
> The entire reason I created the directory (rather than
> just putting *.h into e.g. arch/arm/boot/dts) was to provide a place to
> share binding-defined constants between the DT files and drivers that
> implement that binding. It's
On Mon, Jun 10, 2013 at 8:23 PM, Stephen Warren swar...@wwwdotorg.org wrote:
The entire reason I created the dt-bindings/ directory (rather than
just putting *.h into e.g. arch/arm/boot/dts) was to provide a place to
share binding-defined constants between the DT files and drivers that
On 06/10/2013 01:23 PM, Stephen Warren wrote:
> On 06/10/2013 07:00 AM, Linus Walleij wrote:
>> On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner wrote:
>>
>> (...)
>>> +#include
>>> +#include
>>> +#include
>>
>> Hm I don't know if we're supposed to do things like this actually.
>>
>> It depends
On 06/10/2013 07:00 AM, Linus Walleij wrote:
> On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner wrote:
>
> (...)
>> +#include
>> +#include
>> +#include
>
> Hm I don't know if we're supposed to do things like this actually.
>
> It depends on whether the hierarchy is supposed
> to stay in the
On Mon, Jun 10, 2013 at 3:10 PM, Heiko Stübner wrote:
> Am Montag, 10. Juni 2013, 15:00:41 schrieb Linus Walleij:
>> On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner wrote:
>>
>> (...)
>>
>> > +#include
>> > +#include
>> > +#include
>>
>> Hm I don't know if we're supposed to do things like this
Am Montag, 10. Juni 2013, 15:00:41 schrieb Linus Walleij:
> On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner wrote:
>
> (...)
>
> > +#include
> > +#include
> > +#include
>
> Hm I don't know if we're supposed to do things like this actually.
>
> It depends on whether the hierarchy is supposed
On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner wrote:
(...)
> +#include
> +#include
> +#include
Hm I don't know if we're supposed to do things like this actually.
It depends on whether the hierarchy is supposed
to stay in the kernel after the device trees are moved out to a
separate repo.
On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner wrote:
> This driver adds support the Cortex-A9 based SoCs from Rockchip,
> so at least the RK2928, RK3066 (a and b) and RK3188.
> Earlier Rockchip SoCs seem to use similar mechanics for gpio
> handling so should be supportable with relative small
On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner he...@sntech.de wrote:
This driver adds support the Cortex-A9 based SoCs from Rockchip,
so at least the RK2928, RK3066 (a and b) and RK3188.
Earlier Rockchip SoCs seem to use similar mechanics for gpio
handling so should be supportable with
On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner he...@sntech.de wrote:
(...)
+#include linux/irqchip/chained_irq.h
+#include linux/clk-provider.h
+#include dt-bindings/pinctrl/rockchip.h
Hm I don't know if we're supposed to do things like this actually.
It depends on whether the dt-bindings/*
Am Montag, 10. Juni 2013, 15:00:41 schrieb Linus Walleij:
On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner he...@sntech.de wrote:
(...)
+#include linux/irqchip/chained_irq.h
+#include linux/clk-provider.h
+#include dt-bindings/pinctrl/rockchip.h
Hm I don't know if we're supposed to do
On Mon, Jun 10, 2013 at 3:10 PM, Heiko Stübner he...@sntech.de wrote:
Am Montag, 10. Juni 2013, 15:00:41 schrieb Linus Walleij:
On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner he...@sntech.de wrote:
(...)
+#include linux/irqchip/chained_irq.h
+#include linux/clk-provider.h
+#include
On 06/10/2013 07:00 AM, Linus Walleij wrote:
On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner he...@sntech.de wrote:
(...)
+#include linux/irqchip/chained_irq.h
+#include linux/clk-provider.h
+#include dt-bindings/pinctrl/rockchip.h
Hm I don't know if we're supposed to do things like this
On 06/10/2013 01:23 PM, Stephen Warren wrote:
On 06/10/2013 07:00 AM, Linus Walleij wrote:
On Sun, Jun 9, 2013 at 2:01 AM, Heiko Stübner he...@sntech.de wrote:
(...)
+#include linux/irqchip/chained_irq.h
+#include linux/clk-provider.h
+#include dt-bindings/pinctrl/rockchip.h
Hm I don't
This driver adds support the Cortex-A9 based SoCs from Rockchip,
so at least the RK2928, RK3066 (a and b) and RK3188.
Earlier Rockchip SoCs seem to use similar mechanics for gpio
handling so should be supportable with relative small changes.
Pull handling on the rk3188 is currently a stub, due to
This driver adds support the Cortex-A9 based SoCs from Rockchip,
so at least the RK2928, RK3066 (a and b) and RK3188.
Earlier Rockchip SoCs seem to use similar mechanics for gpio
handling so should be supportable with relative small changes.
Pull handling on the rk3188 is currently a stub, due to
16 matches
Mail list logo
