From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx.adeep.su (mx.adeep.su [185.250.0.168]) (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 D7B6F2F8E8E; Fri, 26 Jun 2026 07:16:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.250.0.168 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782458214; cv=none; b=r+akLOWDLd5CZX2vPKDK+KkejW+1vs4Fhiyb0hbbW7bnKfCwSVu/8ckVkqNrjwvzOjXHbVvUBbMNvMjkrzFCr5vVSUUlpywh/sv/idpikDnMZQaqNZ6VpDGmw78e7F/knaOwlR5ygtUsZN1pVrEp0rPHZGR3FeyQypTyhbRcGYA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782458214; c=relaxed/simple; bh=4GkvO2DZ5KA4iC+jKpP4hkWsAEg72QOLBRDLYAg6IQ8=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=GpVAokdGLN3vW93hCUZB/BziaX9HjePZzeDHjCj6F5SLkvqBAaXE+mG7ZwR8T60LwUrD2p15M/d9HrM0vD4FiKvQ1utKWNtVUcnlDdAh8KsH26N1uZg0+kzO2UzszkGC8PF9/6gM9SniDqVtjkVVN7b5usAEF5VaKzHNWT+8B34= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=baodeep.com; spf=pass smtp.mailfrom=baodeep.com; dkim=fail (2048-bit key) header.d=baodeep.com header.i=@baodeep.com header.b=jyzEzToP reason="signature verification failed"; arc=none smtp.client-ip=185.250.0.168 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=baodeep.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=baodeep.com Authentication-Results: smtp.subspace.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=baodeep.com header.i=@baodeep.com header.b="jyzEzToP" Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id DF51B1BE7A2; Fri, 26 Jun 2026 10:16:44 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baodeep.com; s=dkim; t=1782458207; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:content-language:in-reply-to:references; bh=LLwOaOrVN63ocBzK4TrquFSTvMxdhRBEVjhLSw06WEg=; b=jyzEzToPHt0FZEmcxepLe+ZA6VMW2QaCJLe96oEhXXdQhSolX3SH2aWIN078Or7/guip9m 82ZEJ3DklV52hmqI5FJndHqn9PIWo4eumBRO7PBLUc72cWVkTz7o4dW4o6F7oqqoNRg6Ev wIqMLPn0iDCNqC5LioVBHo/WriwYTTAwiBCvM2c5Pjl9wFs+/OQTMDkQXwpcD9MDj4m9oW 2cAxU05OE0rPKjDz5vAke6MfDIVXYPz8EGK7ENdztgc1A9/lzV/Q/FL0dRIrvZzlV5wPlu UdwruCzDc8Kd7uWA1HZM2Wq5mNsK1N8M7a7jL4uXmIYQCljl3Uil0QPGYpgBqw== Message-ID: <0a9fee08-8945-4c7d-8bea-9efb7d921f10@baodeep.com> Date: Fri, 26 Jun 2026 10:16:27 +0300 Precedence: bulk X-Mailing-List: linux-gpio@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v2 1/2] gpio: shared-proxy: always serialize with a sleeping mutex To: Marek Szyprowski Cc: linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org References: <20260625115718.1678991-1-v@baodeep.com> <20260625115718.1678991-2-v@baodeep.com> Content-Language: ru From: Viacheslav In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Last-TLS-Session-Version: TLSv1.3 Hi! 26.06.2026 08:54, Marek Szyprowski wrote: > On 25.06.2026 13:57, Viacheslav Bocharov wrote: >> The shared GPIO descriptor used either a mutex or a spinlock, chosen at >> runtime from the underlying chip's can_sleep: >> >> shared_desc->can_sleep = gpiod_cansleep(shared_desc->desc); >> ... if (can_sleep) mutex_lock(); else spin_lock_irqsave(); ... >> >> The lock type was added by commit a060b8c511ab ("gpiolib: implement >> low-level, shared GPIO support"); the sleeping call under it arrived with >> the proxy driver. >> >> Fixes: e992d54c6f97 ("gpio: shared-proxy: implement the shared GPIO proxy driver") >> Reported-by: Marek Szyprowski >> Closes: https://lore.kernel.org/all/00107523-7737-4b92-a785-14ce4e93b8cb@samsung.com/ >> Signed-off-by: Viacheslav Bocharov > > > Tested-by: Marek Szyprowski > Thanks! Best regards -- Viacheslav Bocharov