Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1240795 > unrolled thread

[PATCH 00/16] Divorcing irqdomain and device_node

Started byMarc Zyngier <marc.zyngier@arm.com>
First post2015-10-06 19:40 +0200
Last post2015-10-13 10:30 +0200
Articles 3 on this page of 23 — 4 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH 00/16] Divorcing irqdomain and device_node Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:40 +0200
    [PATCH 12/16] irqchip/gic: Switch ACPI support to stacked domains Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:40 +0200
    [PATCH 13/16] irqchip/gic: Kill the xlate method Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:40 +0200
    [PATCH 08/16] irqdomain: Add a fwnode_handle allocator Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:40 +0200
      Re: [PATCH 08/16] irqdomain: Add a fwnode_handle allocator "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2015-10-12 22:10 +0200
    [PATCH 07/16] irqdomain: Introduce irq_domain_create_{linear,tree} Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:40 +0200
    [PATCH 03/16] irqdomain: Allow irq domain lookup by fwnode Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:50 +0200
      Re: [PATCH 03/16] irqdomain: Allow irq domain lookup by fwnode Marc Zyngier <marc.zyngier@arm.com> - 2015-10-13 09:40 +0200
    [PATCH 05/16] irqchip: Convert all alloc/xlate users from of_node to fwnode Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:50 +0200
      Re: [PATCH 05/16] irqchip: Convert all alloc/xlate users from of_node  to fwnode Hanjun Guo <hanjun.guo@linaro.org> - 2015-10-12 08:50 +0200
    [PATCH 06/16] irqdomain: Introduce irq_create_fwspec_mapping Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:50 +0200
    [PATCH 01/16] irqdomain: Use an accessor for the of_node field Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:50 +0200
      Re: [PATCH 01/16] irqdomain: Use an accessor for the of_node field Thomas Gleixner <tglx@linutronix.de> - 2015-10-09 16:30 +0200
        Re: [PATCH 01/16] irqdomain: Use an accessor for the of_node field Marc Zyngier <marc.zyngier@arm.com> - 2015-10-09 16:40 +0200
      Re: [PATCH 01/16] irqdomain: Use an accessor for the of_node field Hanjun Guo <hanjun.guo@linaro.org> - 2015-10-12 08:10 +0200
        Re: [PATCH 01/16] irqdomain: Use an accessor for the of_node field Marc Zyngier <marc.zyngier@arm.com> - 2015-10-12 11:40 +0200
    [PATCH 04/16] irqdomain: Introduce a firmware-specific IRQ specifier structure Marc Zyngier <marc.zyngier@arm.com> - 2015-10-06 19:50 +0200
    Re: [PATCH 00/16] Divorcing irqdomain and device_node Thomas Gleixner <tglx@linutronix.de> - 2015-10-11 23:10 +0200
      Re: [PATCH 00/16] Divorcing irqdomain and device_node Hanjun Guo <hanjun.guo@linaro.org> - 2015-10-12 04:50 +0200
        Re: [PATCH 00/16] Divorcing irqdomain and device_node Hanjun Guo <hanjun.guo@linaro.org> - 2015-10-12 09:20 +0200
      Re: [PATCH 00/16] Divorcing irqdomain and device_node Marc Zyngier <marc.zyngier@arm.com> - 2015-10-12 12:40 +0200
      Re: [PATCH 00/16] Divorcing irqdomain and device_node "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2015-10-12 22:20 +0200
        Re: [PATCH 00/16] Divorcing irqdomain and device_node Marc Zyngier <marc.zyngier@arm.com> - 2015-10-13 10:30 +0200

Page 2 of 2 — ← Prev page 1 [2]


#1244581

FromMarc Zyngier <marc.zyngier@arm.com>
Date2015-10-12 12:40 +0200
Message-ID<qiIGl-4HW-17@gated-at.bofh.it>
In reply to#1244224
On 11/10/15 22:01, Thomas Gleixner wrote:
> On Tue, 6 Oct 2015, Marc Zyngier wrote:
>> [This patch series used to be called "Making the generic ACPI GSI
>> layer irqdomain aware", but as I've radically changed my approach to
>> this problem, I've decided to reset the counters...]
>>
>> The irqdomain code is not entierely ACPI friendly, as it has some
>> built-in knowledge of the device-tree. Nothing too harmful, but enough
>> to scare the ARM ACPI developpers which end up with their own version
>> of the square wheel. And some of the ramifications actually run deeper
>> than initially expected.
>>
>> This series adapts the irqdomain code to use 'struct fwnode_handle'
>> instead of 'struct device_node' as the identifier for a domain
>> (compatibility interfaces are of course added). It also introduces a
>> generic IRQ specifier that firmware interfaces (DT or ACPI) can
>> directly use to configure interrupts, and allow the ACPI GSI code to
>> be plugged into this.
>>
>> As examples, we convert the ARM GIC ACPI support to use irqdomains as
>> originally intended, and rework the MSI code to also move away from
>> using device nodes when using irqdomains.
>>
>> Overall, this gives us a way to use irqdomains on both DT and ACPI
>> enabled platforms, having very little changes made to the actual
>> drivers (other than the probing infrastructure). Because we keep the
>> flow of information between the various layers identical between ACPI
>> and DT, we immediately benefit from the existing infrastructure.
>>
>> This has been test-booted on Juno, is based on 4.3-rc4, and available at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/irq-domain-fwnode-v1
>>
>> Marc Zyngier (16):
>>   irqdomain: Use an accessor for the of_node field
>>   irqdomain: Convert irqdomain->of_node to fwnode
>>   irqdomain: Allow irq domain lookup by fwnode
>>   irqdomain: Introduce a firmware-specific IRQ specifier structure
>>   irqchip: Convert all alloc/xlate users from of_node to fwnode
>>   irqdomain: Introduce irq_create_fwspec_mapping
>>   irqdomain: Introduce irq_domain_create_{linear,tree}
>>   irqdomain: Add a fwnode_handle allocator
>>   acpi/gsi: Always perform an irq domain lookup
>>   acpi/gsi: Add acpi_set_irq_model to initialize the GSI layer
>>   irqchip/gic: Get rid of gic_init_bases()
>>   irqchip/gic: Switch ACPI support to stacked domains
>>   irqchip/gic: Kill the xlate method
>>   acpi/gsi: Cleanup acpi_register_gsi
>>   irqdomain: Introduce irq_domain_create_hierarchy
>>   irqdomain/msi: Use fwnode instead of of_node
> 
> I really like this one way better than the previous attempts and I
> couldn't find any real issue when going through them with a fine comb.
> 
> I'd like to get that into 4.4, so I have to ask for the opinion of
> ACPI folks. Having an ack on those patches would be nice.

FWIW, I've rebased this on top of -rc5, with a couple of fixes to the
first patch (fixing missed of_node accessor conversions), but the series
is otherwise unchanged:

git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
irq/irq-domain-fwnode-v2

I'd very much appreciate some feedback from the ACPI folks as well
(patch 8 is the potential point of contention, as it creates fwnodes
ex-nihilo).

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1245101

From"Rafael J. Wysocki" <rjw@rjwysocki.net>
Date2015-10-12 22:20 +0200
Message-ID<qiRJE-1cM-17@gated-at.bofh.it>
In reply to#1244224
On Sunday, October 11, 2015 11:01:17 PM Thomas Gleixner wrote:
> On Tue, 6 Oct 2015, Marc Zyngier wrote:
> > [This patch series used to be called "Making the generic ACPI GSI
> > layer irqdomain aware", but as I've radically changed my approach to
> > this problem, I've decided to reset the counters...]
> > 
> > The irqdomain code is not entierely ACPI friendly, as it has some
> > built-in knowledge of the device-tree. Nothing too harmful, but enough
> > to scare the ARM ACPI developpers which end up with their own version
> > of the square wheel. And some of the ramifications actually run deeper
> > than initially expected.
> > 
> > This series adapts the irqdomain code to use 'struct fwnode_handle'
> > instead of 'struct device_node' as the identifier for a domain
> > (compatibility interfaces are of course added). It also introduces a
> > generic IRQ specifier that firmware interfaces (DT or ACPI) can
> > directly use to configure interrupts, and allow the ACPI GSI code to
> > be plugged into this.
> > 
> > As examples, we convert the ARM GIC ACPI support to use irqdomains as
> > originally intended, and rework the MSI code to also move away from
> > using device nodes when using irqdomains.
> > 
> > Overall, this gives us a way to use irqdomains on both DT and ACPI
> > enabled platforms, having very little changes made to the actual
> > drivers (other than the probing infrastructure). Because we keep the
> > flow of information between the various layers identical between ACPI
> > and DT, we immediately benefit from the existing infrastructure.
> > 
> > This has been test-booted on Juno, is based on 4.3-rc4, and available at:
> > 
> > git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/irq-domain-fwnode-v1
> > 
> > Marc Zyngier (16):
> >   irqdomain: Use an accessor for the of_node field
> >   irqdomain: Convert irqdomain->of_node to fwnode
> >   irqdomain: Allow irq domain lookup by fwnode
> >   irqdomain: Introduce a firmware-specific IRQ specifier structure
> >   irqchip: Convert all alloc/xlate users from of_node to fwnode
> >   irqdomain: Introduce irq_create_fwspec_mapping
> >   irqdomain: Introduce irq_domain_create_{linear,tree}
> >   irqdomain: Add a fwnode_handle allocator
> >   acpi/gsi: Always perform an irq domain lookup
> >   acpi/gsi: Add acpi_set_irq_model to initialize the GSI layer
> >   irqchip/gic: Get rid of gic_init_bases()
> >   irqchip/gic: Switch ACPI support to stacked domains
> >   irqchip/gic: Kill the xlate method
> >   acpi/gsi: Cleanup acpi_register_gsi
> >   irqdomain: Introduce irq_domain_create_hierarchy
> >   irqdomain/msi: Use fwnode instead of of_node
> 
> I really like this one way better than the previous attempts and I
> couldn't find any real issue when going through them with a fine comb.
> 
> I'd like to get that into 4.4, so I have to ask for the opinion of
> ACPI folks. Having an ack on those patches would be nice.

I've ACKed the generic ones, please let me know if I missed any of them.

The rest seems to be ARM-specific ...

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [next] | [standalone]


#1245460

FromMarc Zyngier <marc.zyngier@arm.com>
Date2015-10-13 10:30 +0200
Message-ID<qj386-Y7-23@gated-at.bofh.it>
In reply to#1245101
On 12/10/15 21:38, Rafael J. Wysocki wrote:
> On Sunday, October 11, 2015 11:01:17 PM Thomas Gleixner wrote:
>> On Tue, 6 Oct 2015, Marc Zyngier wrote:
>>> [This patch series used to be called "Making the generic ACPI GSI
>>> layer irqdomain aware", but as I've radically changed my approach to
>>> this problem, I've decided to reset the counters...]
>>>
>>> The irqdomain code is not entierely ACPI friendly, as it has some
>>> built-in knowledge of the device-tree. Nothing too harmful, but enough
>>> to scare the ARM ACPI developpers which end up with their own version
>>> of the square wheel. And some of the ramifications actually run deeper
>>> than initially expected.
>>>
>>> This series adapts the irqdomain code to use 'struct fwnode_handle'
>>> instead of 'struct device_node' as the identifier for a domain
>>> (compatibility interfaces are of course added). It also introduces a
>>> generic IRQ specifier that firmware interfaces (DT or ACPI) can
>>> directly use to configure interrupts, and allow the ACPI GSI code to
>>> be plugged into this.
>>>
>>> As examples, we convert the ARM GIC ACPI support to use irqdomains as
>>> originally intended, and rework the MSI code to also move away from
>>> using device nodes when using irqdomains.
>>>
>>> Overall, this gives us a way to use irqdomains on both DT and ACPI
>>> enabled platforms, having very little changes made to the actual
>>> drivers (other than the probing infrastructure). Because we keep the
>>> flow of information between the various layers identical between ACPI
>>> and DT, we immediately benefit from the existing infrastructure.
>>>
>>> This has been test-booted on Juno, is based on 4.3-rc4, and available at:
>>>
>>> git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/irq-domain-fwnode-v1
>>>
>>> Marc Zyngier (16):
>>>   irqdomain: Use an accessor for the of_node field
>>>   irqdomain: Convert irqdomain->of_node to fwnode
>>>   irqdomain: Allow irq domain lookup by fwnode
>>>   irqdomain: Introduce a firmware-specific IRQ specifier structure
>>>   irqchip: Convert all alloc/xlate users from of_node to fwnode
>>>   irqdomain: Introduce irq_create_fwspec_mapping
>>>   irqdomain: Introduce irq_domain_create_{linear,tree}
>>>   irqdomain: Add a fwnode_handle allocator
>>>   acpi/gsi: Always perform an irq domain lookup
>>>   acpi/gsi: Add acpi_set_irq_model to initialize the GSI layer
>>>   irqchip/gic: Get rid of gic_init_bases()
>>>   irqchip/gic: Switch ACPI support to stacked domains
>>>   irqchip/gic: Kill the xlate method
>>>   acpi/gsi: Cleanup acpi_register_gsi
>>>   irqdomain: Introduce irq_domain_create_hierarchy
>>>   irqdomain/msi: Use fwnode instead of of_node
>>
>> I really like this one way better than the previous attempts and I
>> couldn't find any real issue when going through them with a fine comb.
>>
>> I'd like to get that into 4.4, so I have to ask for the opinion of
>> ACPI folks. Having an ack on those patches would be nice.
> 
> I've ACKed the generic ones, please let me know if I missed any of them.
> 
> The rest seems to be ARM-specific ...

Thanks a lot Rafael.

I'll repost the series today with a couple of fixes so that Thomas can
stick it into -next.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.kernel


csiph-web