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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6DE77C433FE for ; Sat, 9 Apr 2022 12:55:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241788AbiDIM5T (ORCPT ); Sat, 9 Apr 2022 08:57:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39554 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229641AbiDIM5R (ORCPT ); Sat, 9 Apr 2022 08:57:17 -0400 Received: from aposti.net (aposti.net [89.234.176.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C1B75F3A; Sat, 9 Apr 2022 05:55:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=crapouillou.net; s=mail; t=1649508909; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nRiJT3CDPL495Cp9n4zLCUDvz6FBFEd6LlbAeNnambI=; b=CUseniPcWQGjEDaJrbq/c/Jw9ZFS6UfiVFcbXE3pz59IuH+y4ENHHeBdAnOimBEgbmNK/K n2Hw90Dhfj01qOGNSa1JWeEU076qRJQAYNp66gx0Hd0UqS6+kvVSKD2lqDu7lbdyNOiZ+V giKxprTvyRqSQV1bfi9OjMPSb013q3g= Date: Sat, 09 Apr 2022 13:55:00 +0100 From: Paul Cercueil Subject: Re: [PATCH 13/18] dt-bindings: fix jz4780-nemc issue as reported by dtbscheck To: Krzysztof Kozlowski Cc: "H. Nikolaus Schaller" , Rob Herring , Thomas Bogendoerfer , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-mips@vger.kernel.org, letux-kernel@openphoenux.org Message-Id: In-Reply-To: <2e1495ab-2773-a3bb-0ad2-4af607cccc11@linaro.org> References: <84adfe6237cd4cfd52cb9723416f69926e556e55.1649443080.git.hns@goldelico.com> <036b66b2-c221-6e9e-6a56-510e7a0d20d3@linaro.org> <2e1495ab-2773-a3bb-0ad2-4af607cccc11@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le sam., avril 9 2022 at 14:47:23 +0200, Krzysztof Kozlowski=20 a =E9crit : > On 09/04/2022 14:37, Paul Cercueil wrote: >>> The true question is whether you need simple-mfd. Isn't the binding >>> (and >>> the driver) expected to instantiate its children? >>=20 >> I can explain that one. There is the EFUSE controller located inside >> the nemc's memory area, and the two are pretty much unrelated, hence >> the "simple-mfd" compatible string. >=20 > I saw the efuse children and that's why I asked who is expected to > populate them. You said that simple-mfd is required for this, I say=20 > no. > It should work without simple-mfd... >=20 > I am kind of repeating myself but I really do not see the need of > simple-mfd in the bindings. Well, it is a "simple MFD", so I don't see why we can't use the=20 "simple-mfd" compatible. Why would we not want to use it? Besides, if the nemc driver is responsible for populating the efuse=20 device, that means the nemc driver must be enabled for the efuse to=20 work, which is nonsense, the two IP blocks being unrelated. -Paul