Tegra114 introduces new PLL types. This requires new clocktypes as well
as some new fields in the pll structure.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c | 839 +++
drivers/clk/tegra/clk.h | 50 +++-
2 files changed, 888
This looks awesome for 3.10, but getting a minimal fix for 3.9/stable would be
good, too.
Jan Beulich wrote:
>eboot.o and efi_stub_$(BITS).o didn't get added to "targets", and hence
>their .cmd files don't get included by the build machinery, leading to
>the files always getting rebuilt.
>
The PMC code already accesses to PMC registers so it makes sense to
move this function there as well. While at it, rename the function to
tegra_pmc_pcie_xclk_clamp() for consistency.
Signed-off-by: Thierry Reding
Acked-by: Stephen Warren
---
arch/arm/mach-tegra/pcie.c | 30
PLLC2 and PLLC3 on Tegra114 have separate phaselock and frequencylock bits.
So switch to a lock mask to be able to test both at the same time.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c |6 +++---
drivers/clk/tegra/clk-tegra20.c | 20 ++--
The new struct msi_chip is used to associated an MSI controller with a
PCI bus. It is automatically handed down from the root to its children
during bus enumeration.
This patch provides default (weak) implementations for the architecture-
specific MSI functions (arch_setup_msi_irq(),
In preparation for moving the PCIe driver into the drivers/pci/host
directory, this header, which contains prototypes that are required by
the PCIe driver, needs to be moved to a globally visible location.
Signed-off-by: Thierry Reding
---
Changes in v2:
- keep tegra_pmc_init() prototype in
Some PLLs in Tegra114 don't use a power of 2 mapping for the post divider.
Introduce a table based approach and switch PLLU to it.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c | 38 --
drivers/clk/tegra/clk-tegra20.c |7 +++
Tegra114 PLLC2 and PLLC3 don't have a lock enable bit. The lock bits are
always functional.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c |5 +
drivers/clk/tegra/clk.h |2 ++
2 files changed, 7 insertions(+), 0 deletions(-)
diff --git
On Wed, 3 Apr 2013, Nicolas Pitre wrote:
> On Wed, 3 Apr 2013, Stefano Stabellini wrote:
>
> > On Tue, 2 Apr 2013, Nicolas Pitre wrote:
> > > On Tue, 2 Apr 2013, Stefano Stabellini wrote:
> > >
> > > > @@ -176,27 +178,30 @@ static int __init xen_secondary_init(unsigned int
> > > > cpu)
> > > >
On Wed, Apr 03, 2013 at 09:38:55AM +0900, Jonghwan Choi wrote:
> 3.8-stable review patch. If anyone has any objections, please let me know.
I believe this is applicable to all the other stable kernels.
Cheers,
--
Luis
>
> --
>
> From: "Richard Guy Briggs "
>
> commit
eboot.o and efi_stub_$(BITS).o didn't get added to "targets", and hence
their .cmd files don't get included by the build machinery, leading to
the files always getting rebuilt.
Rather than adding the two files individually, take the opportunity and
add $(VMLINUX_OBJS) to "targets" instead, thus
check_hw_exists has a number of checks which go to two exit paths:
msr_fail and bios_fail. Checks classified as msr_fail will cause
check_hw_exists() to return false, causing the PMU not to be used;
bios_fail checks will only cause a warning to be printed, but will
return true.
The problem is
With the device tree support in place, probe the PCIe controller from
the device tree and remove the corresponding workaround in the board
file.
Signed-off-by: Thierry Reding
---
Changes in v2:
- add missing dummy regulator nodes by Stephen Warren
- rename port 0 DT node and disable unused port
This function can be used to parse a bus-range property as specified by
device nodes representing PCI bridges.
Signed-off-by: Thierry Reding
---
drivers/of/of_pci.c| 25 +
include/linux/of_pci.h | 1 +
2 files changed, 26 insertions(+)
diff --git
On Wed, Apr 03, 2013 at 08:00:37PM +0800, Zhenzhong Duan wrote:
>
> On 2013-04-01 20:41, Konrad Rzeszutek Wilk wrote:
> >On Mon, Apr 01, 2013 at 01:26:34PM +0800, Zhenzhong Duan wrote:
> >>On 2013-03-29 21:46, Konrad Rzeszutek Wilk wrote:
> >>>On Fri, Mar 29, 2013 at 03:22:38PM +0800, Zhenzhong
Not all PLLs in Tegra114 have a bypass bit. Adapt the common code to only use
this bit when available.
Signed-off-by: Peter De Schrijver
---
drivers/clk/tegra/clk-pll.c | 12
drivers/clk/tegra/clk.h |2 ++
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git
Enable the first PCIe root port which is connected to an FPGA on the
Tamonten Evaluation Carrier and add device nodes for each of the PCI
endpoints available in the standard configuration.
Signed-off-by: Thierry Reding
---
Changes in v2:
- remove duplicate nodes and properties defined in
This function can be used to parse the device and function number from a
standard 5-cell PCI resource. PCI_SLOT() and PCI_FUNC() can be used on
the returned value obtain the device and function numbers respectively.
Signed-off-by: Thierry Reding
---
Changes in v2:
- rename devfn and err
From: Andrew Murray
This patch factors out common implementation patterns to reduce overall kernel
code and provide a means for host bridge drivers to directly obtain struct
resources from the DT's ranges property without relying on architecture specific
DT handling. This will make it easier to
Hi -
On Wed, Apr 03, 2013 at 02:49:53PM +0200, Frederic Weisbecker wrote:
> Sounds good, would you like to propose a version? We are also
> interested in a timer tick event tracepoint for dynticks debugging.
How about this?
Author: Frank Ch. Eigler
Date: Wed Apr 3 10:35:21 2013 -0400
tegra_boot_secondary() relies on some of the car ops. This means having an
uninitialized tegra_cpu_car_ops will lead to an early boot panic.
Providing a dummy struct avoids this and makes adding Tegra114 clock support
in a bisectable way a lot easier.
Signed-off-by: Peter De Schrijver
---
This is the nineth version of the Tegra114 clockframework. It is based on the
next-20130320-fixed branch of
git://nv-tegra.nvidia.com/user/swarren/linux-2.6.git,
http://patchwork.ozlabs.org/patch/229972/ and
http://patchwork.ozlabs.org/patch/229978/ and
http://patchwork.ozlabs.org/patch/233415/
On Wed 03-04-13 15:20:19, Mel Gorman wrote:
> On Tue, Apr 02, 2013 at 10:01:43AM -0700, Darrick J. Wong wrote:
> > Hi,
> >
> > A couple of weeks have gone by without further comments about this patch.
> >
> > Are you interested in the minor cleanups and added comments, or is the v2
> > patch
>
On Wed, Apr 3, 2013 at 7:48 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 07:40:44PM +0530, Vivek Gautam wrote:
>> >> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
>> >> > >> >> +{
>> >> > >> >> + if (!x || !x->dev) {
>> >> > >> >> +
On Wed, Apr 03, 2013 at 10:34:06AM -0400, Eric Whitney wrote:
>
> The TI OMAP4 processor on my Pandaboard test system is little endian.
Ah... so basically, we need to find a test platform which allows us to
boot arbitrary kernels and allows us to have root access (which means
it's unlikely we'll
* Theodore Ts'o :
> On Wed, Apr 03, 2013 at 06:22:04PM +0800, Zheng Liu wrote:
> > Subject: [PATCH] ext4: fix a big-endian bug when an extent is zeroed out
> >
> > From: Zheng Liu
> >
> > When an extent was zeroed out, we forgot to do convert from cpu to le16.
> > It could make us hit a BUG_ON
>>> On 03.04.13 at 15:56, William Dauchy wrote:
> On Wed, Apr 3, 2013 at 3:42 PM, Jan Beulich wrote:
>> ChangeLog-3.8.3 for example has
>
> oh sorry, you are right. I wasn't looking is the 3.8.x branch.
> The thing is, the revert seems present only in 3.8.x branch. For
> example in 3.4.x the
Hi,
On Wednesday 03 April 2013 07:57 PM, Felipe Balbi wrote:
hi,
On Wed, Apr 03, 2013 at 07:48:42PM +0530, Kishon Vijay Abraham I wrote:
+struct phy *of_phy_xlate(struct phy *phy, struct of_phandle_args *args)
+{
+ return phy;
+}
+EXPORT_SYMBOL_GPL(of_phy_xlate);
so you get a PHY and
On 1.4.2013 11:28, Chris Clayton wrote:
> Ping!
>
> This is still happening with 3.9-rc5.
>
> [chris:~/kernel/linux]$ make bzImage
> ...
> Kernel: arch/x86/boot/bzImage is ready (#14)
> [chris:~/kernel/linux]$ make kernelrelease
> scripts/kconfig/conf --silentoldconfig Kconfig
> 3.9.0-rc5
>
hi,
On Wed, Apr 03, 2013 at 07:48:42PM +0530, Kishon Vijay Abraham I wrote:
> >>+struct phy *of_phy_xlate(struct phy *phy, struct of_phandle_args *args)
> >>+{
> >>+ return phy;
> >>+}
> >>+EXPORT_SYMBOL_GPL(of_phy_xlate);
> >
> >so you get a PHY and just return it ? What gives ?? (maybe I
This patch adds a new debugfs entry 'device_status' in
/sys/kernel/debug/rssd. The value of this entry shows
devices online and those in the process of removing.
Signed-off-by: Sam Bradshaw
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c | 148
Fix to return 0 from pci probe in case of rebuild. If not, pci consider
probe has failed, and crash during rmmod.
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/block/mtip32xx/mtip32xx.c
The commit "early_printk: consolidate random copies of identical code"
introduces a build failure for the lboxre2_defconfig because arch/sh
unconditionally assumes that there will be an early_console struct
present that it can populate with bios routines to drive the
early printk support.
Making
To recover from command timeouts, reset the device. In addition
to that improved timeout handling of PIO commands.
Signed-off-by: Sam Bradshaw
Signed-off-by: Asai Thambi S P
---
drivers/block/mtip32xx/mtip32xx.c | 177 ++---
1 files changed, 87 insertions(+),
On Wed, Apr 3, 2013 at 4:14 PM, David Ahern wrote:
> On 4/3/13 8:00 AM, Stephane Eranian wrote:
>>>
>>> What's the advantage of changing apps -- like the JIT compiler -- to emit
>>> perf based timestamps versus having perf emit existing timestamps? ie.,
>>> monotonic and realtime clocks already
Hi Jens,
This patchset includes the following. It was generated against your
for-3.9/drivers
* improved recovery for command timeout
* fix for a crash during rmmod
* add new debugfs entry 'device_status'
Asai Thambi S P (3):
mtip32xx: recovery from command timeout
mtip32xx: return 0 from
On Wed, Apr 03, 2013 at 05:06:22PM +0300, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote:
> > While testing your 'next' branch merged with today's next I got some new
> > warnings, caused by a recently introduced __must_check in:
> >
> > c8801a8
On Tue, Apr 02, 2013 at 10:01:43AM -0700, Darrick J. Wong wrote:
> Hi,
>
> A couple of weeks have gone by without further comments about this patch.
>
> Are you interested in the minor cleanups and added comments, or is the v2
> patch
> in -next good enough?
>
> Apparently Mel Gorman's
On Mon, Mar 25, 2013 at 12:15:47PM +0100, Prashant Gaikwad wrote:
> On Friday 22 March 2013 06:09 PM, Peter De Schrijver wrote:
> > The device tree binding models Tegra114 CAR (Clock And Reset) as a single
> > monolithic clock provider.
> >
> > Signed-off-by: Peter De Schrijver
> > ---
>
>
>
>
Hi,
On Wednesday 03 April 2013 07:12 PM, Felipe Balbi wrote:
On Wed, Apr 03, 2013 at 06:23:49PM +0530, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
PHY with or without
Hi,
On Wed, Apr 03, 2013 at 07:40:44PM +0530, Vivek Gautam wrote:
> >> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
> >> > >> >> +{
> >> > >> >> + if (!x || !x->dev) {
> >> > >> >> + dev_err(x->dev, "no PHY or attached device
> >> > >> >>
On 4/3/13 8:00 AM, Stephane Eranian wrote:
What's the advantage of changing apps -- like the JIT compiler -- to emit
perf based timestamps versus having perf emit existing timestamps? ie.,
monotonic and realtime clocks already have vdso mappings for userspace with
well known performance
spinlocks built in a !PREEMPT_COUNT config don't have the compiler
barrier provided by preempt_* routines. This can break lot of code which
relies on barrier semantics.
This manifested as random crashes in timer code when stress testing
ARC Linux (3.9-rc3): !SMP && !PREEMPT_COUNT
Here's the
Hi Felipe,
On Wed, Apr 03, 2013 at 05:06:22PM +0300, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote:
> > While testing your 'next' branch merged with today's next I got some new
> > warnings, caused by a recently introduced __must_check in:
> >
> >
Hi,
On Wed, Apr 3, 2013 at 7:26 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 04:54:14PM +0300, Felipe Balbi wrote:
>> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
>> > >> >> +{
>> > >> >> + if (!x || !x->dev) {
>> > >> >> +
On Thu, Mar 28, 2013 at 6:48 PM, Stephen Warren wrote:
> Why can't we just use the device suspend/resume functions rather than
> global (syscore) suspend/resume functions? Presumably this is to ensure
> that all other drivers suspend first, then the pinctrl driver does, and
> the reverse for
Hi,
On Wed, Apr 03, 2013 at 04:02:24PM +0200, Fabio Baltieri wrote:
> While testing your 'next' branch merged with today's next I got some new
> warnings, caused by a recently introduced __must_check in:
>
> c8801a8 regulator: core: Mark all get and enable calls as __must_check
>
> These
Increase the buffer length from 10 to 300 packets. Consider that traffic on
mac802154 devices will often be 6LoWPAN, and a full-length (1280 octet)
IPv6 packet will fragment into 15 6LoWPAN fragments (because the MTU of
IEEE 802.15.4 is 127). A 300-packet queue is really 20 full-length IPv6
Since regulator_enable() is going to be marked as __must_check in the
next merge window, always check regulator_enable() return value and
print a warning if it fails.
Cc: Hema HK
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-twl6030-usb.c | 11 +--
1 file changed, 9
Since regulator_enable() is going to be marked as __must_check in the
next merge window, always check regulator_enable() return value and
print a warning if it fails.
Cc: Kalle Jokiniemi
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-twl4030-usb.c | 18 +++---
1 file
Since regulator_enable() is going to be marked as __must_check in the
next merge window, always check regulator_enable() return value and
print a warning if it fails.
Cc: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/phy/phy-ab8500-usb.c | 12 +---
1 file changed, 9
On Tue 02-04-13 21:43:44, Robin Holt wrote:
[...]
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index ca9a7c6..7683f6a 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -1185,7 +1185,7 @@ int __weak alloc_bootmem_huge_page(struct hstate *h)
> while (nr_nodes) {
> void *addr;
Hello Felipe,
While testing your 'next' branch merged with today's next I got some new
warnings, caused by a recently introduced __must_check in:
c8801a8 regulator: core: Mark all get and enable calls as __must_check
These patches introduces a check for regulator_enable() return value in
all
Version 2 of this patch series:
Differences from v1:
1. Patches previously numbered 5 and 6 were squashed (to become current
patch #4) at the request of Alexander Smirnov.
2. Current patch #2 had extraneous braces removed.
3. Current patch #1 was changed. It is now a patch to make mac802154
On Tue, Mar 12, 2013 at 11:10 PM, Greg Kroah-Hartman
wrote:
>> > >> IOW I don't see why this got proposed for stable at all.
>> > >
>> > > So, you suggest to just drop this patch for v3.8.3, don't you?
>> >
>> > I do, yes. But I'd suggest to get Konrad to agree.
>>
>> Yes. Lets drop it.
>
> Now
When ops->xmit() fails, drop the packet. Devices which support hardware
ack and retry (which include all devices currently supported by mainline),
will automatically retry sending the packet (in the hardware) up to 3
times, per the 802.15.4 spec. There is no need, and it is incorrect to
try to do
dev_queue_xmit() will return a positive value if the packet could not be
queued, often because the real network device (in our case the mac802154
wpan device) has its queue stopped. lowpan_xmit() should handle the
positive return code (for the debug statement) and return that value to
the higher
Use netif_stop_queue() and netif_wake_queue() to control the flow of
packets to mac802154 devices. Since many IEEE 802.15.4 devices have no
output buffer, and since the mac802154 xmit() function is designed to
block, netif_stop_queue() is called after each packet.
Signed-off-by: Alan Ott
---
On Wed, 2013-04-03 at 13:41 +0200, Sven Joachim wrote:
> On 2013-04-03 00:11 +0200, Greg Kroah-Hartman wrote:
>
> > 3.8-stable review patch. If anyone has any objections, please let me know.
>
> I'm seeing several complaints from udevd at boot in both 3.8.6-rc1 and
> 3.9-rc5: "udevd[56]: sender
On Tue 02-04-13 21:43:44, Robin Holt wrote:
[...]
> diff --git a/mm/bootmem.c b/mm/bootmem.c
> index 2b0bcb0..b2e4027 100644
> --- a/mm/bootmem.c
> +++ b/mm/bootmem.c
> @@ -705,12 +705,16 @@ void * __init __alloc_bootmem(unsigned long size,
> unsigned long align,
>
> void * __init
On Wed, 3 Apr 2013, Stefano Stabellini wrote:
> On Tue, 2 Apr 2013, Nicolas Pitre wrote:
> > On Tue, 2 Apr 2013, Stefano Stabellini wrote:
> >
> > > @@ -176,27 +178,30 @@ static int __init xen_secondary_init(unsigned int
> > > cpu)
> > > return 0;
> > > }
> > >
> > > +static void __init
On Wed, Apr 3, 2013 at 3:55 PM, David Ahern wrote:
> On 4/3/13 3:17 AM, Stephane Eranian wrote:
>>
>> I haven't done any specific testing with either approach yet. The goal is
>> to
>> use this perf timestamp to correlate user level events to hardware
>> events recorded
>> by the kernel. I would
On Tue, 2 Apr 2013, Hugh Dickins wrote:
> I am strongly in favour of removing that limitation from
> __isolate_lru_page() (and the thread you pointed - thank you - shows Mel
> and Christoph were both in favour too); and note that there is no such
> restriction in the confusingly similar but
From: Lars Poeschel
This adds a simple sysfs interface to the pwm subsystem. It is
heavily inspired by the gpio sysfs interface.
/sys/class/pwm
/export ... asks the kernel to export a PWM to userspace
/unexport ... to return a PWM to the kernel
Hi,
On Wed, Apr 03, 2013 at 04:54:14PM +0300, Felipe Balbi wrote:
> > >> >> +static inline void usb_phy_autopm_enable(struct usb_phy *x)
> > >> >> +{
> > >> >> + if (!x || !x->dev) {
> > >> >> + dev_err(x->dev, "no PHY or attached device
> > >> >> available\n");
> > >> >> +
On Wed, Apr 3, 2013 at 3:42 PM, Jan Beulich wrote:
> ChangeLog-3.8.3 for example has
oh sorry, you are right. I wasn't looking is the 3.8.x branch.
The thing is, the revert seems present only in 3.8.x branch. For
example in 3.4.x the last patch is still 01c681d
Should we consider this normal or
On 4/3/13 3:17 AM, Stephane Eranian wrote:
I haven't done any specific testing with either approach yet. The goal is to
use this perf timestamp to correlate user level events to hardware
events recorded
by the kernel. I would assume there would be situations where those user events
could be on
HI,
On Wed, Apr 03, 2013 at 06:42:48PM +0530, Vivek Gautam wrote:
> >> >> Adding APIs to handle runtime power management on PHY
> >> >> devices. PHY consumers may need to wake-up/suspend PHYs
> >> >> when they work across autosuspend.
> >> >>
> >> >> Signed-off-by: Vivek Gautam
> >> >> ---
> >>
On Wed, Apr 03, 2013 at 06:23:50PM +0530, Kishon Vijay Abraham I wrote:
> Used the generic PHY framework API to create the PHY. omap_usb2_suspend
> is split into omap_usb_suspend and omap_usb_resume in order to align
> with the new framework.
>
> However using the old USB PHY library cannot be
On Wed, 2013-04-03 at 14:11 +0100, Matt Fleming wrote:
> This looks like something that will differ between implementations, and the
> fact that it's appearing in our code is a sure sign that this isn't the way to
> go.
Our choices right now are:
1) Break machines that don't garbage collect on
On Wed, Apr 03, 2013 at 12:37:47PM +0200, Nicolas Ferre wrote:
> On 04/03/2013 11:51 AM, Johan Hovold :
> > On Tue, Apr 02, 2013 at 06:36:06PM +0200, Nicolas Ferre wrote:
[...]
> >> I now use a different compatibility string to figure out what is the IP
> >> revision that has the "boggus IMR"
On Wed, Apr 03, 2013 at 06:23:49PM +0530, Kishon Vijay Abraham I wrote:
> The PHY framework provides a set of APIs for the PHY drivers to
> create/destroy a PHY and APIs for the PHY users to obtain a reference to the
> PHY with or without using phandle. To obtain a reference to the PHY without
>
On Wed, 2013-04-03 at 14:09 +0100, Matt Fleming wrote:
> We're fixing a regression in efivars.c, but only for those users that
> boot via the EFI boot stub? That seems likely to upset some people.
Not really - it just makes the estimates more accurate. Applying (2)
without (1) should still fix
>>> On 03.04.13 at 15:25, William Dauchy wrote:
> On Wed, Apr 3, 2013 at 3:01 PM, Jan Beulich wrote:
>> Iirc we requested the earlier commit to be removed from stable
>> trees, and I think Greg also did so.
>
> I'm sorry but I'm unable to find a revert of 01c681d in stable tree.
On Wed, Apr 3, 2013 at 8:24 AM, Tony Prisk wrote:
> v5 changes:
> Changed as requested by Rob Herring:
> Added of_find_property_value_of_size() to drivers/of/base.c to remove some
> code that was being duplicated.
>
> Changed as requested by Stephen Warren:
> Redid the kfree(maps) code as
On my smp platform which is made of 5 cores in 2 clusters, I have the
nr_busy_cpu field of sched_group_power struct that is not null when the
platform is fully idle. The root cause is:
During the boot sequence, some CPUs reach the idle loop and set their
NOHZ_IDLE flag while waiting for others
When using a large number of threads performing AIO operations the
IOCTX list may get a significant number of entries which will cause
significant overhead. For example, when running this fio script:
rw=randrw; size=256k ;directory=/mnt/fio; ioengine=libaio; iodepth=1
blocksize=1024; numjobs=512;
Hi Christian,
On 04/03/2013 06:40 PM, Christian Ruppert wrote:
> This patch adds implicit memory barriers to irqsave/restore functions of
> the ARC architecture port in line with what is done in other architectures.
>
> It seems to fix several seemingly unrelated issues in our platform but for
>
On Fri, Mar 29, 2013 at 2:11 PM, Alexandre Courbot wrote:
> Since I have received no death threat from architecture maintainers I'd like
> to
> proceed with the remainder of this work so that it doesn't go half-baked into
> 3.10. These three patches finish the removal of the GENERIC_GPIO config
Hello Jan,
On Wed, Apr 3, 2013 at 3:01 PM, Jan Beulich wrote:
> Iirc we requested the earlier commit to be removed from stable
> trees, and I think Greg also did so.
I'm sorry but I'm unable to find a revert of 01c681d in stable tree.
Regards,
--
William
--
To unsubscribe from this list: send
On 03/23/2013 09:36 AM, Konrad Rzeszutek Wilk wrote:
From: Boris Ostrovsky
Invoking arch_flush_lazy_mmu_mode() results in calls to
preempt_enable()/disable() which may have performance impact.
Since lazy MMU is not used on bare metal we can patch away
arch_flush_lazy_mmu_mode() so that it is
On Thu, Mar 28, 2013 at 09:46:45PM +0100, Maxime Ripard wrote:
> Now that the arm core code calls irqchip_init, we can remove it from all
> the machines that were using it.
>
> Signed-off-by: Maxime Ripard
> Acked-by: Simon Horman
Acked-by: Jamie Iles
Thanks Maxime!
--
To unsubscribe from
On Tue, Apr 02, 2013 at 01:36:02PM -0700, Yinghai Lu wrote:
[..]
> > You are just describing what your code does. There is no theme or
> > justification behind this behavior. There is no uniformity. A user can
> > question that so far you used to honor last crashkernel= parameter and
> > suddenly
Add non-zero module sections to sysfs on architectures unequal to PARISC.
KGDB needs all module sections for proper module debugging. Therefore, commit
35dead4235e2b67da7275b4122fed37099c2f462 is revoked except for PARISC
architecture.
Signed-off-by: Sebastian Wankerl
Signed-off-by: Philip
Hi Felipe,
On Wed, Apr 3, 2013 at 1:45 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Apr 03, 2013 at 11:48:39AM +0530, Vivek Gautam wrote:
>> >> Adding APIs to handle runtime power management on PHY
>> >> devices. PHY consumers may need to wake-up/suspend PHYs
>> >> when they work across
This patch adds implicit memory barriers to irqsave/restore functions of
the ARC architecture port in line with what is done in other architectures.
It seems to fix several seemingly unrelated issues in our platform but for
the moment it is insufficiently tested (and might even be incomplete).
On 01/04/13 16:14, Matthew Garrett wrote:
> @@ -452,8 +462,33 @@ check_var_size_locked(struct efivars *efivars, u32
> attributes,
> if (status != EFI_SUCCESS)
> return status;
>
> - if (!storage_size || size > remaining_size || size > max_size ||
> -
On 01/04/13 16:13, Matthew Garrett wrote:
> EFI variables can be flagged as being accessible only within boot services.
> This makes it awkward for us to figure out how much space they use at
> runtime. In theory we could figure this out by simply comparing the results
> from QueryVariableInfo()
From: Wei Yongjun
Fix to return a negative error code from the error handling
case instead of 0, as returned elsewhere in this function.
Signed-off-by: Wei Yongjun
---
drivers/spi/spi-mxs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/spi-mxs.c b/drivers/spi/spi-mxs.c
index
Hello Vineet,
In the following a patch for a seemingly unrelated problem (RB-trees in
hrtimer implementation) which seems to fix the original problem at the
same time. For the moment, this patch is insufficiently tested but I am
posting it here (preliminarily) since it seems to be in line with
On 04/03/2013 01:12 PM, Li Zefan wrote:
> Use css_get()/css_put() instead of mem_cgroup_get()/mem_cgroup_put().
>
> Signed-off-by: Li Zefan
> ---
> mm/memcontrol.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index
On 2013年04月03日 19:39, Christopher Covington wrote:
> Maybe somebody else does have a fix, but Catalin mentioned he was going on
> vacation for two weeks on March 28th in "[GIT PULL] Preparatory GIC patches
> for arm64 support".
>
ok, I can wait.
>> > if really no one fix it within this week,
>>> On 03.04.13 at 14:56, William Dauchy wrote:
> On Thu, Feb 28, 2013 at 3:34 AM, Chen Gang wrote:
>> additional information:
>> before commit 01c681d4c70d64cb72142a2823f27c4146a02e63, the value printed
>> here was bogus, as it was the guest provided value from req->u.rw.handle
>> rather
On 04/03/2013 01:11 PM, Li Zefan wrote:
> Use css_get/css_put instead of mem_cgroup_get/put.
>
> Note, if at the same time someone is moving @current to a different
> cgroup and removing the old cgroup, css_tryget() may return false,
> and sock->sk_cgrp won't be initialized.
>
> Signed-off-by:
Used the generic PHY framework API to create the PHY. omap_usb2_suspend
is split into omap_usb_suspend and omap_usb_resume in order to align
with the new framework.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new
Hello,
On Thu, Feb 28, 2013 at 3:34 AM, Chen Gang wrote:
> additional information:
> before commit 01c681d4c70d64cb72142a2823f27c4146a02e63, the value printed
> here was bogus, as it was the guest provided value from req->u.rw.handle
> rather than the actual device.
>
> Signed-off-by: Chen
Use the generic PHY framework API to get the PHY. The usb_phy_set_suspend
and usb_phy_set_resume is replaced with phy_suspend and phy_resume to
align with the new PHY framework.
musb->xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
Used the generic PHY framework API to create the PHY. twl4030_usb_suspend
and twl4030_usb_resume is added to phy_ops in order to align
with the new framework.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined with PHY and moving to the new
framework
In order for controllers to get PHY in case of non dt boot, the phy
binding information should be added in the platform specific
initialization code using phy_bind.
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/mach-omap2/usb-musb.c |7 ++-
1 file changed, 6 insertions(+), 1
Added a generic PHY framework that provides a set of APIs for the PHY drivers
to create/destroy a PHY and APIs for the PHY users to obtain a reference to
the PHY with or without using phandle. To obtain a reference to the PHY
without using phandle, the platform specfic intialization code (say from
401 - 500 of 1516 matches
Mail list logo
