From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 45C80346E6A for ; Fri, 16 Jan 2026 11:41:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768563669; cv=none; b=V7EMAyUbxEj5/IT9y/yiH2ZL69ZBou3qTs2g1fKEOMutzdl9FHk8wcsBFrjSHctM4g1u9fPfdQLAZu70r9YiE0SlKcdwwKPVUMb2kJOnewXrvUJXNc5YwizL8GoZ8GQWekHitSOH8MC4CbDUtL33kY5Egalasrd63cOawJgAmHU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768563669; c=relaxed/simple; bh=SSdyas0vSoBFso07VZJpp3rjIqUNAbo0Zr3hqYuqVJI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=iTAFjW+08kAEDUaOx3XZsVU/EXbQO6Xvv3QLTzqf97CK8zVcGQLy+cw3jp5otHQZ3MKbM8+Ld2mg2tmA8ljWlQXDaKoneoqTNtawSYnChsCMpo1O+zf/PRDJi1dp8I/37FXzFPGwX5/8SzuzOyob+QTm6N17z54B61LjfTkPr0o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=hdN9YOlv; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="hdN9YOlv" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C92A4C116C6; Fri, 16 Jan 2026 11:41:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768563668; bh=SSdyas0vSoBFso07VZJpp3rjIqUNAbo0Zr3hqYuqVJI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=hdN9YOlva0uIEzxBNhn7K4uMha+BoBRFRXw73SXW1Dr2Ya/dw5KMUxLcM1qBaqy+a PIhIJuEi8IgQ9QUE6evsZuR/0lvx2T7YOjW3+4j1wi+nCla3tA58+n9YqrUFUaPcSd mt9E+XTiznHREQ0VndP4Y4rhVqi7xTUy7JrNy2Qdzu/HxO+aJJFS5yElqyAZF4Fdmd 1HFJdKoSBYOAsF2SkHtJhjj7v4YvHeiwwdnoR8W8S0SlUnjNs8119RFcHy9BOmPFtP fJRZmM6AhwNCfU2pqVk/AuhOTOsyN6yd88ctokwl1UQhaF6nIVEv/jnFgOH7akkTft lKzSdYYBlT0Gw== From: Thomas Gleixner To: Yicong Yang , Anup Patel Cc: yang.yicong@picoheart.com, anup@brainfault.org, pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, geshijian@picoheart.com, weidong.wd@picoheart.com, Greg Kroah-Hartman , "Rafael J. Wysocki" , Danilo Krummrich Subject: Re: [PATCH] irqchip/riscv-aplic: Register the driver prior to device creation In-Reply-To: References: <20260114063730.78009-1-yang.yicong@picoheart.com> <7b859dd5-9262-4d68-9a8e-e0be0c24ac4a@picoheart.com> <877btkht2v.ffs@tglx> <87y0lz2ef6.ffs@tglx> Date: Fri, 16 Jan 2026 12:41:04 +0100 Message-ID: <87h5sl3hv3.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Fri, Jan 16 2026 at 14:16, Yicong Yang wrote: > On 1/15/26 9:28 PM, Thomas Gleixner wrote: >> On Thu, Jan 15 2026 at 16:31, Yicong Yang wrote: >>> so based on above, if we use async_wq (with async_schedule* APIs) in >>> acpi_scan_clear_dep_queue() for creating these devices, the issue >>> could be solved since we're sure to have these devices before entering >>> userspace, since the barrier of async_synchronize_full(). This should be >>> a solution with a conceptual support and I did a quick test on our >>> platform it solves the issue. >> >> Sounds about right to me. The drivers core and ACPI folks might have >> opinions though :) >> > sure I'll wait a bit to see if there's further comment before sending out > next version. Btw, there is a reason that this is on the default work queue. See commit dc612486c919 ("ACPI: scan: Fix device object rescan in acpi_scan_clear_dep()") for details. So this needs some more thought. Thanks, tglx