From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-qv1-f49.google.com (mail-qv1-f49.google.com [209.85.219.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DF809566A for ; Thu, 19 Sep 2024 00:42:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.219.49 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1726706555; cv=none; b=fdsC8w5MgeejnJJKcxzYtyYdwTV8OLmNmnaBRAKbm2NGGEeBJ5wTc91XfanGAO1Pr6QIUBcxXfSBYLK0CM74HqzFW3ePqMDsEdcv6DDn2a/I1bqGuzkUOWZT3sk5hL+bB9nc3x4TIIFDWKbofAToRNdOu9YUuzxO3x+LU2Kte40= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1726706555; c=relaxed/simple; bh=Hj382AWUoXPFWPx6kgr27ouvipd9ZtXmyWqbGMtIjiw=; h=Subject:To:Cc:References:From:Message-ID:Date:MIME-Version: In-Reply-To:Content-Type; b=ZpmYTspizzPmEcAK4ArUwd3Dl+mAf0i0ZvxtoVSIKST9wVvPxsJDfugz/bspbk6j5/p5JariYrzsssPWukeyXRuEnZkAAnJX4f5DGSwR8EolP7N2LsCj+S2HqonWjC8J8AlPgRUZKMlywmI1MdztRZs02CMzyF431px/AvDHvLA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=broadcom.com; spf=fail smtp.mailfrom=broadcom.com; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b=V9LebyZc; arc=none smtp.client-ip=209.85.219.49 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=broadcom.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=broadcom.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="V9LebyZc" Received: by mail-qv1-f49.google.com with SMTP id 6a1803df08f44-6c524b4f8b9so1989576d6.3 for ; Wed, 18 Sep 2024 17:42:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1726706552; x=1727311352; darn=vger.kernel.org; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject:from:to:cc :subject:date:message-id:reply-to; bh=JFoCX6U/L9mlQd+6+0Av1Hai/zxXjRmBCa05j8mha+w=; b=V9LebyZcUtFNQYh2Xamk4x8LTr7/+YzFwVmUn8exTchMgOut7xH6J2g103z/9RutG/ WP2s96u8fYKxob69uhurPVvgKw3/Cah3ctV1sFaPNhQwdTAYmBCVOTegGQOQsXz5U5ji hc6776+8sBboW9QrWJRe3k04r0LwaevkLrZrY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726706552; x=1727311352; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:cc:to:subject :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=JFoCX6U/L9mlQd+6+0Av1Hai/zxXjRmBCa05j8mha+w=; b=QEg6n37rq8zf0I5jtnKT2Ef3kpdxV5qi7G7BvgDW996TmcbpiBrVVc6l55S9jLr8m8 7y9I0G2FTPCPxX24AOnnOCfvozpARkW869hRl6VWlIQISzzOWBPy5b9tGlHAOPtiiNgZ Rb6/0/Gy2FQMjfPW+WPrGXJUgo8kvqY3pQ/kC9wyBjvD+zDLYcyrUp0hTQI6g1VoEGZ0 APWfDOpS1cOp22fTONIb6QefTM3DHDAqt14boCTj514mMGFxjVh2PCceVCciTbkfAqeP +BdY0FO2tZJC9Ny7iGbR5GMRDqDzATUzalxXkcVGM0F7HE1VAlv4nKUmbFBYcaFZR3H9 cq7g== X-Forwarded-Encrypted: i=1; AJvYcCWob4kpwAGCM583o263NC28JIvw4B3Ds4eZ9soKmCGOSEKMErpJlgnbATjLLd+s7cyo3tesJ/qHJ0PT@vger.kernel.org X-Gm-Message-State: AOJu0Yx+jMfIK4yEmqwrM2BT+8dccOP2jMEg45WsW7sNy8iMOTRXaofI 4k/75kISM+8/vK6luiHiwS210zKs6eqo72bDLtzLHDLiCfo3XYy3C6LpLxCzlg== X-Google-Smtp-Source: AGHT+IHVO+YDKcGqZvPZxgbDL2WtMIPBUY6XYcqJu1OLQVBsHk5qKLKEJjS7NqjdnP6E+fQwWfzJjA== X-Received: by 2002:a05:6214:5707:b0:6c7:5e78:75f9 with SMTP id 6a1803df08f44-6c75e78766amr14880536d6.8.1726706552608; Wed, 18 Sep 2024 17:42:32 -0700 (PDT) Received: from bcacpedev-irv-3.lvn.broadcom.net ([192.19.161.250]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6c75e44b565sm2284756d6.20.2024.09.18.17.42.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Sep 2024 17:42:32 -0700 (PDT) Subject: Re: [PATCH 0/2] Enable MMIO GPIO on BCMBCA To: Linus Walleij Cc: Bartosz Golaszewski , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Florian Fainelli , linux-gpio@vger.kernel.org, devicetree@vger.kernel.org References: <20240917-bcmbca-gpio-mmio-v1-0-674bae8664cc@linaro.org> <6becd9863d87720dff1a1677c7433af8@mail.gmail.com> From: William Zhang Message-ID: Date: Wed, 18 Sep 2024 17:42:15 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 Precedence: bulk X-Mailing-List: linux-gpio@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit On 09/17/2024 12:03 PM, Linus Walleij wrote: > On Tue, Sep 17, 2024 at 8:13 PM William Zhang > wrote: > >> If we upstream more elaborated driver later, it will be a dedicated gpio >> controller driver and not use this basic mmio gpio and we can have >> the new compatible. > > Thinking of it, in that case the driver would just use one reg = <> > property for the whole I/O range used by the chip and then it need > a new compatible anyway. Let's drop this for now. I'll switch over > to the old compatible. > > It seems the approach taken with this SoC is a combination of > simple GPIO and a separate extint (external interrupt) unit, so > it does not need GPIOs to be able to trigger interrupts, which > was my major worry. > I am looking into this and we should be able to support an irq chip for this gpio controller that control external interrupt controller. So any gpio that is configured in external interrupt controller can trigger an interrupt. Will post such driver for review when it is ready. > Yours, > Linus Walleij >