Received: by 2002:ac0:8845:0:0:0:0:0 with SMTP id g63csp1109796img; Tue, 26 Feb 2019 14:28:46 -0800 (PST) X-Google-Smtp-Source: AHgI3IajEWc7P6UL9KTL3GtDYT3JdpZg+MXzyVpB/4h5IC5th4cA5FYwpUAw5EIrhT9kUZdSH/gJ X-Received: by 2002:a17:902:bf05:: with SMTP id bi5mr11469804plb.259.1551220126197; Tue, 26 Feb 2019 14:28:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551220126; cv=none; d=google.com; s=arc-20160816; b=TI/Zwvv4MP+ZVr2BuifSOgjkR/6zJmyKltTvmRLHZlrltmlzXIOfhSWu51+B3cnDcr yIAJeB/7LzGpgThr1YtBCHSMObumthDyaqiCUGVgd2fvoLNWN+YSqY2+YDc6a7w+fgRs qzpSE+O7Uy3tXypcKwudCc/GCs9IjHjRti9xVdI6NRk4xTTJv74bppnJghMsuKOZwo5o qdG7WwbrXIyc+eGVDEbFwBPGQfKw1pGhoAMgjxqAhf1XxDCK1xeThVeNjNV7A5dKnRJ3 Qlb3et0qbJ4hYE/pFY6Jc9RjhP5n11VeR9BVzpf26sUuwVOl88E80RtnKvpseAmvC6OC ia8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=hAsU8UQX3DVaACmBeu4EA5s08dMiJ4hFaMZIG7ClyoI=; b=NFrJJUgeD9Kfud0ahMmny+N6de1vrdZopXzdgeLHd/jXXO8Rj7w/Nav1VijTNBNNSz emO81zSmq8pTQS7wIgfwzmvjRqjznkYr/XhrCKEgAzH6keSnAgmE+3wXmB7JGzp99Dhg f38VZ361Yp2zfKscpQ46qCiWqSfxp1hdm5EkMI03vm/NQen7eG9XTymnIKaKK7nqrtrS iYeiETMfGEHISh+330DkR1sSOyZbN/sSSr23jPTg21/5jeot1LYuzUhil7kCBxj7KxoL NKCGb3fv8TINUMf0SG1LKaI5tPqGnAQ1UwHyPoIrPpCbcaw0TN1I7iRDRugcnJTgRAFj MPYw== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=PUk1ImZM; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l9si13500514pgu.566.2019.02.26.14.28.21; Tue, 26 Feb 2019 14:28:46 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=PUk1ImZM; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729225AbfBZW1y (ORCPT + 99 others); Tue, 26 Feb 2019 17:27:54 -0500 Received: from mail-pl1-f194.google.com ([209.85.214.194]:42379 "EHLO mail-pl1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728989AbfBZW1x (ORCPT ); Tue, 26 Feb 2019 17:27:53 -0500 Received: by mail-pl1-f194.google.com with SMTP id v11so1493577plg.9; Tue, 26 Feb 2019 14:27:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=hAsU8UQX3DVaACmBeu4EA5s08dMiJ4hFaMZIG7ClyoI=; b=PUk1ImZMGFyrzGO9Q9fC2P4YK/ffSpKobD2kp21P2hlr3b0rdCWcOcZdOxee3YWaY/ 6/3vx/vdlRLtXU+MCfKSQhM5AsWDERIJQoiuOq7UJMUWcik3WpbiLOBAI8dVTV5GO9K2 Lc+rJ941tawXhzmtU4+wQI1QnvAMf/KURiQUjpokp9+sSMLBTEnyrHqrqvmw2+hjmuQ0 LfIQDk91P4d/bj5cm4X3E0O+DwUuquSMubSJ2Va14xUPwCiteiCycrBwhhiI1tnco9J6 AbVkwf0zOD36mLBUKNFDvCO86Ezo9xFRrs7qMhkX9s3zziso0TFBUa7RiTIECd0PFKxz y0mw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=hAsU8UQX3DVaACmBeu4EA5s08dMiJ4hFaMZIG7ClyoI=; b=tHGTgfiesHQL16jh+8iQLQnB9h2Q/OppzqUaiMfzrdL3R6FOuFxhu6CcHxNtGmPzNm GX27Fh+Rtq1p6SbxGm1LGD9GB6SaZEf0uUqSetVLA45CgsyF5y8P+HCMDEs9IPXY7Iz3 8rnkmXLGERARi5VmTvePBa9uGT9pABGBg6wkUi9aPq8gZzTIutVKrquqvzuHD7iZtnEL /Wym1DYCOVp591xqDsOfQ8z5bVL+6o0jat5Ybuhs8t0wUZnNNEa9VaDMYfRNKwAQAgV8 zn0U7Zw8K+7XG8iEadVJ6ck87R0xgzlpwrRU/36JE1SlEOxATeFX52abR27+VRhAKSlY BF3g== X-Gm-Message-State: AHQUAuY6axk4gIWssAd8IofCr/egOJXorlmYxuhbg+BEihnTzCU/j7/U OMPl0YupUCGhEOLJxfqn/5Y= X-Received: by 2002:a17:902:1009:: with SMTP id b9mr27573080pla.42.1551220072536; Tue, 26 Feb 2019 14:27:52 -0800 (PST) Received: from localhost ([2600:1700:e321:62f0:329c:23ff:fee3:9d7c]) by smtp.gmail.com with ESMTPSA id c18sm4706425pfo.44.2019.02.26.14.27.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 26 Feb 2019 14:27:51 -0800 (PST) Date: Tue, 26 Feb 2019 14:27:50 -0800 From: Guenter Roeck To: Rob Herring Cc: Anson Huang , "mark.rutland@arm.com" , "ulf.hansson@linaro.org" , "heiko@sntech.de" , "catalin.marinas@arm.com" , "will.deacon@arm.com" , "bjorn.andersson@linaro.org" , "festevam@gmail.com" , "jagan@amarulasolutions.com" , Andy Gross , dl-linux-imx , "devicetree@vger.kernel.org" , "linux-watchdog@vger.kernel.org" , "arnd@arndb.de" , "marc.w.gonzalez@free.fr" , "s.hauer@pengutronix.de" , "enric.balletbo@collabora.com" , "horms+renesas@verge.net.au" , "wim@linux-watchdog.org" , Daniel Baluta , "linux-arm-kernel@lists.infradead.org" , Aisheng Dong , "linux-kernel@vger.kernel.org" , "kernel@pengutronix.de" , "olof@lixom.net" , "shawnguo@kernel.org" Subject: Re: [PATCH RESEND V2 1/4] dt-bindings: fsl: scu: add watchdog binding Message-ID: <20190226222750.GA30985@roeck-us.net> References: <1550472539-16590-1-git-send-email-Anson.Huang@nxp.com> <1550472539-16590-2-git-send-email-Anson.Huang@nxp.com> <20190222195217.GA22194@bogus> <96932b3e-87f1-d8f2-95bc-0e9a8d5d45ed@roeck-us.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 26, 2019 at 03:34:12PM -0600, Rob Herring wrote: > > > > > > I think Rob suggested that the SCU parent driver should instantiate the > > > watchdog without explicit watchdog node. That would be possible, but it > > > currently uses > > > devm_of_platform_populate() to do the instantiation, and changing that > > > would be a mess. Besides, it does sem to me that your suggested node would > > > describe the hardware, so I am not sure I understand the reasoning. > > It would just be a call to create a platform device instead. How is that a mess? > > It's describing firmware. We have DT for describing h/w we've failed > to make discoverable. We should not repeat that and just describe > firmware in DT. Make the firmware discoverable! Though there are cases > like firmware provided clocks where we still need something in DT, but > this is not one of them. > It requires extra code where an added DT node would accomplish the same. It requires a mix of DT nodes for existing devices plus extra code for newly added devices. To me that looks like a revert to old platform code, which was replaced with DT descriptions over the last several years. But then if that is where things are going, who am I to argue. Guenter