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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 23176C4332F for ; Tue, 8 Nov 2022 18:40:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=/BaH565ueZNqBKcDtGkW/uCKbxAQal4Xe7Ii5E9IUVU=; b=lrh6DZfsF0caBF ihD7Fo627Eo8o7jIkTBmPJUDLCItdI7R8qiyEtjIQvH2dD8tkxytzPFXIjfz+MMcaNj+a6Q3QAXUy zCZOx67P1SMFPIi6O5D8Xz8+Lxq2oDFcOqlqarvHQBLbWHFpuyUZR0iSuXm5Uui/y1R73yR9HirBx RkJDYHNfJ75ZFAeWzQnQL8aAfh84rVYtfqLtlQJQouyQTXqqcxA2RHKg/VXs/AZxVHrO8agbf6qYA qhHXzyhBnkpgJ/LEi0BSqRtdEYW6jK3d/hUI0axsIEQdYFU+lhfM08ll/Gb83ZGpcO7dhMrHs/vD+ gUmWOKdwW5abJzDQgq0g==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1osTVL-007XEm-0z; Tue, 08 Nov 2022 18:39:23 +0000 Received: from mail.skyhub.de ([2a01:4f8:190:11c2::b:1457]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1osTVG-007X9U-HG for linux-arm-kernel@lists.infradead.org; Tue, 08 Nov 2022 18:39:20 +0000 Received: from zn.tnic (p200300ea9733e764329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ea:9733:e764:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id ED7821EC0430; Tue, 8 Nov 2022 19:39:07 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1667932748; h=from:from: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:in-reply-to:in-reply-to: references:references; bh=8fLhmoHxNKU+a+bc3xohiwQRE4EoG7MAtkbqTpQZLlw=; b=mPXbp6FmjW7vXaUgvrmqFNU/7eex8aszg6F8EqeAIN7Fxm7uqSZpr9oT/RQsNKzfXT1yJu gfZ8GTIeyksuECZAYikvBRPCJ1T15c8otctpg41kl6K8MkdwNgODuBP+SF0TuobytFnnU/ vnp4C8FZ4NbYz58keDmRznfRiYdA4KY= Date: Tue, 8 Nov 2022 19:39:02 +0100 From: Borislav Petkov To: Sai Krishna Potthuri Cc: Rob Herring , Krzysztof Kozlowski , Michal Simek , Mauro Carvalho Chehab , Tony Luck , James Morse , Robert Richter , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-edac@vger.kernel.org, saikrishna12468@gmail.com, git@amd.com, Shubhrajyoti Datta , kernel test robot Subject: Re: [PATCH v6 2/2] EDAC/zynqmp: Add EDAC support for Xilinx ZynqMP OCM Message-ID: References: <20221102070655.247511-1-sai.krishna.potthuri@amd.com> <20221102070655.247511-3-sai.krishna.potthuri@amd.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20221102070655.247511-3-sai.krishna.potthuri@amd.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221108_103918_755503_DEA56563 X-CRM114-Status: GOOD ( 13.69 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Nov 02, 2022 at 12:36:55PM +0530, Sai Krishna Potthuri wrote: > Add EDAC support for Xilinx ZynqMP OCM Controller, this driver So a while ago you said that this driver is for the on chip memory controller. Is it possible for such a system to have another memory controller too for which another EDAC driver gets loaded? Because the EDAC core - at least on x86 - assumes that a single driver runs on the system and I don't think I've ever had the case where we need multiple drivers. And in such case to audit it for concurrency issues. So I guess the question is, can a system have zynqmp_ocm_edac and say, synopsys_edac or some other EDAC driver loaded at the same time? Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel