public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Hanjun Guo <guohanjun@huawei.com>,
	D Scott Phillips <scott@os.amperecomputing.com>
Cc: linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v2] ACPI: bus: Consolidate all arm specific initialisation into acpi_arm_init()
Date: Mon, 9 Oct 2023 14:05:45 +0100	[thread overview]
Message-ID: <20231009130545.kpebuas3optwt2ks@bogus> (raw)
In-Reply-To: <00dd9623-a131-53ed-5e73-1eccd626d2d7@huawei.com>

On Mon, Oct 09, 2023 at 08:29:49PM +0800, Hanjun Guo wrote:
> On 2023/10/7 8:11, D Scott Phillips wrote:
> > Sudeep Holla <sudeep.holla@arm.com> writes:
> > 
> > > Move all of the ARM-specific initialization into one function namely
> > > acpi_arm_init(), so it is not necessary to modify/update bus.c every
> > > time a new piece of it is added.
> > > 
> > > Cc: Lorenzo Pieralisi <lpieralisi@kernel.org>
> > > Cc: Rafael J. Wysocki <rafael@kernel.org>
> > > Suggested-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> > > Reviewed-by: Hanjun Guo <guohanjun@huawei.com>
> > > Link: https://lore.kernel.org/r/CAJZ5v0iBZRZmV_oU+VurqxnVMbFN_ttqrL=cLh0sUH+=u0PYsw@mail.gmail.com
> > > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > > ---
> > >   drivers/acpi/arm64/Makefile |  2 +-
> > >   drivers/acpi/arm64/agdi.c   |  2 +-
> > >   drivers/acpi/arm64/apmt.c   |  2 +-
> > >   drivers/acpi/arm64/init.c   | 13 +++++++++++++
> > >   drivers/acpi/arm64/init.h   |  6 ++++++
> > >   drivers/acpi/arm64/iort.c   |  1 +
> > >   drivers/acpi/bus.c          |  7 +------
> > >   include/linux/acpi.h        |  6 ++++++
> > >   include/linux/acpi_agdi.h   | 13 -------------
> > >   include/linux/acpi_apmt.h   | 19 -------------------
> > >   include/linux/acpi_iort.h   |  2 --
> > >   11 files changed, 30 insertions(+), 43 deletions(-)
> > >   create mode 100644 drivers/acpi/arm64/init.c
> > >   create mode 100644 drivers/acpi/arm64/init.h
> > >   delete mode 100644 include/linux/acpi_agdi.h
> > >   delete mode 100644 include/linux/acpi_apmt.h

[...]

> > > @@ -1408,7 +1405,7 @@ static int __init acpi_init(void)
> > >   	acpi_init_ffh();
> > > 
> > >   	pci_mmcfg_late_init();
> > > -	acpi_iort_init();
> > > +	acpi_arm_init();
> > >   	acpi_viot_early_init();
> > >   	acpi_hest_init();
> > >   	acpi_ghes_init();
> > > @@ -1420,8 +1417,6 @@ static int __init acpi_init(void)
> > >   	acpi_debugger_init();
> > >   	acpi_setup_sb_notify_handler();
> > >   	acpi_viot_init();
> > > -	acpi_agdi_init();
> > > -	acpi_apmt_init();
> > 
> > Hi Sudeep, this moves acpi_agdi_init() before acpi_ghes_init().
> > sdei initialization currently happens from ghes_init, so agdi devices
> > using SDEI can no longer probe:
> > 
> > | [    0.515864] sdei: Failed to create event 1073741825: -5
> > | [    0.515866] agdi agdi.0: Failed to register for SDEI event 1073741825
> > | [    0.515867] agdi: probe of agdi.0 failed with error -5
> > | ...
> > | [    0.516022] sdei: SDEIv1.0 (0x0) detected in firmware.
>

Sorry for that.

> How about just move acpi_arm_init() to the place of after
> acpi_ghes_init()?
>

Yes that could work but  I am not comfortable with such play around with
the ordering. I don't have better alternative as well :( so I am OK with
the proposal.

We had all sorts of issues with initcalls in the past but I understand
this one is not as bad as that, I am just cautious.

> I checked the functions in acpi_arm_init(), there are no other
> dependencies except sdei_init().
>

Fair enough.

Anyways, for now Hanjun's suggestion should work.

Can either one of you write a patch and post ? Or you use want me to do
that ?

--
Regards,
Sudeep

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-10-09 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  9:35 [PATCH v2] ACPI: bus: Consolidate all arm specific initialisation into acpi_arm_init() Sudeep Holla
2023-06-06  9:50 ` Lorenzo Pieralisi
2023-06-06 12:02 ` Shaoqin Huang
2023-06-06 14:26 ` Rafael J. Wysocki
2023-06-07 14:11 ` Lorenzo Pieralisi
2023-06-08  7:07   ` Catalin Marinas
2023-06-08 18:17 ` Catalin Marinas
2023-10-07  0:11 ` D Scott Phillips
2023-10-09 12:29   ` Hanjun Guo
2023-10-09 13:05     ` Sudeep Holla [this message]
2023-10-10  7:16       ` Hanjun Guo

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=20231009130545.kpebuas3optwt2ks@bogus \
    --to=sudeep.holla@arm.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=scott@os.amperecomputing.com \
    /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