Lines Matching refs:log

34 Logging can come from a wide variety of places within U-Boot. Each log message
46 * CONFIG_LOG_MAX_LEVEL - Max log level to build (anything higher is compiled
48 * CONFIG_LOG_CONSOLE - Enable writing log records to the console
93 log(category, level, format_string, ...)
95 Also debug() and error() will generate log records - these use LOG_CATEGORY
106 This will write a log record when an error code is detected (a value < 0). This
123 With these the log level is implicit in the name. The category is set by
136 Remember that all uclasses IDs are log categories too.
154 Filters are attached to log drivers to control what those drivers emit. FIlters
155 can either allow or deny a log message when they match it. Only records which
160 * minimum or maximum log level
170 The 'log' command provides access to several features:
172 * level - list log levels or set the default log level
173 * categories - list log categories
174 * drivers - list log drivers
178 * format - access the console log format
179 * rec - output a log record
181 Type 'help log' for details.
186 You can control the log format using the 'log format' command. The basic
191 In the above, file.c:123 is the filename where the log record was generated and
192 func() is the function name. By default ('log format default') only the message
199 To add new filters at runtime, use the 'log filter-add' command. For example, to
202 log filter-add -D -c spi -c mmc
207 log filter-add -A -l info
210 disable all debug and above (log level 7) messages from ``drivers/core/lists.c``
213 log filter-add -D -f drivers/core/lists.c,drivers/core/ofnode.c -L 7
215 To view active filters, use the 'log filter-list' command. Some example output
218 => log filter-list
228 information, consult the usage of the 'log' command, by running 'help log'.
249 implemented! If you do one, please add a test in test/log/log_test.c
250 log filter-add -D -f drivers/core/lists.c,drivers/core/ofnode.c -l 6
263 Convert debug() statements in the code to log() statements
265 Support making printf() emit log statements at L_INFO level
267 Convert error() statements in the code to log() statements
271 Add a way to browse log records
273 Add a way to record log records for browsing using an external tool
275 Add commands to add and remove log devices
277 Allow sharing of printf format strings in log records to reduce storage size
278 for large numbers of log records
280 Consider making log() calls emit an automatic newline, perhaps with a logn()
283 Passing log records through to linux (e.g. via device tree /chosen)
285 Provide a command to access the number of log records generated, and the
286 number dropped due to them being generated before the log system was ready.
288 Add a printf() format string pragma so that log statements are checked properly
290 Add a command to delete existing log records.