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=-3.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no 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 34952C4320A for ; Mon, 2 Aug 2021 17:22:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1723661102 for ; Mon, 2 Aug 2021 17:22:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230265AbhHBRWW (ORCPT ); Mon, 2 Aug 2021 13:22:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36298 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229593AbhHBRWV (ORCPT ); Mon, 2 Aug 2021 13:22:21 -0400 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 030B2C061760 for ; Mon, 2 Aug 2021 10:22:11 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id d6so17877545edt.7 for ; Mon, 02 Aug 2021 10:22:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monstr-eu.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=h2WFxDixB/3t9fazJ8CAmz6nn6qFdm6PXqRa55jZXDc=; b=IGA65fp6Y9kJutWjUbrVyl2Fs2yX4Y5Nyw28VRkXSOrXNKV4pwbGtsURCm+e8WZpUR x0mtLdrpESyaHaw5TKqAI4w4xDOMKeUyHWzIHWMLfffMCzKuK37dchQ901kx1R8JCCCc 6i0KLFK3B4yuhCa1XgAC3ZyvHMLOtcSTV1I39so7gLs1g2zafIyK5AdnKEns1eKgIRoJ nGtoTkpucKVO/x5axn0iLPo+QW+yyDIGhhfKvmu0Pzf9DKd3u0Lv6XI1hGK1b0+n7pl7 +k94W8iuHbX4nsGDg8w9cs/qu5UN3+k2ssGkVkTrkr9PxQhyEot9u7KqB5CxRtuG5T85 3bgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=h2WFxDixB/3t9fazJ8CAmz6nn6qFdm6PXqRa55jZXDc=; b=cKu0tbGY9uVHT+KHjphRQ60vyYi4iYGFqa2hAgTmK412IUJiqtypwMhKScsNA/Nal9 TtSCvqbf9zY4hBIJpG5EPi4Xw3uy/a+2mUZPel6kAIDqiAxNiV3D+3r/6ktv7BZTy7gf t6UCYMAMluauXfDcSJB4ePvm8IJMg0yhcMmUeMfoV18HZ2R9tXS/OtaclrO6ysiurQMs 7tkuaCF/1Re7WB2od/RIuldUUOhHfTQyYfJegUyNdZSavh7cTVzm+zdRzw1I4vdFveiD NnsPHaPaZSmC+/7PtBQrBJgs1/sCQVUYTWBq6HL0YJuqB+grHZ4q62MagSQrlOyCIRx2 id1Q== X-Gm-Message-State: AOAM533K8yYW6eeVCLowj4klEPGFvKKvwQJ9pJKhIuxPojQqZRzUrxPR bhbdQ1juvfgurlV8jl7tu2+N6XSaXd8xx/07hahiRg== X-Google-Smtp-Source: ABdhPJz19+tyHdDM44MeIwvI3vcyw7uKr8xbYUpmMeohq0U2lnKM5LfUtJK3ERmgE2kBTYOttq+f+oTgLkTURIWbxDQ= X-Received: by 2002:a50:9ae3:: with SMTP id p90mr20511605edb.154.1627924929507; Mon, 02 Aug 2021 10:22:09 -0700 (PDT) MIME-Version: 1.0 References: <1626868353-96475-1-git-send-email-lakshmi.sai.krishna.potthuri@xilinx.com> <1626868353-96475-5-git-send-email-lakshmi.sai.krishna.potthuri@xilinx.com> <2f5d9197-4a5e-08b5-7e47-595d337478d2@xilinx.com> In-Reply-To: From: Michal Simek Date: Mon, 2 Aug 2021 19:21:58 +0200 Message-ID: Subject: Re: [PATCH 4/4] arm: dts: zynq: Replace 'io-standard' with 'power-source' property To: Linus Walleij Cc: Rob Herring , Sai Krishna Potthuri , Greg Kroah-Hartman , Linux ARM , linux-kernel , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "open list:GPIO SUBSYSTEM" , git , saikrishna12468@gmail.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org po 2. 8. 2021 v 15:20 odes=C3=ADlatel Linus Walleij napsal: > > On Fri, Jul 30, 2021 at 2:46 PM Michal Simek wr= ote: > > > Linux Zynq pinctrl driver and in tree dts files are using io-standard > > properties at least from 2015. > > Ooops my wrong. > > What about supporting both the new property and io-standard as > a fallback, simply? That's exactly what I have Sai to do and PIN_CONFIG_IOSTANDARD is still the= re. https://lore.kernel.org/linux-arm-kernel/1626868353-96475-1-git-send-email-= lakshmi.sai.krishna.potthuri@xilinx.com/T/#md7d304d9d8f746e51d909237b9073f2= ae8930543 But IIRC I have also asked to show any warning message when io standard property is used to convert to new property. Thanks, Michal --=20 Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs