Re: omap_device prints

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 21, 2011 at 10:51:09AM +0100, Russell King - ARM Linux wrote:
> I spotted this while booting the OMAP4430 SDP:
> 
> omap_device: omap4-keypad.-1: new worst case activate latency 0: 61035
> 
> and found that it came from here:
> 
>         pr_debug("omap_device: %s: activating\n", od->pdev.name);
> 
>                 pr_debug("omap_device: %s: pm_lat %d: activate: elapsed time "
>                          "%llu nsec\n", od->pdev.name, od->pm_lat_level,
>                          act_lat);
> 
>                                 pr_warning("omap_device: %s.%d: new worst case "
>                                            "activate latency %d: %llu\n",
>                                            od->pdev.name, od->pdev.id,
>                                            od->pm_lat_level, act_lat);
>                                 pr_warning("omap_device: %s.%d: activate "
>                                            "latency %d higher than exptected. "
>                                            "(%llu > %d)\n",
>                                            od->pdev.name, od->pdev.id,
>                                            od->pm_lat_level, act_lat,
>                                            odpl->activate_lat);
> 
> Is there something wrong with dev_name(&od->pdev.dev) so that we have
> consistent naming of devices, rather than poking about inside the
> platform_device accessing the name initializers directly ?

or dev_*() macros, instead ?

dev_dbg(&od->pdev.dev, "activating\n");

-- 
balbi

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux