Lines Matching +full:clock +full:- +full:specifier
5 .. _printk-specifiers:
8 :Author: Andrew Murray <amurray@mpc-data.co.uk>
16 If variable is of Type, use printk format specifier:
17 ------------------------------------------------------------
41 If <type> is architecture-dependent for its size (e.g., cycles_t, tcflag_t) or
43 specifier of its largest possible type and explicitly cast to it.
53 unsupported specifier or length qualifier results in a WARN and early
72 --------------
78 Pointers printed without a specifier extension (i.e unadorned %p) are
80 has the added benefit of providing a unique identifier. On 64-bit machines
86 post-hoc. If not possible, and the aim of printing the address is to provide
97 --------------
101 %pe -ENOSPC
105 known are printed in decimal, while a non-ERR_PTR passed as the
109 -------------------------
124 The ``B`` specifier results in the symbol name with offsets and should be
125 used when printing stack backtraces. The specifier takes into
127 when tail-calls are used and marked with the noreturn GCC attribute.
131 specifier.
142 ----------------------------------
150 either kernel memory (k) or user memory (u). The subsequent ``s`` specifier
156 ---------------
163 users. The behaviour of %pK depends on the kptr_restrict sysctl - see
164 Documentation/admin-guide/sysctl/kernel.rst for more details.
172 --------------------
193 -------------------
204 printk("test: difference between pointers: %td\n", ptr2 - ptr1);
207 ----------------
211 %pr [mem 0x60000000-0x6fffffff flags 0x2200] or
213 [mem 0x0000000060000000-0x000000006fffffff flags 0x2200]
215 %pR [mem 0x60000000-0x6fffffff pref] or
217 [mem 0x0000000060000000-0x000000006fffffff pref]
227 ----------------------------------
240 ------------
244 %pra [range 0x0000000060000000-0x000000006fffffff] or
253 ----------------------------
265 -------------------------------
286 - a - ESCAPE_ANY
287 - c - ESCAPE_SPECIAL
288 - h - ESCAPE_HEX
289 - n - ESCAPE_NULL
290 - o - ESCAPE_OCTAL
291 - p - ESCAPE_NP
292 - s - ESCAPE_SPACE
302 --------------------------
308 %*phD 00-01-02- ... -3f
316 ------------------
322 %pMF 00-01-02-03-04-05
326 For printing 6-byte MAC/FDDI addresses in hex notation. The ``M`` and ``m``
330 Where FDDI addresses are concerned the ``F`` specifier can be used after
331 the ``M`` specifier to use dash (-) separators instead of the default
334 For Bluetooth addresses the ``R`` specifier shall be used after the ``M``
335 specifier to use reversed byte order suitable for visual interpretation
341 --------------
349 For printing IPv4 dot-separated decimal addresses. The ``I4`` and ``i4``
355 no specifier is provided the default network/big endian order is used.
360 --------------
368 For printing IPv6 network-order 16-bit hex addresses. The ``I6`` and ``i6``
370 colon-separators. Leading zeros are always used.
372 The additional ``c`` specifier can be used with the ``I`` specifier to
379 ---------------------------------------------------------
391 specified through ``IS`` or ``iS``, can be passed to this format specifier.
399 specifier ``c`` is given. The IPv6 address is surrounded by ``[``, ``]`` in
401 https://tools.ietf.org/html/draft-ietf-6man-text-addr-representation-07
416 -------------------
420 %pUb 00010203-0405-0607-0809-0a0b0c0d0e0f
421 %pUB 00010203-0405-0607-0809-0A0B0C0D0E0F
422 %pUl 03020100-0504-0706-0809-0a0b0c0e0e0f
423 %pUL 03020100-0504-0706-0809-0A0B0C0E0E0F
425 For printing 16-byte UUID/GUIDs addresses. The additional ``l``, ``L``,
427 lower (l) or upper case (L) hex notation - and big endian order in lower (b)
436 ------------
445 equivalent of %s dentry->d_name.name we used to use, %pd<n> prints ``n``
451 ------------------
460 ----------------
482 -----------------
492 - f - device node full_name
493 - n - device node name
494 - p - device node phandle
495 - P - device node path spec (name + @unit)
496 - F - device node flags
497 - c - major compatible string
498 - C - full compatible string
504 %pOF /foo/bar@0 - Node full name
505 %pOFf /foo/bar@0 - Same as above
506 %pOFfp /foo/bar@0:10 - Node full name + phandle
507 %pOFfcF /foo/bar@0:foo,device:--P- - Node full name +
510 D - dynamic
511 d - detached
512 P - Populated
513 B - Populated bus
518 --------------
528 - f - full name of the node, including the path
529 - P - the name of the node including an address (if there is one)
533 %pfwf \_SB.PCI0.CIO2.port@1.endpoint@0 - Full node name
534 %pfwP endpoint@0 - Node name
538 %pfwf /ocp@68000000/i2c@48072000/camera@10/port/endpoint - Full name
539 %pfwP endpoint - Node name
542 -------------
546 %pt[RT] YYYY-mm-ddTHH:MM:SS
547 %pt[RT]s YYYY-mm-dd HH:MM:SS
548 %pt[RT]d YYYY-mm-dd
569 ----------
575 For printing struct clk structures. %pC prints the name of the clock
576 (Common Clock Framework) or a unique 32-bit ID (legacy clock framework).
581 -------------------------------------------------------
586 %*pbl 0,3-6,8-10
597 --------------------------------------------------------
609 - p - [p]age flags, expects value of type (``unsigned long *``)
610 - v - [v]ma_flags, expects value of type (``unsigned long *``)
611 - g - [g]fp_flags, expects value of type (``gfp_t *``)
622 -----------------------
633 ---------------------------------------
646 %p4cc BG12 little-endian (0x32314742)
647 %p4cc Y10 little-endian (0x20303159)
648 %p4cc NV12 big-endian (0xb231564e)
651 -------------------
659 The generic FourCC code is always printed in the big-endian format,
664 using the host, reversed host byte order, little-endian, or big-endian.
668 Examples for a little-endian machine, given &(u32)0x67503030::
675 Examples for a big-endian machine, given &(u32)0x67503030::
683 ----