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=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 89DCBC83007 for ; Tue, 28 Apr 2020 20:07:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 67FE0208E0 for ; Tue, 28 Apr 2020 20:07:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.b="lxlBvAi5" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726436AbgD1UHC (ORCPT ); Tue, 28 Apr 2020 16:07:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58744 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726259AbgD1UGg (ORCPT ); Tue, 28 Apr 2020 16:06:36 -0400 Received: from mail-ua1-x941.google.com (mail-ua1-x941.google.com [IPv6:2607:f8b0:4864:20::941]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 76326C03C1AC for ; Tue, 28 Apr 2020 13:06:35 -0700 (PDT) Received: by mail-ua1-x941.google.com with SMTP id z16so22772622uae.11 for ; Tue, 28 Apr 2020 13:06:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NWN2pTS6iB36h7DaRZrhXtMe3/2D3xJNS6+5ajy+5jY=; b=lxlBvAi5+Kp0E1kvuLZIfX3f5amfiRbPoT6rwz3YRt6V2J5+GvjYw+NTGMfqvzrN5e 8VVsWcLM3UTsASESHTZPQ57s3QqSBVpqWcc2FO4IpeAbwUgcS0LVqe1vsODS2nG7Bz+d FscPV1JN0QyruGS7iIFxIIT5zT9F53xrKisX4= 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; bh=NWN2pTS6iB36h7DaRZrhXtMe3/2D3xJNS6+5ajy+5jY=; b=cBdyiw96syHvA6hWsRFqOKfHtneDCEGTLYFkQoUeq72iYAplLoOPGE5CXA2ewGHuVa TrGYljF81HlViaBavTL+PAlE6lXM9rXdXJT+d8LpZ+u6exJ4vh+d77v5ofb0AYqVfxXN dG7AbDMOAf3FWUOjVERVqYJb0PjEkIrVCV3mdrnaF2BkHHJL4O0gUbPzmLiKYQQD8BzK n+mSarFg+K/0/vvRYxnPTWAVIq8QLSr3PRDH9r+n4RI1eFYwbfRvhBOQa7RgJOm1Dv+y X48mI3pKbjEyMw5PxjCGqPiAl9gqmW+vER8VUo/LpAjl8IfpSK66Dyyit8s0dsXn9Uft XCTg== X-Gm-Message-State: AGi0Pua17fn2EjPc823K3kvBv1HAa4bICfEL5CRVpVjV5vDUbTLko5ux LhcrtBvjuDp1kCcmy9b2+2RJNUZ/VOu52fo0YyHUJQ== X-Google-Smtp-Source: APiQypJ5GASwyuTmq6vb+mMs8GlOiPOB+ZU/74cFC69Z5RtuhkUtZGHT2TQvquei4X23XLIf2FoJH6WJiKs+6iDLpWw= X-Received: by 2002:ab0:689a:: with SMTP id t26mr24178132uar.105.1588104394359; Tue, 28 Apr 2020 13:06:34 -0700 (PDT) MIME-Version: 1.0 References: <20200423044036.234578-1-evanbenn@chromium.org> <20200423143945.v5.2.Ia92bb4d4ce84bcefeba1d00aaa1c1e919b6164ef@changeid> In-Reply-To: From: Julius Werner Date: Tue, 28 Apr 2020 13:06:21 -0700 Message-ID: Subject: Re: [PATCH v5 2/2] watchdog: Add new arm_smc_wdt watchdog driver To: Evan Benn Cc: Julius Werner , LKML , Xingyu Chen , Anson Huang , Bjorn Andersson , Catalin Marinas , "David S. Miller" , Geert Uytterhoeven , Greg Kroah-Hartman , Guenter Roeck , Leonard Crestez , Li Yang , Marcin Juszkiewicz , Matthias Brugger , Mauro Carvalho Chehab , Olof Johansson , Rob Herring , Shawn Guo , Valentin Schneider , Will Deacon , Wim Van Sebroeck , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , "moderated list:ARM/Mediatek SoC support" , LINUX-WATCHDOG Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I think I have misunderstood the device tree json-schema spec. > My intention was for the device tree to fill in a default value in the dtb for > arm,smc-id if it was omitted in the dts. But now I see that does not seem to > happen, I cannot really find any documentation of `default`, so I will just put > a documentation string in instead and force the default in the driver. The bindings in Documentation/device-tree are just for informational purposes, they do not have any direct effect on anything. If you want there to be a default, you'll have to write the kernel code to fill it in.