Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9216EC433EF for ; Tue, 7 Dec 2021 06:37:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237058AbhLGGkw (ORCPT ); Tue, 7 Dec 2021 01:40:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45740 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237000AbhLGGkv (ORCPT ); Tue, 7 Dec 2021 01:40:51 -0500 Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C13BC061359; Mon, 6 Dec 2021 22:37:21 -0800 (PST) Received: by mail-qt1-x82f.google.com with SMTP id l8so13373156qtk.6; Mon, 06 Dec 2021 22:37:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jms.id.au; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=BuPbZ3VtbSIjqnE4li/0FsndAvm28ZetgFRErcRuEKc=; b=XP94ejYtBoGp3CPNwPRTtjZAJDYGpC7q3UhIlavb3Qy5UG6U2a5g+ZmxpCvrAmpepg H8r4Y2hVq52rVahyvO7ktsq9NOplyDQfcH4Q1q61qcpK0HbK9bT2SFFbiRM8COUUJxdv S9iYakIZiJOflzwrxN/gN9hmQFeeK6S7ryrrE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=BuPbZ3VtbSIjqnE4li/0FsndAvm28ZetgFRErcRuEKc=; b=EGdTxsGA8xYrtIvOCzo8neCnOMLMdxiqes30MbgY06PHnGiioihajuSwQWxS1nIPf6 6FiGMOqvzq2YnY0McJGDE7R7ZVWbBIhVXgaL2ITedH4hfyKIfZ6HpU/lQc85oCqOeIHf BsWTLbHXPXrW52E4HRnxlmnJ+NEk/jIm9bz606bIAEIyz6VUgLUw6F0u7/ldetIjpXNt +4MMLyBziq2Bf3UBq7TS7irXGpqJdl6iX2wP3chscFbQ0qlaDoC7g27W+K/QksxOQYZS 3jB81Oei/kqz+2dKJXB4FfE8zvXOGaRjdWfJ4fRH2tYMw8vjt+6YurXrTUs1UvqIVtBu x1VA== X-Gm-Message-State: AOAM533k6fKsavN8I8sQdHOXxo/SKhU4jDFiuHRgUolBNkBw4nJaIWo/ 82x72Vm5GWTl2EzOcIx7qd137RKXjHnnyMv/+nG8E04ye01EKQ== X-Google-Smtp-Source: ABdhPJwobWKCEjWiDe29bOj06oYLkQcx6GatlI2ptGP1TEfsNFjVDXsxHLouFqQM/ML7vXh1iILGWrI6spNE5ksGE5g= X-Received: by 2002:a05:622a:38d:: with SMTP id j13mr45726900qtx.159.1638859040480; Mon, 06 Dec 2021 22:37:20 -0800 (PST) MIME-Version: 1.0 References: <20211201033738.121846-1-howard.chiu@quantatw.com> In-Reply-To: From: Joel Stanley Date: Tue, 7 Dec 2021 06:37:07 +0000 Message-ID: Subject: Re: [PATCH v6] ARM: dts: aspeed: Adding Facebook Bletchley BMC To: =?UTF-8?B?SG93YXJkIENoaXUgKOmCseWGoOedvyk=?= Cc: Patrick Williams , Howard Chiu , Arnd Bergmann , Olof Johansson , SoC Team , Rob Herring , Andrew Jeffery , Linux ARM , devicetree , Linux Kernel Mailing List , linux-aspeed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 7 Dec 2021 at 06:34, Howard Chiu (=E9=82=B1=E5=86=A0=E7=9D=BF) wrote: > > Hi Joel > > > I'd suggest no, omit those features for now, and you can add them in > > once we have a driver. The device tree bindings for the tach/pwm need > > some work before they can be approved. > > The driver you mentioned is for OpenBMC Linux or upstream? > If it is for OpenBMC, the upstream robot will reject my DTS because the a= speed-g6.dtsi did not contain pwm/tach node. > > If it is for upstream, it will be a long time that OpenBMC Linux won't ha= ve tach driver for ast2600 series, and my patch to commit with Billy's earl= y driver for OpenBMC Linux is also meaningless. Once we've fixed the issues with the bindings, we can put the driver in the openbmc tree. Let's spend our effort fixing that. > > > When I asked you to fix the patch, I was referring to the usb-c > > warnings that I posted about the other week. > I will fix it and others you mentioned in the v7 patch. > > Howard > > > -----Original Message----- > > From: Joel Stanley > > Sent: Tuesday, December 7, 2021 11:30 AM > > To: Howard Chiu (=E9=82=B1=E5=86=A0=E7=9D=BF) > > Cc: Patrick Williams ; Howard Chiu > > ; Arnd Bergmann ; Olof > > Johansson ; SoC Team ; Rob Herring > > ; Andrew Jeffery ; Linux ARM > > ; devicetree > > ; Linux Kernel Mailing List > > ; linux-aspeed > > Subject: Re: [PATCH v6] ARM: dts: aspeed: Adding Facebook Bletchley BMC > > > > On Tue, 7 Dec 2021 at 02:53, Howard Chiu (=E9=82=B1=E5=86=A0=E7=9D=BF) > > wrote: > > > > > > Hi Joel > > > > > > Bletchley platform needs to support fan control. > > > Since Billy's patch for upstream is still under review, I can't add p= wm/tach > > node into dts or the build would fail. > > > > > > As you know, I had committed the pwm/tach driver for ast26xx to OpenB= MC > > linux, could I commit the dts to OpenBMC linux instead of upstream for = early > > build? > > > > I'd suggest no, omit those features for now, and you can add them in > > once we have a driver. The device tree bindings for the tach/pwm need > > some work before they can be approved. > > > > When I asked you to fix the patch, I was referring to the usb-c > > warnings that I posted about the other week. > > > > > > > > Howard > > > > > > > -----Original Message----- > > > > From: Joel Stanley > > > > Sent: Tuesday, December 7, 2021 6:52 AM > > > > To: Patrick Williams > > > > Cc: Howard Chiu ; Arnd Bergmann > > > > ; Olof Johansson ; SoC Team > > > > ; Rob Herring ; Andrew Jeffery > > > > ; Linux ARM = ; > > > > devicetree ; Linux Kernel Mailing List > > > > ; linux-aspeed > > ; > > > > Howard Chiu (=E9=82=B1=E5=86=A0=E7=9D=BF) > > > > Subject: Re: [PATCH v6] ARM: dts: aspeed: Adding Facebook Bletchley= BMC > > > > > > > > On Mon, 6 Dec 2021 at 21:25, Patrick Williams w= rote: > > > > > > > > > > On Wed, Dec 01, 2021 at 11:37:38AM +0800, Howard Chiu wrote: > > > > > > Initial introduction of Facebook Bletchley equipped with > > > > > > Aspeed 2600 BMC SoC. > > > > > > > > > > > > Signed-off-by: Howard Chiu > > > > > > > > > > > > > > > > ... > > > > > > > > > > > Change since v2: > > > > > > - Remove uart5 workaround > > > > > > - Remove gpio nodes of pca9552/pca9539 > > > > > > - Modify gpio-line-name of led/power/presence pins with openbmc > > > > pattern > > > > > > > > > > A number of the GPIOs do not have defined openbmc patterns for th= em > > yet. > > > > The > > > > > names you have chosen are ok for now, but we will be changing the= m as > > we > > > > refine > > > > > development of this machine further. > > > > > > > > > > > + gpio-line-names =3D > > > > > > + > > > > > > "SLED0_MS_DETECT1","SLED0_VBUS_BMC_EN","SLED0_INA230_ALERT","SLE > > > > D0_P12V_STBY_ALERT", > > > > > > + > > > > > > "SLED0_SSD_ALERT","SLED0_MS_DETECT0","SLED0_RST_CCG5","SLED0_FUSB > > > > 302_INT", > > > > > > + > > > > > > "SLED0_MD_STBY_RESET","SLED0_MD_IOEXP_EN_FAULT","SLED0_MD_DIR"," > > > > SLED0_MD_DECAY", > > > > > > + > > > > > > "SLED0_MD_MODE1","SLED0_MD_MODE2","SLED0_MD_MODE3","power-ho > > > > st0"; > > > > > > > > > > Such as these... > > > > > > > > > > > -- > > > > > > 2.25.1 > > > > > > > > > > > > > > > > Otherwise, > > > > > > > > > > Reviewed-by: Patrick Williams > > > > > > > > Thanks for reviewing. > > > > > > > > Howard, I'm merging patches for v5.17 but I can't apply this until = you > > > > fix the warnings I mentioned. > > > > > > > > Cheers, > > > > > > > > Jeol > > > > > > > > > > -- > > > > > Patrick Williams