From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.tipi-net.de (mail.tipi-net.de [194.13.80.246]) (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 F41AD3DE42F; Thu, 4 Jun 2026 07:08:47 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.13.80.246 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780556932; cv=none; b=GwJEkQGqYKYgjVxpUL/CG5FqEA5KM8xL3oP8TaLD38Oi7/+gTBd3+MFjeAMQH9/HW+jJCqgIbKA8a7tIK/oQGjJ/5ttMTcCrSG1xJ74Q5PAKaqG8Pi7KF7qfte6H3nvGuuax9sPkiEbhVTslP0rioRNtnVfHagWNhqfG6MGlxP4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780556932; c=relaxed/simple; bh=KxyJGkwPDoOBqy5XW77REpfneG4cVhH63Z/648+fpPc=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type; b=VX5UnCIv1WACx8bUEA+iCu3iWwN4r6GUq9GHA1xPUwd+enmrx+ZDIZDIL/h2FeBWlXeZZlzA0So6ZytdLT6y+jm0URwyeO0xMfgTWeuEpT+dIOw1GvXAqyM29blBVaPF0ipRFC9K4E/7iDJnFoiSnbZ7/7w0CAnxKUXXaBZK0vs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=tipi-net.de; spf=pass smtp.mailfrom=tipi-net.de; dkim=pass (2048-bit key) header.d=tipi-net.de header.i=@tipi-net.de header.b=EiZwVPya; arc=none smtp.client-ip=194.13.80.246 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=tipi-net.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=tipi-net.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=tipi-net.de header.i=@tipi-net.de header.b="EiZwVPya" Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 919B2A12E1; Thu, 4 Jun 2026 09:08:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tipi-net.de; s=dkim; t=1780556924; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=VBkqgVxnrPw423JfYWcKCfXKl/tFbBF8vWm0ExUBrv0=; b=EiZwVPyaADsIVsBgsc593DKqKW6IGwIXOJwDa6xSzKHI7Pdw0kOUMlzQTWGhzf3ztr1Ldb GiSserTRH/KC7Njs7cUPdkR9KSf5gWe+YhTR2agbVU89klfosN5+E4MM9E4Sc/C07L5r09 eO/oJ2O2r7WABpxrqGrWyJoJsKyn5w2R0DS4TrcpQ0XQ4NyY7/n606eqv1a4cM7a6NebBc 7u17mVQ5ZrTDAL8KHZMLZ3szM35JsSFakHZZlD8VxWbpdCqlVJhhmCUehAbQFU6ru5JmAr o9yqMJUYVMdnF8cQ/QpmECQxlg/JZo7X+HTAjqfSaqoz4WklgIk1FaF0qDeASw== Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Date: Thu, 04 Jun 2026 09:08:42 +0200 From: Nicolai Buchwitz To: Parthiban.Veerasooran@microchip.com Cc: Selvamani.Rajagopal@onsemi.com, conor@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, Pier.Beruto@onsemi.com, andrew@lunn.ch, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, Conor.Dooley@microchip.com, devicetree@vger.kernel.org Subject: Re: [PATCH net v3 2/2] dt-bindings: net: updated interrupt type to be active low, level triggered In-Reply-To: References: <20260601-level-trigger-v3-0-da73e7010532@onsemi.com> <20260601-level-trigger-v3-2-da73e7010532@onsemi.com> <20260602-rebel-snide-5036c97e410d@spud> Message-ID: <16a277ff339663c52d57d290ca3ebe50@tipi-net.de> X-Sender: nb@tipi-net.de Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Last-TLS-Session-Version: TLSv1.3 Hi Parthiban On 4.6.2026 08:29, Parthiban.Veerasooran@microchip.com wrote: > [...] > One possible alternative could be to use a threaded IRQ handler with > IRQF_ONESHOT, where the IRQ line is disabled until the handler > completes, and sleeping is allowed. In that case, we could perform the > SPI transfer in the threaded handler to send the data header and > deassert the interrupt, while deferring the remaining work to a > separate > kthread (the current SPI thread). However, I have not yet tried this > implementation, so I cannot comment on its behavior or effectiveness > without implementing and testing it. AFAIK both ks8851 and adin1110 request the IRQ as IRQF_TRIGGER_LOW | IRQF_ONESHOT with a NULL primary handler and do everything in the threaded handler. SO looking at these two drivers might be worth the inspiration. > [...] REgards Nicolai