On Tue, Jan 21, 2014 at 10:22 PM, Paul Gortmaker
paul.gortma...@windriver.com wrote:
None of these files are actually using any __init type directives
and hence don't need to include linux/init.h. Most are just a
left over from __devinit and __cpuinit removal, or simply due to
code getting
On Tue, Jan 21, 2014 at 10:23 PM, Paul Gortmaker
paul.gortma...@windriver.com wrote:
None of these files are actually using any __init type directives
and hence don't need to include linux/init.h. Most are just a
left over from __devinit and __cpuinit removal, or simply due to
code getting
From: Len Brown len.br...@intel.com
Linux suspend-to-RAM was unreliable when first developed,
and so sys_sync() was invoked inside the kernel at the
start of every suspend flow.
Today, many devices invoke suspend with
high reliability and high frequency.
They may not want to be forced to pay
the
On Tue, Jan 21, 2014 at 11:38 PM, Sherman Yin s...@broadcom.com wrote:
To be consistent with other Broadcom drivers, the Broadcom Capri pinctrl
driver and its related CONFIG option are renamed to bcm281xx.
Devicetree compatible string and binding documentation use
brcm,bcm11351-pinctrl to
On Wed, Jan 22, 2014 at 1:10 AM, Markus Mayer markus.ma...@linaro.org wrote:
The GPIO_CONTROL macro returns the control register offset when given a
GPIO number.
Update the argument name in the macro to reflect that it takes in a
GPIO number and not a bank.
Signed-off-by: Markus Mayer
On Wed, Jan 22, 2014 at 02:34:52PM +, Mel Gorman wrote:
On Wed, Jan 22, 2014 at 09:10:48AM -0500, Ric Wheeler wrote:
On 01/22/2014 04:34 AM, Mel Gorman wrote:
On Tue, Jan 21, 2014 at 10:04:29PM -0500, Ric Wheeler wrote:
One topic that has been lurking forever at the edges is the current
On Wed, Jan 22, 2014 at 1:10 AM, Markus Mayer markus.ma...@linaro.org wrote:
Rather than unlock/re-lock for every write access, unlock a GPIO when
it is requested and re-lock it when it is freed. As a result, the GPIO
helper functions no longer have to deal with unlocking and re-locking
the
Linus,
Please pull the following:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-linus
This contains a fix for a potential use-after-module-unload bug noticed by Al
and caching improvements for read-only fuse filesystems by Andrew Gallagher.
Thanks,
Miklos
Andrew
On Wed, Jan 22, 2014 at 09:21:40AM -0800, James Bottomley wrote:
On Wed, 2014-01-22 at 17:02 +, Chris Mason wrote:
On Wed, 2014-01-22 at 15:19 +, Mel Gorman wrote:
On Wed, Jan 22, 2014 at 09:58:46AM -0500, Ric Wheeler wrote:
On 01/22/2014 09:34 AM, Mel Gorman wrote:
On Wed,
On Wed, Jan 22, 2014 at 4:14 AM, Chris Ruehl chris.ru...@gtsys.com.hk wrote:
The offset to ICONFB was incorrect, this patch set the correct value 0x14.
dev_dbg in function imx1_write_2bit print the wrong address and had been
moved after address calculation.
Signed-off-by: Chris Ruehl
On Wed, Jan 22, 2014 at 4:14 AM, Chris Ruehl chris.ru...@gtsys.com.hk wrote:
The offset for the 2bit register calculate wrong, this patch
fixes the problem. The debugfs printout for oconf, iconfa, iconfb
now shows the real values.
Signed-off-by: Chris Ruehl chris.ru...@gtsys.com.hk
Markus:
At Tue, 21 Jan 2014 11:16:57 -0800,
Linus Torvalds wrote:
On Mon, Nov 25, 2013 at 4:39 PM, Mark Brown broo...@kernel.org wrote:
If you're OK with octopus merges for things like this I'll definitely
take another look at using them, the enormous stack of merge commits
always looks noisy
On Thu, Jan 23, 2014 at 12:11:04PM -0500, Dongsheng Yang wrote:
On 01/22/2014 11:00 PM, Steven Rostedt wrote:
Bah, I just noticed that TASK_NICE is in kernel/sched/sched.h not
include/linux/sched.h
Peter, is there a reason that task_nice() is not a static inline in
sched.h and have these
On Wed, Jan 22, 2014 at 10:13:59AM -0800, James Bottomley wrote:
On Wed, 2014-01-22 at 18:02 +, Chris Mason wrote:
On Wed, 2014-01-22 at 09:21 -0800, James Bottomley wrote:
On Wed, 2014-01-22 at 17:02 +, Chris Mason wrote:
[ I like big sectors and I cannot lie ]
I think I
On Wed, Jan 22, 2014 at 11:50:02AM -0800, Andrew Morton wrote:
On Wed, 22 Jan 2014 11:30:19 -0800 James Bottomley
james.bottom...@hansenpartnership.com wrote:
But this, I think, is the fundamental point for debate. If we can pull
alignment and other tricks to solve 99% of the problem is
On Thu, Jan 23, 2014 at 9:17 AM, Linus Walleij linus.wall...@linaro.org wrote:
On Tue, Jan 21, 2014 at 11:38 PM, Sherman Yin s...@broadcom.com wrote:
To be consistent with other Broadcom drivers, the Broadcom Capri pinctrl
driver and its related CONFIG option are renamed to bcm281xx.
On 01/23/2014 01:40 PM, Len Brown wrote:
From: Len Brown len.br...@intel.com
Linux suspend-to-RAM was unreliable when first developed,
and so sys_sync() was invoked inside the kernel at the
start of every suspend flow.
Today, many devices invoke suspend with
high reliability and high
On Thu, Jan 23, 2014 at 7:31 AM, Tony Prisk li...@prisktech.co.nz wrote:
Due to an assumption in the VT8500 pinctrl driver, the value passed
from devicetree for 'wm,pull' was not explicitly translated before
being passed to pinconf.
With changes to 'enum pin_config_param',
On 01/23/2014 03:26 AM, Peter Zijlstra wrote:
On Thu, Jan 23, 2014 at 12:11:04PM -0500, Dongsheng Yang wrote:
On 01/22/2014 11:00 PM, Steven Rostedt wrote:
Bah, I just noticed that TASK_NICE is in kernel/sched/sched.h not
include/linux/sched.h
Peter, is there a reason that task_nice() is not
Signed-off-by: Xiubo Li li.xi...@freescale.com
Cc: Nicolin Chen guangyu.c...@freescale.com
---
sound/soc/fsl/fsl_sai.c | 243 +---
sound/soc/fsl/fsl_sai.h | 47 +-
2 files changed, 150 insertions(+), 140 deletions(-)
diff --git
Due to an assumption in the VT8500 pinctrl driver, the value passed
from devicetree for 'wm,pull' was not explicitly translated before
being passed to pinconf.
Since v3.10, changes to 'enum pin_config_param', PIN_CONFIG_BIAS_PULL_(UP/DOWN)
no longer map 1-to-1 with the expected values in
The version of the kernel is 3.4.43.
Any reply is appreciated.
Best Regards!
Zhu Yanjun
On 01/23/2014 03:33 PM, zhuyj wrote:
Hi, Maintainers
We want to identify different ip tunnels.
For example, we use “ip tunnel add xxx” command in linux to create an
ipv4/6 tunnel interface,then,we can
Linus,
Could you please consider pulling the cross-rename patches. The git tree has a
conflict in arch/x86/syscalls/syscall_64.tbl where the syscall number needs to
be fixed. The patchset has been reviewed by Jan Kara and the man page and
usperpace API by Michael Kerrisk.
Due to an assumption in the VT8500 pinctrl driver, the value passed
from devicetree for 'wm,pull' was not explicitly translated before
being passed to pinconf.
Since v3.10, changes to 'enum pin_config_param', PIN_CONFIG_BIAS_PULL_(UP/DOWN)
no longer map 1-to-1 with the expected values in
On 01/17/2014 06:04 PM, Arnd Bergmann wrote:
On Thursday 16 January 2014, Mark Brown wrote:
On Thu, Jan 16, 2014 at 12:19:00PM +0100, Arnd Bergmann wrote:
1. Other platforms also require the syscon driver to be active before
the regular device driver probing starts. Michal Simek has the same
On Thursday, January 23, 2014 2:20 AM, Jenny TC wrote:
This patch introduces BQ24261 charger driver. The driver makes use of power
supply charging driver to setup charging. So the driver does hardware
abstraction and handles h/w specific corner cases. The charging logic resides
with power
On 23/01/14 21:43, Linus Walleij wrote:
On Thu, Jan 23, 2014 at 7:31 AM, Tony Prisk li...@prisktech.co.nz wrote:
Due to an assumption in the VT8500 pinctrl driver, the value passed
from devicetree for 'wm,pull' was not explicitly translated before
being passed to pinconf.
With changes to
On Thursday, January 23, 2014 2:20 AM, Jenny TC wrote:
Add new power supply properties for input current, charge termination
current, min and max temperature
POWER_SUPPLY_PROP_TEMP_MIN - minimum operatable temperature
POWER_SUPPLY_PROP_TEMP_MAX - maximum operatable temperature
On Wed, Jan 15, 2014 at 08:24:18PM -0500, Matthew Wilcox wrote:
This series of patches add support for XIP to ext4. Unfortunately,
it turns out to be necessary to rewrite the existing XIP support code
first due to races that are unfixable in the current design.
Since v4 of this patchset,
of_pwm_n_cells for the of_xlate handler is stored in struct pwm_chip,
but it is only ever used by the of_xlate handler itsel. Remove
of_pwm_n_cells from struct pwm_chip and let the handler do the argument
count checking to simplify the code.
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
---
Let of_pwm_simple_xlate behave like of_pwm_xlate_with_flags when
the argument count is 3. This makes of_pwm_xlate_with_flags unncessary.
Signed-off-by: Sascha Hauer s.ha...@pengutronix.de
---
drivers/pwm/core.c| 30 ++
drivers/pwm/pwm-atmel-tcb.c | 1 -
Hi Mark,
I see a issue with one of the davinci boards, where regulator_get() fails
from this patch regulator: core: Provide a dummy regulator with full
constraints.
as I see regulator_get() supports dummy regulators by default.
So currently I am booting it traditional way (NON DT way) and
I thinking more of the following. I haven't tested it, but it has a negative
diffstat, so it must be good ;)
Sascha
Sascha Hauer (2):
PWM: let of_xlate handlers check args count
PWM: handle additional flags in
On Sat, 18 Jan, at 12:48:13PM, Borislav Petkov wrote:
From: Borislav Petkov b...@suse.de
Hi all,
this is the latest incarnation which should hopefully work just fine. It
tpasses esting at least on all our boxes so we have *some* coverage.
It took us a long time to debug the unmapping
* Kees Cook keesc...@chromium.org wrote:
Include kASLR offset in VMCOREINFO ELF notes to assist in debugging.
Signed-off-by: Eugene Surovegin surove...@google.com
Signed-off-by: Kees Cook keesc...@chromium.org
The signoff sequence is weird. If this came from Eugene then the patch
is
On 01/23/2014 01:44 PM, Jingoo Han wrote:
On Wednesday, January 22, 2014 6:36 PM, Jani Nikula wrote:
On Mon, 20 Jan 2014, Liu Ying ying@freescale.com wrote:
We don't have to turn backlight on/off everytime a blanking
or unblanking event comes because the backlight status may
have already
From: Lad, Prabhakar prabhakar.cse...@gmail.com
This patch drops CONFIG_REGULATOR_DUMMY as this obsolete.
Signed-off-by: Lad, Prabhakar prabhakar.cse...@gmail.com
---
arch/arm/configs/da8xx_omapl_defconfig |1 -
1 file changed, 1 deletion(-)
diff --git
The version of isci driver has not been updated for 2 years.
It was 83 isci commits ago. Suspend/resume support has been implemented
and many bugs have been fixed since 1.1. Now update the version to 1.2.
Signed-off-by: Lukasz Dorau lukasz.do...@intel.com
Cc: sta...@vger.kernel.org
---
On Mon 2014-01-20 14:54:12, Linus Torvalds wrote:
So I pulled this, but one question:
On Mon, Jan 20, 2014 at 8:47 AM, H. Peter Anvin h...@zytor.com wrote:
+config RANDOMIZE_BASE
+ bool Randomize the address of the kernel image
+ depends on RELOCATABLE
+ depends on
On Thursday, January 23, 2014 10:39 AM Lukasz Dorau lukasz.do...@intel.com
wrote:
The version of isci driver has not been updated for 2 years.
It was 83 isci commits ago. Suspend/resume support has been implemented
and many bugs have been fixed since 1.1. Now update the version to 1.2.
On Wed, Jan 22, 2014 at 10:17:40PM +0100, Markus Trippelsdorf wrote:
Yes. Thanks Peter.
Ah much simpler patch that should have the same effect:
---
Subject: sched/x86/tsc: Initialize multiplier to 0
From: Peter Zijlstra pet...@infradead.org
Date: Wed, 22 Jan 2014 22:08:14 +0100
Since we keep
The version of isci driver has not been updated for 2 years.
It was 83 isci commits ago. Suspend/resume support has been implemented
and many bugs have been fixed since 1.1. Now update the version to 1.2.
Signed-off-by: Lukasz Dorau lukasz.do...@intel.com
Signed-off-by: Dave Jiang
On 01/23/2014 05:27 PM, Liu Ying wrote:
On 01/23/2014 01:44 PM, Jingoo Han wrote:
On Wednesday, January 22, 2014 6:36 PM, Jani Nikula wrote:
On Mon, 20 Jan 2014, Liu Ying ying@freescale.com wrote:
We don't have to turn backlight on/off everytime a blanking
or unblanking event comes
On Thu, Jan 23, 2014 at 02:49:25PM +0800, Alex Shi wrote:
On 01/23/2014 02:10 AM, Jason Low wrote:
P64(avg_idle);
+ P64(max_idle_balance_cost);
#endif
P(ttwu_count);
Not also the per-sd value in sd_alloc_ctl_domain_table() ?
Yeah, tracking the
On Thu, Jan 23, 2014 at 02:33:25AM +0400, Cyrill Gorcunov wrote:
On Wed, Jan 22, 2014 at 11:19:28PM +0400, Cyrill Gorcunov wrote:
commit. Test case was simple -- try and open the large file described in
the bug. I did not investigate the patch itself as I'm just reporting
the results of
From: Lad, Prabhakar prabhakar.cse...@gmail.com
In the gen_pool_dma_alloc() the dma pointer can be NULL
and while assigning gen_pool_virt_to_phys(pool, vaddr) to
dma caused the following crash on da850 evm,
Unable to handle kernel NULL pointer dereference at virtual address
pgd =
On 2014.01.23 at 10:48 +0100, Peter Zijlstra wrote:
On Wed, Jan 22, 2014 at 10:17:40PM +0100, Markus Trippelsdorf wrote:
Ah much simpler patch that should have the same effect:
Yes. FWIW it also seems to be fine.
--
Markus
--
To unsubscribe from this list: send the line unsubscribe
On Thu, Jan 23, 2014 at 11:01:00AM +0100, Markus Trippelsdorf wrote:
On 2014.01.23 at 10:48 +0100, Peter Zijlstra wrote:
On Wed, Jan 22, 2014 at 10:17:40PM +0100, Markus Trippelsdorf wrote:
Ah much simpler patch that should have the same effect:
Yes. FWIW it also seems to be fine.
On Wed, Jan 22, 2014 at 04:33:55PM -0500, Waiman Long wrote:
+/**
+ * queue_read_unlock - release read lock of a queue rwlock
+ * @lock : Pointer to queue rwlock structure
+ */
+static inline void queue_read_unlock(struct qrwlock *lock)
+{
+ /*
+ * Atomically decrement the reader
Hi Prabhakar,
On 23 January 2014 15:26, Prabhakar Lad prabhakar.cse...@gmail.com wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
In the gen_pool_dma_alloc() the dma pointer can be NULL
and while assigning gen_pool_virt_to_phys(pool, vaddr) to
dma caused the following crash on da850
On Thu, Jan 23, 2014 at 5:48 AM, Xiubo Li li.xi...@freescale.com wrote:
static int fsl_sai_set_dai_sysclk(struct snd_soc_dai *cpu_dai,
int clk_id, unsigned int freq, int dir)
{
- struct fsl_sai *sai = snd_soc_dai_get_drvdata(cpu_dai);
int ret;
if
Hi Amit,
From: Amit Grover [mailto:amit.gro...@samsung.com]
Sent: Monday, December 30, 2013 11:43 AM
This patch adds Controls to set Horizontal and Vertical search range
for Motion Estimation block for Samsung MFC video Encoders.
Signed-off-by: Swami Nathan swaminat...@samsung.com
Hello All,
On 15 January 2014 14:47, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
This patch set adds use of clk_prepare/clk_unprepare as
required by generic clock framework.
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
Hello All,
On 15 January 2014 14:46, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
This patch adds the device tree node for SSS module
found on Exynos5420 and Exynos5250
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
Reviewed-by: Tomasz Figa t.f...@samsung.com
TO:
Hello All,
On 15 January 2014 14:44, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
From: Naveen Krishna Ch ch.nav...@samsung.com
This patch uses the platform_get_irq() instead of the
platform_get_irq_byname(). Making feeder control interrupt
as resource 0 and hash interrupt as 1.
Hello All,
On 15 January 2014 14:47, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
This patch adds code to validate iv buffer before trying to
memcpy the contents
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
---
Changes since v3:
None
drivers/crypto/s5p-sss.c |
Hello All,
On 15 January 2014 14:46, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
This patch adds gating clock for SSS(Security SubSystem)
module on Exynos5250/5420.
Signed-off-by: Naveen Krishna Chatradhi ch.nav...@samsung.com
TO: linux-samsung-...@vger.kernel.org
TO: Tomasz Figa
Hello All,
On 15 January 2014 14:44, Naveen Krishna Chatradhi
ch.nav...@samsung.com wrote:
This patch adds device tree support to the s5p-sss.c crypto driver.
Also, Documentation under devicetree/bindings added.
Signed-off-by: Naveen Krishna Ch ch.nav...@samsung.com
CC: Herbert Xu
Hi,
On 23/01/14 11:11, Kamil Debski wrote:
diff --git a/drivers/media/platform/s5p-mfc/s5p_mfc_enc.c
b/drivers/media/platform/s5p-mfc/s5p_mfc_enc.c
index 4ff3b6c..a02e7b8 100644
--- a/drivers/media/platform/s5p-mfc/s5p_mfc_enc.c
+++ b/drivers/media/platform/s5p-mfc/s5p_mfc_enc.c
@@
Hi,
In the context of solving the below original issue, I came across
below error while I was running sudo make install. Wondering what
the below error means?
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for
module r8169
-Madhu
On Wed, Jan 22, 2014 at 11:11 PM, Mark
Hi Sachin,
On Thu, Jan 23, 2014 at 3:38 PM, Sachin Kamat sachin.ka...@linaro.org wrote:
Hi Prabhakar,
On 23 January 2014 15:26, Prabhakar Lad prabhakar.cse...@gmail.com wrote:
From: Lad, Prabhakar prabhakar.cse...@gmail.com
In the gen_pool_dma_alloc() the dma pointer can be NULL
and while
On Wed, 22 Jan 2014, Linus Torvalds wrote:
But refcounting seems like an overkill for this - there is exactly one
fanotify_response_event structure iff it is a permission event. So
something like the (completely untested) attached patch should fix the
problem. But I agree it's a bit ugly
This this patch fix kiocb_cancel() function.
If cancel() function ends successfully:
- kiocb request is removed from ctx-active_reqs,
- new event is added to ring buffer (this behavior is described in comment
in io_cancel function, but was not implemented)
- kiocb_free function is called
-
Hi,
(Adding missing devicetre ML list at CC.)
On 15/01/14 10:14, Naveen Krishna Chatradhi wrote:
This patch adds device tree support to the s5p-sss.c crypto driver.
Also, Documentation under devicetree/bindings added.
Signed-off-by: Naveen Krishna Ch ch.nav...@samsung.com
CC: Herbert Xu
On Thu, Jan 23, 2014 at 02:33:25AM +0400, Cyrill Gorcunov wrote:
On Wed, Jan 22, 2014 at 11:19:28PM +0400, Cyrill Gorcunov wrote:
commit. Test case was simple -- try and open the large file described in
the bug. I did not investigate the patch itself as I'm just reporting
the results of
Flash chip commands are issued using a set of predefined opcodes. These
are mostly the same for all flash devices, but do differ on occasion.
This patch supplies the majority of the key ones which will be used in
this driver.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 172
Version 4:
Tended to Brian's review comments
- Checkpatch acceptance
- MODULE_DEVICE_TABLE() name slip correction
- Timeout issue(s) resolved
- Potential infinite loop mitigated
- Code clarity suggests heeded
- Duplication with MTD core code removed
- Upgraded to
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.
Cc: devicet...@vger.kernel.org
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 Documentation/devicetree/bindings/mtd/st-fsm.txt
diff --git
When a read is issued by userspace the MFD framework calls back into
the driver to conduct the actual command issue and data extraction.
Here we provide the routines which do exactly that.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 99
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
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 b/drivers/mtd/devices/st_spi_fsm.c
index 1b0fa67..92071fa 100644
---
On Wed, Jan 22, 2014 at 08:47:58PM +, Stephen Boyd wrote:
On 01/21/14 10:37, Stephen Boyd wrote:
On 01/21/14 10:07, Will Deacon wrote:
Do you need isbs to ensure the pmresrn side-effects have happened, or are
the registers self-synchronising? Similarly for your other IMP DEF
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
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 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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 65
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
All supported platforms are able to pass specific configurations via
the Device Tree on boot. Here we add a function which is to be called
during the probing process which will extract them, or make other
assumptions based on capabilities provided.
Signed-off-by: Lee Jones lee.jo...@linaro.org
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
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/boot/dts/stih416-b2105.dts| 14 ++
When a write is requested by userspace the MFD framework calls back
into the driver to conduct the actual command issue and data send.
Here we provide the routines which do exactly that.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 150
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 b/drivers/mtd/devices/st_spi_fsm.c
index 88017d8..ddfff35 100644
---
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
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 eac23df..5f291dc 100644
--- a/drivers/mtd/devices/st_spi_fsm.c
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 5f291dc..1b0fa67 100644
---
static int fsl_sai_set_dai_sysclk(struct snd_soc_dai *cpu_dai,
int clk_id, unsigned int freq, int dir)
{
- struct fsl_sai *sai = snd_soc_dai_get_drvdata(cpu_dai);
int ret;
if (dir == SND_SOC_CLOCK_IN)
return 0;
-
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
On Thu, Jan 23, 2014 at 09:55:41AM +, Mel Gorman wrote:
On Thu, Jan 23, 2014 at 02:33:25AM +0400, Cyrill Gorcunov wrote:
On Wed, Jan 22, 2014 at 11:19:28PM +0400, Cyrill Gorcunov wrote:
commit. Test case was simple -- try and open the large file described in
the bug. I did not
When we write data to the FIFO the FSM Controller subsequently writes
that data out to the Serial Flash chip.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/mtd/devices/st_spi_fsm.c
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
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
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
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
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 53
The GOOGLE_SMI Kconfig symbol depends on DMI and selects EFI. This
causes problems on other archs when introducing DMI support that
depends on EFI, as it results in a recursive dependency:
arch/arm/Kconfig:1845:error: recursive dependency detected!
arch/arm/Kconfig:1845: symbol DMI depends on
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 17 +
1 file changed, 17
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
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
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
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.
Signed-off-by: Lee Jones lee.jo...@linaro.org
---
drivers/mtd/devices/st_spi_fsm.c | 27
1 - 100 of 1382 matches
Mail list logo
