On Thu, Jun 01, 2017 at 04:28:55PM +0800, Jia-Ju Bai wrote:
> The driver may sleep under a spin lock, and the function call path is:
> post_one_send (acquire the lock by spin_lock_irqsave)
> init_send_wqe
> copy_from_user --> may sleep
>
> To fix it, the lock is released before copy_from_use
On Thu, May 18, 2017 at 08:49:00AM +0800, Peter Chen wrote:
> Some hard-wired USB devices need to do power sequence to let the
> device work normally, the typical power sequence like: enable USB
> PHY clock, toggle reset pin, etc. But current Linux USB driver
> lacks of such code to do it, it may c
This patchset adds PMU driver for Cavium's ThunderX2 SoC UNCORE devices.
The SoC has PMU support in its L3 cache controller (L3C) and in the
DDR4 Memory Controller (DMC).
v3:
- fixed warning reported by kbuild robot
v2:
- rebased to 4.12-rc1
- Removed Arch VULCAN dependency
-
This patch adds a perf driver for the PMU UNCORE devices DDR4 Memory
Controller(DMC) and Level 3 Cache(L3C).
Signed-off-by: Ganapatrao Kulkarni
---
drivers/perf/Kconfig | 8 +
drivers/perf/Makefile| 1 +
drivers/perf/thunderx2_pmu.c | 968 +
Documentation for the UNCORE PMUs on Cavium's ThunderX2 SoC.
The SoC has PMU support in its L3 cache controller (L3C) and in the
DDR4 Memory Controller (DMC).
Signed-off-by: Ganapatrao Kulkarni
---
Documentation/perf/thunderx2-pmu.txt | 60
1 file changed, 60
On Thu, May 18, 2017 at 08:48:58AM +0800, Peter Chen wrote:
> We have an well-known problem that the device needs to do some power
> sequence before it can be recognized by related host, the typical
> example like hard-wired mmc devices and usb devices.
>
> This power sequence is hard to be descri
On Mon, Jun 05, 2017 at 02:57:49PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> include/uapi/linux/tty.h
>
> between commit:
>
> 8a8dabf2dd68 ("tty: handle the case where we cannot restore a line
> discipline")
>
> from
On Mon, Jun 05, 2017 at 06:52:27AM +0200, Mike Galbraith wrote:
> This is just in case. While it works, I consider it to be diagnostic
> data for those unfortunate enough to be intimate with tty locking :)
Can you redo this against 4.12-rc4 which has the original tty locking
patch reverted?
than
On Sat 03-06-17 10:24:40, Wei Yang wrote:
> Hi, Michal
>
> Just go through your patch.
>
> I have one question and one suggestion as below.
>
> One suggestion:
>
> This patch does two things to me:
> 1. Replace __GFP_REPEAT with __GFP_RETRY_MAYFAIL
> 2. Adjust the logic in page_alloc to provide
On Sun, Jun 04, 2017 at 09:15:03PM +0300, Andy Shevchenko wrote:
> On Sun, Jun 4, 2017 at 6:06 PM, Mika Westerberg
> wrote:
> > On Sun, Jun 04, 2017 at 06:00:02PM +0300, Mika Westerberg wrote:
> >> On Sun, Jun 04, 2017 at 03:52:29PM +0200, Lukas Wunner wrote:
> >> > On Fri, Jun 02, 2017 at 05:05:0
On Mon, Jun 05, 2017 at 07:13:50AM +0100, Al Viro wrote:
> On Sun, Jun 04, 2017 at 12:42:52AM +0900, Greg Kroah-Hartman wrote:
> > On Sat, Jun 03, 2017 at 09:32:55AM +0200, Adam Borowski wrote:
> > > Hi!
> > > In a recent discussion, Linus and Al Viro said quite a bit of expletives
> > > about __pu
On Mon, Jun 05, 2017 at 09:26:35AM +0800, Jia-Ju Bai wrote:
> Last patch lacks code explanation, and it is included in this patch.
That should go below the --- line, as a 'v2' patch. Please fix it up so
I don't have to hand-edit this and resend.
Please read Documentation/SubmittingPatches for ho
On 2017-06-03 00:01, Stephen Boyd wrote:
On 06/01, kgu...@codeaurora.org wrote:
On 2017-05-31 07:14, Stephen Boyd wrote:
>On 05/30, Kiran Gunda wrote:
>>diff --git a/drivers/spmi/spmi-pmic-arb.c
>>b/drivers/spmi/spmi-pmic-arb.c
>>index 7201611..6320f1f 100644
>>--- a/drivers/spmi/spmi-pmic-arb.c
On 2017-06-02 23:59, Stephen Boyd wrote:
On 06/01, kgu...@codeaurora.org wrote:
>>@@ -209,23 +210,24 @@ static void pa_read_data(struct
>>spmi_pmic_arb_dev *dev, u8 *buf, u32 reg, u8 bc)
>> * @buf: buffer to write. length must be bc + 1.
>> */
>> static void
>>-pa_write_data(struct spmi_
The 'linkup' variable would always increment by one whether the link
status is true or not. Therefore, this patch fixes the return value in
mtk_pcie_parse_and_add_res() and removes unnecessary 'linkup' variable.
Signed-off-by: Ryder Lee
---
drivers/pci/host/pcie-mediatek.c | 8
1 file c
On Sat, Jun 3, 2017 at 10:59 AM, Brendan Higgins
wrote:
> Added device tree binding documentation for Aspeed I2C Interrupt
> Controller.
>
> Signed-off-by: Brendan Higgins
> Acked-by: Rob Herring
Acked-by: Joel Stanley
Hi,
On 6/4/2017 12:25 AM, Christian Lamparter wrote:
> On Saturday, June 3, 2017 12:57:50 PM CEST Varadarajan Narayanan wrote:
>> Add initial pinctrl driver to support pin configuration with
>> pinctrl framework for ipq8074.
>>
>> Signed-off-by: Manoharan Vijaya Raghavan
>> Signed-off-by: Varadar
Hi,
Chunyan Zhang writes:
>> Maybe that's why they consider it an extra overhead? Have you considered
>> off-loading raw data for further post processing?
>
> Yes, that's also the way off-loading function trace has been implemented now.
> And like you said below, I also believe we can do the sim
2017-06-05 15:05 GMT+09:00 Masahiro Yamada :
> I tested the code above, and it worked fine.
>
> Could you send v3? Then, I will apply it soon.
>
> Or, if you are not reluctant to do so,
> may I modify your patch like above?
I meant "if you are reluctant to do so..."
--
Best Regards
Masahiro
In P9, OCC(On Chip Controller) can be sent commands inband via shared
memory based command response interface. This patch adds a platform
driver to support the OCC command-response interface.
The skiboot patch for the interface is posted here:
https://lists.ozlabs.org/pipermail/skiboot/2017-June/
In P9, OCC (On-Chip-Controller) supports shared memory based
commad-response interface. Within the shared memory there is an OPAL
command buffer and OCC response buffer that can be used to send
inband commands to OCC. This patch adds a platform driver to support
the command/response interface betwe
This patch adds support to get a unique token for async completion
requests. This will be used for creating non-repititive request
handles for consecutive requests in OPAL-OCC command/response
interface.
Signed-off-by: Shilpasri G Bhat
---
arch/powerpc/include/asm/opal.h | 1 +
arch
On Fri, Jun 2, 2017 at 5:50 PM, Tobias Klauser wrote:
> struct irq_domain_ops is not modified, so it can be made const.
>
> Cc: Joel Stanley
> Signed-off-by: Tobias Klauser
Acked-by: Joel Stanley
Cheers,
Joel
> ---
> drivers/irqchip/irq-aspeed-vic.c | 2 +-
> 1 file changed, 1 insertion(+)
On Sun, Jun 04, 2017 at 12:42:52AM +0900, Greg Kroah-Hartman wrote:
> On Sat, Jun 03, 2017 at 09:32:55AM +0200, Adam Borowski wrote:
> > Hi!
> > In a recent discussion, Linus and Al Viro said quite a bit of expletives
> > about __put_user() and __get_user(), that it's a bad interface that's
> > alm
Hi Christoph,
After merging the uuid tree, today's linux-next build (arm
multi_v7_defconfig and x86_64 allmodconfig) produced these warnings:
In file included from drivers/usb/dwc2/core.h:45:0,
from drivers/usb/dwc2/core_intr.c:53:
drivers/usb/dwc2/hw.h:230:0: warning: "GUID" red
On Tue, 2017-05-16 at 14:53 +0200, Roberto Sassu wrote:
> Through the new interface binary_kexec_runtime_measurements, it will be
> possible to read the same content returned by binary_runtime_measurements,
> with the kexec header prepended.
>
> The new interface has been added for testing ima_res
Hi Robert,
2017-05-07 0:57 GMT+09:00 Masahiro Yamada :
> Hi Robert,
>
> 2017-05-04 15:29 GMT+09:00 Robert Jarzmik :
>> Masahiro Yamada writes:
>>
>>> Hi Robert,
>>>
>>> 2017-04-26 5:07 GMT+09:00 Robert Jarzmik :
Masahiro Yamada writes:
> Hi Robert,
>> diff --git a/scripts/tags
Since 7e60d1b427c51cf2525e5d736a71780978cfb828, the ELF_ET_DYN_BASE
for powerpc applications has been set to 512MB.
Recently there have been several reports of applications SEGV'ing
and newer version of glibc also SEGV'ing (while testing) when using the
following
test method:
LD_LIBRARY_PATH
Hi Marc,
On Mon, May 22, 2017 at 10:25 PM, Chen-Yu Tsai wrote:
> On Mon, May 22, 2017 at 5:41 PM, Icenowy Zheng wrote:
>>
>>
>> 于 2017年5月22日 GMT+08:00 下午5:39:22, Marc Zyngier 写到:
>>>On 18/05/17 08:16, Icenowy Zheng wrote:
Add support for the newly imported compatible for the A64 R_INTC in
On Tue, 2017-05-16 at 14:53 +0200, Roberto Sassu wrote:
> Through the new interface restore_kexec_list, it will be possible
> to restore a measurements list, previously read from
> binary_kexec_runtime_measurements.
For development, this was fine. You were able to save and restore the
measurement
Hi Roberto,
On Tue, 2017-05-16 at 14:53 +0200, Roberto Sassu wrote:
> ima_parse_buf() takes as input the buffer start and end pointers, and
> stores the result in a static array of ima_field_data structures,
> where the len field contains the length parsed from the buffer, and
> the data field con
Balbir Singh writes:
> On Mon, May 29, 2017 at 6:00 PM, Christophe LEROY
> wrote:
>> Le 25/05/2017 à 18:45, kbuild test robot a écrit :
>>> All errors (new ones prefixed by >>):
>>>
> kernel//power/snapshot.c:40:28: fatal error: asm/set_memory.h: No such
> file or directory
>>>
>>> #
On Sun, Jun 04, 2017 at 12:36:48PM +0200, Johannes Thumshirn wrote:
> Allow overriding the announced NVMe Version of a via configfs.
>
> This is particularly helpful when debugging new features for the host
> or target side without bumping the hard coded version (as the target
> might not be fully
On Sun, Jun 04, 2017 at 06:04:53PM +0800, joeyli wrote:
> Hi Andy,
>
> Thanks for your help to review my patch.
>
> On Sat, Jun 03, 2017 at 08:37:51PM +0300, Andy Shevchenko wrote:
> > On Sat, Jun 3, 2017 at 8:20 PM, Lee, Chun-Yi
> > wrote:
> > > In hotplug logic, it always indicates non-specif
> + }
> + len = NVME_NIDT_UUID_LEN;
> + memcpy(ns->uuid, data + pos + sizeof(*cur), len);
> + break;
> + default:
> + dev_warn(ns->ctrl->dev,
> + "Invalid Nam
On Tue, May 30, 2017 at 07:11:19PM +0300, Leonard Crestez wrote:
> Suspend and resume on imx6ull is currenty not working because of some
> missed checks where behavior should match imx6ul.
>
> Signed-off-by: Leonard Crestez
> ---
> arch/arm/mach-imx/mxc.h | 6 ++
> arch/arm/mach-imx/pm-i
Hi Boris,
Thank you very much for your detailed review.
I just comming back from busy week for conference and started to look it.
I have a question regarding to the following comment.
>> static int toshiba_nand_init(struct nand_chip *chip)
>> {
>> +struct mtd_info *mtd = nand_to_mtd(chip);
I think this needs to zero the remainder of the 4k
buffer, quoting the spec:
"The controller may return any number of variable length Namespace
Identification Descriptor structures that fit into the 4096 byte Identify
payload. All remaining bytes after the namespace identification descriptor
struc
Fix inconsistent format and spelling in hash tests error messages.
Signed-off-by: Gilad Ben-Yossef
---
crypto/testmgr.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/crypto/testmgr.c b/crypto/testmgr.c
index 6f5f3ed..8c68c99 100644
--- a/crypto/testmgr.c
On Sun, Jun 04, 2017 at 05:59:06PM +0300, Sagi Grimberg wrote:
>> +struct nvme_ns_identifier_hdr {
>> +__u8 nidt;
>> +__u8 nidl;
>> +__le16 reserved;
>> +};
>
> Nit: _hdr is usually associated with a message or alike.
>
> Maybe nvme_ns_id_desc is more consistent with the spec language
On Sun, Jun 04, 2017 at 12:36:41PM +0200, Johannes Thumshirn wrote:
> The Namespace Identification Descriptor list is the only way a target
> can identify itself via the newly introduced UUID to the host (instead
> of the EUI-64 or NGUID).
s/instead/in addition/
> While I was already touching the
What about a little helper like this: ?
static u16 nvmet_copy_ns_identifier(struct nvmet_req *req, u8 type, u8 len,
void *id, off_t *off)
{
struct nvme_ns_identifier_hdr hdr = {
.nidt = type,
.nidl = len,
};
u16 status;
On 5/31/2017 18:50, Jani Nikula wrote:
From: Chris Wilson
An error during suspend (e100e_pm_suspend),
[ 429.994338] ACPI : EC: event blocked
[ 429.994633] e1000e: EEE TX LPI TIMER: 0011
[ 430.955451] pci_pm_suspend(): e1000e_pm_suspend+0x0/0x30 [e1000e] returns -2
[ 430.955454] dpm_run
Hi.
2017-05-23 22:34 GMT+09:00 Javier Martinez Canillas :
> The at24 driver allows to register I2C EEPROM chips using different vendor
> and devices, but the I2C subsystem does not take the vendor into account
> when matching using the I2C table since it only has device entries.
>
> But when match
[CC Andrew]
On Sun 04-06-17 13:01:09, Yu Zhao wrote:
> Saw need_resched() warnings when swapping on large swapfile (TBs)
> because continuously allocating many pages in swap_cgroup_prepare()
> took too long.
>
> We already cond_resched when freeing page in swap_cgroup_swapoff().
> Do the same for
On Fri, 2017-06-02 at 18:29 -0700, Brendan Higgins wrote:
> Added initial master support for Aspeed I2C controller. Supports
> fourteen busses present in AST24XX and AST25XX BMC SoCs by Aspeed.
>
> Signed-off-by: Brendan Higgins
I exercised this patch on an AST2500-based machine. The results wer
Hi Greg,
Today's linux-next merge of the staging tree got a conflict in:
include/uapi/linux/tty.h
between commit:
8a8dabf2dd68 ("tty: handle the case where we cannot restore a line
discipline")
from the tty tree and commit:
1ab92da32e37 ("staging: speakup: add tty-based comms functions
On Fri, 2017-06-02 at 18:29 -0700, Brendan Higgins wrote:
> The Aspeed 24XX/25XX chips share a single hardware interrupt across 14
> separate I2C busses. This adds a dummy irqchip which maps the single
> hardware interrupt to software interrupts for each of the busses.
>
> Signed-off-by: Brendan H
This is just in case. While it works, I consider it to be diagnostic
data for those unfortunate enough to be intimate with tty locking :)
---
V1 (925bb1ce47f4) changelog:
tty_insert_flip_string_fixed_flag() is racy against itself when called
from the ioctl(TCXONC, TCION/TCIOFF) path [1] and the f
Mon, Jun 05, 2017 at 02:57:21AM CEST, yanhaishu...@cmss.chinamobile.com wrote:
>We must free allocated skb when genlmsg_put() return fails.
>
>Fixes: 1555d204e743 ("devlink: Support for pipeline debug (dpipe)")
>Signed-off-by: Haishuang Yan
Acked-by: Jiri Pirko
Thanks.
On Tue, May 30, 2017 at 06:25:52PM +0200, Johan Hovold wrote:
> In an attempt to work around a pinmux over-allocation issue in driver
> core, commit dc5878abf49c ("usb: core: move root hub's device node
> assignment after it is added to bus") moved the device-tree node
> assignment until after the
Sun, Jun 04, 2017 at 11:44:13PM CEST, sudipm.mukher...@gmail.com wrote:
>The build of mips ar7_defconfig was failing with the error:
>../net/sched/act_api.c: In function 'tcf_action_goto_chain_init':
>../net/sched/act_api.c:37:18: error:
> implicit declaration of function 'tcf_chain_get'
>
On 17-05-17, 12:32, Viresh Kumar wrote:
> Hi,
>
> Here is the 7th version of the series and it looks very different from
> whatever is sent until now. Almost a rewrite.
Gentle reminder as 3 weeks have passed since this was last posted :)
@Kevin/Ulf: Any inputs ?
--
viresh
On Sat, Jun 3, 2017 at 10:59 AM, Brendan Higgins
wrote:
> Added device tree binding documentation for Aspeed I2C busses.
>
> Signed-off-by: Brendan Higgins
> Acked-by: Rob Herring
Acked-by: Joel Stanley
On Sat, Jun 3, 2017 at 10:59 AM, Brendan Higgins
wrote:
> Added initial master support for Aspeed I2C controller. Supports
> fourteen busses present in AST24XX and AST25XX BMC SoCs by Aspeed.
>
> Signed-off-by: Brendan Higgins
Reviewed-by: Joel Stanley
I have also tested this on an ast2500evb.
The A64 device tree file has some remnants of raw number references
to the CCU node, likely from when the CCU bindings and device tree
changes were first merged.
Convert these, and the R_CCU ones, to use the proper defined macros
from their respective device tree binding header files.
Signed-off-
Hi Maxime,
These are some clean up patches for 4.12. They convert raw number
references for the CCU and R_CCU nodes, from when the CCU/R_CCU stuff
was first added, to the defined macros in the device tree header files.
These affect the A64 and H3/H5.
These are based on our sunxi/fixes-for-4.12 b
Now that the R_CCU device tree binding headers have been merged, we
can convert the raw number references in the device trees to use the
defined macros.
Signed-off-by: Chen-Yu Tsai
---
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/
Hi, Benjamin
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: [WIP PATCH 3/4] ACPI: button: Let input filter out the LID events
>
> The input stack already filters out the LID events. So instead of
> filtering them out at the source, we can hook up after the input
> pr
2017-04-26 22:56 GMT+08:00 Paolo Bonzini :
> native_safe_halt enables interrupts, and you just shouldn't
> call rcu_irq_enter() with interrupts enabled. Reorder the
> call with the following local_irq_disable() to respect the
> invariant.
>
> Reported-by: Ross Zwisler
> Cc: sta...@vger.kernel.org
The driver may sleep under a write spin lock, and the function
call path is:
cachefiles_mark_object_active (acquire the lock by write_lock)
cachefiles_printk_object
kmalloc(GFP_NOIO) --> may sleep
cachefiles_mark_object_buried (acquire the lock by write_lock)
cachefiles_printk_object
k
Hi RT Devs,
I enabled cpu/cpuacct/cpuset/devices/freezer subsystems in cgroup.
Attach serveral thread ids to these systems' tasks file frequently
last 4 or 5 hours(start process, echo thread ids to tasks, stop
process). The system will hung, no response to user keyboard input.
Through I have ena
Follow the recent trend for the license description, and fix the wrongly
stated X11 to MIT.
The X11 license text [1] is explicitly for the X Consortium and has a
couple of extra clauses. The MIT license text [2] is actually what the
current DT files claim.
[1] https://spdx.org/licenses/X11.html
Follow the recent trend for the license description, and fix the wrongly
stated X11 to MIT.
The X11 license text [1] is explicitly for the X Consortium and has a
couple of extra clauses. The MIT license text [2] is actually what the
current DT files claim.
[1] https://spdx.org/licenses/X11.html
Hi Finley,
On 2017/5/12 10:44, Finley Xiao wrote:
This adds the necessary data for handling eFuse on the rk322x.
Signed-off-by: Finley Xiao
---
Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt | 1 +
drivers/nvmem/rockchip-efuse.c | 4
2 files cha
These functions are simple convenience wrappers that call
wait_for_random_bytes before calling the respective get_random_*
function.
Signed-off-by: Jason A. Donenfeld
---
include/linux/net.h| 2 ++
include/linux/once.h | 2 ++
include/linux/random.h | 25 +
3 file
Otherwise, we might use bad random numbers which, particularly in the
case of IV generation, could be quite bad. It makes sense to use the
synchronous API here, because we're always in process context (as the
code is littered with GFP_KERNEL and the like).
Signed-off-by: Jason A. Donenfeld
Cc: Da
Ceph uses the RNG for various nonce generations, and it shouldn't accept
using bad randomness. So, we wait for the RNG to be properly seeded. We
do this by calling wait_for_random_bytes() in a function that is
certainly called in process context, early on, so that all subsequent
calls to get_random
It's not safe to use weak random data here, especially for the challenge
response randomness. Since we're always in process context, it's safe to
simply wait until we have enough randomness to carry out the
authentication correctly.
While we're at it, we clean up a small memleak during an error
co
This enables an important dmesg notification about when drivers have
used the crng without it being seeded first. Prior, these errors would
occur silently, and so there hasn't been a great way of diagnosing these
types of bugs for obscure setups. By adding this as a config option, we
can leave it o
Otherwise, we might be seeding the RNG using bad randomness, which is
dangerous.
Cc: Herbert Xu
Signed-off-by: Jason A. Donenfeld
---
crypto/rng.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/crypto/rng.c b/crypto/rng.c
index f46dac5288b9..e042437e64b4 100644
--- a/
This protocol uses lots of complex cryptography that relies on securely
generated random numbers. Thus, it's important that the RNG is actually
seeded before use. Fortuantely, it appears we're always operating in
process context (there are many GFP_KERNEL allocations and other
sleeping operations),
As discussed in [1], there is a problem with get_random_bytes being
used before the RNG has actually been seeded. The solution for fixing
this appears to be multi-pronged. One of those prongs involves adding
a simple blocking API so that modules that use the RNG in process
context can just sleep (i
This enables users of get_random_{bytes,u32,u64,int,long} to wait until
the pool is ready before using this function, in case they actually want
to have reliable randomness.
Signed-off-by: Jason A. Donenfeld
---
drivers/char/random.c | 41 +++--
include/linux
The driver may sleep under a spin lock, and the function call path is:
ubifs_change_lp (acquire the lock by spin_lock)
change_category
ubifs_remove_from_cat
remove_from_lpt_heap
dbg_check_heap
ubifs_lpt_lookup
ubifs_get_pnode
read_pnode
for SPI controllers on imx53 and later SoCs, there is HW issue when
work in slave mode, as new device type 'IMX53_ECSPI' has been added
for these SPI controllers which is compatible with 'fsl,imx53-ecspi'.
This patch updates DTS to make imx53 later SPI controller only be
compatibile with 'fsl,imx5
Different ECSPI controller has different fifosize and DMA capability,
instead of calling functions to identify these information by check
devtype. add fifo_size and has_dmamode to spi_imx_devtype_data.
so that these information can be directly accessed.
Signed-off-by: Jiada Wang
---
drivers/spi/
Changes in v3:
* renamed several variables for for better readability
* created spi_imx_pio_transfer_slave() for slave pio transfer
* added fifo_size, has_dmamode and has_slavemode in spi_imx_devtype_data
Changes in v2:
* re-workd i.MX ECSPI controller slave mode support based on Geert's work
Jia
ECSPI contorller for iMX53 and iMX6 has few hardware issues
comparing to iMX51.
The change add possibility to detect which controller is used
to apply possible workaround and limitations.
Signed-off-by: Jiada Wang
---
.../devicetree/bindings/spi/fsl-imx-cspi.txt | 1 +
drivers/spi/spi-imx
Previously i.MX SPI controller only works in Master mode.
This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI
controller to work also in Slave mode.
Currently SPI Slave mode support patch has the following limitations:
1. The stale data in RXFIFO will be dropped when the Slave does any new
The driver may sleep under a spin lock, and the function call path is:
ubifs_change_lp (acquire the lock by spin_lock)
change_category
ubifs_remove_from_cat
remove_from_lpt_heap
dbg_check_heap
ubifs_lpt_lookup
ubifs_read_nnode
kzalloc(GFP_NOFS
On Tue, May 30, 2017 at 06:25:48PM +0200, Johan Hovold wrote:
> Make sure to release any OF device-node reference taken when creating
> the USB device.
>
> Note that we currently do not hold a reference to the root hub
> device-tree node (i.e. the parent controller node).
>
> Fixes: 69bec7259853
On Sat, Jun 03, 2017 at 09:04:42AM +0100, David Howells wrote:
> Eric Biggers wrote:
>
> > This patch is in the "keys-fixes" branch now, but it doesn't remove
> > KEYS_COMPAT
> > from arch/arm64/Kconfig. David, can you fix it? Thanks!
>
> Done. See below.
>
> David
> ---
Looks good now, th
Hi,
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: [WIP PATCH 4/4] ACPI: button: Fix lid notification locks
>
> From: Lv Zheng
>
> acpi/button.c now contains the logic to avoid frequently replayed events
> which originally was ensured by using blocking notifier.
>
Hi David,
On Wed, 31 May 2017 16:58:48 +0200 David Sterba wrote:
>
> On Wed, May 31, 2017 at 02:29:20AM -0700, Omar Sandoval wrote:
> > diff --git a/fs/btrfs/free-space-tree.c b/fs/btrfs/free-space-tree.c
> > index fc0bd8406758..5abd3cd71144 100644
> > --- a/fs/btrfs/free-space-tree.c
> > +++ b/f
Hi Lee,
On Wed, 31 May 2017 12:23:32 +1000 Stephen Rothwell
wrote:
>
> After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> drivers/usb/typec/typec_wcove.c: In function 'wcove_typec_pr
> obe':
> drivers/usb/typec/typec_wcove.c:306:32: error: 'struct
Hi, Benjamin
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: [WIP PATCH 2/4] ACPI: button: remove the LID input node when the
> state is unknown
>
> Because of the variation of firmware implementation, there is a chance
> the LID state is unknown:
> 1. Some platforms
Hi Stephen,
On 3 June 2017 at 06:56, Stephen Boyd wrote:
> On 06/01, Chunyan Zhang wrote:
>> The value of property 'clock-cells' is not determined only by the number of
>> clock outputs in one clock node, it is actually determined by whether the
>> clock output in this node can be referenced dire
From: Haishuang Yan
Date: Sun, 4 Jun 2017 14:43:43 +0800
> Since iptunnel_pull_header() can call pskb_may_pull(),
> we must reload any pointer that was related to skb->head.
>
> Fixes: a09a4c8dd1ec ("tunnels: Remove encapsulation offloads on decap")
> Signed-off-by: Haishuang Yan
Applied and
From: "Jason A. Donenfeld"
Date: Sun, 4 Jun 2017 04:16:21 +0200
> Changes v9->v10:
>- Spaces to tabs on one line.
>- Added some acked-by, reviewed-by lines.
I wish in the future you would retain the entire change history, and
keep it in it's entirety here in the header postings. That l
On Sun, Jun 4, 2017 at 7:37 PM, David Carrillo-Cisneros
wrote:
> On Thu, May 25, 2017 at 1:09 AM, Jiri Olsa wrote:
>> On Tue, May 23, 2017 at 12:48:47AM -0700, David Carrillo-Cisneros wrote:
>>> As preparation for using header records in pipe mode, replace
>>> int fd with struct feat_fd fd in pri
From: Eric Dumazet
Date: Sat, 03 Jun 2017 09:29:25 -0700
> From: Eric Dumazet
>
> Alexander reported various KASAN messages triggered in recent kernels
>
> The problem is that ping sockets should not use udp_poll() in the first
> place, and recent changes in UDP stack finally exposed this old
From: Florian Fainelli
Date: Fri, 2 Jun 2017 22:05:23 -0700
> Commit 9520ed8fb841 ("net: dsa: use cpu_switch instead of ds[0]")
> replaced the use of dst->ds[0] with dst->cpu_switch since that is
> functionally equivalent, however, we can now run into an use after free
> scenario after unbinding
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in:
drivers/gpu/drm/i915/intel_dp.c
between commit:
8001b7541aa7 ("drm/i915/dp: rename rate_to_index() to intel_dp_rate_index()
and reuse")
from Linus' tree and commit:
3194102439f6 ("drm/i915/dp: use known correct array
Hi,
>-Original Message-
>From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
>Behalf Of Gerd Hoffmann
>Sent: Friday, June 02, 2017 11:24 PM
>To: Alex Williamson ; Chen, Xiaoguang
>
>Cc: Tian, Kevin ; intel-...@lists.freedesktop.org; linux-
>ker...@vger.kernel.org;
While activating the CMA area, we check to make sure that all the
PFNs in the range are inside the same zone. This is a requirement
for alloc_contig_range() to work. Any CMA area failing the check
is disabled for good. This happens silently right now making all
future cma_alloc() allocations failur
On Thu, May 25, 2017 at 1:09 AM, Jiri Olsa wrote:
> On Tue, May 23, 2017 at 12:48:47AM -0700, David Carrillo-Cisneros wrote:
>> As preparation for using header records in pipe mode, replace
>> int fd with struct feat_fd fd in print functions for all header
>> record types.
>>
>> Add offset and siz
On Thu, May 25, 2017 at 1:08 AM, Jiri Olsa wrote:
> On Tue, May 23, 2017 at 12:48:45AM -0700, David Carrillo-Cisneros wrote:
>> Now that writen takes a const buffer, use it in do_write instead
>> of duplicating readn functionality..
>
> readn?
Will fix.
>
> jirka
Hi, Benjamin
> From: Benjamin Tissoires [mailto:benjamin.tissoi...@redhat.com]
> Subject: [WIP PATCH 0/4] Rework the unreliable LID switch exported by ACPI
>
> Hi,
>
> Sending this as a WIP as it still need a few changes, but it mostly works as
> expected (still not fully compliant yet).
>
> So
Changed code indent to be tabs across whole driver
Found using checkpatch
Signed-off-by: Derek Robson
---
drivers/staging/ccree/ssi_cipher.c | 45 +-
drivers/staging/ccree/ssi_driver.c | 6 ++---
drivers/staging/ccree/ssi_driver.h | 6 ++---
drivers/
1 - 100 of 345 matches
Mail list logo
