From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shawn Guo Subject: Re: [PATCH v2 1/3] arm64: dts: imx: Add i.mx8mm dtsi support Date: Fri, 22 Mar 2019 10:13:32 +0800 Message-ID: <20190322021331.GX12513@dragon> References: <1552369779-7614-1-git-send-email-ping.bai@nxp.com> <20190321082253.GD12513@dragon> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Jacky Bai Cc: "mark.rutland@arm.com" , Aisheng Dong , "devicetree@vger.kernel.org" , "s.hauer@pengutronix.de" , "robh+dt@kernel.org" , dl-linux-imx , "kernel@pengutronix.de" , "festevam@gmail.com" , "linux-arm-kernel@lists.infradead.org" , "l.stach@pengutronix.de" List-Id: devicetree@vger.kernel.org On Fri, Mar 22, 2019 at 01:55:45AM +0000, Jacky Bai wrote: > > > + gpc: gpc@303a0000 { > > > > interrupt-controller for node name? > > > > For the i.MX8MM and future i.MX8M serious, it is not very necessary to use GPC as a interrupt controller > in linux kernel side. For system suspend, ATF can config the GPC IMRs based on IRQ enable status in GICv3. > For cpuidle support, GICv3 has per-CPU core wakeup signals connected to the GPC logic, so GICv3 has the ability > to wake up the corresponding CPU core if the IRQ is routed to that CPU core. Additionally, I am thinking to > config the GPC as a secure resource in the future. > > Maybe, we can remove the GPC node for now. If necessary, we can add it back again? Sounds good to me. Shawn From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5AD6AC43381 for ; Fri, 22 Mar 2019 02:14:03 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 235F5213F2 for ; Fri, 22 Mar 2019 02:14:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="mZ3ODorD"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="mdpAD1wl" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 235F5213F2 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=CLwh+KVq8b60kDemmU1mp685WgbLX6/Rooahd9Xk8DI=; b=mZ3ODorDW0CgPf qNoJ9LFaAZd1GC5W8RAAlmavizhYnXo2d65zd07ZLfUIaX0trzi/R9Vj3YRywCXZka+jSY60V6Ifs tx2Ndhngo1IRb6yQBnKtzjzASRyA44qkWogGg0WEs6+vBDm4jEYsxk1lhJ6IZF29c2QpSgE5O7Cnd 3HghiCzLeocQUuSl6cKGuhlrICd4FK9OrjDT3C8L3fsyKao5ntPEiDO+k9UTucBT6MgAtTm7tJsg+ a3QBFg5Ba0i9iv+bhYTb46AP6r5k+btXlgMF8TFMqTwXdlz9+LOMkBeT8cFu39gHMjhcNOzkoN46I QXkrBmRodErxSATHLJPQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1h79h2-0003QG-6A; Fri, 22 Mar 2019 02:14:00 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1h79gz-0003Pv-Uw for linux-arm-kernel@lists.infradead.org; Fri, 22 Mar 2019 02:13:59 +0000 Received: from dragon (98.142.130.235.16clouds.com [98.142.130.235]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F1F7F213F2; Fri, 22 Mar 2019 02:13:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1553220837; bh=DZ4l971WYUnGfq6rjHhCehf2Wah83Jun+NB94u5+s4k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mdpAD1wleeRea5uwVzW2bEavQfYSBaRkuhcEP8FuWt1HorL4W9Svbktg7xaTb9a3c MK+1epDvl4j2QQ3p5ebfB5o/8MEuMgX4BB9Hk79fNAHCjdID8KwAD7CDn75pJF2nEe ZB7UzAItt7A1gPayZuRnHWv06D45yHDBSBAE0+6I= Date: Fri, 22 Mar 2019 10:13:32 +0800 From: Shawn Guo To: Jacky Bai Subject: Re: [PATCH v2 1/3] arm64: dts: imx: Add i.mx8mm dtsi support Message-ID: <20190322021331.GX12513@dragon> References: <1552369779-7614-1-git-send-email-ping.bai@nxp.com> <20190321082253.GD12513@dragon> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190321_191358_017109_45DCA235 X-CRM114-Status: GOOD ( 11.73 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "mark.rutland@arm.com" , Aisheng Dong , "devicetree@vger.kernel.org" , "s.hauer@pengutronix.de" , "robh+dt@kernel.org" , dl-linux-imx , "kernel@pengutronix.de" , "festevam@gmail.com" , "linux-arm-kernel@lists.infradead.org" , "l.stach@pengutronix.de" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, Mar 22, 2019 at 01:55:45AM +0000, Jacky Bai wrote: > > > + gpc: gpc@303a0000 { > > > > interrupt-controller for node name? > > > > For the i.MX8MM and future i.MX8M serious, it is not very necessary to use GPC as a interrupt controller > in linux kernel side. For system suspend, ATF can config the GPC IMRs based on IRQ enable status in GICv3. > For cpuidle support, GICv3 has per-CPU core wakeup signals connected to the GPC logic, so GICv3 has the ability > to wake up the corresponding CPU core if the IRQ is routed to that CPU core. Additionally, I am thinking to > config the GPC as a secure resource in the future. > > Maybe, we can remove the GPC node for now. If necessary, we can add it back again? Sounds good to me. Shawn _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel