Hi Steve,
I retried the test program (with the kernel patch). It does block from
time to time. I spotted the ee.events is not set to EPOLLIN before
calling epll_ctl(eft, EPOLL_CTL_ADD,...). I fixed it and ran
the test in a bash-loop.
I have the kafai-2 version attached (with some more logging
Hi Linus,
exynos, i915 and msm fixes and one core fix.
exynos: hdmi power off and mixer issues,
msm: iommu, build fixes,
i915: regression races and warns!
Dave.
The following changes since commit a497c3ba1d97fc69c1e78e7b96435ba8c2cb42ee:
Linux 3.16-rc2 (2014-06-21 19:02:54 -1000)
are avail
Hi Rickard
On 06/26/2014 03:44 PM, Rickard Strandqvist wrote:
Remove variable that are never used
This was found using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
drivers/pinctrl/pinctrl-st.c |6 ++
1 file changed, 2 insertions(+), 4 delet
Hi Jeroen,
On Tue, 24 Jun 2014 21:36:06 +0200
Jeroen Hofstee wrote:
> >> KBuild (ab)uses the asm statement to write to a file and
> >> llvm integrated as chokes about these invalid asm statements.
> >> Workaround it by making it look like valid asm code.
> >>
> >> Signed-off-by: Jeroen Hofstee
On 2014/6/25 23:00, Tejun Heo wrote:
> Hey,
>
> On Wed, Jun 25, 2014 at 09:56:31AM +0800, Li Zefan wrote:
>>> Hmmm? Why does that matter? The only region in cgroup_mount() which
>>> needs to be put inside such mutex would be root lookup, no?
>>
>> unfortunately that won't help. I think what you
On Wed, 25 Jun, at 02:24:27PM, Yinghai Lu wrote:
> We could load it high if it is more than 2G when kernel support
> LOAD_ABOVE_4G.
>
> -v2: Use macro instead of (1<<1) directly for LOAD_ABOVE_4G.
>
> Signed-off-by: Yinghai Lu
>
> ---
> loaders/bzimage/bzimage.c |9 -
> loaders/bzi
Hi, sir,
We saw your information from internet, wondering if we have chance to cooperate
with Marine propeller products?
We accept OEM and ODM with competitive price ,if you like ,i can send you the
catalogue to refer.ok?
May be you are already have your own supplier ,it’s ok ,just give a chance
On Wed, Jun 25, 2014 at 01:03:31PM +0100, Lee Jones wrote:
> On Wed, 25 Jun 2014, Thierry Reding wrote:
> > On Wed, Jun 25, 2014 at 10:54:47AM +0100, Lee Jones wrote:
> > > > Make use of the new devm_gpiod_get_optional() to simplify the probe
> > > > code.
> > > >
> > > > Signed-off-by: Alexandre
As Murata Manufactures the NTC based thermistors. The vendor
name in the compatibility is preposed to change to "murata"
This patch uses the new compatibility string in exynos4412 based
Trats2 board.
Signed-off-by: Naveen Krishna Chatradhi
Cc: Chanwoo Choi
Reviewed-by: Chanwoo Choi
---
Changes
This patch creates a thermistor fragment carrying the NTC Thermistor
nodes as children of the IIO based ADC.
This fragment is included in exynos5420-peach-pit.dts and
exynos5800-peach-pi.dts.
Signed-off-by: Naveen Krishna Chatradhi
---
Changes since v1:
As per the comments https://lkml.org/lkml/
This patchset does the following
1. Create a thermistor dtsi fragment file cros-adc-thermistors.dtsi for
exynos5420-peach-pit.dts and exynos5800-peach-pi.dts
2. Adds the ADC based Thermistor nodes and enables them in peach_pit.dts
and peach_pi.dts
3. Corrects the vendor prefix for thermistors
Patch 'spi: omap-uwire: use devm_ functions' (b3f6a57506b8) introduced a
build error due to a missing include file. Add it.
Cc: Himangi Saraogi
Cc: Julia Lawall
Signed-off-by: Olof Johansson
---
drivers/spi/spi-omap-uwire.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/sp
Palmas class of devices can provide 32K clock(s) to be used by other devices
on the board. Depending on the actual device the provided clocks can be:
CLK32K_KG and CLK32K_KGAUDIO
or only one:
CLK32K_KG (TPS659039 for example)
Use separate compatible flags for the two 32K clock.
A system which need
On Thu, Jun 26, 2014 at 01:41:41PM -0400, Steven Rostedt wrote:
>
> I know you wrote this patch, but you may want to test it out with
> the ftrace: Remove check for HAVE_FUNCTION_TRACE_MCOUNT_TEST patch
> applied too.
In order to compile this, I'd have to apply all common code patches, I think.
B
Hi Mike,
This is a resend of the v2 version of the palmas clock driver which seamingly
missed the 3.16 merge window. I have added Nishanth's Reviewed-by tag to the
patches.
Changes since v1:
- binding documentation and driver has been separated based on Nishanth Menon's
comment
v2 of the serie
On Thu, 26 Jun 2014, Sasha Levin wrote:
> On 06/25/2014 06:36 PM, Hugh Dickins wrote:
> > Sasha, may I trespass on your time, and ask you to revert the previous
> > patch from your tree, and give this patch below a try? I am very
> > interested to learn if in fact it fixes it for you (as it did fo
Palmas class of devices can provide 32K clock(s) to be used by other devices
on the board. Depending on the actual device the provided clocks can be:
CLK32K_KG and CLK32K_KGAUDIO
or only one:
CLK32K_KG (TPS659039 for example)
Use separate compatible flags for the two 32K clock.
A system which need
On Wed, Jun 25, 2014 at 05:45:45PM +0400, Vladimir Davydov wrote:
> On Tue, Jun 24, 2014 at 04:38:41PM +0900, Joonsoo Kim wrote:
> > On Fri, Jun 13, 2014 at 12:38:22AM +0400, Vladimir Davydov wrote:
> > And, you said that this way of implementation would be slow because
> > there could be many obje
On Wed, Jun 25, 2014 at 12:48:02AM +0200, Michal Nazarewicz wrote:
> With [f495d26: “generalize CMA reserved area management
> functionality”] patch CMA has its place under mm directory now so
> there is no need to shoehorn a highly CMA specific functions inside of
> page_alloc.c.
>
> As such move
On Fri, 2014-06-27 at 07:29 +0200, Julia Lawall wrote:
> On Thu, 26 Jun 2014, Joe Perches wrote:
> > The cast of a const void * to a void * was odd.
> >
> > Maybe a mechanism to verify appropriateness of
> > loss of constness for any pointer might be useful.
>
> I tried the following, but didn't
On Wed, Jun 25, 2014 at 10:59:19AM +0200, Vlastimil Babka wrote:
> On 06/25/2014 02:53 AM, Joonsoo Kim wrote:
> >On Tue, Jun 24, 2014 at 05:42:50PM +0200, Vlastimil Babka wrote:
> >>On 06/24/2014 10:33 AM, Joonsoo Kim wrote:
> >>>On Fri, Jun 20, 2014 at 05:49:34PM +0200, Vlastimil Babka wrote:
> >>
On 06/26/2014 10:05 PM, Oren Twaig wrote:
> ping
This patch conflicts with the changes on the tip:x86/apic branch. Could
you please rebase the patch on top of that branch?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord
[Cc Johannes: at the end I have a particular question for you]
On Thu, 26 Jun 2014, Vlastimil Babka wrote:
> On 06/26/2014 12:36 AM, Hugh Dickins wrote:
> > On Tue, 24 Jun 2014, Vlastimil Babka wrote:
> >
> > Sorry for the slow response: I have got confused, learnt more, and
> > changed my mind,
On 2013/10/18 20:37, Naveen N. Rao wrote:
> On 10/18/2013 01:53 PM, Chen, Gong wrote:
>> This H/W error log driver (a.k.a eMCA driver) is implemented based on
>> http://www.intel.com/content/www/us/en/architecture-and-technology/enhanced-mca-logging-xeon-paper.html
>>
>> After errors are captured,
On Thu, 26 Jun 2014, Joe Perches wrote:
> On Thu, 2014-06-26 at 22:58 +0530, Himangi Saraogi wrote:
> > This patch removes the cast on data of type void* as it is not needed.
>
> Hi Himangi
>
> The cast of a const void * to a void * was odd.
>
> Maybe a mechanism to verify appropriateness of
On Fri, Jun 27, 2014 at 09:10:09AM +0530, Punnaiah Choudary Kalluri wrote:
> Zynq soc usb controller is a synopsys IP and it is compatible
> with the chipidea spec. So, reusing chipidea drivers for zynq usb
> controller.
What means "... usb controller is a synopsys IP", or it should be "uses
synop
On Fri, Jun 27, 2014 at 9:09 AM, Peter Chen wrote:
> On Fri, Jun 27, 2014 at 09:10:09AM +0530, Punnaiah Choudary Kalluri wrote:
>> Zynq soc usb controller is a synopsys IP and it is compatible
>> with the chipidea spec. So, reusing chipidea drivers for zynq usb
>> controller.
>
> What means "... u
On Fri, Jun 27, 2014 at 11:25:07AM +0800, Peter Chen wrote:
> On Tue, Jun 24, 2014 at 12:35:16PM +0200, Antoine Ténart wrote:
> > Add a generic ChipIdea driver, with optional PHY and clock, to support
> > ChipIdea controllers that doesn't need specific functions.
> >
> > + return 0;
> > +}
> > +
Hi all,
The powerpc allyesconfig is again broken more than usual.
Changes since 20140626:
New tree: usb-serial-fixes
The staging tree still had its build failure for which I disabled a driver.
The akpm-current tree its build failure (I applied a supplied patch).
Non-merge commits (relative
ping
On 06/23/2014 08:35 AM, Oren Twaig wrote:
> Remove invalid code which caused TSC to be declared as "unstable" on vSMP
> Foundation box even if it was stable and let the kernel decide for itself.
>
> When a vSMP Foundation box is detected, the function apic_cluster_num() counts
> the number of
On 06/26/2014 09:57 PM, Jeff Layton wrote:
> From: Jeff Layton
>
> Open file description locks have been merged into the Linux kernel for
> v3.15. Add the appropriate command-value definitions and an update to
> the manual that describes their usage.
What's the hold-up here? Jeff's patches have
On Tue, Jun 24, 2014 at 12:35:16PM +0200, Antoine Ténart wrote:
> Add a generic ChipIdea driver, with optional PHY and clock, to support
> ChipIdea controllers that doesn't need specific functions.
>
> Needed for the Marvell Berlin SoCs SUB controllers.
>
> Signed-off-by: Antoine Ténart
> ---
>
On Friday, June 27, 2014 1:33 PM, Jingoo Han wrote:
> On Friday, June 27, 2014 8:25 PM, Alvin Chen wrote:
> >
> > From: Bryan O'Donoghue
> >
> > The EHCI packet buffer in/out threshold is programmable for Intel Quark
> > X1000 USB host
> > controller, and the default value is 0x20 dwords. The in/
On Friday, June 27, 2014 8:25 PM, Alvin Chen wrote:
>
> From: Bryan O'Donoghue
>
> The EHCI packet buffer in/out threshold is programmable for Intel Quark X1000
> USB host
> controller, and the default value is 0x20 dwords. The in/out threshold can be
> programmed
> to 0x80 dwords, but only wh
This patch control special clock for ADC in Exynos series's FSYS block.
If special clock of ADC is registerd on clock list of common clk framework,
Exynos ADC drvier have to control this clock.
Exynos3250/Exynos4/Exynos5 has 'adc' clock as following:
- 'adc' clock: bus clock for ADC
Exynos3250 ha
This patch add DT binding documentation for Exynos3250 ADC IP. Exynos3250 has
special clock ('sclk_adc') for ADC which provide clock to internal ADC.
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
Reviewed-by: Naveen Krishna Chatradhi
---
.../devicetree/bindings/arm/samsung/exynos-adc.txt
This patchset add 'exynos_adc_data' structure which includes some functions
to control ADC operation and specific data according to ADC version (v1 or v2).
Signed-off-by: Chanwoo Choi
Acked-by: Kyungmin Park
Reviewed-by: Naveen Krishna Chatradhi
---
drivers/iio/adc/exynos_adc.c | 226 +
Changes from v4:
- Use 'exynos_adc_data' structure instead of 'exynos_adc_ops' structure
and remove enum variable of ADC version
- Fix wrong name of special clock (sclk_tsadc -> sclk_adc)
- Add reviewed message by Naveen Krishna Chatradhi
- Add functions for ADC clock control
Changes from v3:
-
This patchset fix wrong compatible string for Exynos3250 ADC. Exynos3250 SoC
need to control only special clock for ADC. Exynos SoC except for Exynos3250
has not included special clock for ADC. The exynos ADC driver can control
special clock if compatible string is 'exynos3250-adc-v2'.
Signed-off-
On Thu, Jun 26, 2014 at 08:52:10PM -0700, Steven Noonan wrote:
> On Thu, Jun 26, 2014 at 5:23 PM, Josh Boyer wrote:
> > On Thu, Jun 26, 2014 at 3:26 PM, Greg KH wrote:
> >> I'm announcing the release of the 3.15.2 kernel.
> >>
> >> All users of the 3.15 kernel series must upgrade.
> >>
> >> The u
On Thu, Jun 26, 2014 at 08:52:10PM -0700, Steven Noonan wrote:
> On Thu, Jun 26, 2014 at 5:23 PM, Josh Boyer wrote:
> > On Thu, Jun 26, 2014 at 3:26 PM, Greg KH wrote:
> >> I'm announcing the release of the 3.15.2 kernel.
> >>
> >> All users of the 3.15 kernel series must upgrade.
> >>
> >> The u
Hi Mikulas,
On Mon, 2014-06-23 at 13:42 -0400, Mikulas Patocka wrote:
> target: fix deadlock on unload
>
> On uniprocessor preemptible kernel, target core deadlocks on unload. The
> following events happen:
> * iscsit_del_np is called
> * it calls send_sig(SIGINT, np->np_thread, 1);
> * the sched
On Thu, Jun 26, 2014 at 10:43:55PM +0800, Cheng-Wei Lee wrote:
> This patch fixes the following checkpatch.pl issues in hfa384x_usb.c:
> WARNING: Missing a blank line after declarations
>
> Signed-off-by: Quentin Lee
> ---
> drivers/staging/wlan-ng/hfa384x_usb.c |1 +
> 1 file changed, 1 ins
BUG: unable to handle kernel NULL pointer dereference at 0046
IP: [] dec_count+0x5f/0x80 [dm_mod]
PGD 0
Oops: [#1] SMP
last sysfs file:
/sys/devices/pci:00/:00:02.2/:02:00.0/host0/scsi_host/host0/proc_name
Pid: 2708, comm: kcopyd Tainted: GW --- H
On Sun, Jun 22, 2014 at 01:01:50PM +0200, Thomas Vegas wrote:
> The variable 'pxmitbuf' is already set to NULL when entering the
> function. We can remove the first conditional. When _rtw_queue_empty()
> returns false, 'pxmitbuf' if not NULL. We can merge the second and
> third conditional.
>
> Si
This patch fixed the coding style issues reported by checkpatch.pl
following issues fixed:
CHECK: Alignment should match open parenthesis
WARNING: line over 80 characters
CHECK: Blank lines aren't necessary before a close brace '}'
WARNING: networking block comments
On Wed, Jun 25, 2014 at 09:14:30AM +0200, Raphael Poggi wrote:
> This patch fix checkpath "WARNING: Missing a blank line after declarations"
>
> Signed-off-by: Raphaël Poggi
> ---
> drivers/staging/media/lirc/lirc_imon.c |3 +++
Please use scripts/get_maintainer.pl to find out who patches fo
On Wed, Jun 25, 2014 at 03:46:19PM -0700, Bryan Wu wrote:
> On Wed, Jun 25, 2014 at 10:08 AM, Johan Hovold wrote:
> > LED-class device attributes should be created using the attribute groups
> > of struct device, rather than be added manually after the device has
> > been registered in order to av
Document device tree binding information as required by
the ZYNQ USB controller.
Signed-off-by: Punnaiah Choudary Kalluri
---
.../devicetree/bindings/usb/ci-hdrc-zynq.txt | 23
1 files changed, 23 insertions(+), 0 deletions(-)
create mode 100644 Documentation/device
Zynq soc usb controller is a synopsys IP and it is compatible
with the chipidea spec. So, reusing chipidea drivers for zynq usb
controller.
Signed-off-by: Punnaiah Choudary Kalluri
---
drivers/usb/chipidea/Makefile |1 +
drivers/usb/chipidea/ci_hdrc_zynq.c | 115 ++
From: Graeme Gregory
Add Kconfigs to build ACPI on ARM64, and make ACPI available on ARM64.
acpi_idle driver is x86/IA64 dependent now, so make CONFIG_ACPI_PROCESSOR
depend on X86 || IA64, and implement it on ARM64 in the future.
Reviewed-by: Grant Likely
Signed-off-by: Graeme Gregory
Signed-
Since EC (Embedded controller) needs SCI for the interupt which
is not available on ARM64, make the EC debugfs depend on X86 || IA64
only in the Kconfig file.
Reviewed-by: Grant Likely
Signed-off-by: Hanjun Guo
---
drivers/acpi/Kconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/driv
CONFIG_ACPI depends CONFIG_PCI now, and ACPI provides ACPI based
PCI hotplug and PCI host bridge hotplug, introduce some PCI
functions to make ACPI core can be compiled, some of the functions
should be revisited when implemented on ARM64.
Reviewed-by: Grant Likely
Originally-by: Graeme Gregory
S
From: Al Stone
ACPI reduced hardware mode is disabled by default, but ARM64
can only run properly in ACPI hardware reduced mode, so select
ACPI_REDUCED_HARDWARE_ONLY if ACPI is enabled on ARM64.
Reviewed-by: Grant Likely
Signed-off-by: Al Stone
Signed-off-by: Hanjun Guo
---
arch/arm64/Kconfi
arch_fix_phys_package_id() will be called in ACPI core to use
the slot number provided by ACPI to update the physical package
id, then we can get the right value in the "physical id" field
of /proc/cpuinfo.
Reviewed-by: Grant Likely
Signed-off-by: Hanjun Guo
---
arch/arm64/include/asm/topology.
On Thu, Jun 26, 2014 at 5:23 PM, Josh Boyer wrote:
> On Thu, Jun 26, 2014 at 3:26 PM, Greg KH wrote:
>> I'm announcing the release of the 3.15.2 kernel.
>>
>> All users of the 3.15 kernel series must upgrade.
>>
>> The updated 3.15.y git tree can be found at:
>>
>> git://git.kernel.org/p
From: Graeme Gregory
If the early boot methods of acpi are happy that we have valid ACPI
tables and acpi=off has not been passed. Then do not unflat devicetree
effectively disabling further hardware probing from DT.
Signed-off-by: Graeme Gregory
---
arch/arm64/kernel/setup.c |3 ++-
1 file
From: Graeme Gregory
ACPI core requires a cpu.h, add a dummy one here temporarily.
This file will be updated in the future to add definitions for
arch_(un)register_cpu which are required for ACPI based physical
CPU hotplug when these standards have be ratified by the ASWG.
Reviewed-by: Grant Lik
From: Al Stone
Introduce two early parameters for "acpi", one is the parameter
to disable ACPI on ARM64 and another one is acpi=strict to disable
out-of-spec workarounds.
Reviewed-by: Grant Likely
Signed-off-by: Al Stone
Signed-off-by: Graeme Gregory
Signed-off-by: Hanjun Guo
---
Documentat
From: Al Stone
ACPI core need lots extern variables and functions which should
be provided by arch dependent code to make itself compilable. so
introduce arm-core.c and its related header file here, we need:
- asm/acenv.h for arch specific ACPICA environments and
implementation;
- asm/acp
From: Graeme Gregory
acpi_wakeup_address is used on x86 as the address bios jumps into
when machine wakes up from suspend. As arm64 does not have such a
bios this mechanism will be provided by other means. But the define
is still required inside the acpi core.
Introduce a null stub for acpi_susp
From: Graeme Gregory
With the addition of ARM64 that does not have a traditional BIOS to
scan, add a config option which is selected on x86 and ia64 to do
the traditional BIOS scanning for tables.
Signed-off-by: Graeme Gregory
---
arch/ia64/Kconfig|1 +
arch/x86/Kconfig |1 +
d
From: Graeme Gregory
Now ARM64 support is being added to ACPI so architecture specific
values can not be used in core ACPI code.
Following on the patch "ACPI / processor: Check if LAPIC is present
during initialization" which uses acpi_lapic in acpi_processor.c,
on ARM64 platform, GIC is used in
This patch set is the first part of ARM64 ACPI core patches to
running ACPI on ARM64, it just handle some compile errors when
ACPI is introduced to ARM64 platform and enable ACPI on ARM64
in Kconfig.
Following core patch sets for ACPI based SMP/GIC/Arch Timer
initialization to enable ACPI on ARM64
The use of _PDC is deprecated in ACPI 3.0 in favor of _OSC,
as ARM platform is supported only in ACPI 5.0 or higher version,
_PDC will not be used in ARM platform, so make Make _PDC only for
platforms with Intel CPUs.
Introduce ARCH_HAS_ACPI_PDC and move _PDC related code in ACPI
processor driver
On 06/27/2014 11:25 AM, Guenter Roeck wrote:
> On 06/26/2014 07:47 PM, Chen Gang wrote:
>> On 06/27/2014 10:11 AM, Lennox Wu wrote:
>>> Acked-by: Lennox Wu
>>>
>>
>> OK, thank, and excuse me, I am not quite familiar with the version
>> merging of upstream kernel: "who will apply it, next, if it is
On 06/26/2014 09:38 PM, Kevin Hilman wrote:
> Tushar Behera writes:
>
>> On Thu, Jun 26, 2014 at 4:51 AM, Kevin Hilman wrote:
>>> Doug Anderson writes:
>>>
Tushar,
On Tue, Jun 10, 2014 at 10:32 PM, Tushar Behera
wrote:
> Currently CLK_FOUT_EPLL was set as one of the pa
On 06/27/2014 04:53 AM, Arnd Bergmann wrote:
On Thursday 26 June 2014 21:48:54 zhangfei wrote:
Since you mention that this is a synopsys part, it may however be
good to also define a compatible string for the generic device,
to allow other SoCs to share this driver, and to make it easier
for
On Sat, Jun 21, 2014 at 2:08 PM, Thomas Gleixner wrote:
> Jiang,
>
> On Mon, 9 Jun 2014, Jiang Liu wrote:
>
>> On x86 platforms, IRQ number are statically allocated to IOAPIC pins at boot.
>> There are two issues with this design. First it causes trouble to IOAPIC
>> hotplug because we need to all
Hi Florian,
On 06/27/2014 02:00 AM, Florian Fainelli wrote:
Hello,
2014-06-25 0:24 GMT-07:00 Bo Shen :
If the fixups parameters get from dtb, it won't set has_fixups
parameters, so when read phy_has_fixups attribute, it always
present as 0.
Add this patch to make phy_has_fixups attribute read
From: "Alvin (Weike) Chen"
Hi,
Intel Quark X1000 consists of one USB host controller which can be PCI
enumerated.
And the exsiting EHCI-PCI framework supports it with the default packet buffer
in/out
threshold. We reconfigure the in/out threshold as maximal as possible.
Bryan O'Donoghue (1):
From: Bryan O'Donoghue
The EHCI packet buffer in/out threshold is programmable for Intel Quark X1000
USB host
controller, and the default value is 0x20 dwords. The in/out threshold can be
programmed
to 0x80 dwords, but only when isochronous/interrupt transactions are not
initiated by
the USB h
On 06/26/2014 07:47 PM, Chen Gang wrote:
On 06/27/2014 10:11 AM, Lennox Wu wrote:
Acked-by: Lennox Wu
OK, thank, and excuse me, I am not quite familiar with the version
merging of upstream kernel: "who will apply it, next, if it is past all
reviewers' checking".
Normal procedure would be
On Thu, 26 Jun 2014, Jeff Moyer wrote:
> Jens Axboe writes:
>
> > On 2014-06-26 10:08, Jeff Moyer wrote:
> >> Joe Lawrence writes:
> >>
> >>> v1->v2: incorporate Jeff's feedback in bsg_map_hdr() and Reviewed-by
> >>> tags.
> >>>
> >>> Joe Lawrence (2):
> >>>block,scsi: verify retur
On Thu, 2014-06-26 at 17:07 -0700, Austin Schuh wrote:
> If I'm reading the rt patch correctly, wq_worker_sleeping was moved
> out of __schedule to sched_submit_work. It looks like that changes
> the conditions under which wq_worker_sleeping is called. It used to
> be called whenever a task was
I am Peter Tracey a private lender located in USA.I can help you with a loan
you are looking for @ 2% interest rate,For Urgent Response Email:
peterstraceyloan...@gmail.com
Peter Tracey
Email: peterstraceyloan...@gmail.com
Telephone:408 713 0573
--
To unsubscribe from this list: send the line "u
On Thu, 2014-06-26 at 21:06 -0400, Steven Rostedt wrote:
> As this patch is in my 3.17 queue and it touches the kvm and scsi
> tracepoint code, I figured I should at least do the courtesy of
> notifying the maintainers of those subsystems.
>
> Do you have any issues with this going through my tree
Add driver for arm pl353 static memory controller nand interface with
HW ECC support. This controller is used in xilinx zynq soc for interfacing
the nand flash memory.
Signed-off-by: Punnaiah Choudary Kalluri
---
Changes in v3:
- implemented the proper error codes
- further breakdown this patch
Added ONDIE ECC support. Currently this ecc mode is supported for
specific micron parts with oob size 64 bytes.
Signed-off-by: Punnaiah Choudary Kalluri
---
drivers/mtd/nand/pl353_nand.c | 131 +++-
1 files changed, 127 insertions(+), 4 deletions(-)
diff --g
Added software ecc support.
Signed-off-by: Punnaiah Choudary Kalluri
---
drivers/mtd/nand/pl353_nand.c | 163 +
1 files changed, 163 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/nand/pl353_nand.c b/drivers/mtd/nand/pl353_nand.c
index 0be8ca2..e
Added notes about the controller and driver
Signed-off-by: Punnaiah Choudary Kalluri
---
Documentation/mtd/nand/pl353-nand.txt | 92 +
1 files changed, 92 insertions(+), 0 deletions(-)
create mode 100644 Documentation/mtd/nand/pl353-nand.txt
diff --git a/Docum
The following patches add arm pl353 static memory controller driver for
xilinx zynq soc. The arm pl353 smc supports two interfaces i.e nand and
nor/sram memory interfaces. The current implementation supports only a
single SMC instance and nand specific configuration.
xilinx zynq TRM link:
http://w
The following patches add arm pl353 static memory controller driver for
xilinx zynq soc. The arm pl353 smc supports two interfaces i.e nand and
nor/sram memory interfaces. The current implementation supports only a
single SMC instance and nand specific configuration.
xilinx zynq TRM link:
http://w
Add driver for arm pl353 static memory controller. This controller is
used in xilinx zynq soc for interfacing the nand and nor/sram memory
devices.
Signed-off-by: Punnaiah Choudary Kalluri
---
Changes in v2:
- Since now the timing parameters are in nano seconds, added logic to convert
them to
Add pl353 static memory controller devicetree binding information.
Signed-off-by: Punnaiah Choudary Kalluri
---
Changes in v2:
- modified timing binding info as per onfi timing parameters
- add suffix nano second as timing unit
- modified the clock names as per the IP spec
---
.../bindings/me
On Thu, Jun 26, 2014 at 02:10:28PM +0200, Bernd Schubert wrote:
> On 06/26/2014 01:57 PM, Lukáš Czerner wrote:
> >On Thu, 26 Jun 2014, Artem Bityutskiy wrote:
> >>On Thu, 2014-06-26 at 12:36 +0200, Bernd Schubert wrote:
> >>>On 06/26/2014 08:13 AM, Artem Bityutskiy wrote:
> On Thu, 2014-06-26 a
On Thu, Jun 26, 2014 at 09:13:19AM +0300, Artem Bityutskiy wrote:
> On Thu, 2014-06-26 at 11:06 +1000, Dave Chinner wrote:
> > Your particular use case can be handled by directing your benchmark
> > at a filesystem mount point and unmounting the filesystem in between
> > benchmark runs. There is n
On Thu, Jun 26, 2014 at 10:50:49PM +0200, Pavel Machek wrote:
>
> And for every bug in kernel, there's one in fsck: I did not expect it, but
> fsck actually
> suceeded, and marked fs as clean. But second fsck had issues with
> /lost+found...
I'd need the previous fsck transcript to have any ide
On 06/27/2014 10:11 AM, Lennox Wu wrote:
> Acked-by: Lennox Wu
>
OK, thank, and excuse me, I am not quite familiar with the version
merging of upstream kernel: "who will apply it, next, if it is past all
reviewers' checking".
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, an
On Thu, Jun 26, 2014 at 10:30:52PM +0200, Pavel Machek wrote:
>
> It looks like the filesystem contains _way_ too many 0x's:
That sounds like it's a hardware issue. It may be that the controller
did something insane while trying to do a write at the point when the
disk drive was disconnected
Hey Fellow Kernel Developers ,
I known this message is during the merge window of 3.16 -r3 so if you
get back to me after this window ,it's fine.
I seem to be finding lots of bugs on the kernel Bugzilla that are now
fixed , it would be great if the maintainers or bug
reporters closed them. In addi
On 06/26/2014 08:12 AM, Stephen Rothwell wrote:
Hi James,
On Wed, 25 Jun 2014 20:51:43 +1000 James Morris
wrote:
I haven't pulled in Paul's tree, I merged with the latest Linus release.
Ummm, yesterday your security tree
(git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security
On 27 June 2014 05:36, Stephen Boyd wrote:
> I gave it a spin. It looks mostly good except for the infinite loop:
Great !!
> diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c
> index b7ee67c4d1c0..6744321ae33d 100644
> --- a/drivers/cpufreq/cpufreq-cpu0.c
> +++ b/drive
On 27 June 2014 07:23, Mike Turquette wrote:
>> but it isn't future-proof if/when the clock framework starts returning
>> dynamically allocated clock pointers for each clk_get() invocation.
>> Maybe we need a function in the common clock framework that tells us if
>> the clocks are the same either
Acked-by: Lennox Wu
2014-06-27 7:28 GMT+08:00 Chen Gang :
>
>
> On 06/27/2014 05:56 AM, David Rientjes wrote:
>> On Thu, 26 Jun 2014, Chen Gang wrote:
>>
>>> 'COUNTER' and other same kind macros are too common to use, and easy to
>>> get conflict with other modules.
>>>
>>> At present, they are n
On 06/26/2014 12:10 PM, Rickard Strandqvist wrote:
> After some discussion, all agreed that the previous value was incorrect.
>
> Signed-off-by: Rickard Strandqvist
This is better but still sort of incorrect as userspace would be getting 2
bogus entries at indexes 0 and 1. be2iscsi is also broke
Quoting Stephen Boyd (2014-06-26 17:06:00)
> Finally, checking for equivalent pointers from clk_get() will work now,
Please don't do that. Even though it works for the current
implementation, comparing those pointers from a driver violates how
clkdev is supposed to work. The pointer returned by cl
seeing is the following:
[ 4806.833452] Kernel panic - not syncing: hung_task: blocked tasks
[ 4806.834701] CPU: 26 PID: 3252 Comm: khungtaskd Not tainted
3.16.0-rc2-next-20140626-sasha-00023-g9256882-dirty #732
[ 4806.837672] 003ffcda 880bb2d6bd38 b1529940
0001
[ 4
As this patch is in my 3.17 queue and it touches the kvm and scsi
tracepoint code, I figured I should at least do the courtesy of
notifying the maintainers of those subsystems.
Do you have any issues with this going through my tree? If not, please
give me an Acked-by.
Thanks!
-- Steve
On Thu,
On Thu, 26 Jun 2014 09:58:31 -0400
Steven Rostedt wrote:
> What we can do is force ring_buffer_swap_cpu() to only work for the CPU
> that it is on. As we have snapshot in per_cpu buffers, to make that
> work, we will need to change the per_cpu version of snapshot to do a
> smp_call_function_singl
1 - 100 of 649 matches
Mail list logo
