From patchwork Thu Feb 9 07:13:37 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Randy Dunlap X-Patchwork-Id: 13134080 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 077A1C636D4 for ; Thu, 9 Feb 2023 07:15:11 +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:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=UyIFcNu/QMCO9Vc9teORQlG3ROjEKNsHaXZdKpglc9c=; b=RXawQAGtu19oSP Nc0qlyAxazAkSg1WhQKStCMyUmkGTnU/mXLAReUp2YxrnalBz6H16PMlPWXB47iT1xqaa31MKbuV4 808CkXCW2VCyYO8k7L95tQPwCnMhfbXX87gAXs7WJ+idmXWLx8MZj4L6N4Xdx+psvV/KPaUeoNTUM WgktJeF7H3g+XKZXdGvGOsz8h9yuie9aG7jrmZlv8U0FwAdZzDDCg0p+FDY/rGrC1zsrMAmF4/dIM WGC6XRses6oHDa/0H8WvADPWGt/KnMrPoWZiawMYqqlXr+Ea0H9+Ei/YjOavCYkEiG0D6z5ihc4e3 2k3jDw5kWmixnCU2ugFg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pQ18D-000LQq-8U; Thu, 09 Feb 2023 07:14:09 +0000 Received: from [2601:1c2:980:9ec0::df2f] (helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1pQ189-000LPt-I2; Thu, 09 Feb 2023 07:14:05 +0000 From: Randy Dunlap To: linux-kernel@vger.kernel.org Cc: Randy Dunlap , Russell King , linux-arm-kernel@lists.infradead.org, Jonathan Corbet , linux-doc@vger.kernel.org, Mukesh Ojha Subject: [PATCH 01/24] Documentation: arm: correct spelling Date: Wed, 8 Feb 2023 23:13:37 -0800 Message-Id: <20230209071400.31476-2-rdunlap@infradead.org> X-Mailer: git-send-email 2.39.1 In-Reply-To: <20230209071400.31476-1-rdunlap@infradead.org> References: <20230209071400.31476-1-rdunlap@infradead.org> MIME-Version: 1.0 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Correct spelling problems for Documentation/arm/ as reported by codespell. Signed-off-by: Randy Dunlap Cc: Russell King Cc: linux-arm-kernel@lists.infradead.org Cc: Jonathan Corbet Cc: linux-doc@vger.kernel.org Reviewed-by: Mukesh Ojha --- Documentation/arm/arm.rst | 2 +- Documentation/arm/ixp4xx.rst | 4 ++-- Documentation/arm/keystone/knav-qmss.rst | 2 +- Documentation/arm/stm32/stm32-dma-mdma-chaining.rst | 6 +++--- Documentation/arm/sunxi/clocks.rst | 2 +- Documentation/arm/swp_emulation.rst | 2 +- Documentation/arm/tcm.rst | 2 +- Documentation/arm/vlocks.rst | 2 +- 8 files changed, 11 insertions(+), 11 deletions(-) diff -- a/Documentation/arm/ixp4xx.rst b/Documentation/arm/ixp4xx.rst --- a/Documentation/arm/ixp4xx.rst +++ b/Documentation/arm/ixp4xx.rst @@ -78,9 +78,9 @@ IXP4xx provides two methods of accessing 1) A direct mapped window from 0x48000000 to 0x4bffffff (64MB). To access PCI via this space, we simply ioremap() the BAR into the kernel and we can use the standard read[bwl]/write[bwl] - macros. This is the preffered method due to speed but it + macros. This is the preferred method due to speed but it limits the system to just 64MB of PCI memory. This can be - problamatic if using video cards and other memory-heavy devices. + problematic if using video cards and other memory-heavy devices. 2) If > 64MB of memory space is required, the IXP4xx can be configured to use indirect registers to access PCI This allows diff -- a/Documentation/arm/swp_emulation.rst b/Documentation/arm/swp_emulation.rst --- a/Documentation/arm/swp_emulation.rst +++ b/Documentation/arm/swp_emulation.rst @@ -1,7 +1,7 @@ Software emulation of deprecated SWP instruction (CONFIG_SWP_EMULATE) --------------------------------------------------------------------- -ARMv6 architecture deprecates use of the SWP/SWPB instructions, and recommeds +ARMv6 architecture deprecates use of the SWP/SWPB instructions, and recommends moving to the load-locked/store-conditional instructions LDREX and STREX. ARMv7 multiprocessing extensions introduce the ability to disable these diff -- a/Documentation/arm/tcm.rst b/Documentation/arm/tcm.rst --- a/Documentation/arm/tcm.rst +++ b/Documentation/arm/tcm.rst @@ -71,7 +71,7 @@ in . Using this interface it - Have the remaining TCM RAM added to a special allocation pool with gen_pool_create() and gen_pool_add() - and provice tcm_alloc() and tcm_free() for this + and provide tcm_alloc() and tcm_free() for this memory. Such a heap is great for things like saving device state when shutting off device power domains. diff -- a/Documentation/arm/stm32/stm32-dma-mdma-chaining.rst b/Documentation/arm/stm32/stm32-dma-mdma-chaining.rst --- a/Documentation/arm/stm32/stm32-dma-mdma-chaining.rst +++ b/Documentation/arm/stm32/stm32-dma-mdma-chaining.rst @@ -359,7 +359,7 @@ Driver updates for STM32 DMA-MDMA chaini descriptor you want a callback to be called at the end of the transfer (dmaengine_prep_slave_sg()) or the period (dmaengine_prep_dma_cyclic()). Depending on the direction, set the callback on the descriptor that finishes - the overal transfer: + the overall transfer: * DMA_DEV_TO_MEM: set the callback on the "MDMA" descriptor * DMA_MEM_TO_DEV: set the callback on the "DMA" descriptor @@ -371,7 +371,7 @@ Driver updates for STM32 DMA-MDMA chaini As STM32 MDMA channel transfer is triggered by STM32 DMA, you must issue STM32 MDMA channel before STM32 DMA channel. - If any, your callback will be called to warn you about the end of the overal + If any, your callback will be called to warn you about the end of the overall transfer or the period completion. Don't forget to terminate both channels. STM32 DMA channel is configured in @@ -412,4 +412,4 @@ Resources :Authors: -- Amelie Delaunay \ No newline at end of file +- Amelie Delaunay diff -- a/Documentation/arm/arm.rst b/Documentation/arm/arm.rst --- a/Documentation/arm/arm.rst +++ b/Documentation/arm/arm.rst @@ -141,7 +141,7 @@ ST506 hard drives `*configure` harddrive set to 2). I've got an internal 20MB and a great big external 5.25" FH 64MB drive (who could ever want more :-) ). - I've just got 240K/s off it (a dd with bs=128k); thats about half of what + I've just got 240K/s off it (a dd with bs=128k); that's about half of what RiscOS gets; but it's a heck of a lot better than the 50K/s I was getting last week :-) diff -- a/Documentation/arm/keystone/knav-qmss.rst b/Documentation/arm/keystone/knav-qmss.rst --- a/Documentation/arm/keystone/knav-qmss.rst +++ b/Documentation/arm/keystone/knav-qmss.rst @@ -39,7 +39,7 @@ CPPI/QMSS Low Level Driver document (doc git://git.ti.com/keystone-rtos/qmss-lld.git -k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports upto 48 accumulator +k2_qmss_pdsp_acc48_k2_le_1_0_0_9.bin firmware supports up to 48 accumulator channels. This firmware is available under ti-keystone folder of firmware.git at diff -- a/Documentation/arm/sunxi/clocks.rst b/Documentation/arm/sunxi/clocks.rst --- a/Documentation/arm/sunxi/clocks.rst +++ b/Documentation/arm/sunxi/clocks.rst @@ -5,7 +5,7 @@ Frequently asked questions about the sun This document contains useful bits of information that people tend to ask about the sunxi clock system, as well as accompanying ASCII art when adequate. -Q: Why is the main 24MHz oscillator gatable? Wouldn't that break the +Q: Why is the main 24MHz oscillator gateable? Wouldn't that break the system? A: The 24MHz oscillator allows gating to save power. Indeed, if gated diff -- a/Documentation/arm/vlocks.rst b/Documentation/arm/vlocks.rst --- a/Documentation/arm/vlocks.rst +++ b/Documentation/arm/vlocks.rst @@ -155,7 +155,7 @@ the basic algorithm: optimisation. If there are too many CPUs to read the currently_voting array in - one transaction then multiple transations are still required. The + one transaction then multiple transactions are still required. The implementation uses a simple loop of word-sized loads for this case. The number of transactions is still fewer than would be required if bytes were loaded individually. From patchwork Thu Feb 9 07:13:57 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Randy Dunlap X-Patchwork-Id: 13134081 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 E2104C05027 for ; Thu, 9 Feb 2023 07:15:20 +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:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=p71l0F6BG208/9+lTjrlJIOOXwL9MHQdnniiuFJZwiw=; b=y8t1t0BhiWvDmn 62t+/0X6xE80DWJSnDreukJHGyzAJhyK9asUDKt1ejZbFl1Wc4UlyV6n9p348MR97GPWXNsYJyg2U C9mSn3Hb8FcshFk5pU7ePwaHmm/hxrN1f576VxlZDJPWYAsTwdbbJU7o/WIqwMmcpnxUmrb2iONCN rmgjiIw4hEBjE0DqAtRIUxzaqeLDC0B+cINuekyXVNXtIHcRh9fMD1qGI3LYOIzgt+bjkxfig05fc w9BHC5h+sWvR8pzZ8lvkGr2cuSUTxpDPPuNbDsFEPrP3meBrkSOU8CJXEw4kflfp6Bafhn0aNX9MT 2QyO+GExY+De12Eto2LA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pQ18L-000LY2-I7; Thu, 09 Feb 2023 07:14:17 +0000 Received: from [2601:1c2:980:9ec0::df2f] (helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.94.2 #2 (Red Hat Linux)) id 1pQ18H-000LPt-Fx; Thu, 09 Feb 2023 07:14:13 +0000 From: Randy Dunlap To: linux-kernel@vger.kernel.org Cc: Randy Dunlap , Steven Rostedt , Masami Hiramatsu , Daniel Bristot de Oliveira , linux-trace-kernel@vger.kernel.org, Mathieu Poirier , Suzuki K Poulose , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, Jonathan Corbet , linux-doc@vger.kernel.org, Mukesh Ojha Subject: [PATCH 21/24] Documentation: trace: correct spelling Date: Wed, 8 Feb 2023 23:13:57 -0800 Message-Id: <20230209071400.31476-22-rdunlap@infradead.org> X-Mailer: git-send-email 2.39.1 In-Reply-To: <20230209071400.31476-1-rdunlap@infradead.org> References: <20230209071400.31476-1-rdunlap@infradead.org> MIME-Version: 1.0 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: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Correct spelling problems for Documentation/trace/ as reported by codespell. Signed-off-by: Randy Dunlap Cc: Steven Rostedt Cc: Masami Hiramatsu Cc: Daniel Bristot de Oliveira Cc: linux-trace-kernel@vger.kernel.org Cc: Mathieu Poirier Cc: Suzuki K Poulose Cc: coresight@lists.linaro.org Cc: linux-arm-kernel@lists.infradead.org Cc: Jonathan Corbet Cc: linux-doc@vger.kernel.org Reviewed-by: Mukesh Ojha Acked-by: Steven Rostedt (Google) Acked-by: Suzuki K Poulose # for coresight Acked-by: Daniel Bristot de Oliveira Acked-by: Masami Hiramatsu (Google) Acked-by: Steven Rostedt (Google) --- Documentation/trace/coresight/coresight-etm4x-reference.rst | 2 +- Documentation/trace/events.rst | 6 +++--- Documentation/trace/fprobe.rst | 2 +- Documentation/trace/ftrace-uses.rst | 2 +- Documentation/trace/hwlat_detector.rst | 2 +- Documentation/trace/uprobetracer.rst | 2 +- 7 files changed, 9 insertions(+), 9 deletions(-) diff -- a/Documentation/trace/coresight/coresight-etm4x-reference.rst b/Documentation/trace/coresight/coresight-etm4x-reference.rst --- a/Documentation/trace/coresight/coresight-etm4x-reference.rst +++ b/Documentation/trace/coresight/coresight-etm4x-reference.rst @@ -675,7 +675,7 @@ Bit assignments shown below:- reconstructed using only conditional branches. There is currently no support in Perf for supplying modified binaries to the decoder, so this - feature is only inteded to be used for debugging purposes or with a 3rd party tool. + feature is only intended to be used for debugging purposes or with a 3rd party tool. Choosing this option will result in a significant increase in the amount of trace generated - possible danger of overflows, or fewer instructions covered. Note, that this option also diff -- a/Documentation/trace/events.rst b/Documentation/trace/events.rst --- a/Documentation/trace/events.rst +++ b/Documentation/trace/events.rst @@ -903,7 +903,7 @@ functions can be used. To create a kprobe event, an empty or partially empty kprobe event should first be created using kprobe_event_gen_cmd_start(). The name -of the event and the probe location should be specfied along with one +of the event and the probe location should be specified along with one or args each representing a probe field should be supplied to this function. Before calling kprobe_event_gen_cmd_start(), the user should create and initialize a dynevent_cmd object using @@ -983,7 +983,7 @@ The basic idea is simple and amounts to layer that can be used to generate trace event commands. The generated command strings can then be passed to the command-parsing and event creation code that already exists in the trace event -subystem for creating the corresponding trace events. +subsystem for creating the corresponding trace events. In a nutshell, the way it works is that the higher-level interface code creates a struct dynevent_cmd object, then uses a couple @@ -1056,7 +1056,7 @@ to add an operator between the pair (her appended onto the end of the arg pair (here ';'). There's also a dynevent_str_add() function that can be used to simply -add a string as-is, with no spaces, delimeters, or arg check. +add a string as-is, with no spaces, delimiters, or arg check. Any number of dynevent_*_add() calls can be made to build up the string (until its length surpasses cmd->maxlen). When all the arguments have diff -- a/Documentation/trace/fprobe.rst b/Documentation/trace/fprobe.rst --- a/Documentation/trace/fprobe.rst +++ b/Documentation/trace/fprobe.rst @@ -111,7 +111,7 @@ saved at function entry and passed to ex the instruction pointer of @regs may be different from the @entry_ip in the entry_handler. If you need traced instruction pointer, you need to use @entry_ip. On the other hand, in the exit_handler, the instruction - pointer of @regs is set to the currect return address. + pointer of @regs is set to the correct return address. Share the callbacks with kprobes ================================ diff -- a/Documentation/trace/ftrace-uses.rst b/Documentation/trace/ftrace-uses.rst --- a/Documentation/trace/ftrace-uses.rst +++ b/Documentation/trace/ftrace-uses.rst @@ -193,7 +193,7 @@ FTRACE_OPS_FL_RECURSION Not, if this flag is set, then the callback will always be called with preemption disabled. If it is not set, then it is possible (but not guaranteed) that the callback will be called in - preemptable context. + preemptible context. FTRACE_OPS_FL_IPMODIFY Requires FTRACE_OPS_FL_SAVE_REGS set. If the callback is to "hijack" diff -- a/Documentation/trace/hwlat_detector.rst b/Documentation/trace/hwlat_detector.rst --- a/Documentation/trace/hwlat_detector.rst +++ b/Documentation/trace/hwlat_detector.rst @@ -14,7 +14,7 @@ originally written for use by the "RT" p kernel is highly latency sensitive. SMIs are not serviced by the Linux kernel, which means that it does not -even know that they are occuring. SMIs are instead set up by BIOS code +even know that they are occurring. SMIs are instead set up by BIOS code and are serviced by BIOS code, usually for "critical" events such as management of thermal sensors and fans. Sometimes though, SMIs are used for other tasks and those tasks can spend an inordinate amount of time in the diff -- a/Documentation/trace/uprobetracer.rst b/Documentation/trace/uprobetracer.rst --- a/Documentation/trace/uprobetracer.rst +++ b/Documentation/trace/uprobetracer.rst @@ -55,7 +55,7 @@ Synopsis of uprobe_tracer (\*1) only for return probe. (\*2) this is useful for fetching a field of data structures. - (\*3) Unlike kprobe event, "u" prefix will just be ignored, becuse uprobe + (\*3) Unlike kprobe event, "u" prefix will just be ignored, because uprobe events can access only user-space memory. Types