This patch enables CPU cores on Exynos4, on Exynos4412 secondary CPU cores
are power-gated, therefore we must turn on the CPU cores on the system boot.
Shows below log message on boot.
[0.045000] CPU: Testing write buffer coherency: ok
[0.045000] CPU0: thread -1, cpu 0, socket 10, mpidr
This patch support to control USB HSIC of EXYNOS4,
edited based on Samsung's GT-i9100 ICS Opensource Update7.
Change-Id: Ifba33c6a5166abf3644794eee6abe528bd71f521
Signed-off-by: Dongjin Kim
---
arch/arm/mach-exynos/common.c|5 +
This patch assign the I2C channel for HDMIPHY for Exynos4x12
in s5p_i2c_hdmiphy_set_platdata() and s5p_hdmi_set_platdata()
Change-Id: I7e66c8f9327e2f7dce7440efb8583b506d65831a
Signed-off-by: Dongjin Kim
---
arch/arm/plat-samsung/devs.c |4
1 file changed, 4 insertions(+)
diff --git
GPIO functions are not registered for Exynos4412 yet,
therefore exynos4_gpiolib_init() is added to initialize Exynos4412 SoC.
Change-Id: I5945d94c6fbfc309ccf882eba067864a338c04ca
Signed-off-by: Dongjin Kim
---
drivers/gpio/gpio-samsung.c |6 --
1 file changed, 4 insertions(+), 2
Memory fragmentation introduced by ballooning might reduce significantly
the number of 2MB contiguous memory blocks that can be used within a guest,
thus imposing performance penalties associated with the reduced number of
transparent huge pages that could be used by the guest workload.
This
Memory fragmentation introduced by ballooning might reduce significantly
the number of 2MB contiguous memory blocks that can be used within a guest,
thus imposing performance penalties associated with the reduced number of
transparent huge pages that could be used by the guest workload.
This
This was sent encoded as base64 which is awkward.
On Sat, Aug 04, 2012 at 01:01:38PM +0545, Devendra Naga wrote:
> -} else {
> -priv->bh_thread.prio = DEFAULT_PRIO;
> -}
> + } else
> + priv->bh_thread.prio = DEFAULT_PRIO;
Probably it's not worth resending if this
__neigh_create() returns either a pointer to struct neighbour or PTR_ERR().
But the caller expects it to return either a pointer or NULL. Replace
the NULL check with IS_ERR() check.
The bug was introduced in a263b3093641fb1ec377582c90986a7fd0625184.
Signed-off-by: Vasily Kulikov
---
Compile
On Sat, Aug 04, 2012 at 03:44:14PM +1000, Francois Rigaut wrote:
> Seth,
>
> [CC'd people, sorry we exchanged a few emails with Seth outside of
> the lists, I passed him the acpi tables and here are gmux dumps]
>
> Allright. thanks for gmux-dump. There seems to be progress, as I can
> see the
Add ocp2scp data node in omap4 device tree file.
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 04cbbcb..8a780b2
This patch series is done as a preparatory step for adding phy drivers
for dwc3 and musb.
This series adds a new driver for ocp2scp (only dt) to which phy
drivers are connected.
Since currently there is no generic way to create a child device along
with doing a pm_runtime_enable (the exact
Adds a new driver *omap-ocp2scp*. This driver takes the responsibility of
creating all the devices that is connected to OCP2SCP. In the case of OMAP4,
USB2PHY is connected to ocp2scp.
This also includes device tree support for ocp2scp driver and
the documentation with device tree binding
On 6 Aug 2012, Alex Deucher outgrape:
> On Sat, Aug 4, 2012 at 12:13 PM, Nix wrote:
>> Something appears to be wrong, but I have no idea what. I've not changed
>> anything other than the kernel since my last non-huge-delayed startup
>> earlier this week, and both the monitors still work,
On Sat, Aug 4, 2012 at 12:13 PM, Nix wrote:
> Possibly-relevant info:
>
> - Two DVI monitors, identical specs, one dual-head graphics card
>(so no VGA switcheroo or awesome-yet-terrifying PRIME madness needed)
>
> - KMS, Xserver 1.12.3, driver 6.14.6-28 (trunk current as of today),
>
On Fri, Aug 03, 2012 at 03:48:26PM -0700, Pandita, Vikram wrote:
> On Fri, Aug 3, 2012 at 3:36 PM, Greg KH wrote:
> > On Fri, Aug 03, 2012 at 03:25:17PM -0700, Pandita, Vikram wrote:
> >> >> This was something that got used internally and helped at times.
> >> >
> >> > Could you have used the
On 8/6/2012 9:26 AM, Russell King - ARM Linux wrote:
On Mon, Aug 06, 2012 at 09:19:10AM -0400, Cyril Chemparathy wrote:
With a flush_cache_all(), we could avoid having to operate a cacheline
at a time, but that clobbers way more than necessary.
You can't do that, because flush_cache_all() on
On Mon, Aug 6, 2012 at 9:24 PM, Michal Hocko wrote:
> On Sat 04-08-12 14:08:31, Hillf Danton wrote:
>> The computation of page offset index is incorrect to be used in scanning
>> prio tree, as huge page offset is required, and is fixed with well
>> defined routine.
>>
>> Changes from v1
>>
On 8/6/2012 7:14 AM, Russell King - ARM Linux wrote:
On Tue, Jul 31, 2012 at 07:04:39PM -0400, Cyril Chemparathy wrote:
This patch fixes up the types used when converting back and forth between
physical and virtual addresses.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Cyril Chemparathy
On Mon, Aug 06, 2012 at 09:19:10AM -0400, Cyril Chemparathy wrote:
> With a flush_cache_all(), we could avoid having to operate a cacheline
> at a time, but that clobbers way more than necessary.
You can't do that, because flush_cache_all() on some CPUs requires the
proper MMU mappings to be in
>>> On 06.08.12 at 15:16, JérômeCarretero wrote:
> If it helps:
>
> - I can bisect the patch further down (might be a bit silly because
> I don't quite understand it),
> - you can suggest some modifications and at least I can test them
What would help most would be the full kernel log up to
On Sat 04-08-12 14:08:31, Hillf Danton wrote:
> The computation of page offset index is incorrect to be used in scanning
> prio tree, as huge page offset is required, and is fixed with well
> defined routine.
>
> Changes from v1
> o s/linear_page_index/linear_hugepage_index/ for clearer
This patch series adds dt data for MUSB and related modules to
get MUSB working
These patches were initially part of
[PATCH v6 00/11] omap: musb: Add device tree support
These patches can be tested by applying it over
[PATCH v7 0/7] omap: musb: Add device tree support
These patches were
Add twl6030-usb data node in twl6030 device tree file
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4-panda.dts |4
arch/arm/boot/dts/omap4-sdp.dts |4
arch/arm/boot/dts/twl6030.dtsi|5 +
3 files changed, 13 insertions(+)
Add omap-usb2 data node in omap4 device tree file.
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 8a780b2..d774733 100644
Add twl4030-usb data node in twl4030 device tree file.
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/twl4030.dtsi | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/twl4030.dtsi b/arch/arm/boot/dts/twl4030.dtsi
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-.dts file.
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap3-beagle.dts |6 ++
arch/arm/boot/dts/omap3-evm.dts|6 ++
On 8/6/2012 7:12 AM, Russell King - ARM Linux wrote:
On Tue, Jul 31, 2012 at 07:04:37PM -0400, Cyril Chemparathy wrote:
+static void __init init_patch_kernel(void)
+{
+ const void *start = &__patch_table_begin;
+ const void *end = &__patch_table_end;
+
+
On Mon, 06 Aug 2012 14:08:03 +0100
"Jan Beulich" wrote:
> with the change at hand I merely tried to be proactive).
Jan,
If it helps:
- I can bisect the patch further down (might be a bit silly because
I don't quite understand it),
- you can suggest some modifications and at least I can test
Hi,
> Hi,
>
> On Mon, Aug 06, 2012 at 06:12:05PM +0800, Peiyong Feng wrote:
> > I got a kernel panic when try hsotg of ok6410 which is based on
> > s3c6410:
As you said, you are using the ok6410. And it is "based" on the s3c6410
CPU. S3C6410 is a single core CPU. I assume that ok6410 is also
can confirm - this fixed it!
Am 06.08.2012 14:37, schrieb Avi Kivity:
On 08/06/2012 03:12 PM, Avi Kivity wrote:
On 08/06/2012 11:46 AM, Stefan Priebe - Profihost AG wrote:
But still i got the segfault and core dump - this is my main problem? I
mean qemu-kvm master isn't declared as stable. So
All the PHY configuration other than VBUS, ID GND and OTG SRP are removed
from twl6030. The phy configurations are taken care by the dedicated
usb2 phy driver. So twl6030 is made as comparator driver for VBUS and
ID detection.
Writing to control module which is now handled in omap2430.c should be
Add device tree support for twl4030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/usb/twl-usb.txt| 19 ++
drivers/usb/otg/twl4030-usb.c | 26
All phy related programming like enabling/disabling the clocks, powering
on/off the phy is taken care of by this driver. It is also used for OTG
related functionality like srp.
This also includes device tree support for usb2 phy driver and
the documentation with device tree binding information is
The mailbox register for usb otg in omap is present in control module.
On detection of any events VBUS or ID, this register should be written
to send the notification to musb core.
Till we have a separate control module driver to write to control module,
omap2430 will handle the register writes
All the unnessary functions in omap-phy-internal is removed.
These functionality are now handled by omap-usb2 phy driver.
Cc: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Tony Lindgren
---
arch/arm/mach-omap2/omap_phy_internal.c | 138 ---
Added device tree support for omap musb driver and updated the
Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 34 +++-
drivers/usb/musb/omap2430.c| 54
Add device tree support for twl6030 usb driver.
Update the Documentation with device tree binding information.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/usb/twl-usb.txt| 21 +++
drivers/usb/otg/twl6030-usb.c | 39
This patch series adds device tree support for MUSB and device
tree support for all the related modules to get MUSB working in
OMAP platform.
A new omap-usb2 phy driver has been added (with only dt suppport)
to perform phy configurations. Previously this configuration was
performed by twl6030,
>>> On 06.08.12 at 14:52, Matthew Garrett wrote:
> On Mon, Aug 06, 2012 at 07:44:34AM +0100, Jan Beulich wrote:
>
>> In any case, without having seen _how_ things break I don't
>> think a decision should be taken if/how to address this
>> (apparent) regression.
>
> Machines that previously
On 08/03/2012 10:36 AM, Xiao Guangrong wrote:
> There are two bugs:
> - the 'error page' is forgot to be released
> [ it is unneeded after commit a2766325cf9f9, for backport, we
> still do kvm_release_pfn_clean for the error pfn ]
>
> - guest pages are always released regardless of the
On 08/06/2012 04:01 PM, Avi Kivity wrote:
> On 08/03/2012 10:37 AM, Xiao Guangrong wrote:
>> After that, the exported and un-inline function, get_fault_pfn,
>> can be removed
>>
>>
>> +#define KVM_PFN_ERR_FAULT (-EFAULT)
>> +
>
> IMO this symbol isn't needed, just use -EFAULT (and -EHWPOISON
On 08/03/2012 10:37 AM, Xiao Guangrong wrote:
> After that, the exported and un-inline function, get_fault_pfn,
> can be removed
>
>
> +#define KVM_PFN_ERR_FAULT(-EFAULT)
> +
IMO this symbol isn't needed, just use -EFAULT (and -EHWPOISON etc.)
directly. Just document it in hva_to_pfn(),
On Mon, Aug 06, 2012 at 12:03:01PM +1000, Stephen Rothwell wrote:
> Hi Mark,
>
> After merging the spi-mb tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
I've dropped these patches. Daniel, please fix and resubmit.
--
To unsubscribe from this list: send the line
Both find_vma and find_vma_prev have code for walking rb tree, and we can
walk less.
To cut the walk in find_vma_prev off, find_vma is changed to take care of
vm_prev while walking rb tree, and we end up wrapping find_vma_prev with
find_vma.
btw, what happened to LKML?
Signed-off-by: Hillf
On Mon, Aug 06, 2012 at 07:44:34AM +0100, Jan Beulich wrote:
> In any case, without having seen _how_ things break I don't
> think a decision should be taken if/how to address this
> (apparent) regression.
Machines that previously worked no longer work. That's a pretty strong
argument in favour
On 08/06/2012 03:37 PM, Avi Kivity wrote:
> On 08/06/2012 03:12 PM, Avi Kivity wrote:
>> On 08/06/2012 11:46 AM, Stefan Priebe - Profihost AG wrote:
>>
>>> But still i got the segfault and core dump - this is my main problem? I
>>> mean qemu-kvm master isn't declared as stable. So i don't care
From: Martin Pelikan
Remove some useless and invalid comments; (char *)0 where NULL should be
used; static array is zeroed by definition and therefore it's reasonable
to specify its size explicitly, rather than having tens of bonkers lines.
If someone can document the original meaning or
On 08/06/2012 01:58 PM, Michal Nazarewicz wrote:
>
> Tomasz Stanislawski writes:
>> I recommend to change the semantics for unlimited number of segments
>> from 'value 0' to:
>>
>> #define DMA_SEGMENTS_COUNT_UNLIMITED ((unsigned long)INT_MAX)
Sorry. It should be:
#define
2012/8/6 Cong Wang :
> From: WANG Cong
>
> This patch fixes the following warning:
>
> usr/include/linux/string.h:8: userspace cannot reference function or variable
> defined in the kernel
Thanks for finding this problem.
Looks good to me.
> Cc: Akinobu Mita
> Signed-off-by: WANG Cong
>
>
On 08/06/2012 03:12 PM, Avi Kivity wrote:
> On 08/06/2012 11:46 AM, Stefan Priebe - Profihost AG wrote:
>
>> But still i got the segfault and core dump - this is my main problem? I
>> mean qemu-kvm master isn't declared as stable. So i don't care about the
>> slowness here.
>>
>> What can we do
On Mon, Aug 06, 2012 at 11:46:42AM +0100, Lee Jones wrote:
> If we're booting with Device Tree enabled, we want the IRQ numbers to
> be taken and translated from the Device Tree binary. If not, they
> should be taken from the resource allocation defined in the AB8500 MFD
> core driver.
>
>
On Sun, Aug 05, 2012 at 09:43:44PM +0100, Anthony Olech wrote:
> This is the REGULATOR component driver of the Dialog DA9058 PMIC.
Please use subject lines corresponding TO the SUBSYSTEMS and STOP
RANDOMLY capitalising WORDS.
> +static int da9058_buck_ramp_voltage(struct regulator_dev *rdev,
>
On Mon, 2012-08-06 at 11:44 +0200, Eric Dumazet wrote:
> On Mon, 2012-08-06 at 17:08 +0800, Cong Wang wrote:
> > On Fri, 2012-08-03 at 12:10 +0200, Eric Dumazet wrote:
> > >
> > > I did this , just take it ;)
> >
> > Do we have to pass gfp to ->ndo_netpoll_setup() too? It seems no, so far
> > I
If we're booting with Device Tree enabled, we want the IRQ numbers to
be taken and translated from the Device Tree binary. If not, they
should be taken from the resource allocation defined in the AB8500 MFD
core driver.
Tested-by: Linus Walleij
Signed-off-by: Lee Jones
---
From: WANG Cong
This patch fixes the following warning:
usr/include/linux/string.h:8: userspace cannot reference function or variable
defined in the kernel
Cc: Akinobu Mita
Signed-off-by: WANG Cong
---
diff --git a/include/linux/string.h b/include/linux/string.h
index ffe0442..b917881
On Sun, Aug 05, 2012 at 09:43:42PM +0100, Anthony Olech wrote:
> @@ -3,6 +3,7 @@
> #
>
> if HAS_IOMEM
> +
> menu "Multifunction device drivers"
Hrm?
> +static int da9058_automatic_adc_conversion(struct da9058 *da9058,
> + const int channel, int *value)
> +{
I
On Mon, Aug 6, 2012 at 1:08 PM, Johannes Thumshirn
wrote:
> Changed call to simple_strtoul to kstrtoint in pcm_set_impulse_volume(...)
>
> Signed-off-by: Johannes Thumshirn
> ---
> drivers/staging/line6/pcm.c | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
Reviewed-by: Stefan
At this moment in time there is only one known configuration for the
Nomadik I2C driver. By not holding that configuration in the driver
adds some unnecessary overhead in platform code. The configuration
as already been removed from platform code, this patch checks for any
over-riding
This patch adds device tree decriptors for dove SoC and currently
supported boards.
Signed-off-by: Sebastian Hesselbarth
Cc: Russell King
Cc: Jason Cooper
Cc: Andrew Lunn
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: Rabeeh Khoury
Cc: Ian Molton
Cc: Arnd
This adds a generic DT_MACHINE for mach-dove. As with other orion based
SoCs there still is some glue code required to make all internal devices
work, i.e. auxdata is provided to pass clocks to corresponding device
drivers.
Signed-off-by: Sebastian Hesselbarth
Cc: Russell King
Cc: Jason Cooper
This patch adds clock gates from the clock gating control register
available on dove. All clock gates are hooked up to tclk, except for
gigabit ethernet controller (ge) which is a child of gephy to allow
both enabled/disabled at the same time.
Signed-off-by: Sebastian Hesselbarth
Cc: Russell
This patch adds basic support for the SolidRun CuBox to DT based
mach-dove. There are still some issues related to ongoing orion/mvebu
development, e.g. gpio-led will not work as there is no DT pinctrl
for dove yet and we don't have board specific setup code. Nevertheless,
the DT description is
The main purpose of this function is to exclude ME devices
without support for MEI/HECI interface from binding
Currently affected systems are C600/X79 based servers
that expose PCI device even though it doesn't supported ME Interface.
MEI driver accessing such nonfunctional device can corrupt
the
This patch synchronizes the clock setup of dove with other orion-based
platforms.
In dove_find_tclk there was a note about DOVE_SAMPLE_HI/LO register to
detect tclk. While it might be possible to set a different tclk frequency
with reset strapping the Dove datasheets don't tell anything about
This patch set adds DT support for Marvell Dove SoC and three boards
equipped with this SoC. The work is based on device tree support for
Marvell Orion based SoCs introduced in 3.6-rc1.
The first three patches move mach-dove closer to Marvell Kirkwood's
setup code by unifying the clock setup
On Sun, Aug 05, 2012 at 11:40:16PM +0200, Daniel Vetter wrote:
> As long as it's only apple shipping multi-gpu machines with
> broken/non-existing vbt, I'll happily stomach the quirk list entries.
> They're bad, but imo the lesser evil.
Doing this via quirks means that we'll always be broken on
On Sun, Aug 05, 2012 at 07:57:19PM +, Opensource [Anthony Olech] wrote:
> Hi Mark,
Don't send top posted mails and fix your mail client ti wrod wrap within
paragraphs.
> The problem is that the auto allocated "irq_base" comes back as zero.
> I repeat - in v3.4 the daa9058 driver work, but
On Mon, Aug 06, 2012 at 12:50:10PM +0200, Joerg Roedel wrote:
> On Sat, Aug 04, 2012 at 12:08:46PM -0600, Alex Williamson wrote:
> Hmm, tried it here, At least pci_request_acs() still gets called. How do
> you detect if ACS is really enabled?
Okay, I found a problem. pci_request_acs needs to be
On 08/06/2012 11:46 AM, Stefan Priebe - Profihost AG wrote:
> But still i got the segfault and core dump - this is my main problem? I
> mean qemu-kvm master isn't declared as stable. So i don't care about the
> slowness here.
>
> What can we do about the core dump and crash?
Okay, I reproduced
Changed call to simple_strtoul to kstrtoint in pcm_set_impulse_volume(...)
Signed-off-by: Johannes Thumshirn
---
drivers/staging/line6/pcm.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/line6/pcm.c b/drivers/staging/line6/pcm.c
index
Tomasz Stanislawski writes:
> I recommend to change the semantics for unlimited number of segments
> from 'value 0' to:
>
> #define DMA_SEGMENTS_COUNT_UNLIMITED ((unsigned long)INT_MAX)
>
> Using INT_MAX will allow using safe conversions between signed and
> unsigned integers.
LONG_MAX seems
Ingo,
just a "ping" message, so that this change won't be forgotten.
It was waiting for v3.6: https://lkml.org/lkml/2012/6/6/134
thank you!
Anton.
On Fri, 2012-06-01 at 14:49 +0530, Srikar Dronamraju wrote:
> From: Srikar Dronamraju
>
> Since read_opcode() reads from the referenced page
On Monday 06 August 2012, qiang@freescale.com wrote:
>
> From: Qiang Liu
>
> The use of spin_lock_irqsave() is a stronger locking mechanism than is
> required throughout the driver. The minimum locking required should be
> used instead. Interrupts will be turned off and context will be
On Mon, Aug 06, 2012 at 01:27:56AM +0200, Heiko Stübner wrote:
> 500). Therefore if 500mA are the upper limit but the regulator also supports
> lower values, these lower values always get selected (100mA in my case).
> In contrast pda_power sets the target current as both lower and upper limit.
On Mon, Aug 06, 2012 at 04:55:30PM +0530, Kishon Vijay Abraham I wrote:
> Adds a new driver *omap-ocp2scp*. This driver takes the responsibility of
> creating all the devices that is connected to OCP2SCP. In the case of OMAP4,
> USB2PHY is connected to ocp2scp.
>
> This also includes device tree
On Monday 06 August 2012, Lee Jones wrote:
>
> +struct irq_domain *db8500_irq_domain;
> +
Should this be static?
> @@ -2583,7 +2585,7 @@ static void prcmu_irq_mask(struct irq_data *d)
>
> spin_lock_irqsave(_transfer.dbb_irqs_lock, flags);
>
> - mb0_transfer.req.dbb_irqs &=
Hello Hans
Am Donnerstag, den 19.07.2012, 01:47 +0200 schrieb Hans J. Koch:
> You'll hear from me soon, thanks for your work! Comments and reviews
> from others are welcome...
Is there any progress on this topic?
--
Gruß
Dominic
Frankfurt Institute for Advanced Studies (FIAS)
The source file needed a change that was told in the description to
know that the #include needed to be fixed, and the function changed
another value to 0 (yes) in the description (that said FIXME.) The
patch fixes a typo-like error and has been checked with checkpatch.pl
in the scripts
From: Dragos Tatulea
If gcc has a different default fpmath set (e.g. sse),
many unuseful warnings will be spewed when compiling on an
architecture that doesn't support it.
An example would be Google's Android 4.1 x86 toochain which
is compiled with -mfpmath=sse.
This can affect out of tree
This patch series is done as a preparatory step for adding phy drivers
for dwc3 and musb.
This series adds a new driver for ocp2scp (only dt) to which phy
drivers are connected.
Since currently there is no generic way to create a child device along
with doing a pm_runtime_enable (the exact
Adds a new driver *omap-ocp2scp*. This driver takes the responsibility of
creating all the devices that is connected to OCP2SCP. In the case of OMAP4,
USB2PHY is connected to ocp2scp.
This also includes device tree support for ocp2scp driver and
the documentation with device tree binding
Add ocp2scp data node in omap4 device tree file.
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap4.dtsi |8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
index 04cbbcb..8a780b2
On Mon, Aug 6, 2012 at 12:46 PM, Lee Jones wrote:
> If we're booting with Device Tree enabled, we want the IRQ numbers to
> be taken and translated from the Device Tree binary. If not, they
> should be taken from the resource allocation defined in the AB8500 MFD
> core driver.
>
> Signed-off-by:
On Wed, 1 Aug 2012, Konrad Rzeszutek Wilk wrote:
> On Thu, Jul 26, 2012 at 04:33:51PM +0100, Stefano Stabellini wrote:
> > bind_evtchn_to_irqhandler can legitimately return 0 (irq 0): it is not
> > an error.
> >
> > If Linux is running as an HVM domain and is running as Dom0, use
> >
Around Mon 06 Aug 2012 18:32:09 +0900 or thereabout, Jingoo Han wrote:
> This patch removes goto err_free_mem, which makes code a bit smaller.
>
> Cc: Hans-Christian Egtvedt
> Cc: Richard Purdie
> Signed-off-by: Jingoo Han
Acked-by: Hans-Christian Egtvedt
--
Hans-Christian Egtvedt
--
To
On Tue, Jul 31, 2012 at 07:04:39PM -0400, Cyril Chemparathy wrote:
> This patch fixes up the types used when converting back and forth between
> physical and virtual addresses.
>
> Signed-off-by: Vitaly Andrianov
> Signed-off-by: Cyril Chemparathy
> ---
> arch/arm/include/asm/memory.h | 17
On Tue, Jul 31, 2012 at 07:04:37PM -0400, Cyril Chemparathy wrote:
> +static void __init init_patch_kernel(void)
> +{
> + const void *start = &__patch_table_begin;
> + const void *end = &__patch_table_end;
> +
> + BUG_ON(patch_kernel(start, end - start));
> +
On 8/6/2012 5:58 PM, Johannes Stezenbach wrote:
> On Mon, Aug 06, 2012 at 08:35:51AM +0200, Linus Walleij wrote:
>> On Mon, Aug 6, 2012 at 4:18 AM, Stephen Warren wrote:
>>
>>> I can't comment on the sysfs-vs-dev interface location, but I don't
>>> think it addresses Johannes' issue; finding out
On Monday, August 06, 2012, Alan Stern wrote:
> On Sun, 5 Aug 2012, Rafael J. Wysocki wrote:
>
> > > v2
> > > use ktime_to_ns() instead of comparisons on .tv64 field
>
> What is the reason for this? It apparently adds complexity and code
> (on non-64-bit systems) to no purpose.
I don't think
On Monday, August 06, 2012, Huang Ying wrote:
> This patch fixes the following bug:
>
> http://marc.info/?l=linux-pci=134338059022620=2
>
> Where lspci does not work properly if a device and the corresponding
> parent bridge (such as PCIe port) is suspended. This is because the
> device
From: Qiang Liu
The use of spin_lock_irqsave() is a stronger locking mechanism than is
required throughout the driver. The minimum locking required should be
used instead. Interrupts will be turned off and context will be saved,
there is needless to use irqsave.
Change all instances of
Hi all,
Please ignore this one. Thanks.
> -Original Message-
> From: Liu Qiang-B32616
> Sent: Monday, August 06, 2012 6:15 PM
> To: linux-cry...@vger.kernel.org; linuxppc-...@lists.ozlabs.org;
> dan.j.willi...@intel.com; linux-kernel@vger.kernel.org;
> dan.j.willi...@gmail.com;
From: Qiang Liu
These drivers set the DMA_INTERRUPT capability bit when requesting a DMA
controller channel. This was historical, and is no longer needed.
Recent changes to the drivers/dma/fsldma.c driver have removed support
for this flag. This makes the carma drivers unable to find a DMA
From: Qiang Liu
These functions will be modified in the next patch in the series. By
moving the function in a patch separate from the changes, it will make
review easier.
Cc: Dan Williams
Cc: Dan Williams
Cc: Vinod Koul
Cc: Li Yang
Signed-off-by: Ira W. Snyder
Signed-off-by: Qiang Liu
---
From: Qiang Liu
Fix a warning of unitialized value when compile with -Wuninitialized.
Cc: Dan Williams
Cc: Dan Williams
Cc: Vinod Koul
Cc: Li Yang
Signed-off-by: Qiang Liu
Reported-by: Kim Phillips
Acked-by: Ira W. Snyder
---
drivers/dma/fsldma.c |2 +-
1 files changed, 1
On Wed, 1 Aug 2012, Konrad Rzeszutek Wilk wrote:
> > > > +struct pvclock_wall_clock {
> > > > + u32 version;
> > > > + u32 sec;
> > > > + u32 nsec;
> > > > +} __attribute__((__packed__));
> > >
> > > That is weird. It is 4+4+4 = 12 bytes? Don't you want it to be 16 bytes?
On Sun, Aug 05, 2012 at 21:48:42, Daniel Mack wrote:
> Ping, anyone?
>
> On 30.07.2012 09:36, Daniel Mack wrote:
> > This patch adds logic to parse lis3 properties from a device tree node
> > and store them in a freshly allocated lis3lv02d_platform_data.
> >
> > Note that the actual match tables
On Sat, Aug 04, 2012 at 12:08:46PM -0600, Alex Williamson wrote:
> Joerg, I notice that ACS isn't getting enabled on my AMD system on
> 3.6-rc1. I'll investigate more, but mention it in case you get to
> it first.
Hmm, tried it here, At least pci_request_acs() still gets called. How do
you
It's understood that the AB8500 should be subordinate to the DB8500;
however, the AB8500 uses the GIC as it's interrupt controller. If
we do not specify which IRQ controller to use the default is to use
the next encountered IRQ controller as we climb the tree. This would
be the DB8500. This patch
Without this patch the default behaviour is to climb the Device
Tree and use the first encountered interrupt controller. This
does not take into account if a device node has specified to use
a particular IRQ controller using the interrupt-parent property.
This patch ensures that property is
501 - 600 of 1480 matches
Mail list logo
