plumbers device tree track -- last call
The Plumbers conference has officially filled up and closed registration BUT I might be able to get one or two more people into the conference. If you think that your presence will provide a positive contribution to the device tree track, please email me by Monday afternoon (California time, PDT, UTC-7:00), with a very brief comment on why your attendance will be useful. Regards, Frank Rowand -- To unsubscribe from this list: send the line unsubscribe linux-embedded in
Re: Device Tree at Plumbers, early registration ends Friday
On 5/30/2015 2:36 PM, Frank Rowand wrote: The Linux Plumbers Device Tree track was accepted by the Plumbers conference. The above is a pasto, ycch. The track is, of course: Device Tree Tools, Validation, and Troubleshooting The DEADLINE for EARLY BIRD REGISTRATION at a reduced price ends Friday, June 5. I have a limited number of free registration discounts available for presenters at the device tree track. General information about plumbers is at: http://linuxplumbersconf.org/2015/ Plumbers will be co-located with LinuxCon North America in Seattle (Plumbers is Aug 19-21, Linuxcon is Aug 17-19). On Wed Aug 19 there is a shared technical track between the two conferences. The schedule for that track should be announced very soon now. Preliminary results are that I will be presenting a talk on DT debugging in that track. LinuxCon North America info is at: http://events.linuxfoundation.org/events/linuxcon-north-america Hope to see many of you in Seattle. Regards, Frank Rowand -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Device Tree at Plumbers, looking for topics and session leaders
I am looking for additional topics to include in the device tree track at Plumbers 2015. I am also soliciting people who would like to be session leaders or scribes. I have a limited number of free registration discounts available for session leaders / presenters. The format at Plumbers is less about presentations and more about discussions. So enough slides and presentation to set the foundation of the discussion. Then lots of talking. The role of the session leader is to - present a balanced description of the topic / subject area - ensure multiple view points and alternatives are heard If you want to help shape the future of device tree, then your role as a member of the audience is to talk. To provide ideas, inspiration, your experiences, how the world you live in may be different than the one that I live in. The track description is: The Linux Plumbers 2015 Device Tree Tools, Validation, and Troubleshooting track focuses on tools (programs and scripts), techniques, and core support to enable creation of correct device trees and to support troubleshooting and debugging of incorrect device trees, drivers, and subsystems. The tools encompass static (build and pre-boot) and dynamic (boot and run-time) environments. Areas of interest include - inspection - verification and validation - troubleshooting - debugging - core support for debugging - unit tests - designing and implementing drivers for effective debugging - impact of overlays (boot and run-time updates to the device tree) - bindings - documentation Topics unrelated to the overall track but of current Device Tree interest may be accepted if there is available time - ordering of device creation and driver binding Please contact me if you plan to attend the device tree track. If you are also attending other tracks, please list those tracks so that the Plumbers planning committee can try to minimize the schedule conflicts between tracks. General information about plumbers is at: http://linuxplumbersconf.org/2015/ Plumbers will be co-located with LinuxCon North America in Seattle (Plumbers is Aug 19-21, Linuxcon is Aug 17-19). Hope to see many of you in Seattle. Regards, Frank Rowand -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Device Tree at Plumbers, early registration ends Friday
The Linux Plumbers Device Tree track was accepted by the Plumbers conference. The DEADLINE for EARLY BIRD REGISTRATION at a reduced price ends Friday, June 5. I have a limited number of free registration discounts available for presenters at the device tree track. General information about plumbers is at: http://linuxplumbersconf.org/2015/ Plumbers will be co-located with LinuxCon North America in Seattle (Plumbers is Aug 19-21, Linuxcon is Aug 17-19). On Wed Aug 19 there is a shared technical track between the two conferences. The schedule for that track should be announced very soon now. Preliminary results are that I will be presenting a talk on DT debugging in that track. LinuxCon North America info is at: http://events.linuxfoundation.org/events/linuxcon-north-america Hope to see many of you in Seattle. Regards, Frank Rowand -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Why is the deferred initcall patch not mainline?
On 10/21/2014 12:37 PM, Bird, Tim wrote: snip With regards to doing it dynamically, I'd have to think about how to do that. Having text-based lists of things to do at runtime seems to fit with how we're using device tree these days, but I'm not sure how that would work. Initcall function names are not available without KALLSYMS. That dependency would increase kernel size. So text based does not seem too good. Of course, if you are creating a text based list at compile time, a macro could easily convert an init function text name to the function pointer that is used in do_initcall_level(). Thus you would have a not so large list of function pointers. snip -Frank -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Remove CONFIG_PM altogether, enable power management all the time
On 02/09/11 09:07, Rafael J. Wysocki wrote: On Wednesday, February 09, 2011, Mark Brown wrote: On Tue, Feb 08, 2011 at 03:35:29PM -0800, Frank Rowand wrote: For 2.6.38-rc4, x86_64, CONFIG_NR_CPUS=4: size vmlinux text data bss dec hex filename 6553910 3555020 9994240 20103170 132c002 vmlinuxwithCONFIG_PM 6512652 3553116 9994240 20060008 1321768 vmlinuxwithout CONFIG_PM 41258 1904 0 43162 delta That is big enough for me to care. Hrm, that's pretty surprising. It'd be interesting to know how much of that is due to the PM core itself and how much of that is from drivers. For the drivers CONFIG_PM isn't really the option they should be using in the first place - they mostly want some combination of PM_SLEEP and PM_RUNTIME for the specific functionality. I'm running some checks now. CONFIG_PM_SLEEP=y Raphael's patch will make this a user visible option in place of raw CONFIG_PM by default so you'd be able to turn that off. No, it won't (just to clarify). Raphael's patch will turn on CONFIG_PM in the correct circumstances, and leave it off when not needed by other config options. That means that the size overhead will _not_ be an issue for me because CONFIG_PM will not be enabled when not needed. -Frank -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Remove CONFIG_PM altogether, enable power management all the time
On 02/09/11 10:40, Mark Brown wrote: On Wed, Feb 09, 2011 at 10:31:29AM -0800, Frank Rowand wrote: Raphael's patch will turn on CONFIG_PM in the correct circumstances, and leave it off when not needed by other config options. That means that the size overhead will _not_ be an issue for me because CONFIG_PM will not be enabled when not needed. That's not the issue you seemed to be raising, though. While PM is now turned on by PM_SLEEP that'll end up getting turned on by default due to the dependency on SUSPEND - you appeared to be raising the concern that this could happen and surprise users. No, that is not my concern. I was saying that Raphael's patches do not trigger any concern from me. My concern was that in your very first email that started this thread, you wrote: On 02/07/11 04:22, Mark Brown wrote: It is very rare to find a current system which is both sufficiently resource constrained to want to compile out power management support and sufficiently power insensitive to be able to tolerate doing so. Since having the configuration option requires non-zero effort to maintain, with ifdefery in most drivers, but it is used with vanishing rarity it is simpler to just remove the option. and my understanding of this proposal was a goal to remove the ability to have CONFIG_PM disabled, which results in increased memory usage for some configurations. -Frank -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] Remove CONFIG_PM altogether, enable power management all the time
On 02/08/11 04:21, Ingo Molnar wrote: snip Also, i've Cc:-ed Linus, to check whether the idea to make power management a permanent, core portion of Linux has any obvious downsides we missed. Rafael, could you do a defconfig-ish x86 build with and without CONFIG_PM, and post the 'size vmlinux' comparison - so that we can see the size difference? We make some things CONFIG_EXPERT configurable just to enable folks who *really* want to cut down on kernel size to configure it out. For 2.6.38-rc4, x86_64, CONFIG_NR_CPUS=4: size vmlinux text data bss dec hex filename 6553910 3555020 9994240 20103170 132c002 vmlinuxwithCONFIG_PM 6512652 3553116 9994240 20060008 1321768 vmlinuxwithout CONFIG_PM 41258 1904 0 43162 delta That is big enough for me to care. Turning on CONFIG_PM also forces a few other options on: 295a296 CONFIG_XEN_SAVE_RESTORE=y 422c423,431 # CONFIG_PM is not set --- CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_PM_SLEEP_SMP=y CONFIG_PM_SLEEP=y # CONFIG_SUSPEND is not set # CONFIG_HIBERNATION is not set # CONFIG_PM_RUNTIME is not set CONFIG_PM_OPS=y # CONFIG_ACPI is not set 451,454c460 CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y # CONFIG_INTEL_IDLE is not set --- # CONFIG_CPU_IDLE is not set Note that those usecases, even if they want a super-small kernel, might not care about PM at all while they care about size: small boot kernels in ROMs, or simple devices where CPU-idling implies deep low power mode, etc. So the vmlinux size comparisons would be needed really. If it's 5k nobody will care. If it's 50k-100k that's borderline. In the other side of the scale we have the 1500+ #ifdef CONFIG_PM lines strewn around the kernel source, and the frequent !PM build breakages. Ingo -Frank -- To unsubscribe from this list: send the line unsubscribe linux-embedded in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
