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 70CA3C61DA4 for ; Thu, 23 Feb 2023 11:37:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234097AbjBWLhB (ORCPT ); Thu, 23 Feb 2023 06:37:01 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39020 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233986AbjBWLg5 (ORCPT ); Thu, 23 Feb 2023 06:36:57 -0500 Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D73074C6C9; Thu, 23 Feb 2023 03:36:56 -0800 (PST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 4F13C3200903; Thu, 23 Feb 2023 06:36:55 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 23 Feb 2023 06:36:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flygoat.com; h= cc:cc:content-transfer-encoding:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm2; t=1677152214; x=1677238614; bh=T8PK2cQRLY5A4FxRWK8i+aaat tnc3laKSanQcycFaLk=; b=d/Brj8CoyOxr+FX8rjApAyHLj8+0+L5/R+SFdsgHl YNU/mVw/fZAbKmb6HOzQWEXlYO0O/siHHu90N9nna5M7Dh23Y/UWWIoVolKCCTQf gQ0+WFr+bbJuMAlllLbygp2Ha5tspYQ3+o5sLSqo/vt8DpcPUjb8GjoDqOgYhUa7 s26FcE9GflBxxraMzH/MnAWUc4Faqwpina4odmEJZJSPmnecDY3j/BeH88dyOYxA k25rpqeQH+Lhi0mL3dv9E2JodaprQyX/gQEhCmbTryFkw+9/oSb9fuK4WEFhpMj/ 5u0yxBbdeGq9xvrPJ4gtgTrmTs9hJsiLGJg4n+gbL0f9g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1677152214; x=1677238614; bh=T8PK2cQRLY5A4FxRWK8i+aaattnc3laKSan QcycFaLk=; b=K4CuWUtFqoffTZpcwTRNJph6ugM/Wlx2m9JxCmfh/EJc+pP2b0a H37hoMSzVu6TC23e6sD7KZOhFR5+xVb14xZcXtDgW/bBn7iNh0Yc8r8iCz8SVOm4 QGIGZculzBn0kr/ujNwu3LxVMxN+YB+rZp4boOkQh05VZm9BTx40J109BqsFsgKY hIJTZVZtHjCpJzh2WT5FHzeWHD0kPW5tXrDtttPmxr6pybBMqwUR/cPFj4IXdYuC XNeX9Nx313DO9Vj7jHgcWX4OudYbOw8CxVWjowalRH57mXj0BPPtaeWGzVrZtcv5 Ik6WAy6++wQKjdypKrEpNaGVLmbFNr/HcZg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudekuddgvdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkffoggfgsedtkeertd ertddtnecuhfhrohhmpeflihgrgihunhcujggrnhhguceojhhirgiguhhnrdihrghnghes fhhlhihgohgrthdrtghomheqnecuggftrfgrthhtvghrnhephfetuddtudevieeljeejte ffheeujeduhefgffejudfhueelleduffefgfffveeknecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepjhhirgiguhhnrdihrghnghesfhhlhihgoh grthdrtghomh X-ME-Proxy: Feedback-ID: ifd894703:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 23 Feb 2023 06:36:50 -0500 (EST) From: Jiaxun Yang To: linux-mips@vger.kernel.org Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, tsbogend@alpha.franken.de, mpe@ellerman.id.au, paul.walmsley@sifive.com, palmer@dabbelt.com, robh+dt@kernel.org, hch@lst.de, m.szyprowski@samsung.com, robin.murphy@arm.com, linux-riscv@lists.infradead.org, Jiaxun Yang Subject: [PATCH v2 0/5] Use dma_default_coherent for devicetree default coherency Date: Thu, 23 Feb 2023 11:36:39 +0000 Message-Id: <20230223113644.23356-1-jiaxun.yang@flygoat.com> X-Mailer: git-send-email 2.37.1 (Apple Git-137.1) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, This series split out second half of my previous series "[PATCH 0/4] MIPS DMA coherence fixes". It intends to use dma_default_coherent to determine the default coherency of devicetree probed devices instead of hardcoding it with Kconfig options. For some MIPS systems, dma_default_coherent is determined with either bootloader or hardware registers in platform initilization code, and devicetree does not explicility specify the coherency of the device, so we need the ability to change the default coherency of devicetree probed devices. For other platforms that supports noncoherent, dma_default_coherent is a fixed value set by arch code. It's defaulted to false for most archs except RISC-V. Thanks - Jiaxun --- v2: - Add PATCH 1 to help with backporting - Use Kconfig option to set dma_default_coherent Jiaxun Yang (5): of: address: Fix default coherency for MIPS dma-mapping: Provide a fallback dma_default_coherent dma-mapping: Provide CONFIG_ARCH_DMA_DEFAULT_COHERENT riscv: Select ARCH_DMA_DEFAULT_COHERENT of: address: Always use dma_default_coherent for default coherency arch/powerpc/Kconfig | 1 - arch/riscv/Kconfig | 2 +- drivers/of/Kconfig | 4 ---- drivers/of/address.c | 2 +- include/linux/dma-map-ops.h | 1 + kernel/dma/Kconfig | 3 +++ kernel/dma/mapping.c | 6 +++++- 7 files changed, 11 insertions(+), 8 deletions(-) -- 2.37.1 (Apple Git-137.1)