From: Mika Westerberg mika.westerb...@linux.intel.com
Add support for Intel Low Power I/O subsystem PWM controllers found on
Intel BayTrail SoC.
Signed-off-by: Mika Westerberg mika.westerb...@linux.intel.com
Signed-off-by: Chew, Kean Ho kean.ho.c...@intel.com
Signed-off-by: Chang, Rebecca Swee
This patch adds support for building Intel uncore driver as module.
It adds clean-up code and config option for the Intel uncore driver
Signed-off-by: Yan, Zheng zheng.z@intel.com
---
Changes since v1:
move config option to General setup/Kernel Performance Events and Counters
On 03/19/2014 06:00 PM, Jan Kara wrote:
On Wed 19-03-14 11:08:08, Jane Li wrote:
On 02/12/2014 05:19 AM, Andrew Morton wrote:
On Tue, 11 Feb 2014 14:50:00 +0800j...@marvell.com wrote:
Umm, I disagree with the patch. What I proposed in my answer to your patch
is something like the patch
From: Jane Li j...@marvell.com
This patch tries to fix a warning about possible circular locking
dependency.
If do in following sequence:
enter suspend - resume - plug-out CPUx (echo 0 cpux/online)
lockdep will show warning as following:
MADV_FREEed pages should be discarded before working set pages
are reclaimed because most of users(ex, tcmalloc and jemalloc)
have used it instead of MADV_DONTNEED which zap pages instantly.
Signed-off-by: Minchan Kim minc...@kernel.org
---
mm/memory.c | 1 +
1 file changed, 1 insertion(+)
diff
Linux doesn't have an ability to free pages lazy while other OS
already have been supported that named by madvise(MADV_FREE).
The gain is clear that kernel can evict freed pages rather than
swapping out or OOM if memory pressure happens.
Without memory pressure, freed pages would be reused by
This patch is an attempt to support MADV_FREE for Linux.
Rationale is following as.
Allocators call munmap(2) when user call free(3) if ptr is
in mmaped area. But munmap isn't cheap because it have to
clean up all pte entries, unlinking a vma and returns free pages
to page allocator so that
Now, deactivate_page works for file page but MADV_FREE will use
it to move lazyfree pages to inactive LRU's tail so this patch
makes deactivate_page work with anon pages as well as file pages.
Signed-off-by: Minchan Kim minc...@kernel.org
---
include/linux/mm_inline.h | 9 +
mm/swap.c
Hi,
On 03/20/2014 02:20 PM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 20 March 2014 07:52 AM, Chanwoo Choi wrote:
Hi,
On 03/19/2014 09:08 PM, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 18 March 2014 05:34 PM, Chanwoo Choi wrote:
This patch remove unnecessary function call in
Hi all,
This tree still fails (more than usual) the powerpc allyesconfig build.
Changes since 20140319:
The powerpc tree still had its build failure.
The net-next tree lost its another build failure.
The wireless-next tree lost its build failure.
The drm-intel tree lost its build failure.
On 2014/03/19, 1:55 PM, Peter Zijlstra pet...@infradead.org wrote:
On Wed, Mar 19, 2014 at 07:44:29PM +, Dilger, Andreas wrote:
The original reason for l_wait_event() not using TASK_UNINTERRUPTIBLE
is to avoid the load on the server continually being
num_service_threads
regardless of
Hi Lee,
I really can't take this patch separately. You'll need to resend the
whole series soon.
On Tue, Mar 11, 2014 at 08:23:16AM +, Lee Jones wrote:
Sorry about the previous fixup misses. There were a couple of patches
which I had failed to squash into the pack. Hopefully the rest of the
On Thu, Mar 20, 2014 at 11:03:50AM +0530, Srikar Dronamraju wrote:
Joy,.. let me look at that with ppc in mind.
OK; so while pretty much all the comments from that patch are utter
nonsense (what was I thinking), I cannot actually find a real bug.
But could you try the below which
On Tue, Feb 18, 2014 at 02:55:54PM +, Lee Jones wrote:
When we write data to the Serial Flash chip we'll wait a predetermined
period of time before giving up. During that period of time we poll the
status register until completion.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by:
On Tue, Feb 18, 2014 at 02:55:38PM +, Lee Jones wrote:
Take some known parameters, namely size and number of sectors and use
them to determine weather a device can support 32bit addressing or not.
If it can, set the associated flash capability flag for latter use.
Acked-by Angus Clark
This patch add a correct out of memory handling for setup a 32 bit vDSO.
The patch is against tip commit 4e40112c4ff6a577dd06d92b2a54cdf06265bf74
Signed-off-by: Stefani Seibold stef...@seibold.net
---
arch/x86/vdso/vdso32-setup.c | 17 -
1 file changed, 16 insertions(+), 1
Hello Dave,
On Wed, Mar 19, 2014 at 05:38:10PM -0700, Dave Hansen wrote:
On 03/18/2014 05:24 AM, Michal Hocko wrote:
On Fri 14-03-14 11:33:30, John Stultz wrote:
[...]
Volatile ranges provides a method for userland to inform the kernel that
a range of memory is safe to discard (ie: can
-Original Message-
From: Stephane Eranian [mailto:eran...@google.com]
Sent: Thursday, March 20, 2014 11:35 AM
To: Zhang, Rui
Cc: Lu, Aaron; Rafael J. Wysocki; Borislav Petkov; lkml; x...@kernel.org;
Bjorn Helgaas; Linux PCI; ACPI Devel Maling List; Yinghai Lu; H. Peter
Anvin; Yan,
Hi Rafael,
On Wed, Mar 19, 2014 at 11:50 PM, Rafael J. Wysocki r...@rjwysocki.net wrote:
On Monday, March 17, 2014 09:26:10 PM Geert Uytterhoeven wrote:
From: Geert Uytterhoeven geert+rene...@linux-m68k.org
Why exactly are they errors?
checkpatch.pl says: WARNING: please, no space before
On Tue, Feb 18, 2014 at 02:55:52PM +, Lee Jones wrote:
diff --git a/drivers/mtd/devices/st_spi_fsm.c
b/drivers/mtd/devices/st_spi_fsm.c
index fe538bb..e4815fe 100644
--- a/drivers/mtd/devices/st_spi_fsm.c
+++ b/drivers/mtd/devices/st_spi_fsm.c
@@ -942,6 +945,100 @@ static int
Hi Joe,
On Thu, Mar 20, 2014 at 3:21 AM, Joe Perches j...@perches.com wrote:
SUSPEND TO RAM
+M: Rafael J. Wysocki r...@rjwysocki.net
-M: Rafael J. Wysocki r...@rjwysocki.net
Please keep the quotes around your name.
It makes it easier for some systems to accept
names with periods via
Hi
On Thu, Mar 20, 2014 at 4:49 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
Is there really any use-case where the sealer isn't also the same
thing that *created* the file in the first place? Because I would be a
ton happier with the notion that you can only seal things that you
On Tue, Feb 18, 2014 at 02:55:27PM +, Lee Jones wrote:
This should be the final version.
:)
I had a few more comments. Contrary to my comment on patch 1, I don't
think too many of my comments were repeats. But nothing too big anyway.
I expect that I'll merge this as soon as you address my
Hi Bartlomiej,
On Tuesday 18 March 2014 12:01 AM, Bartlomiej Zolnierkiewicz wrote:
The new driver is named ahci_da850 and is only compile tested. Once it
is tested on the real hardware and verified to work correctly, the legacy
platform code (which depends on the deprecated struct
Stephan Mueller wrote:
This is a clean-room implementation of the DRBG defined in SP800-90A.
Why? I guess it's for certification?
+static bool drbg_fips_continuous_test(struct drbg_state *drbg,
+ unsigned char *buf)
...
+ ret = memcmp(drbg-prev, buf,
Hi Stephen,
Thank you for your reply.
(2014/03/20 4:51), Stephen Warren wrote:
On 03/19/2014 04:15 AM, Yoshihiro YUNOMAE wrote:
Add tunable RX interrupt trigger I/F of FIFO buffers.
Serial devices are used as not only message communication devices but control
or sending communication devices.
On Thu 20-03-14 10:09:54, Minchan Kim wrote:
Hello,
On Wed, Mar 19, 2014 at 11:12:02AM +0100, Jan Kara wrote:
On Wed 19-03-14 09:49:18, Minchan Kim wrote:
On Tue, Mar 18, 2014 at 11:07:50AM -0700, John Stultz wrote:
On Tue, Mar 18, 2014 at 8:11 AM, Minchan Kim minc...@kernel.org
Looks good,
Reviewed-by: Christoph Hellwig h...@lst.de
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 03/20/2014 03:53 PM, Zhang, Rui wrote:
The resource length is also hardcoded to 0x6000, right?
This is probably a problem, because
only if the resource length read from PCI config space is larger than 0x4000,
drivers/pnp/quirks.c will detect the conflict and disable the PNP0C02
resource
(2014/03/18 8:26), Greg KH wrote:
On Wed, Mar 12, 2014 at 10:24:21AM +0900, Nobuhiro Iwamatsu wrote:
Register for the device are mapped in uio_mmap_physical().
In this case, it might not be the same as the size of VMA always.
Why wouldn't this be the case?
size contained in the mem- size is
On Thu, Mar 20, 2014 at 02:03:46PM +0800, Yan, Zheng wrote:
This patch adds support for building Intel uncore driver as module.
It adds clean-up code and config option for the Intel uncore driver
Signed-off-by: Yan, Zheng zheng.z@intel.com
---
Changes since v1:
move config option to
On 19/03/14 23:15, Jason Gunthorpe wrote:
This describes a compatible entry of the form:
ethernet-phy-id,
Which is modelled after the PCI structured compatible entry
(pci,...RR)
If present the OF core will be able to use this information to
directly create the correct
On 19 March 2014 20:15, Dietmar Eggemann dietmar.eggem...@arm.com wrote:
On 17/03/14 11:52, Peter Zijlstra wrote:
On Wed, Mar 12, 2014 at 01:28:07PM +, Dietmar Eggemann wrote:
[...]
By making it robust, I guess you mean that the core scheduler has to
check that the provided set-ups are
Hi Lothar,
On Wednesday 19 March 2014 14:23:26 y...@karo-electronics.de wrote:
With a flash-based BBT there is no reason to move the Factory Bad
Block Marker from the data area buffer (to where it is mapped by the
GPMI NAND controller) to the OOB buffer. Thus, make this feature
configurable
On 03/20/2014 10:09 AM, Viresh Kumar wrote:
On 19 March 2014 17:45, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 199b52b..e90388f 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@
On 20 March 2014 14:02, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 199b52b..5283f10 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -349,6 +349,39 @@ void
Except bond mode 1, in other bond modes, inactive slaves should keep inactive
flag to
1 to refuse to receive broadcast packets. Now, active slave send broadcast
packets
(for example ARP requests) which will arrive inactive slaves on same host from
switch,
but inactive slave's inactive flag is
On 02/12/2014 06:00 PM, rogera...@realtek.com wrote:
From: Roger Tseng rogera...@realtek.com
Realtek USB memstick host driver provides memstick host support based on the
Realtek USB card reader MFD driver.
Signed-off-by: Roger Tseng rogera...@realtek.com
Andrew,
Would you please Ack or
Hi,
On Tuesday 18 March 2014 04:11 PM, Bartlomiej Zolnierkiewicz wrote:
devm_ioremap_resource() returns a pointer to the remapped memory or
an ERR_PTR() encoded error code on failure. Fix the checks inside
csc_create() and sc_create() accordingly.
Cc: Archit Taneja arc...@ti.com
Cc: Hans
Hi,
On Thursday 20 March 2014 12:26 PM, Chanwoo Choi wrote:
Hi,
On 03/20/2014 02:20 PM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 20 March 2014 07:52 AM, Chanwoo Choi wrote:
Hi,
On 03/19/2014 09:08 PM, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 18 March 2014 05:34 PM, Chanwoo
On Wed, Mar 19, 2014 at 08:06:48PM +0100, David Herrmann wrote:
memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor
that you can pass to mmap(). It explicitly allows sealing and
avoids any connection to user-visible mount-points. Thus, it's not
subject to quotas on
On 03/20/2014 12:47 PM, Cyrill Gorcunov wrote:
On Wed, Mar 19, 2014 at 08:06:48PM +0100, David Herrmann wrote:
memfd_create() is similar to mmap(MAP_ANON), but returns a file-descriptor
that you can pass to mmap(). It explicitly allows sealing and
avoids any connection to user-visible
Since the the v4l2_clk_get() may return a EPROBE_DEFER during async
probing. So move the v4l2_clk_get() to the beginning of the
probe(). Only when we get mclk successfully we continue the probe.
Signed-off-by: Josh Wu josh...@atmel.com
---
v1 - v2:
just return PTR_ERR(clk) as it can be
On Tue, Mar 18, 2014 at 02:31:58AM +0800, Bartlomiej Zolnierkiewicz wrote:
The new driver is named ahci_spear1340 and is only compile tested. Once
it is tested on the real hardware and verified to work correctly, the legacy
platform code (which depends on the deprecated struct
于 2014年03月19日 21:23, y...@karo-electronics.de 写道:
configurable via DT. This is required for the Ka-Ro electronics
platforms.
If you disable the swapping, you will disable the NAND boot in actually.
do you need the nand boot?
could you please tell me more detail background?
thanks
Huang
On Tue, Mar 18, 2014 at 07:00:08PM +0800, Viresh Kumar wrote:
On Tue, Mar 18, 2014 at 4:28 PM, Bartlomiej Zolnierkiewicz
b.zolnier...@samsung.com wrote:
Make sata_miphy_exit(), sata_suspend() and sata_resume() static.
Signed-off-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
On Thu, Mar 20, 2014 at 7:27 AM, Dave Jones da...@redhat.com wrote:
On Thu, Mar 20, 2014 at 01:43:44PM +1030, Rusty Russell wrote:
drivers/mtd/devices/docg3.c:
__ATTR(f##id##_dps0_protection_key, S_IWUGO, NULL, dps0_insert_key), \
__ATTR(f##id##_dps1_protection_key, S_IWUGO,
This should be the final version (again) :)
Version 6:
Serviced 3 nits picked up by Brian during final review.
Version 5:
Tended to Christophe, Ludovic and Angus' comments.
Version 4:
Tended to Brian's review comments
- Checkpatch acceptance
- MODULE_DEVICE_TABLE() name slip
The FSM Serial Flash Controller is driven by issuing a standard set of
register writes we call a message sequence. This patch supplies a method
to prepare the message sequence responsible for setting 32bit addressing
mode on the Flash chip.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by:
Once we start supporting devices it will be handy go detect them
dynamically. This will be done using the chip's unique JEDEC ID. This
patch allows us to extract a device's JEDEC ID using the a predefined
FSM register write sequence.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee
Most chips require a predefined set of FSM message sequences for read,
write and erase operations. This patch provides a way to set them up,
which it will do so if a chip specific initialisation routine isn't
been provided.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones
Take some known parameters, namely size and number of sectors and use
them to determine weather a device can support 32bit addressing or not.
If it can, set the associated flash capability flag for latter use.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
This patch allows us to prepare some of the message sequences which will
be required to talk to the S25FLxxx family of Serial Flash devices. It
also allows us to do some required extra operations after any busy wait
failures.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones
The old API expected a partitions property provided a phandle to a
separate partitions node, which itself contained yet more nodes each
representing one partition. The new API rids the requirement for the
superfluous intermediary partitions node. This patch provides the
added information required
Hi,
Huang Shijie wrote:
于 2014年03月19日 21:23, y...@karo-electronics.de 写道:
configurable via DT. This is required for the Ka-Ro electronics
platforms.
If you disable the swapping, you will disable the NAND boot in actually.
No. All our modules do boot from NAND and none of them does the
Here we add the necessary device nodes required for successful device
probing and Pinctrl setup for the FSM.
Acked-by: Srinivas Kandagatla srinivas.kandaga...@st.com
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/stih416-pinctrl.dtsi |
Hi,
Juergen Beisert wrote:
Hi Lothar,
On Wednesday 19 March 2014 14:23:26 y...@karo-electronics.de wrote:
With a flash-based BBT there is no reason to move the Factory Bad
Block Marker from the data area buffer (to where it is mapped by the
GPMI NAND controller) to the OOB buffer. Thus,
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 82 +++-
1 file changed, 81 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/devices/st_spi_fsm.c
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/mtd/devices/st_spi_fsm.c b/drivers/mtd/devices/st_spi_fsm.c
index 34aac3f..5e315e3
Until now the dynamically configurable message sequences for read, write
and enable 32bit addressing have been global. Brian makes a good point
why this should not be the case. If there are ever two FSM's located on
the same platform, we could be potentially introducing a race condition
on
When an erase is requested by userspace the MTD framework calls back
into the driver to conduct the actual command issue. Here we provide the
routines which do exactly that. We can choose to either do an entire chip
erase or by sector.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 47
1 file changed, 43 insertions(+), 4 deletions(-)
diff --git a/drivers/mtd/devices/st_spi_fsm.c
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 36
1 file changed, 36 insertions(+)
diff --git a/drivers/mtd/devices/st_spi_fsm.c b/drivers/mtd/devices/st_spi_fsm.c
index
When we write data to the Serial Flash chip we'll wait a predetermined
period of time before giving up. During that period of time we poll the
status register until completion.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
On 03/20/2014 02:07 PM, Viresh Kumar wrote:
On 20 March 2014 14:02, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 199b52b..5283f10 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@
When we write data to the FIFO the FSM Controller subsequently writes
that data out to the Serial Flash chip.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 14 ++
1 file changed, 14 insertions(+)
diff
The I2C address (reg) is required for the TDA998x driver to be loaded
and initialized.
Signed-off-by: Jean-Francois Moine moin...@free.fr
---
This patch applies to linux-next.
---
Documentation/devicetree/bindings/drm/i2c/tda998x.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git
When a read is issued by userspace the MTD framework calls back into
the driver to conduct the actual command issue and data extraction.
Here we provide the routines which do exactly that.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
In the FSM driver we handle chip differences by providing the possibility
of calling back into a chip specific initialisation routine. In this patch
we provide one for the N25Qxxx series, which endeavours to setup things
like the read, write and erase sequences, as they differ from the
default. We
The N25Qxxx Serial Flash devices required different sequence
configurations depending on whether they're running in 24bit (3Byte)
or 32bit (4Byte) mode. We provide those here.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
The FSM Serial Flash Controller is driven by issuing a standard set of
register writes we call a message sequence. This patch supplies a method
to prepare the message sequence responsible for updating a chip's VCR.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones
Message sequences can vary depending on how many pads (lines) are
required to address the chip (mode dummy), how many data pads (lines)
are required to write out to the chip which will determine speed
amongst other things which are detailed by the SFDP specification. We
are able to use multiple
Firstly we search for our preference read/write configuration based on a
given chip's capabilities. Then we actually set up the message sequence
accordingly.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 17
Based on information we can obtain though platform specific data and/or
chip capabilities we are able to determine whether or not we can handle
a SoC reset or not. To find out why this is important please read the
comment provided in the patch.
Acked-by Angus Clark angus.cl...@st.com
The FSM Serial Flash Controller is driven by issuing a standard set of
register writes we call a message sequence. This patch supplies a method
to prepare the message sequence responsible for erasing a single sector.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones
The FSM Serial Flash Controller is driven by issuing a standard set of
register writes we call a message sequence. This patch supplies a method
to prepare read/write FSM message sequence(s) based on chip capability
and configuration.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee
Most Serial Flash chips support 24bit addressing as a default but more
recent incarnations can support 32bit. Based on information provided
though platform specific data and capabilities we can determine whether
or not our current chip can. This patch provides a means to setup the
FSM message
Cc: devicet...@vger.kernel.org
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
Documentation/devicetree/bindings/mtd/st-fsm.txt | 26
1 file changed, 26 insertions(+)
create mode 100644
It's important for us to determine which device was used to boot from in
order to make some correct decisions surrounding Power Management. On
each of the platforms which support the FSM this is communicated via
a set of mode pins held in the system configuration area. This patch
determine the
Using previously added infrastructure we can now extract a device's JEDEC
ID, compare it to a list of known and supported devices and make assumptions
based on known characteristics of a given chip.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
Here we provide a means to traverse though all supplied FSM message
sequence configurations and pick one based on our chip's capabilities.
The first one we match will be the preferred one, as they are
presented in order of preference.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee
Here we provide the FSM's register addresses, register bit names/offsets
and some commands which will prove useful as we start bulk the FMS's
driver out with functionality.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c
This patch uses default values to initialise a connected flash chip. This
includes; a device soft reset, setting of a safe working frequency, a
switch into Fast Sequencing Mode, configuring of timing data and a purge
of the FIFO.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones
When invoked the driver will attempt to read any available data from
the FSM's data register. Any data collected from this FIFO would have
originated from the flash chip.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c |
Supply a lookup table of all the devices we intend to support. This table
is used to store device information such as; a human readable device name,
their JEDEC ID (plus the extended version), sector size and amount, a bit
store of a device's capabilities, its maximum running frequency and
JEDEC have helped to standardise a great deal of the commands which
can be issued to a Serial Flash devices. Many of the Serial Flash
Discoverable Parameters (SFDP) commands are generic across devices.
This patch provides a shared point where these commands can be
defined.
Suggested-by: Mark
On 03/12/2014 09:25 AM, Bob Liu wrote:
On 03/12/2014 04:07 AM, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running latest -next
kernel
I've stumbled on the following spew:
[ 477.301955] kernel BUG at mm/swap.c:609!
[ 477.302564] invalid opcode:
On 20 March 2014 14:54, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
On 03/20/2014 02:07 PM, Viresh Kumar wrote:
WARN_ON(policy-transition_ongoing);
I guess you meant WARN_ON(!policy-transition_ongoing)
perhaps?
Ooops!!
I'm not sure whether its really worth it, because it
The FSM hardware works by setting a predetermined sequence of register
writes. Rather than open coding them inside each functional block we're
going to define them in a series of formatted 'sequence structures'.
This patch provides the framework which shall be used for every action.
Acked-by
This is a new driver. It's used to communicate with a special type of
optimised Serial Flash Controller called the FSM. The FSM uses a subset
of the SPI protocol to communicate with supported NOR-Flash devices.
Acked-by Angus Clark angus.cl...@st.com
Signed-off-by: Lee Jones lee.jo...@linaro.org
On Thu, 2014-03-20 at 08:58 +0100, Geert Uytterhoeven wrote:
Hi Joe,
On Thu, Mar 20, 2014 at 3:21 AM, Joe Perches j...@perches.com wrote:
SUSPEND TO RAM
+M: Rafael J. Wysocki r...@rjwysocki.net
-M: Rafael J. Wysocki r...@rjwysocki.net
Please keep the quotes around your name.
On Wed, Mar 19, 2014 at 01:09:20PM +, Lothar Waßmann wrote:
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
---
.../bindings/input/touchscreen/edt-ft5x06.txt | 41 ++
drivers/input/touchscreen/edt-ft5x06.c | 144
+++-
2 files changed,
On 2014/3/20 16:51, Zheng Li wrote:
Except bond mode 1, in other bond modes, inactive slaves should keep inactive
flag to
1 to refuse to receive broadcast packets. Now, active slave send broadcast
packets
(for example ARP requests) which will arrive inactive slaves on same host
from
The validity of the arguments passed to the program are checked. PID is a
mandatory argument. The core file name is optional, if not specified the
default file name is core.pid.
If a self dump is requested then, the application is called with a --daemon
option or the --socket option.
If the
Fetch the process status from /proc/pid/stat as it will be required for the
dump.
Signed-off-by: Suzuki K. Poulose suz...@in.ibm.com
Signed-off-by: Janani Venkataraman janan...@linux.vnet.ibm.com
---
src/Makefile.am |2 +
src/coredump.c |4 +++
src/coredump.h | 13
Fetching virtual memory areas through /proc/pid/maps and storing it in a
linked list in order to populate the program headers and file maps.
Signed-off-by: Janani Venkataraman janan...@linux.vnet.ibm.com
---
src/coredump.c |8 +
src/coredump.h | 11 ++
src/proc.c | 95
Getting number of threads and their respective IDs through /proc/pid/stat and
/proc/pid/task.
The threads are then seized and interrupted. After the dump is taken they are
detached.
Signed-off-by: Janani Venkataraman janan...@linux.vnet.ibm.com
---
src/coredump.c | 149
Hi all,
The following series implements an infrastructure for capturing the core of an
application without disrupting its process.
Kernel Space Approach:
1) Posted an RFD to LKML explaining the various kernel-methods being analysed.
https://lkml.org/lkml/2013/9/3/122
2) Went ahead to
Populates the prps_info by reading /proc/pid/stat and /proc/pid/cmdline.
Signed-off-by: Janani Venkataraman janan...@linux.vnet.ibm.com
---
src/coredump.h | 10 +
src/elf-compat.h | 48 +
src/elf.c| 58
We handle SIGTERM on the child, by sending a message to the client and then
closing the socket opened for that connection.
Signed-off-by: Janani Venkataraman janan...@linux.vnet.ibm.com
---
src/coredump.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/src/coredump.c
1 - 100 of 2032 matches
Mail list logo
