Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp219238pxb; Wed, 18 Nov 2020 02:45:39 -0800 (PST) X-Google-Smtp-Source: ABdhPJxTaXgQWrms7lWy1SXsxAmRJyw0EKdIxWsQkYwK48DWtLApIP53tUPCfLOd1M1HIgvvCHqy X-Received: by 2002:a17:907:396:: with SMTP id ss22mr7053436ejb.24.1605696339168; Wed, 18 Nov 2020 02:45:39 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605696339; cv=none; d=google.com; s=arc-20160816; b=m+qzTCm50t8Mfc2izllIjP2XiPOM0+pww8aCzfzJgH86WsU2/KZQZpGhdvrOs3yP8/ afUezFZju7pPbA1kHQnLG4RdV3RdycWgdAVqE0CwWS7x+9a3wNT0PDQq0hI+BAMUm/pg BOpp7AhTMuXdpZGw58qZSmVZbVMQ/kX6awEFX/J3Gw5UpUINprJa4tjLkQBYV5Tcd1qQ 4hJe0h59ZWp3hH5njcKmBm60Htpx/R2Slbe9yWK95GkdgVFh05ajaWrIQLeFmCFeAv+u ONn/LH5zPrpPjjZBZhIUW8OjrrwF71J5gDGBCRUp1EADhfEqTdeHk4vg1Vk4mLhUhrN6 +ZzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=RSpyNr9ImM7m91CBLdyW5FUGxR8gG95LO/PYe+GLcPM=; b=uroCW8VUpcVygsKfhqXwvGJG3ST2MQo9DaCBey4fNg4y9O4IvLNMYIKmOAyv4YBQ6S hhH5bLj6csOVoG/GQtqCM2uZ8KFU8sgBJxHCP4sCWqGbViTr4P5G45651vv/qqquMf0d g/O8GYjMX9BM+WSrrODvYm+esRH0DQ0ppEFo4hXkez/rFT2BzUgpOs+oyH60m62CUvVG P7lhmrFZE+H4D+1D0byqJYSkwyiUp6j/4gcspld4KFYaQdsHfnXaaTJ0JUgYVAt0eHSO MWGuGUiCDarevzOCY2zepXqvHqieL/O5imLgnMeZSMhXAmsDcn3iYA5zWchGR0xWtwje jZCQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id um9si15437979ejb.521.2020.11.18.02.45.16; Wed, 18 Nov 2020 02:45:39 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726802AbgKRKmb (ORCPT + 99 others); Wed, 18 Nov 2020 05:42:31 -0500 Received: from mail-ej1-f65.google.com ([209.85.218.65]:45772 "EHLO mail-ej1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725446AbgKRKma (ORCPT ); Wed, 18 Nov 2020 05:42:30 -0500 Received: by mail-ej1-f65.google.com with SMTP id dk16so2012564ejb.12; Wed, 18 Nov 2020 02:42:29 -0800 (PST) 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; bh=RSpyNr9ImM7m91CBLdyW5FUGxR8gG95LO/PYe+GLcPM=; b=rDkONH0ooGN6zPjwQT/PAJ+R1//Dlt+Ps0mBcq6GY522GsSLeaBTktGzulLuJ3eymO ZZSpk1cnb5kBLhUzTulVSCZAo041hnsFvQUZ1asVr2bKTEW0P6PP+bbqZqf0zqNytHsy ABF8Y30p/VTTbzl8KcQZiOxBV+T5nL2GFsDW9kT1ZIFLPThn3CIHdmqea56DM+t2B9es tURslJX0FtONvQ3nRAnGo3DKY5wLvTyHh+aiXpZrjerA/aAR7BnNv2tbk20FDGzBr4dm veVM7EA//tckyX1rlMwd9SdKkpHqvK9thsYp5kLGlaPy9N9gLuXGz77ze1E20omfpnv2 Ik6g== X-Gm-Message-State: AOAM531MOrtIEVx6dfrPpLBUNYJSjZoTdMd18Ak4IQpY1PVW016TtzX5 lp7QjBUq61+YKTONgEgsDSk= X-Received: by 2002:a17:906:1408:: with SMTP id p8mr22992702ejc.548.1605696148906; Wed, 18 Nov 2020 02:42:28 -0800 (PST) Received: from kozik-lap (adsl-84-226-167-205.adslplus.ch. [84.226.167.205]) by smtp.googlemail.com with ESMTPSA id f13sm12601074ejf.42.2020.11.18.02.42.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Nov 2020 02:42:28 -0800 (PST) Date: Wed, 18 Nov 2020 11:42:26 +0100 From: Krzysztof Kozlowski To: Alice Guo Cc: "robh+dt@kernel.org" , "shawnguo@kernel.org" , "s.hauer@pengutronix.de" , dl-linux-imx , Peng Fan , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [EXT] Re: [PATCH v3 4/4] soc: imx8m: change to use platform driver Message-ID: <20201118104226.GA23766@kozik-lap> References: <20201113110409.13546-1-alice.guo@nxp.com> <20201113110409.13546-4-alice.guo@nxp.com> <20201114164128.GD14989@kozik-lap> <20201116161338.GB25108@kozik-lap> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 18, 2020 at 10:28:47AM +0000, Alice Guo wrote: > > > If it is properly explained and there is no other way then yes, you could. Here, for > > old DTBs, I would prefer to use > > of_platform_device_create() and bind to "soc" node (child of root). > > This way you would always have device and exactly one entry point for the > > probe. > > > > static struct platform_driver imx8_soc_init_driver = { > .probe = imx8_soc_init_probe, > .driver = { > .name = "soc@0", > }, > }; > Can I use "soc@0" to match this driver? It will not use of_platform_device_create(). It will use of_find_property() to determine whether > and nvmem-cells can be used. If there is no nvmem-cells, it will use the old way, which supports old DTBS. There is no need to add new > compatible. No, the soc@0 is not a proper name for the driver. Best regards, Krzysztof