forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge tag 'devprop-5.5-rc1' of git://git.kernel.org/pub/scm/linux/ker…
…nel/git/rafael/linux-pm Pull device properties framework updates from Rafael Wysocki: "Add support for printing fwnode names using a new conversion specifier "%pfw" (Sakari Ailus), clean up the software node and efi/apple-properties code in preparation for improved software node reference properties handling (Dmitry Torokhov) and fix the struct fwnode_operations description (Heikki Krogerus)" * tag 'devprop-5.5-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (22 commits) software node: simplify property_entry_read_string_array() software node: unify PROPERTY_ENTRY_XXX macros software node: remove property_entry_read_uNN_array functions software node: get rid of property_set_pointer() software node: clean up property_copy_string_array() software node: mark internal macros with double underscores efi/apple-properties: use PROPERTY_ENTRY_U8_ARRAY_LEN software node: introduce PROPERTY_ENTRY_XXX_ARRAY_LEN() software node: remove DEV_PROP_MAX device property: Fix the description of struct fwnode_operations lib/test_printf: Add tests for %pfw printk modifier lib/vsprintf: Add %pfw conversion specifier for printing fwnode names lib/vsprintf: OF nodes are first and foremost, struct device_nodes lib/vsprintf: Make use of fwnode API to obtain node names and separators lib/vsprintf: Add a note on re-using %pf or %pF lib/vsprintf: Remove support for %pF and %pf in favour of %pS and %ps device property: Add a function to obtain a node's prefix device property: Add fwnode_get_name for returning the name of a node device property: Add functions for accessing node's parents device property: Move fwnode_get_parent() up ...
- Loading branch information
Showing
11 changed files
with
414 additions
and
293 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -98,8 +98,6 @@ Symbols/Function Pointers | |
|
||
%pS versatile_init+0x0/0x110 | ||
%ps versatile_init | ||
%pF versatile_init+0x0/0x110 | ||
%pf versatile_init | ||
%pSR versatile_init+0x9/0x110 | ||
(with __builtin_extract_return_addr() translation) | ||
%pB prev_fn_of_versatile_init+0x88/0x88 | ||
|
@@ -109,14 +107,6 @@ The ``S`` and ``s`` specifiers are used for printing a pointer in symbolic | |
format. They result in the symbol name with (S) or without (s) | ||
offsets. If KALLSYMS are disabled then the symbol address is printed instead. | ||
|
||
Note, that the ``F`` and ``f`` specifiers are identical to ``S`` (``s``) | ||
and thus deprecated. We have ``F`` and ``f`` because on ia64, ppc64 and | ||
parisc64 function pointers are indirect and, in fact, are function | ||
descriptors, which require additional dereferencing before we can lookup | ||
the symbol. As of now, ``S`` and ``s`` perform dereferencing on those | ||
platforms (when needed), so ``F`` and ``f`` exist for compatibility | ||
reasons only. | ||
|
||
The ``B`` specifier results in the symbol name with offsets and should be | ||
used when printing stack backtraces. The specifier takes into | ||
consideration the effect of compiler optimisations which may occur | ||
|
@@ -440,6 +430,30 @@ Examples:: | |
|
||
Passed by reference. | ||
|
||
Fwnode handles | ||
-------------- | ||
|
||
:: | ||
|
||
%pfw[fP] | ||
|
||
For printing information on fwnode handles. The default is to print the full | ||
node name, including the path. The modifiers are functionally equivalent to | ||
%pOF above. | ||
|
||
- f - full name of the node, including the path | ||
- P - the name of the node including an address (if there is one) | ||
|
||
Examples (ACPI):: | ||
|
||
%pfwf \[email protected]@0 - Full node name | ||
%pfwP endpoint@0 - Node name | ||
|
||
Examples (OF):: | ||
|
||
%pfwf /ocp@68000000/i2c@48072000/camera@10/port/endpoint - Full name | ||
%pfwP endpoint - Node name | ||
|
||
Time and date (struct rtc_time) | ||
------------------------------- | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.