All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 03/10] rockchip: spl: add documentation for spl_node_to_boot_device()
Date: Mon, 11 Sep 2017 13:59:03 +0200	[thread overview]
Message-ID: <1505131150-39480-4-git-send-email-philipp.tomsich@theobroma-systems.com> (raw)
In-Reply-To: <1505131150-39480-1-git-send-email-philipp.tomsich@theobroma-systems.com>

In the expectation that the spl-boot-order code will eventually
gain use outside of mach-rockchip: let's add documentation on the
spl_node_to_boot_device() function, which is likely to become a
publicly exported function.

Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
---

 arch/arm/mach-rockchip/spl-boot-order.c | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/arch/arm/mach-rockchip/spl-boot-order.c b/arch/arm/mach-rockchip/spl-boot-order.c
index 4f78c72..0bb9a73 100644
--- a/arch/arm/mach-rockchip/spl-boot-order.c
+++ b/arch/arm/mach-rockchip/spl-boot-order.c
@@ -10,6 +10,25 @@
 #include <spl.h>
 
 #if CONFIG_IS_ENABLED(OF_CONTROL)
+/**
+ * spl_node_to_boot_device() - maps from a DT-node to a SPL boot device
+ * @node:	of_offset of the node
+ *
+ * The SPL framework uses BOOT_DEVICE_... constants to identify its boot
+ * sources.  These may take on a device-specific meaning, depending on
+ * what nodes are enabled in a DTS (e.g. BOOT_DEVICE_MMC1 may refer to
+ * different controllers/block-devices, depending on which SD/MMC controllers
+ * are enabled in any given DTS).  This function maps from a DT-node back
+ * onto a BOOT_DEVICE_... constant, considering the currently active devices.
+ *
+ * Returns
+ *   -ENOENT, if no device matching the node could be found
+ *   -ENOSYS, if the device matching the node can not be mapped onto a
+ *            SPL boot device (e.g. the third MMC device)
+ *   -1, for unspecified failures
+ *   a positive integer (from the BOOT_DEVICE_... family) on succes.
+ */
+
 static int spl_node_to_boot_device(int node)
 {
 	struct udevice *parent;
-- 
2.1.4

  parent reply	other threads:[~2017-09-11 11:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 11:59 [U-Boot] [PATCH 00/10] For the RK3399-Q7, we have a few additional features in the SPL boot Philipp Tomsich
2017-09-11 11:59 ` [U-Boot] [PATCH 01/10] rockchip: rk3399: make spl_board_init board-specific Philipp Tomsich
2017-09-13  4:25   ` Simon Glass
2017-09-11 11:59 ` [U-Boot] [PATCH 02/10] rockchip: bootrom: add definitions to retrieve BROM boot-source Philipp Tomsich
2017-09-13  4:25   ` Simon Glass
2017-09-11 11:59 ` Philipp Tomsich [this message]
2017-09-13  4:25   ` [U-Boot] [PATCH 03/10] rockchip: spl: add documentation for spl_node_to_boot_device() Simon Glass
2017-09-11 11:59 ` [U-Boot] [PATCH 04/10] rockchip: spl: support a 'same-as-spl'-specifier in the spl-boot-order Philipp Tomsich
2017-09-13  4:25   ` Simon Glass
2017-09-13  8:13     ` Dr. Philipp Tomsich
2017-09-11 11:59 ` [U-Boot] [PATCH 05/10] rockchip: spl: rk3399: implement chip-specific board_spl_was_booted_from() Philipp Tomsich
2017-09-13  4:25   ` Simon Glass
2017-09-13  8:10     ` Dr. Philipp Tomsich
2017-09-11 11:59 ` [U-Boot] [PATCH 06/10] rockchip: dts: rk3399-puma: add 'same-as-spl' to the front of the boot-order Philipp Tomsich
2017-09-13  4:26   ` Simon Glass
2017-09-11 11:59 ` [U-Boot] [PATCH 07/10] rockchip: puma-rk3399: update board_init() Philipp Tomsich
2017-09-13  4:26   ` Simon Glass
2017-09-11 11:59 ` [U-Boot] [PATCH 08/10] rockchip: rk3399-puma: add boot-on regulator to override BIOS_DISABLE Philipp Tomsich
2017-09-13  4:26   ` Simon Glass
2017-09-11 11:59 ` [U-Boot] [PATCH 09/10] power: spl: add SPL_DM_REGULATOR_FIXED in Kconfig Philipp Tomsich
2017-09-13  4:26   ` Simon Glass
2017-09-13  8:20     ` Dr. Philipp Tomsich
2017-09-17 17:52       ` Simon Glass
2017-09-11 11:59 ` [U-Boot] [PATCH 10/10] rockchip: defconfig: puma-rk3399: update for DM_REGULATOR support in SPL Philipp Tomsich
2017-09-13  4:26   ` Simon Glass

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1505131150-39480-4-git-send-email-philipp.tomsich@theobroma-systems.com \
    --to=philipp.tomsich@theobroma-systems.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.