From 1b0647783282c3f1b235b0b023aeb6821d105de6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Barna=C5=9B?= Date: Mon, 9 Aug 2021 13:59:15 +0200 Subject: [PATCH] doc: change functions arguments in drivers documentation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fix functions arguments in documentation to match order of their real declarations Signed-off-by: Michał Barnaś --- doc/reference/drivers/index.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/reference/drivers/index.rst b/doc/reference/drivers/index.rst index af33e7a5861..8e606b4b02f 100644 --- a/doc/reference/drivers/index.rst +++ b/doc/reference/drivers/index.rst @@ -147,7 +147,7 @@ A subsystem API definition typically looks like this: struct subsystem_api *api; api = (struct subsystem_api *)dev->api; - api->do_that(dev, foo, bar); + api->do_that(dev, baz); } A driver implementing a particular subsystem will define the real implementation @@ -474,7 +474,7 @@ is made within the init function: { ... /* Write some data to the MMIO region */ - sys_write32(DEVICE_MMIO_GET(dev), 0xDEADBEEF); + sys_write32(0xDEADBEEF, DEVICE_MMIO_GET(dev)); ... } @@ -536,8 +536,8 @@ For example: { ... /* Write some data to the MMIO regions */ - sys_write32(DEVICE_MMIO_GET(dev, grault), 0xDEADBEEF); - sys_write32(DEVICE_MMIO_GET(dev, courge), 0xF0CCAC1A); + sys_write32(0xDEADBEEF, DEVICE_MMIO_GET(dev, grault)); + sys_write32(0xF0CCAC1A, DEVICE_MMIO_GET(dev, courge)); ... }