Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3314392pxb; Tue, 19 Jan 2021 21:11:59 -0800 (PST) X-Google-Smtp-Source: ABdhPJz326GnizNOEr+e4qMhiFaFg7kx5ii4R0WKANM9i8b/GTGdmZV5Vj3RsHtMHHh2xzZ0JXnM X-Received: by 2002:a05:6402:2c5:: with SMTP id b5mr6292993edx.258.1611119519057; Tue, 19 Jan 2021 21:11:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611119519; cv=none; d=google.com; s=arc-20160816; b=LNxyurBb1L/ch8cx/0I6NKYW3GEzOrVhd7grcPjOiy9E7EvO5oKoECo7D7WiiRjzor wOsewxJEOj3o3Ke2jCzcdbThpH8iDELPcKol3Ld73SxdIAE+ltwc16r+FSvjcuPyrU/7 iEk1tmmBzt21vOydev7zljdixfUYqdupo4nZTBVsbpTdSoElFe2MVRkPhfkO/seTNezs U9awUVHIQDXBOzqlccxxJ5YDe1N46E53Xp8LmOeoEp9STCSzf3ffXONPPBxomUXzgdl7 PQp8ksdCjbwHi2ISl6iYwAov4gTOFb3zGSiCNY8eG94A/hfFI2QpVGgjwlDez1FGK/+J /QrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:subject:cc:to:from:date:references:in-reply-to :message-id:mime-version:user-agent:dkim-signature:dkim-signature; bh=Xzm1/rS4H5PuGurLJPLZvaUpqeI5TgRjZU293uiw6+I=; b=xIaYU106jIZNAGZMaGOQVzaD7ILAk+FQQoy8QEtUdLFdWVO7Tf1VThv3t0sKcWU2SF K5WvpEz7kS1HpL1bF1u4jQOO2rDVbmgUEwm6BPlTBnkjYyCe3EjZgy7Ocu6L+nxXSFZB Aj8zwz8d1hukaY0N29QEISRVLTA9JBAvWlg9iY4oyepfBbFyX3GtUbLGY+zGrAcJt3IC vuT19mAIMowfzIa3EjZ22NZgtohUszDnJerbSroGuYIk/xX3iSSdcs9WG1oTHaFmuti9 AgcOsbLCjPK8H1uz7KbvVWXdCfSKzlXePkll59idpLuCItD78odIPCFES0Eag2Nkww95 XxHg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm1 header.b=P24yY3z1; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=mWT3KX8g; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i34si455480edd.44.2021.01.19.21.11.35; Tue, 19 Jan 2021 21:11:59 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@aj.id.au header.s=fm1 header.b=P24yY3z1; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=mWT3KX8g; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729781AbhATFGa (ORCPT + 99 others); Wed, 20 Jan 2021 00:06:30 -0500 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:52221 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729334AbhATFCu (ORCPT ); Wed, 20 Jan 2021 00:02:50 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 81FAC5804C4; Wed, 20 Jan 2021 00:02:04 -0500 (EST) Received: from imap2 ([10.202.2.52]) by compute3.internal (MEProxy); Wed, 20 Jan 2021 00:02:04 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aj.id.au; h= mime-version:message-id:in-reply-to:references:date:from:to:cc :subject:content-type; s=fm1; bh=Xzm1/rS4H5PuGurLJPLZvaUpqeI5TgR jZU293uiw6+I=; b=P24yY3z15/L4B7lxaydItYA4CLoWr6VA726Wz1eKfo/tgN4 dTAwH9XMR9zVWUsf9F60+BazxWYMNZe5GdJf+MQwRX6zNXt98c1Kj89e/VGvScvn lOhXmqdRA8osmB6XKVP5cVH0bGwPL408+Dtyux5ZcyNW0ZAtXDCFK2rfigJpqgU1 pSLzqV4ZEcN54lj0YmGEvdLgzWrp++UzwQYCYX8bqYfxvsKBzarpkUEB2HWXFlyJ mWONS+9cecOvSby+mxkv1fk152uyQgxo3lfS00Pjl0RGxw+WEyF9XECT3iFV7wPk DcRlz/uvnGHczYuO6BFuunBvjFxB9TKT9Hiox4Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Xzm1/r S4H5PuGurLJPLZvaUpqeI5TgRjZU293uiw6+I=; b=mWT3KX8groTC8G4KBtzThz g5yDxRt/vpcgvBEDLkZY6f9igVJ8kFp2NunCaS//O1LWgUB2jjHKdZde8AuXmnnR TOLAG55xn6P33BzQ+7rEk5gZaZ6ckPEYI23X7NirttLyHVEUeucqsGDWleEF/zKj kScbzCvM5Qv/7+l6lh/MOjl57I/DzL7LVQ5v8WhVhFvmDW6Azhi9evmh5tjAnLdc F8Xn1rhdu5aA1ET9MjoRwqOSGZztYU2s3gsHrdTbkIEeLbdX2HtsXJkUeREqYZVJ f1XxjgL/Qv5+GEe+FTi+8bdU39dClxJDAWBJjN1XFOAkKfyUaqQu+JGWgKfgsSnQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledruddugdejlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderredtnecuhfhrohhmpedftehnughr vgifucflvghffhgvrhihfdcuoegrnhgurhgvfiesrghjrdhiugdrrghuqeenucggtffrrg htthgvrhhnpeehhfefkefgkeduveehffehieehudejfeejveejfedugfefuedtuedvhefh veeuffenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe grnhgurhgvfiesrghjrdhiugdrrghu X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 0AAC7A0005D; Wed, 20 Jan 2021 00:02:03 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88 Mime-Version: 1.0 Message-Id: In-Reply-To: <20210114131622.8951-3-chiawei_wang@aspeedtech.com> References: <20210114131622.8951-1-chiawei_wang@aspeedtech.com> <20210114131622.8951-3-chiawei_wang@aspeedtech.com> Date: Wed, 20 Jan 2021 15:31:41 +1030 From: "Andrew Jeffery" To: "Chia-Wei, Wang" , "Rob Herring" , "Lee Jones" , "Joel Stanley" , "Linus Walleij" , "Corey Minyard" , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org, openbmc@lists.ozlabs.org Cc: BMC-SW@aspeedtech.com, "Haiyue Wang" , "Cyril Bur" , "Robert Lippert" Subject: Re: [PATCH v5 2/5] ARM: dts: Remove LPC BMC and Host partitions Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 14 Jan 2021, at 23:46, Chia-Wei, Wang wrote: > The LPC controller has no concept of the BMC and the Host partitions. > > A concrete instance is that the HICRB[5:4] are for the I/O port address > configurtaion of KCS channel 1/2. However, the KCS driver cannot access > HICRB for channel 1/2 initialization via syscon regmap interface due to > the parition boundary. (i.e. offset 80h) > > In addition, for the HW design backward compatibility, a newly added HW > control bit could be located at any reserved one over the LPC addressing > space. Thereby, this patch removes the lpc-bmc and lpc-host child node > and thus the LPC partitioning. > > Note that this change requires the synchronization between device tree > change and the driver change. To prevent the misuse of old devicetrees > with new drivers, or vice versa, the v2 compatible strings are adopted > for the LPC device as listed: > > "aspeed,ast2400-lpc-v2" > "aspeed,ast2500-lpc-v2" > "aspeed,ast2600-lpc-v2" > > Signed-off-by: Chia-Wei, Wang Reviewed-by: Andrew Jeffery