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 2256230C618 for ; Wed, 12 Nov 2025 11:00: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=1762945209; cv=none; b=TMaY6TVM5pj4vrn36kfwxfpSxf0tbu3bRFMRizA77DtTuo1Zj4dwHrw8vl9VZ5b6Ug2j3ovZS9q7mpwJsM6wIBcdd8FCB7RKtY9D4I6ZYs5HtX14NrKCxU2EkiFht4SOIjkNIlkvpyV41yjvPuD7uIRZ2A+BkB37WUyaJ6diUps= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762945209; c=relaxed/simple; bh=MoI+zCjPUouomucxHrl4Tm9QWJIl5C3ILMFkQq123zg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Xp4IefrNEqBvb5VPe8xz69ddgEjkETE3adHdJRCh0p3kuwx+f4QhF4TwWrwU95Cq06SCZZY3ROY/zw+lq6SVLq0q8+iBcLQBlxDzkJQLKSh5p1Fa8olmhFS0mpv8R1FBoi1STOcjXk/wuVTPmS4AgIzc7ON9NKmJyS6Ct1CUNXU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=hxEs6The; 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="hxEs6The" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 83BF5C2BC86; Wed, 12 Nov 2025 11:00:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1762945208; bh=MoI+zCjPUouomucxHrl4Tm9QWJIl5C3ILMFkQq123zg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=hxEs6The13lWerIlCALfpC9a53iUcOx4yeRK93Bg4SRTYYz1kngeKFEZpnlY1WGfl WLYetw4VLDk9i3O8UdykpKdVPcQS4C87AViibteGdkAUFtPiyrLxHg1lGpc5y0Sqr+ XgveBCmYEZe3RJ77E0ilJzT9OSFw/lQLWqztllwX4R4fKNurvqLKNSft7mk/PqN+EY gjPncjDMk/4saWjeN3DuC6qrU7hRpICBUD1r5gqu17vGwke/JwKyDQFH0pNFncCQn4 LkwKqGypRn33HL99W9EXveGoAhoy3pM5+Ufd5cmc5IWVevv5tH1TAR4nCy9AJVRIJk g/BocBSJ/zStw== Received: from johan by xi.lan with local (Exim 4.98.2) (envelope-from ) id 1vJ8a8-0000000027v-21Dy; Wed, 12 Nov 2025 12:00:08 +0100 Date: Wed, 12 Nov 2025 12:00:08 +0100 From: Johan Hovold To: Daniel Lezcano Cc: Mark Rutland , Marc Zyngier , Thomas Gleixner , linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/3] clocksource/drivers: Prevent clockevent driver unbind Message-ID: References: <20251111153226.579-1-johan@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Wed, Nov 12, 2025 at 10:48:22AM +0100, Daniel Lezcano wrote: > On 11/11/25 16:32, Johan Hovold wrote: > > Clockevents cannot be deregistered so suppress driver bind attributes to > > prevent drivers from being unbound and, for example, releasing > > underlying resources after registration. > > For non architected timers, we want to be able to convert the timers as > modules. > > That's an on-going work [1]. > > Your series assumes we won't convert that into modules, so you do the > conversion to builtin. But actually, there is a slow move to module > conversion. No, that's not the case. The builtin_platform_driver macro still allows building drivers as modules, it just prevents unloading them. Johan