From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-172.mta0.migadu.com (out-172.mta0.migadu.com [91.218.175.172]) (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 DADC647426F for ; Wed, 29 Jul 2026 11:28:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785324498; cv=none; b=E5yDAU1gAPaiZI06O+H9jA1lN8wKhuzOT8nccp9V2OPb2v8bYW6oRSkS/QwCFqZ/rqZO4uXDRmMqr+XHo1/IbVrIdj3yOoz3N0I8KNMRzI8cav+tHW5YIOF8NHibNm0b28wrZju/+4SxiKLPwop94k7mBPcNo+uw5ZmCEYXkWm0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785324498; c=relaxed/simple; bh=Wkx3+aJoKnYv0BAzvXHIEBKX6Oqfxg6+3jdUDYhewhM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=pXR3hTc+lwhSVqOAbKf6vwfz7YBd7i5KDBQlCizctADp5LZd3ZrVPZdq272uBp1bLa37k6BZIs1Gt0A1o6pgs1drDF//0s+bU79YMu0zhwDph+0reETlmakDMPlxZ1SQlDAQ4e8folVHUxfn1YQgASxLkBzyFZN0lKQ9nNckNYQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=pqrs.dk; spf=pass smtp.mailfrom=pqrs.dk; dkim=pass (2048-bit key) header.d=pqrs.dk header.i=@pqrs.dk header.b=CQ+Iy2xR; arc=none smtp.client-ip=91.218.175.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=pqrs.dk Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=pqrs.dk Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=pqrs.dk header.i=@pqrs.dk header.b="CQ+Iy2xR" Date: Wed, 29 Jul 2026 13:28:02 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pqrs.dk; s=key1; t=1785324491; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GwTpUBtPVL2Yxdscvdw/yb+5/UzTPHHhAC/JAlyJ45Q=; b=CQ+Iy2xR7iYM1znXVFrQOuqg4tq5s+0pJlWi7og500VHXjKQGQKTmWJ6BHrSGjjBZJ/ziA X9rAK4Ca/ykjFYEIGGagUerVl8CmT6DwpuCs5EAU6JUs3czSNh4ULDtfYBDNRZF8xm/bkN mMuHcPjrO1KoLjgOSdDelSRjPjJEVhEFizkvNAJvpR/gOGA7cVq2CgAHxa0e8tfU6SOMDM K6da3LR4XulN2c5t12E7+r3g/rvOkq5iJocbgxzVrD96CSjNljbQkxKPYt/pyKL12cwYTQ QJs+zZYeL8ZBQL8IaNkohVoU1x7z+4ocscajk5Gwm+1aXIR9BkDGm0sw4u2fpw== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Alvin =?utf-8?Q?=C5=A0ipraga?= To: Advait Dhamorikar Cc: myungjoo.ham@samsung.com, cw00.choi@samsung.com, linux-kernel@vger.kernel.org, alsi@bang-olufsen.dk, gregkh@linuxfoundation.org, marex@denx.de, heikki.krogerus@linux.intel.com Subject: Re: [PATCH] extcon: usbc-tusb320: always rewrite REG9 to deassert INT_N Message-ID: References: <20260728153744.321743-1-advaitd@mechasystems.com> 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=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Migadu-Flow: FLOW_OUT Hi Advait, On Wed, Jul 29, 2026 at 04:38:52PM +0530, Advait Dhamorikar wrote: > Hi Alvin, > > Thanks for taking a look. > > > Can you say a bit more about your hardware? > > This is on an NXP i.MX8MP based board using a TUSB320 connected over I²C. > The INT_N signal is connected to a GPIO configured as a level-low interrupt. (I think we agree your patch is wrong, so I cut the rest of your reply) [snip] > I'm trying to understand why the hardware presents an asserted > INT_N while REG9 reports no pending interrupt. The INT_N signal is an open-drain output, so you need an external pull-up resistor on the line. The TUSB320 will not drive it high when there is no interrupt. Perhaps that's the problem? If you have a pull-up resistor, check the behaviour when you hold the TUSB320 in reset (use EN_N signal or power it off). If it's still low then it's not the TUSB320 that's the problem. If you have some kind of measuring tool (oscilloscope/etc.) it will be more meaningful to probe the physical line than to listen to what Linux or /proc/interrupts is telling you. Hope that helps. Kind regards, Alvin