You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
35 lines
1.6 KiB
35 lines
1.6 KiB
From 8f14bc2a883316dfd95383900c61d7d9183e8eaf Mon Sep 17 00:00:00 2001
|
|
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
|
|
Date: Fri, 5 Jul 2013 14:54:25 +0200
|
|
Subject: [PATCH 051/203] bus: mvebu-mbus: Update main description
|
|
|
|
After replacing the MBus name-based by the new ID-based API
|
|
let's fix the general description of the driver at the beginning
|
|
of the file.
|
|
|
|
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
|
|
Tested-by: Andrew Lunn <andrew@lunn.ch>
|
|
Tested-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
|
|
---
|
|
drivers/bus/mvebu-mbus.c | 10 +++-------
|
|
1 file changed, 3 insertions(+), 7 deletions(-)
|
|
|
|
--- a/drivers/bus/mvebu-mbus.c
|
|
+++ b/drivers/bus/mvebu-mbus.c
|
|
@@ -35,13 +35,9 @@
|
|
*
|
|
* - Provides an API for platform code or device drivers to
|
|
* dynamically add or remove address decoding windows for the CPU ->
|
|
- * device accesses. This API is mvebu_mbus_add_window(),
|
|
- * mvebu_mbus_add_window_remap_flags() and
|
|
- * mvebu_mbus_del_window(). Since the (target, attribute) values
|
|
- * differ from one SoC family to another, the API uses a 'const char
|
|
- * *' string to identify devices, and this driver is responsible for
|
|
- * knowing the mapping between the name of a device and its
|
|
- * corresponding (target, attribute) in the current SoC family.
|
|
+ * device accesses. This API is mvebu_mbus_add_window_by_id(),
|
|
+ * mvebu_mbus_add_window_remap_by_id() and
|
|
+ * mvebu_mbus_del_window().
|
|
*
|
|
* - Provides a debugfs interface in /sys/kernel/debug/mvebu-mbus/ to
|
|
* see the list of CPU -> SDRAM windows and their configuration
|
|
|