From mboxrd@z Thu Jan 1 00:00:00 1970 From: Viresh Kumar Subject: Re: [PATCH] dt-bindings: gpio: Convert Arm PL061 to json-schema Date: Wed, 12 Jun 2019 08:49:27 +0530 Message-ID: <20190612031927.mgr62xiirjqrzkeu@vireshk-i7> References: <20190514005033.15593-1-robh@kernel.org> <20190527064146.5rlm2audk6uojdxn@vireshk-i7> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: Linus Walleij , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , Bartosz Golaszewski , "open list:GPIO SUBSYSTEM" List-Id: linux-gpio@vger.kernel.org On 11-06-19, 13:54, Rob Herring wrote: > On Mon, May 27, 2019 at 12:41 AM Viresh Kumar wrote: > > I checked SPEAr and it is missing interrupt-controller at few places and clocks > > everywhere. Missing clocks should be fine as SPEAr doesn't get clocks from DT. > > Clocks not from DT was supposed to be a transitional thing... Right, but by the time I left ST in 2012, mainline clock's DT support wasn't there and the SPEAr core team got fired soon after that. No one was left in ST to do the porting, but there are still people using the SPEAr boards and there are products in market, so we can't delete the platform as well. So, no one is going to add clock DT support now. > > And interrupt-controller can be just added, I don't think there would be any > > platform dependent side-affects ? > > There shouldn't be. Okay, will send a patch for that then. -- viresh 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.9 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_NEOMUTT 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 AE507C31E44 for ; Wed, 12 Jun 2019 03:19:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7A74A2082C for ; Wed, 12 Jun 2019 03:19:33 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="wONe3ABj" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391947AbfFLDTc (ORCPT ); Tue, 11 Jun 2019 23:19:32 -0400 Received: from mail-pg1-f193.google.com ([209.85.215.193]:37702 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2391176AbfFLDTc (ORCPT ); Tue, 11 Jun 2019 23:19:32 -0400 Received: by mail-pg1-f193.google.com with SMTP id 20so8106225pgr.4 for ; Tue, 11 Jun 2019 20:19:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ate72NuJmVUI6S2BuZQCuvpskZE3U2N/nMIH2X9inqs=; b=wONe3ABjpXyvX++muN+ZuuQPCqABZNEGqIqxYQ/Kt3+uMGojPLxRSIvfb/BY+fdwuG KekIHVfMMPWEt2iVGpYLRtMDFlvWdWZQ5k1LeLMG6u/GZrzIezH7XP6vIhGcsBW+ii0L gOnSHP9g6CBDUTxhU2oTLwRXVDlXsKmhEbPEYheQAqd7KVigbRcszf2ZesnwW85PE1dO iyU20ncmowoBO3l8SVj5VyrMj5LmSNEaWqBtwhga5wxb4uKNqWI9n7cGRT4AetHicKKc Aw/YlYfKfl5ziY0qdFhe1J71Org6PQArMHzDhgPN6gLNsPPoPq3bsND8qGL8LNA0flRp 9Seg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ate72NuJmVUI6S2BuZQCuvpskZE3U2N/nMIH2X9inqs=; b=tNiJuzK2D9r7+0uWuMwNJtO6bp6qdHzU7A9SBa9vKo4V+pcEkliTgFXzxe6lgjTBxj lOrDwBGkTXZc6d/VRr+Ep270CoI2j90CkcrwXIufSMVPZbDnaReWOwtq+ZjM2u9u2D1G HGQvmCtInQDnWxifv89HzFPLnH2XLpYtWNJOJswmDUeF7Vv2FXUY/qGJ6gdIC1jjGrZl 0/FtDuarnURPWuJYdISpdPU++7Fv5KAhlyW3ANxs3M0aQV0SRIoVox9dImOdS2lcJrru fSD9x/qMWxgS7C19OZ/MxX9GmHwHKlUslClh+Um+gsva3R3WJyT8ANlfrep2Dy8oxE+t bdUw== X-Gm-Message-State: APjAAAUdSmDLTx9C2IhbHTymQPcmCJJ5lQx9hvxpgrC1krt6ZZKxEEL6 H+jUb+ShH+4v+YfXAO0igkgqxw== X-Google-Smtp-Source: APXvYqzHGgDNU6Vo6rIo/Aq12B4nqhPE19OxuX8C/VoLATKTH5QzhJS9otDk/sgsXlZcHlrej3ZyIg== X-Received: by 2002:a17:90a:22c6:: with SMTP id s64mr30744352pjc.5.1560309571012; Tue, 11 Jun 2019 20:19:31 -0700 (PDT) Received: from localhost ([122.172.66.84]) by smtp.gmail.com with ESMTPSA id d9sm14160236pgj.34.2019.06.11.20.19.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Jun 2019 20:19:30 -0700 (PDT) Date: Wed, 12 Jun 2019 08:49:27 +0530 From: Viresh Kumar To: Rob Herring Cc: Linus Walleij , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , Bartosz Golaszewski , "open list:GPIO SUBSYSTEM" Subject: Re: [PATCH] dt-bindings: gpio: Convert Arm PL061 to json-schema Message-ID: <20190612031927.mgr62xiirjqrzkeu@vireshk-i7> References: <20190514005033.15593-1-robh@kernel.org> <20190527064146.5rlm2audk6uojdxn@vireshk-i7> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716-391-311a52 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11-06-19, 13:54, Rob Herring wrote: > On Mon, May 27, 2019 at 12:41 AM Viresh Kumar wrote: > > I checked SPEAr and it is missing interrupt-controller at few places and clocks > > everywhere. Missing clocks should be fine as SPEAr doesn't get clocks from DT. > > Clocks not from DT was supposed to be a transitional thing... Right, but by the time I left ST in 2012, mainline clock's DT support wasn't there and the SPEAr core team got fired soon after that. No one was left in ST to do the porting, but there are still people using the SPEAr boards and there are products in market, so we can't delete the platform as well. So, no one is going to add clock DT support now. > > And interrupt-controller can be just added, I don't think there would be any > > platform dependent side-affects ? > > There shouldn't be. Okay, will send a patch for that then. -- viresh