linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Stone <al.stone@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-acpi@vger.kernel.org, linaro-acpi@lists.linaro.org,
	Al Stone <ahs3@redhat.com>
Subject: Re: [PATCH 04/12] ACPI: HW reduced mode does not allow use of the FADT sci_interrupt field
Date: Wed, 20 Nov 2013 14:24:29 -0700	[thread overview]
Message-ID: <528D288D.9060902@linaro.org> (raw)
In-Reply-To: <6357288.C9cEqtMB8J@vostro.rjw.lan>

On 11/17/2013 03:06 PM, Rafael J. Wysocki wrote:
> On Saturday, November 09, 2013 06:36:14 PM al.stone@linaro.org wrote:
>> From: Al Stone <ahs3@redhat.com>
>
> -ENOCHANGELOG

Yup.  Will be added.

>> Signed-off-by: Al Stone <al.stone@linaro.org>
>> ---
>>   drivers/acpi/bus.c      |  3 ++-
>>   drivers/acpi/osl.c      | 10 ++++++----
>>   drivers/acpi/pci_link.c | 14 ++++++++------
>>   3 files changed, 16 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/acpi/bus.c b/drivers/acpi/bus.c
>> index b587ec8..6a54dd5 100644
>> --- a/drivers/acpi/bus.c
>> +++ b/drivers/acpi/bus.c
>> @@ -540,7 +540,8 @@ void __init acpi_early_init(void)
>>   		goto error0;
>>   	}
>>
>> -#ifdef CONFIG_X86
>> +#if (!CONFIG_ACPI_REDUCED_HARDWARE)
>
> Why don't you use #ifndef here?

No particular reason; I'll change it.

>> +	/* NB: in HW reduced mode, FADT sci_interrupt has no meaning */
>
> I'm not sure what the "NB" stands for, but it looks like that's what "NOTE:" is
> used for elsewhere.

Ah.  Whups.  "NB" == "Nota Bene" -- Latin for "note well" and a
personal habit when writing.  Yes, it should be "NOTE:".

>>   	if (!acpi_ioapic) {
>>   		/* compatible (0) means level (3) */
>>   		if (!(acpi_sci_flags & ACPI_MADT_TRIGGER_MASK)) {
>> diff --git a/drivers/acpi/osl.c b/drivers/acpi/osl.c
>> index 54a20ff..017b85c 100644
>> --- a/drivers/acpi/osl.c
>> +++ b/drivers/acpi/osl.c
>> @@ -84,6 +84,7 @@ static int (*__acpi_os_prepare_extended_sleep)(u8 sleep_state, u32 val_a,
>>
>>   static acpi_osd_handler acpi_irq_handler;
>>   static void *acpi_irq_context;
>> +static u32 acpi_irq_number;
>>   static struct workqueue_struct *kacpid_wq;
>>   static struct workqueue_struct *kacpi_notify_wq;
>>   static struct workqueue_struct *kacpi_hotplug_wq;
>> @@ -797,9 +798,9 @@ acpi_os_install_interrupt_handler(u32 gsi, acpi_osd_handler handler,
>>
>>   	/*
>>   	 * ACPI interrupts different from the SCI in our copy of the FADT are
>> -	 * not supported.
>> +	 * not supported, except in HW reduced mode.
>>   	 */
>> -	if (gsi != acpi_gbl_FADT.sci_interrupt)
>> +	if (!acpi_gbl_reduced_hardware && (gsi != acpi_gbl_FADT.sci_interrupt))
>
> The inner parens are not necessary.

Ack.

> Also it seems that we may need to support gsi != acpi_gbl_FADT.sci_interrupt
> generically, because there may be GPE device objects with interrupts different
> from the SCI.

In reduced HW mode, there are no GPE blocks defined; all
interrupts of that nature are required to use GPIO interrupts
instead, afaict.  The spec unfortunately has this info scattered
through out -- the earlier parts of the spec discussing the
reduced HW mode and the discussion around the FADT go into
some of the details.

>>   		return AE_BAD_PARAMETER;
>>
>>   	if (acpi_irq_handler)
>> @@ -818,13 +819,14 @@ acpi_os_install_interrupt_handler(u32 gsi, acpi_osd_handler handler,
>>   		acpi_irq_handler = NULL;
>>   		return AE_NOT_ACQUIRED;
>>   	}
>> +	acpi_irq_number = irq;
>>
>>   	return AE_OK;
>>   }
>>
>>   acpi_status acpi_os_remove_interrupt_handler(u32 irq, acpi_osd_handler handler)
>>   {
>> -	if (irq != acpi_gbl_FADT.sci_interrupt)
>> +	if (!acpi_gbl_reduced_hardware && (irq != acpi_gbl_FADT.sci_interrupt))
>
> The inner parens are not necessary.

Ack.

>>   		return AE_BAD_PARAMETER;
>>
>>   	free_irq(irq, acpi_irq);
>> @@ -1806,7 +1808,7 @@ acpi_status __init acpi_os_initialize1(void)
>>   acpi_status acpi_os_terminate(void)
>>   {
>>   	if (acpi_irq_handler) {
>> -		acpi_os_remove_interrupt_handler(acpi_gbl_FADT.sci_interrupt,
>> +		acpi_os_remove_interrupt_handler(acpi_irq_number,
>>   						 acpi_irq_handler);
>
> It looks like this could be one line now?

Yup.  Will fix.

>>   	}
>>
>> diff --git a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
>> index 2652a61..c0ab28a 100644
>> --- a/drivers/acpi/pci_link.c
>> +++ b/drivers/acpi/pci_link.c
>
> I'm not sure how the comment changes below belong to this patch.

Sigh.  They don't.  Will omit.

>> @@ -23,7 +23,7 @@
>>    *
>>    * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>    *
>> - * TBD:
>> + * TBD:
>>    *      1. Support more than one IRQ resource entry per link device (index).
>>    *	2. Implement start/stop mechanism and use ACPI Bus Driver facilities
>>    *	   for IRQ management (e.g. start()->_SRS).
>> @@ -268,8 +268,8 @@ static int acpi_pci_link_get_current(struct acpi_pci_link *link)
>>   		}
>>   	}
>>
>> -	/*
>> -	 * Query and parse _CRS to get the current IRQ assignment.
>> +	/*
>> +	 * Query and parse _CRS to get the current IRQ assignment.
>>   	 */
>>
>>   	status = acpi_walk_resources(link->device->handle, METHOD_NAME__CRS,
>> @@ -415,7 +415,7 @@ static int acpi_pci_link_set(struct acpi_pci_link *link, int irq)
>>   /*
>>    * "acpi_irq_balance" (default in APIC mode) enables ACPI to use PIC Interrupt
>>    * Link Devices to move the PIRQs around to minimize sharing.
>> - *
>> + *
>>    * "acpi_irq_nobalance" (default in PIC mode) tells ACPI not to move any PIC IRQs
>>    * that the BIOS has already set to active.  This is necessary because
>>    * ACPI has no automatic means of knowing what ISA IRQs are used.  Note that
>> @@ -433,7 +433,7 @@ static int acpi_pci_link_set(struct acpi_pci_link *link, int irq)
>>    *
>>    * Note that PCI IRQ routers have a list of possible IRQs,
>>    * which may not include the IRQs this table says are available.
>> - *
>> + *
>>    * Since this heuristic can't tell the difference between a link
>>    * that no device will attach to, vs. a link which may be shared
>>    * by multiple active devices -- it is not optimal.
>> @@ -505,7 +505,9 @@ int __init acpi_irq_penalty_init(void)
>>   		}
>>   	}
>
> Why don't you simply put
>
> 	if (acpi_gbl_reduced_hardware)
> 		return 0;
>
> here?

Aha.  Much more obvious.  Thanks.  Will fix.

>>   	/* Add a penalty for the SCI */
>> -	acpi_irq_penalty[acpi_gbl_FADT.sci_interrupt] += PIRQ_PENALTY_PCI_USING;
>> +	if (!acpi_gbl_reduced_hardware)
>> +		acpi_irq_penalty[acpi_gbl_FADT.sci_interrupt] +=
>> +			PIRQ_PENALTY_PCI_USING;
>>   	return 0;
>>   }
>>
>>


-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Linaro Enterprise Group
al.stone@linaro.org
-----------------------------------

  reply	other threads:[~2013-11-20 21:24 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10  1:36 [PATCH 00/12] Hardware Reduced Mode cleanup for ACPI al.stone
2013-11-10  1:36 ` [PATCH 01/12] ACPI: introduce CONFIG_ACPI_REDUCED_HARDWARE to enable this ACPI mode al.stone
2013-11-17 22:29   ` Rafael J. Wysocki
     [not found]     ` <CAGHbJ3ArVr+4g8UHyxFSL9Bu2ehsUAqsapGuxYLgfoR4NfT02w@mail.gmail.com>
2013-11-18 13:24       ` Rafael J. Wysocki
     [not found]         ` <CAGHbJ3DkXQ1-kQSdzXZ7=YSNhTstebGrdX4qXygBWmh2vYe0Bw@mail.gmail.com>
2013-11-18 13:37           ` Rafael J. Wysocki
2013-11-19  7:32             ` Hanjun Guo
2013-11-19 13:10               ` Rafael J. Wysocki
2013-11-20  1:30                 ` Hanjun Guo
2013-11-22  6:14   ` Zheng, Lv
2013-11-22  9:56     ` Hanjun Guo
2013-11-25  7:43       ` Zheng, Lv
2013-11-25  8:14         ` Zheng, Lv
2013-11-27  9:02           ` Hanjun Guo
2013-11-10  1:36 ` [PATCH 02/12] ACPI: bus master reload not supported in reduced HW mode al.stone
2013-11-17 21:56   ` Rafael J. Wysocki
2013-11-20 21:11     ` Al Stone
2013-11-21  0:31       ` Rafael J. Wysocki
2013-11-10  1:36 ` [PATCH 03/12] ACPI: clean up compiler warning about uninitialized field al.stone
2013-11-17 21:58   ` Rafael J. Wysocki
2013-11-20 21:13     ` Al Stone
2013-11-10  1:36 ` [PATCH 04/12] ACPI: HW reduced mode does not allow use of the FADT sci_interrupt field al.stone
2013-11-17 22:06   ` Rafael J. Wysocki
2013-11-20 21:24     ` Al Stone [this message]
2013-11-21  0:27       ` Rafael J. Wysocki
2013-11-21 19:36         ` Al Stone
2013-11-21 21:36           ` Rafael J. Wysocki
2013-11-21 22:19             ` Al Stone
2013-11-10  1:36 ` [PATCH 05/12] ACPI: ARM: exclude calls on ARM platforms, not include them on x86 al.stone
2013-11-17 22:08   ` Rafael J. Wysocki
2013-11-20 21:25     ` Al Stone
2013-11-22  6:19   ` Zheng, Lv
2013-11-10  1:36 ` [PATCH 06/12] ACPI: ensure several FADT fields are only used in HW reduced mode al.stone
2013-11-22  6:05   ` Zheng, Lv
2013-11-22  6:26     ` Zheng, Lv
2013-11-10  1:36 ` [PATCH 07/12] ACPI: do not reserve memory regions for some FADT entries " al.stone
2013-11-17 22:15   ` Rafael J. Wysocki
2013-11-20 21:27     ` Al Stone
2013-11-10  1:36 ` [PATCH 08/12] ACPI: in HW reduced mode, getting power latencies from FADT is not allowed al.stone
2013-11-17 22:17   ` Rafael J. Wysocki
2013-11-20 21:48     ` Al Stone
2013-11-10  1:36 ` [PATCH 09/12] ACPI: add clarifying comment about processor throttling in HW reduced mode al.stone
2013-11-17 22:20   ` Rafael J. Wysocki
2013-11-20 21:54     ` Al Stone
2013-11-21  0:14       ` Rafael J. Wysocki
2013-11-21 23:11         ` Al Stone
2013-11-10  1:36 ` [PATCH 10/12] ACPI: ACPI_FADT_C2_MP_SUPPORTED must be ignored " al.stone
2013-11-17 22:24   ` Rafael J. Wysocki
2013-11-20 21:55     ` Al Stone
2013-11-10  1:36 ` [PATCH 11/12] ACPI: use of ACPI_FADT_32BIT_TIMER is not allowed " al.stone
2013-11-17 22:26   ` Rafael J. Wysocki
2013-11-20 22:15     ` Al Stone
2013-11-21 23:43       ` Al Stone
2013-11-22 12:08         ` Rafael J. Wysocki
2013-11-10  1:36 ` [PATCH 12/12] ACPI: correct #ifdef so compilation without ACPI_REDUCED_HARDWARE works al.stone
2013-11-17 22:28   ` Rafael J. Wysocki
2013-11-20 22:17     ` Al Stone
2013-11-17 21:47 ` [PATCH 00/12] Hardware Reduced Mode cleanup for ACPI Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=528D288D.9060902@linaro.org \
    --to=al.stone@linaro.org \
    --cc=ahs3@redhat.com \
    --cc=linaro-acpi@lists.linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).