Received: by 2002:a05:6358:bb9e:b0:b9:5105:a5b4 with SMTP id df30csp1515969rwb; Sat, 3 Sep 2022 18:21:26 -0700 (PDT) X-Google-Smtp-Source: AA6agR5q9/j1GnrSk6tbRFinqgHSQCv5akHVUZmj57f++T9ktmsI4HKGVCht3jNhczet6jXsdwNS X-Received: by 2002:a17:906:7714:b0:74f:f771:4e0 with SMTP id q20-20020a170906771400b0074ff77104e0mr6471119ejm.623.1662254486394; Sat, 03 Sep 2022 18:21:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662254486; cv=none; d=google.com; s=arc-20160816; b=WYHAw4Q9xRjRM4rhi1WxbuLuNwf4vvwduvsBqGzUsD8uTXC1NXpVagBspkN+vpyIvK qasC4CvALeq/OhsuU9h4NfZvJyCZUqdZK1SjczptR73Ajbdg1WzsaFkTm1qg8r8zBQ3F iPNaD0NT76BEfjf8Y3HA7Tc+YNUsR0hQi8wqiHN/0yRIe5pm45adOWuOLonr+Afmkb6L it9itOhnQYu6BBXjDbSJdat6VZ/Y39m4ZC8mZS5ZlDEbDIm+trGdow7tVNzZQ9mnWoK8 TBVd51iAJkk6NhXst0aEPda99qFhdt0JAc7HxkGjKDcgL6n81X8GXCXQipxRh1paFhrc 7TjQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=ATZI2fowS/AxNbsIyQzG4QYaMmr60ObaKExsdpSgzzM=; b=OOB1EjaUoTP134Daj7v2Zgt5FNdoS7WgVCeFitTIYVDigfGseQ/fQJpwb/QCJHjLji vc7ZShDLTsqJY3HcnVkrTRurLpA58uE2TNUOuDWqNrOcNnwAjjv25dQyedDpjgGNRmgJ Qsz5ujCboOGKDKHmNZhQkXtr7qz78h37DjpI2f+Bj+4eldYTxxaKcD8Y5/JbDO7IpNDZ cgFhDbAMhUTnq4uqHC2jsah2ttsNjVrxIIrPZPsWusFUGwczuXdMyIveEFDwh4SZ1J9X 2lcT0Fhey8ceZOYRtk4K6WLuzvnFs4obNngecmYvbOv6lC/x0yntT5ZBHQMmYLUp6dC4 pFnA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=ZG5uY2Ca; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id a27-20020a17090640db00b00732034524b9si4067357ejk.527.2022.09.03.18.21.01; Sat, 03 Sep 2022 18:21:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=ZG5uY2Ca; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230320AbiIDBDX (ORCPT + 99 others); Sat, 3 Sep 2022 21:03:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40934 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229478AbiIDBDV (ORCPT ); Sat, 3 Sep 2022 21:03:21 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3C98D4F67F; Sat, 3 Sep 2022 18:03:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=ATZI2fowS/AxNbsIyQzG4QYaMmr60ObaKExsdpSgzzM=; b=ZG5uY2CawXp8WZ17SgfqwPmxnT DwbUmf6KngHXLwGvOHgfAD6NRtTRCXgElbWKF1PL/km3GaOQLvahBGD9kYBI7ar8JY4pEppA/S50K C4RlWab0Lb5CtCJ286X64mS1bqK+gi4VRc/N6jllxtM80TV7cozuzG3HxLcmwoX5/cps=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1oUe2K-00FXdb-PA; Sun, 04 Sep 2022 03:02:56 +0200 Date: Sun, 4 Sep 2022 03:02:56 +0200 From: Andrew Lunn To: Pali =?iso-8859-1?Q?Roh=E1r?= Cc: Gregory Clement , Sebastian Hesselbarth , Rob Herring , Krzysztof Kozlowski , Marek Behun , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ARM: dts: turris-omnia: Add mcu node Message-ID: References: <20220819131152.6513-1-pali@kernel.org> <20220831142809.lcmnv3l4rnulo522@pali> <20220903152735.2ga3iwrivh6zhibf@pali> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220903152735.2ga3iwrivh6zhibf@pali> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > I'm also not sure what the DT people will say about the node name mcu. > > I don't see any examples of that in the binding documentation. They > > might request you rename it to gpio-controller, unless it does more > > than GPIO? And if it does do more than GPIO we are then into mfd > > territory, and the binding then becomes much more interesting. Then we > > start the questions, are you defining a ABI now, before there is even > > a driver for it? > > > > Andrew > > Yes, there is already driver. See my previous email, I mentioned it and > also I wrote link for this driver. Moreover now driver is merged in > upstream u-boot. I'm not comfortable accepting a DT binding for a driver which does not exist in Linux. As i said, there are interesting ABI issues here, and it could be the MFD, GPIO or reset Maintainers don't accept a binding until a Linux driver exists. At minimum, you need an Acked-by from the GPIO Maintainer, of the binding before this DT change is merged via MVEBU. Andrew