linaro-kernel

linaro-kernel@lists.linaro.org

10094 discussions

[ACTIVITY][weekly][linaro] (Dave Martin) 2011-10-24 - 2011-10-11

by Dave Martin

On Mon, Oct 24, 2011 at 12:31:29PM +0100, Dave Martin wrote: == Dave Martin <dmart> == === Activity Summary === Three weeks mostly taken up with preparing for, attending, and cleaning up after Linaro Connect * Investigated how to port vexpress to the proposed common struct clk. Looks straightforward. There appears to be no specfic blueprint for this yet(?) === Plans === * Finish Reviewing Pawel's patches and move Versatile Express DT work forward. * Finish collecting actions from Linaro Connect, map to blueprints and prioritise. === Work Items === https://blueprints.launchpad.net/linux-linaro/+spec/kernel-versatile-boad-d… * Review Pawel Moll's multi coretile support updates: INPROGRESS === Absences === (none planned)

13 years, 5 months

[Activity] (Linus Walleij) 2011-11-05 - 2011-11-11

by Linus Walleij

== Linus Walleij linusw == === Highlights === * Harvesting some fixes for pinctrl * Sent out v2 of the pinctrl config patch set, blueprint duly updated: https://blueprints.launchpad.net/linux-linaro/+spec/pinctrl-pinprops-2011.11 * Internal presentation of kernel WoW for our internal subsystem maintainers and management, agenda driven by the Snowball people. === Plans === * Grant requested me to look after patches for the GPIO subsystem for the next two weeks so that's what I'm gonna do. * Drive generalization of U300 and Nomadik GPIO by using the pinctrl framework. drivers/gpio/gpio-[nomadik|u300] * Test the PL08x patches on the Ericsson Research PB11MPCore and submit platform data for using pl08x DMA on that platform. * Pushed out the AB8500 HWMON driver, will try to address review comments. * Look into other Ux500 stuff in need of mainlining... === Issues === * My last status mail *DISAPPEARED* from the Linaro Google mail account! However the mailing list archives house a copy: http://lists.linaro.org/pipermail/linaro-kernel/2011-November/000942.html Thanks, Linus Walleij

13 years, 5 months

ACTIVITY (Rajendra Nayak) Nov 7 - Nov 11

by Rajendra Nayak

== Rajendra Nayak <rnayak> == === Highlights === * Read through documentation, sample drivers, mailing list archives for pinctrl framework. Hacked up a basic pinmux-omap.c with minimal support for omap4 with very few functions/pin-groups defined. Needs some more work around enable/disable callbacks since OMAP pin-controller register organization is very different from existing ones which are adapted. Also in sync with Tony Lindgren (who did the existing omap-pinmux f/w) on the progress/approach. * Worked on v5 of core-regulator binding patches (fixing all comments from Olof). Will repost along with twl-regulator (including twl-smps support) after a rebase on the latest omap-i2c-twl dt adaptation patches which are under rework by Benoit Cousson. * Reworked some minor comments on omap-hsmmc dt adaptations by Olof. * Reworked omap-serial dt on top of latest serial runtime adaptation patches (rebased on 3.2-rc1). Need some more validation/cleanup before I post it out for review. === Plans === * Post an early pinmux omap support (with limited support on OMAP4 to begin with). hack up the existing auto-generation python scripts which auto-generate all OMAP pinmux data to generate the data in the new format needed by the pinctrl framework. * Repost existing series under rework, once the dependent series hit the list.

13 years, 5 months

[PATCH] totally untested attachment of device nodes to usb devices

by Grant Likely

Proof of concept, needs to be made compilable and add the unwind path on error and remove. Bodged-together-by: Grant Likely <grant.likely(a)secretlab.ca> --- Hi Deepak, Here's the code I hacked together on Friday. It would be useful to have someone take on this work and finish it so that device nodes can be attached to usb devices. g. drivers/usb/core/hub.c | 13 +++++++++++++ 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c index 96f05b2..bafd31d 100644 --- a/drivers/usb/core/hub.c +++ b/drivers/usb/core/hub.c @@ -1856,6 +1856,8 @@ fail: */ int usb_new_device(struct usb_device *udev) { + struct device_node *np = udev->bus->dev.of_node; + struct device_node *child; int err; if (udev->parent) { @@ -1864,6 +1866,17 @@ int usb_new_device(struct usb_device *udev) * sysfs power/wakeup controls wakeup enabled/disabled */ device_init_wakeup(&udev->dev, 0); + + /* Grab the device node for the hub */ + np = udev->parent->dev.of_node; + } + + /* Do we have a device tree node for this USB device? */ + if (np) { + for_each_child_of_node(child, np) { + if (value_of_reg_property(child) == udev->portnum) + udev->dev.of_node = of_node_get(child); + } } /* Tell the runtime-PM framework the device is active */ -- 1.7.5.4

13 years, 5 months

[ACTIVITY] (Thomas Abraham) 2011-11-02 - 2011-11-04

by Thomas Abraham

== Thomas Abraham <thomas-ab> == === Highlights === * Submitted rebased version of the samsung's sdhci driver device tree patches. * Started with device tree support for samsung's i2s audio interface driver. * Started looking into pinmux driver based on the pinctrl subsystem for samsung platforms. === Plans === * Submit next version of the sdhci driver dt patches with all comments addressed. * Complete the device tree support for i2s driver. * Complete the intial version of the pinmux driver for samsung platforms and submit for review.

13 years, 5 months

[Activity] (Linus Walleij) 2011-10-25 - 2011-11-04

by Linus Walleij

== Linus Walleij linusw == === Highlights === * Torvalds has pulled the pinctrl subssystem for Linux v3.2. * Several other subsystems have also been pulled for 3.2, many patches created or signed-off by me have made their way into mainline due to this, including LP5521 and LM3530 LEDs, Nomadik I2C, DB8500 CPUfreq, MMC core and the PL180 MMCI driver, AB8500 Core, a bunch of DB8500 PRCMU patches, AB5500 driver, AB8500 GPADC, a few Integrator patches, PL022 SPI and of course a stack of Ux500 core patches. * All GPIO cleanups initially started in the Cambourne sprint in cooperation with Ben Dooks, have been pulled into Torvalds tree. * Fixed bugs in my own patches that have been pulled in by Torvalds, predominantly <mach/gpio.h> cleanup fallout and AB8500 MFD core. * Attended Linaro connect in Orlando. Mainly talking and planning, not much hands-on work here. === Plans === * Prepare a second patch for generic pin control. Shawn Guo and other developers are requesting this to be able to create complete pinctrl drivers targeted for 3.3. * Drive generalization of U300 and Nomadik GPIO by using the pinctrl framework. drivers/gpio/gpio-[nomadik|u300] * Test the PL08x patches on the Ericsson Research PB11MPCore and submit platform data for using pl08x DMA on that platform. * Pushed out the AB8500 HWMON driver, will try to address review comments. * Mainline some ux500 U-Boot stuff so it can atleast boot the system. === Issues === * Some ST-Ericsson internal time-stealing as usual. Thanks, Linus Walleij

13 years, 5 months

[PATCH] totally untested attachment of device nodes to usb devices

by Grant Likely

Proof of concept, needs to be made compilable and add the unwind path on error and remove. Bodged-together-by: Grant Likely <grant.likely(a)secretlab.ca> --- Resend... I messed up Deepak's email addr. g. drivers/usb/core/hub.c | 13 +++++++++++++ 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c index 96f05b2..bafd31d 100644 --- a/drivers/usb/core/hub.c +++ b/drivers/usb/core/hub.c @@ -1856,6 +1856,8 @@ fail: */ int usb_new_device(struct usb_device *udev) { + struct device_node *np = udev->bus->dev.of_node; + struct device_node *child; int err; if (udev->parent) { @@ -1864,6 +1866,17 @@ int usb_new_device(struct usb_device *udev) * sysfs power/wakeup controls wakeup enabled/disabled */ device_init_wakeup(&udev->dev, 0); + + /* Grab the device node for the hub */ + np = udev->parent->dev.of_node; + } + + /* Do we have a device tree node for this USB device? */ + if (np) { + for_each_child_of_node(child, np) { + if (value_of_reg_property(child) == udev->portnum) + udev->dev.of_node = of_node_get(child); + } } /* Tell the runtime-PM framework the device is active */ -- 1.7.5.4

13 years, 5 months

Fwd: FYI: OpenID auth disabled on android-build.linaro.org

by Deepti Kalakeri

Hello, OpenID plugin usage has been disabled in ci.linaro.org due to some vulnerability detected with the plugin. Hence the Single Sig On option using your launchpad id wont work for now till it gets fixed. If you need to use ci.linaro.org services and need a way to login please create a new user on ci.linaro.org and mail me the details and I will give you appropriate access to the service. ---------- Forwarded message ---------- From: Paul Sokolovsky <paul.sokolovsky(a)linaro.org> Date: Fri, Oct 28, 2011 at 4:09 PM Subject: FYI: OpenID auth disabled on android-build.linaro.org To: linaro-android <linaro-android(a)linaro.org>, Alexander Sack < asac(a)linaro.org>, Danilo Šegan <danilo.segan(a)linaro.org>, Infrastructure < infrastructure(a)linaro.org> Hello, Due to suspected security issue, OpenID auth was disabed on android-build.linaro.org. OpenID was never recommended as auth means there, and instead username/passwd auth was recommended, so this change should not affect users. Please let me know if you have any issues. ETA for being enabled back is so far not known, Danilo Shegan tracks this issue. -- Best Regards, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog -- Thanks and Regards, Deepti Infrastructure Team Member, Linaro Platform Teams Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

13 years, 6 months

Platform tests for kernel CI-loop

by Deepak Saxena

Hi all, I have created a blueprint [1] for connect to discuss the topic of platform level testing and want us to have some sense of what we want before going into a face to face discussion. I would like all the landing team leads to attend this session, so I've marked you as essential. The overall problem we are trying to solve is how do we ensure that hardware enablement (USB, MMC, etc) does not break across kernel versions. We've had several cases where a patch got merged into kernel.org that broke a device driver and we didn't catch it until just before our release. This causes us to scramble and reduces the quality of the work we're delivering to our members. With the CI loop in place, we now have the opportunity to catch these type of issues early on, before they even make it into the -rc kernels. My hope is that by the end of the summit session, we have a enough information to go back and develop a high level roadmap of test cases to deliver. The questions I'd like us to think about before the connect session include: 1) What are the different devices on each board that we want to test and how do we test them? We need to go through board by board and determine which I/O devices can be tested and come up with common methods to test them across all our existing platforms. One of the questions that comes up for me is what level of testing do we want? We can do simple discovery tests such as look for sysfs device nodes and poke at values in there or we can right small applications that test specific functionality (mounting block devices and running benchmark tests and also testing ioctls for example). 2) Who develops these tests? I think the answer to this is to have Landing Team engineers developing the board-specific tests with a KWG engineer assigned to coordinate overall direction of the work. 3) Do we integrate those tests into an existing framework (LTP for example) or develop a separate framework for these tests? Related to this question is whether some of the vendors will provide us test cases we can just pull into Lava? ~Deepak [1] https://blueprints.launchpad.net/linux-linaro/+spec/linaro-kernel-platform-…

13 years, 6 months

Key signing party for UDS/Linaro in Orlando

by Jorge O. Castro

On Mon, Oct 3, 2011 at 6:32 PM, Christian Robottom Reis <kiko(a)linaro.org> wrote: > On Mon, Oct 03, 2011 at 12:20:38PM -0700, Deepak Saxena wrote: >> Is there usually a key-signing at UDS? If not, should we organize a >> Linaro one? > > Copying Jorge. > > Yes, there's usually always a massive key-signing at UDS; Jorge, can you > get us details as to whether and when the Orlando one is? As far as I can tell there hasn't been an officially scheduled keysigning in a while, usually people organize one on their own after hours, however in light of recent events it might be prudent to organize one with Linaro on a certain day after sessions. CCing ubuntu-devel to see if anyone has plans/interest in getting this together.

13 years, 6 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel