From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH v4 2/4] arm64: Add Mellanox BlueField SoC config option Date: Mon, 29 Oct 2018 16:26:13 +0100 Message-ID: References: <1540403734-137721-1-git-send-email-lsun@mellanox.com> <1540403734-137721-2-git-send-email-lsun@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Liming Sun Cc: DTML , David Woods , arm-soc , Olof Johansson , Robin Murphy , Linux ARM List-Id: devicetree@vger.kernel.org On Mon, Oct 29, 2018 at 3:58 PM Liming Sun wrote: > > It would be nice if you could still include the dts sources in the submission. > > Since this is not a classic server hardware, DT is probably more suitable > > here, and there are likely use cases that won't work with ACPI, so it's > > good to have a starting point for your users if they need to override > > the ACPI tables with a DT, or build systems with a simpler boot loader. > > Sure, I'll keep this DT change for reference. A little explanation that > Mellanox BlueField SOC could be PCIe NIC or standalone device (server) form which > can do PXE boot, CentOS installation even on the NIC, etc. The same software/driver > works on both. Ok, good. > DT seems not working well for some requirement/features like > NVDIMM (which requires ACPI DSM). That's why we switched to ACPI though > DT support is preserved. This is probably something we need to look at separately, I'm sure we will want to use NVDIMM with DT based systems in the future. Can you explain what the DSM is used for here? Is this something that could be done in software in the NVDIMM hardware specific driver? Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Mon, 29 Oct 2018 16:26:13 +0100 Subject: [PATCH v4 2/4] arm64: Add Mellanox BlueField SoC config option In-Reply-To: References: <1540403734-137721-1-git-send-email-lsun@mellanox.com> <1540403734-137721-2-git-send-email-lsun@mellanox.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Oct 29, 2018 at 3:58 PM Liming Sun wrote: > > It would be nice if you could still include the dts sources in the submission. > > Since this is not a classic server hardware, DT is probably more suitable > > here, and there are likely use cases that won't work with ACPI, so it's > > good to have a starting point for your users if they need to override > > the ACPI tables with a DT, or build systems with a simpler boot loader. > > Sure, I'll keep this DT change for reference. A little explanation that > Mellanox BlueField SOC could be PCIe NIC or standalone device (server) form which > can do PXE boot, CentOS installation even on the NIC, etc. The same software/driver > works on both. Ok, good. > DT seems not working well for some requirement/features like > NVDIMM (which requires ACPI DSM). That's why we switched to ACPI though > DT support is preserved. This is probably something we need to look at separately, I'm sure we will want to use NVDIMM with DT based systems in the future. Can you explain what the DSM is used for here? Is this something that could be done in software in the NVDIMM hardware specific driver? Arnd