From: Manjunath Goudar <manjunath.goudar(a)linaro.org>
This patch adds an ohci->priv field for private use by OHCI
platform drivers.
Until now none of the platform drivers has used this private space,
but that's about to change in the next patch of this series.
In V2:
No changes.
Signed-off-by: Manjunath Goudar <manjunath.goudar(a)linaro.org>
Cc: Arnd Bergmann <arnd(a)arndb.de>
Cc: Greg KH <greg(a)kroah.com>
Cc: Alan Stern <stern(a)rowland.harvard.edu>
Cc: linux-usb(a)vger.kernel.org
---
drivers/usb/host/ohci.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/host/ohci.h b/drivers/usb/host/ohci.h
index 3b58482..e2e5faa 100644
--- a/drivers/usb/host/ohci.h
+++ b/drivers/usb/host/ohci.h
@@ -421,6 +421,9 @@ struct ohci_hcd {
struct dentry *debug_periodic;
struct dentry *debug_registers;
#endif
+ /* platform-specific data -- must come last */
+ unsigned long priv[0] __aligned(sizeof(s64));
+
};
#ifdef CONFIG_PCI
--
1.7.9.5
Hi -
We're using one kernel binary with BL Switcher enabled in config, but
able to work on SoC without Big Little.
This is OK except where the BL patches touch the PMU driver. It makes
an assumption about BL configured == in use which is not true. PMU init
fails and when you try to use perf list later, it blows chunks.
I worked around it with the hack below, so it can fail out from the
bigLITTLE path when it doesn't see the cluster property in DT, but
there's presumably a better way to do that which more directly checks if
we care about BL in this execution environment.
-Andy
Author: Andy Green <andy.green(a)linaro.org>
Date: Thu May 30 09:44:17 2013 +0800
bl switcher fix dont assume bl active in pmu probe
Signed-off-by: Andy Green <andy.green(a)linaro.org>
diff --git a/arch/arm/kernel/perf_event_cpu.c
b/arch/arm/kernel/perf_event_cpu.c
index b3ae24f..c02ea21 100644
--- a/arch/arm/kernel/perf_event_cpu.c
+++ b/arch/arm/kernel/perf_event_cpu.c
@@ -440,6 +440,9 @@ static int cpu_pmu_device_probe(struct
platform_device *pdev)
hwid = of_get_property(ncluster, "reg", &len);
if (hwid && len == 4)
cluster = be32_to_cpup(hwid);
+ } else {
+ ret = probe_current_pmu(pmu);
+ goto bail;
}
/* set sibling mask to all cpu mask if socket is not
specified */
/*
@@ -501,7 +504,7 @@ static int cpu_pmu_device_probe(struct
platform_device *pdev)
} else {
ret = probe_current_pmu(pmu);
}
-
+bail:
if (ret)
goto error;
--
Andy Green | Fujitsu Landing Team Leader
Linaro.org │ Open source software for ARM SoCs | Follow Linaro
http://facebook.com/pages/Linaro/155974581091106 -
http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog
Hi,
I have downloaded and compiled/installed (on Ubuntu 12.04 the arm-probe from: https://git.linaro.org/gitweb?p=tools/arm-probe.git;a=tree
Now I am facing some issues using the tool. My Arm Energy Probe shows up as virtual serial port as /dev/ttyACM0 and I am able to open that port via "
# sudo screen /dev/ttyACM0
and when I "ctrl-c" in screen I get a response from the energy probe saying "ARM Energy Probe". So the probe should be working fine.
If I however run
# arm-probe -c ch1
All it just shows is the blelow, there are no data streamed out at all:
# configuration: ./config
# config_name: K70-SOM
# trigger: 0.400000V (hyst 0.200000V) 0.000000W (hyst 0.200000W) 400us
Configuration: K70-SOM
# date: Fri, 24 May 2013 15:45:57 +0200
# host: rb
#
This is the content of my configuration file:
# arm-probe configuration file
#
# setup name
K70-SOM
/dev/ttyACM0
ch1 0.470 1 -0.000253 0 VCORE1/MPU
ch2 0.470 2 -0.000253 0 VCORE1/MPU
ch3 0.470 3 -0.000253 0 VCORE1/MPU
I have changed file permissions for /dev/ttyACM0, so that should be fine. Additionally when I run the above arm-probe command it doesn't really care if the Arm Energy probe is connected or not - it doesn't complain it the /dev/ttyACM0 is there or not.
Any help on that would be appreciated.
Thanks.
Best,
Rob.
This series of patches begins the process of splitting ohci-hcd up into
a core library module and independent pci driver modules.
Patch 1/3 prepares the way by exporting a few functions from ohci-hcd
and adding a new mechanism for platform-specific drivers to initialize
their hc_driver structures. This deserves to be done in the core
because almost all of the entries in these structures are pure
boilerplate -- practically none of the drivers need to override more
than three of the standard core values.
Patch 2/3 is part of separating the ohci pci host controller
driver from ohci-hcd host code.
Moved sb800_prefetch() function from ohci-pci.c to pci-quirks.c file
and EXPORTed, this is part of the effort to move the ohci pci related
code to generic pci code.
Patch 3/3 separate out ohci-pci into independent driver modules.
Manjunath Goudar (3):
USB: OHCI: prepare to make ohci-hcd a library module
USB: OHCI: Generic changes to make ohci-pci a separate driver
USB: OHCI: make ohci-pci a separate driver
drivers/usb/host/Kconfig | 4 +-
drivers/usb/host/Makefile | 3 +
drivers/usb/host/ohci-hcd.c | 132 +++++++++++++++++++++++++----------
drivers/usb/host/ohci-hub.c | 1 -
drivers/usb/host/ohci-pci.c | 152 ++++++++++++-----------------------------
drivers/usb/host/ohci-q.c | 6 +-
drivers/usb/host/ohci.h | 17 +++++
drivers/usb/host/pci-quirks.c | 13 ++++
drivers/usb/host/pci-quirks.h | 2 +
9 files changed, 181 insertions(+), 149 deletions(-)
--
1.7.9.5
Hi all,
Now, we want to boot a specific operation system running on Foundation Model. Because Foundation Model isa virtual platform incorporating an AArch64 architecture <http://www.arm.com/zh/products/tools/development-tools-for-armv8.php> simulation model, we need more detailed and comprehensive technical support.
What we want to know as following:
First, whether Foundation Model can support debugging application and kernel code which should need to run on Foundation Model step by step? If Foundation Model can support debug, what should we do next? If Foundation Model cannot support debug,
are there some other tools which can support debugging application and kernel code? Are there some documents which can introduce the way to use the tool?
Second, whether Foundation Model can support usb driver, network driver? If Foundation Model can support them, how we can transmit boot loader to Foundation Model and can boot loader run on Foundation Model?
· Third, how many boot modes Foundation Model can support? Such as uBoot, whether Foundation Model can support the bootmode <app:ds:starting%20mode> such as aBoot? The introduction of aBoot is as following:http://wiki.barrelfish.org/PandaBoard
Thanks
Xiaoke Wu
hi there,
i am aware and familiar with hwpacks that were initially designed and used
to generate ubuntu/android Linaro images.
however i don't know if hwpacks are being used for OE images nowadays? OE
has intrinsic mechanism to generate/construct full images which include
machine dependent binaries as well as generic components. So are we still
using hwpacks for building OE images somehow or not? Can someone point me
to relevant documentation?
in the short future i will have to build OE images for a couple of
different h/w boards, so i am trying to understand the process to do that
a-la Linaro.
thanks
nicolas
This series of patches begins the process of splitting ohci-hcd up into
a core library module and independent pci driver modules.
Patch 1/3 prepares the way by exporting a few functions from ohci-hcd
and adding a new mechanism for platform-specific drivers to initialize
their hc_driver structures. This deserves to be done in the core
because almost all of the entries in these structures are pure
boilerplate -- practically none of the drivers need to override more
than three of the standard core values.
Patch 2/3 is part of separating the ohci pci host controller
driver from ohci-hcd host code.
Moved sb800_prefetch() function from ohci-pci.c to pci-quirks.c file
and EXPORTed, this is part of the effort to move the ohci pci related
code to generic pci code.
Patch 3/3 separate out ohci-pci into independent driver modules.
Manjunath Goudar (3):
USB: OHCI: prepare to make ohci-hcd a library module
USB: OHCI: Generic changes to make ohci-pci a separate driver
USB: OHCI: make ohci-pci a separate driver
drivers/usb/host/Kconfig | 4 +-
drivers/usb/host/Makefile | 3 +
drivers/usb/host/ohci-hcd.c | 129 +++++++++++++++++++++++++---------
drivers/usb/host/ohci-hub.c | 1 -
drivers/usb/host/ohci-pci.c | 152 ++++++++++++-----------------------------
drivers/usb/host/ohci-q.c | 8 ++-
drivers/usb/host/ohci.h | 21 ++++++
drivers/usb/host/pci-quirks.c | 14 ++++
drivers/usb/host/pci-quirks.h | 3 +
9 files changed, 189 insertions(+), 146 deletions(-)
--
1.7.9.5