On Sat, Nov 7, 2015 at 1:02 PM, Dilger, Andreas
wrote:
> On 2015/11/06, 10:19, "Shivani Bhardwaj" wrote:
>
>>Remove the prototype of function cfs_trace_free_string_buffer() as it is
>>no longer needed.
>
> These patches would be a lot more useful if the summary contained the name
> of the
Remove the prototype of the function ll_finish_md_op_data() as it is no
longer needed.
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/llite_internal.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/llite/llite_internal.h
Substitute standard function kfree() in place of the function
ll_finish_md_op_data().
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/llite_close.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/llite/llite_close.c
Remove the function ll_finish_md_op_data() and replace all its calls
with the standrd function ll_finish_md_op_data().
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/llite_lib.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git
Replace the calls of the function ll_finish_md_op_data() with the
standard function kfree().
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/llite_nfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/llite/llite_nfs.c
Substitute the standard function kfree() for the function
ll_finish_md_op_data().
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/symlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/llite/symlink.c
Change the calls of the function ll_finish_md_op_data() to the standard
function kfree().
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/xattr_cache.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/llite/xattr_cache.c
On 2015/11/5 13:12, Tejun Heo wrote:
6f60eade2433 ("cgroup: generalize obtaining the handles of and
notifying cgroup files") introduced cftype->file_offset so that the
handles for per-css file instances can be recorded. These handles
then can be used, for example, to generate file modified
Replace the calls of the function ll_finish_md_op_data() with thr
stndard function kfree().
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/namei.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git
Replace the calls of the function ll_finish_md_op_data() with the
standard function kfree().
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/file.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git
Replace the calls of the function ll_finish_md_op_data() with the
standard function kfree().
Signed-off-by: Shivani Bhardwaj
---
drivers/staging/lustre/lustre/llite/dir.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/lustre/lustre/llite/dir.c
This patchset removes an unnecessary wrapper function and replaces all
its calls in different files with the standard function that it wrapped.
Also, one patch removes its prototype.
After applying this patch, code becomes cleaner.
Shivani Bhardwaj (9):
Staging: lustre: dir: Replace function
On 7 November 2015 at 08:09, Ingo Molnar wrote:
>
> * Matt Fleming wrote:
>
>> On Fri, 06 Nov, at 07:55:50AM, Ingo Molnar wrote:
>> >
>> > 3) We should fix the EFI permission problem without relying on the
>> > firmware: it
>> > appears we could just mark everything R-X optimistically, and
On 2015/11/06, 10:19, "Shivani Bhardwaj" wrote:
>Remove the prototype of function cfs_trace_free_string_buffer() as it is
>no longer needed.
These patches would be a lot more useful if the summary contained the name
of the function being removed, rather than "remove function prototype" and
On Fri, Nov 06, 2015 at 04:24:07PM -0800, Greg Kroah-Hartman wrote:
> On Fri, Oct 30, 2015 at 08:13:11AM -0700, Dmitry Torokhov wrote:
> > On Fri, Oct 30, 2015 at 07:40:37AM -0700, Greg Kroah-Hartman wrote:
> > > On Fri, Oct 30, 2015 at 04:47:06AM -0700, Dmitry Torokhov wrote:
> > > > Many drivers
On Sat, Nov 07, 2015 at 01:35:36AM +0100, Richard Weinberger wrote:
> Am 04.11.2015 um 15:15 schrieb Octavian Purdila:
> > We could redefine the syscalls/libc symbols to call lkl_sys_ functions
> > in launch-lkl, e.g.:
> >
> > int opendir(const char *path)
> > {
> >return
On Thu, Oct 15, 2015 at 01:32:44PM +0200, Daniel Wagner wrote:
> The cpu hotplug state machine in smpboot.c is reusing the states from
> cpu.h. That is confusing when it comes to the CPU_DEAD_FROZEN usage.
> Paul explained to me that he was in need of an additional state
> for destinguishing
On Fri, Nov 06, 2015 at 02:46:30PM -0800, a...@linux-foundation.org wrote:
>
> The patch titled
> Subject: mm-hwpoison-adjust-for-new-thp-refcounting-fix
> has been added to the -mm tree. Its filename is
> mm-hwpoison-adjust-for-new-thp-refcounting-fix.patch
>
> This patch should soon
* Matt Fleming wrote:
> On Fri, 06 Nov, at 07:55:50AM, Ingo Molnar wrote:
> >
> > 3) We should fix the EFI permission problem without relying on the
> > firmware: it
> > appears we could just mark everything R-X optimistically, and if a
> > write fault
> > happens (it's pretty
* Matt Fleming wrote:
> On Thu, 05 Nov, at 01:33:10PM, Linus Torvalds wrote:
> >
> > And if this turns out to be due to EFI wanting those permissions, what
> > should
> > we do? People have talked about running the EFI callbacks in their own
> > private
> > page table setup, which sounds
* Andy Lutomirski wrote:
> On Thu, Nov 5, 2015 at 10:55 PM, Ingo Molnar wrote:
> >
> > * Linus Torvalds wrote:
> >
> >> On Wed, Nov 4, 2015 at 6:17 PM, Dave Jones wrote:
> >> > On Wed, Nov 04, 2015 at 05:31:59PM -0800, Linus Torvalds wrote:
> >> > >
> >> > > I don't have that later debug
On Fri, 6 Nov 2015, H. Peter Anvin wrote:
> On 11/06/15 15:17, Dan Williams wrote:
> >>
> >> Is it really required to do that on all cpus?
> >
> > I believe it is, but I'll double check.
> >
>
> It's required on all CPUs on which the DAX memory may have been dirtied.
> This is similar to the
On Wed, 04 Nov 2015 04:21:51 PST (-0800), pet...@infradead.org wrote:
> On Wed, Nov 04, 2015 at 12:41:06PM +0100, Peter Zijlstra wrote:
>> On Tue, Nov 03, 2015 at 11:46:30AM -0800, Palmer Dabbelt wrote:
>> > This has a "#ifdef CONFIG_*" that used to be exposed to userspace.
>> >
>> > The names in
On 11/5/2015 11:17 AM, Sinan Kaya wrote:
On 11/5/2015 7:05 AM, Vinod Koul wrote:
On Wed, Nov 04, 2015 at 09:42:46PM -0500, Sinan Kaya wrote:
Here is what I proposed.
- a common file that gets compiled into a module that wants to use
self-test with a public API. It can be called from
On Sat, 7 Nov 2015, Julian Calaby wrote:
> Hi Julia,
>
> On Fri, Nov 6, 2015 at 5:44 PM, Julia Lawall wrote:
> > On Fri, 6 Nov 2015, Julian Calaby wrote:
> >
> >> Hi Linus,
> >>
> >> On Fri, Nov 6, 2015 at 11:56 AM, Linus Torvalds
> >> wrote:
> >> > On Thu, Nov 5, 2015 at 4:43 PM, Linus
aarch64 and s390x support eBPF JIT too, correct document to reflect this and
avoid any confusion.
Signed-off-by: Yang Shi
---
Documentation/networking/filter.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/networking/filter.txt
Please ignore this one, forgot to cc to linux-arm-kernel list.
Sorry for the inconvenience.
Yang
On 11/6/2015 9:34 PM, Yang Shi wrote:
ARM64 JIT used FP (x29) as eBPF fp register, but FP is subjected to
change during function call so it may cause the BPF prog stack base address
change too.
ARM64 JIT used FP (x29) as eBPF fp register, but FP is subjected to
change during function call so it may cause the BPF prog stack base address
change too. Whenever, it pointed to the bottom of BPF prog stack instead of
the top.
So, when copying data via bpf_probe_read, it will be copied to (SP -
ARM64 JIT used FP (x29) as eBPF fp register, but FP is subjected to
change during function call so it may cause the BPF prog stack base address
change too. Whenever, it pointed to the bottom of BPF prog stack instead of
the top.
So, when copying data via bpf_probe_read, it will be copied to (SP -
On Fri, Nov 6, 2015 at 4:48 PM, Andy Lutomirski wrote:
> On Fri, Nov 6, 2015 at 4:16 PM, Kees Cook wrote:
>> On Fri, Nov 6, 2015 at 4:11 PM, Kees Cook wrote:
>>> On Fri, Nov 6, 2015 at 2:30 PM, Andy Lutomirski wrote:
On Fri, Nov 6, 2015 at 1:59 PM, Kees Cook wrote:
> Adding Ted, who
I sent these patches a few weeks ago. Due to the recent changes in pstore,
these patched might not apply anymore. So I refresh and resend them.
---
Changes in v2:
- refresh the patches.
---
Geliang Tang (3):
pstore: check PSTORE_FLAGS_FRAGILE in pstore_unregister
efi-pstore: implement
The original efivars_pstore_exit() is empty. I
1) add a bufsize check statement.
2) call pstore_unregister as it is defined now.
3) free the memory and set bufsize to 0.
Signed-off-by: Geliang Tang
---
drivers/firmware/efi/efi-pstore.c | 7 +++
1 file changed, 7 insertions(+)
diff --git
When PSTORE_FLAGS_FRAGILE flag is set, only kmsg is registered in
pstore_register. So, under these circumstances, only kmsg needs to
be unregistered in pstore_unregister.
Signed-off-by: Geliang Tang
---
fs/pstore/platform.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff
In my recent commit, I added '.owner = THIS_MODULE' in both
pstore_fs_type and pstore_file_operations to increase a reference count
when pstore filesystem is mounted and pstore file is opened.[1]
But, it's repetitive. There is no need to increase the opened reference
count. We only need to
From: SF Markus Elfring
Date: Fri, 6 Nov 2015 08:15:30 +0100
> From: Markus Elfring
> Date: Fri, 6 Nov 2015 08:00:22 +0100
>
> The of_node_put() function tests whether its argument is NULL and then
> returns immediately. Thus the test around the call is not needed.
>
> This issue was detected
On Friday 06 November 2015 03:55 PM, Peter Zijlstra wrote:
> On Fri, Nov 06, 2015 at 09:04:00PM +1100, Michael Ellerman wrote:
>> It's a perrenial request from our hardware PMU folks to be able to see the
>> raw
>> values of the PMU registers.
>>
>> I think partly it's so that they can verify
On Friday 06 November 2015 03:34 PM, Michael Ellerman wrote:
> On Fri, 2015-11-06 at 10:24 +0100, Peter Zijlstra wrote:
>> On Fri, Nov 06, 2015 at 12:57:17PM +0530, Madhavan Srinivasan wrote:
>>> On Thursday 05 November 2015 06:37 PM, Peter Zijlstra wrote:
On Thu, Nov 05, 2015 at 02:16:15AM
Hi,
Bike & Snow wrote on 11/06/2015 10:55 AM:
> Hello Vlad
>
> Excellent news on all the updates.
>
> Regarding this:
> - QLogic target driver has been significantly improved.
>
> Does that mean I should stop building the QLogic target driver from here?
> git://git.qlogic.com/scst-qla2xxx.git
On 11/07/2015 10:14 AM, Greg Kroah-Hartman wrote:
On Fri, Nov 06, 2015 at 10:17:29PM +0700, Ivan Safonov wrote:
goto is not needed here.
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/core/rtw_cmd.c | 25 +++--
1 file changed, 11 insertions(+), 14
Add efi_procfs in efi_rtc_ops to show rtc-efi info in /proc/driver/rtc.
Most of the code comes from efi_rtc_proc_show() in efirtc.
Signed-off-by: Geliang Tang
---
drivers/rtc/rtc-efi.c | 66 +++
1 file changed, 62 insertions(+), 4 deletions(-)
rtc-proc.c is not built as a module. Thus, rather than dealing with
THIS_MODULE's reference count, we should deal with rtc->owner's
reference count.
Signed-off-by: Geliang Tang
---
drivers/rtc/rtc-proc.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git
From: Michal Hocko
Date: Fri, 6 Nov 2015 17:46:57 +0100
> On Fri 06-11-15 11:19:53, Johannes Weiner wrote:
>> You might think sending these emails is helpful, but it really
>> isn't. Not only is it not contributing code, insights, or solutions,
>> you're now actively sabotaging someone else's
Hi Julia,
On Fri, Nov 6, 2015 at 5:44 PM, Julia Lawall wrote:
> On Fri, 6 Nov 2015, Julian Calaby wrote:
>
>> Hi Linus,
>>
>> On Fri, Nov 6, 2015 at 11:56 AM, Linus Torvalds
>> wrote:
>> > On Thu, Nov 5, 2015 at 4:43 PM, Linus Torvalds
>> > wrote:
>> >>
>> >> Not that this *matters*, but it's
If OF_ADDRESS is not configured, builds can fail with errors such as
drivers/net/ethernet/hisilicon/hns_mdio.c:
In function 'hns_mdio_bus_name':
drivers/net/ethernet/hisilicon/hns_mdio.c:411:3:
error: implicit declaration of function 'of_translate_address'
as currently seen when
On Fri, Nov 06, 2015 at 09:08:03PM -0500, y...@ccs.ornl.gov wrote:
> From: James Simmons
>
> The ioctl IOC_LIBCFS_PING_TEST has not been used in
> ages. The recent nidstring changes which moved all
> the nidstring operations from libcfs to the LNet
> layer but this ioctl code was still using an
I am desperately in need of your assistance. Please get back to me
--
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
On Fri, Nov 06, 2015 at 10:17:29PM +0700, Ivan Safonov wrote:
> goto is not needed here.
>
> Signed-off-by: Ivan Safonov
> ---
> drivers/staging/rtl8188eu/core/rtw_cmd.c | 25 +++--
> 1 file changed, 11 insertions(+), 14 deletions(-)
>
I've applied most of these patches,
W dniu 07.11.2015 o 07:33, Rob Herring pisze:
> On Fri, Oct 30, 2015 at 11:55:31AM +0530, Alim Akhtar wrote:
>> From: Thomas Abraham
>>
>> Add dt-binding documentation for s2mps15 PMIC device. The s2mps15 device
>> is similar to s2mps11/14 PMIC device and has 27 LDO and 10 buck regulators.
>>
On Fri, Nov 06, 2015 at 07:53:08PM -0700, Shuah Khan wrote:
> On 11/06/2015 12:18 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.2.6 release.
> > There are 110 patches in this series, all will be posted as a response
> > to this one. If anyone has any
Jarkko,
On Fri, Oct 16, 2015 at 09:40:22PM +0300, Jarkko Sakkinen wrote:
> Added a new function __compat_only_sysfs_link_group_to_kobj() that adds
> a symlink from attribute or group to a kobject. This needed for
> maintaining backwards compatibility with PPI attributes in the TPM
> driver.
>
>
On 11/06/2015 12:24 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.93 release.
> There are 24 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 11/06/2015 12:21 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.13 release.
> There are 86 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 11/06/2015 12:24 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.57 release.
> There are 37 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
Jarkko,
On Wed, Nov 04, 2015 at 10:17:05AM -0800, Jeremiah Mahler wrote:
> Jarkko, all,
>
> On Fri, Oct 16, 2015 at 09:40:23PM +0300, Jarkko Sakkinen wrote:
> > Moved PPI attributes to the character device directory. This aligns with
> > the sysfs guidelines and makes them race free because they
On 11/06/2015 12:18 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.2.6 release.
> There are 110 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On Fri, Nov 06, 2015 at 05:45:29PM -0800, Guenter Roeck wrote:
> On 11/06/2015 11:18 AM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 4.2.6 release.
> >There are 110 patches in this series, all will be posted as a response
> >to this one. If anyone has any
On Sun, Nov 01, 2015 at 02:12:29PM +0530, Paul Davies C wrote:
> Fix the following warning given by sparse:
>
> drivers/staging/lustre/lustre/obdclass/cl_lock.c:690:5: warning: symbol
> 'cl_lock_mutex_try' was not declared. Should it be static?
>
> Signed-off-by: Paul Davies C
> ---
>
On Fri, Nov 06, 2015 at 02:04:21AM +0530, Amitoj Kaur Chawla wrote:
> This patch moves extern declarations to respective header files.
>
> This patch also removes extern keyword from function declarations
> since functions have the extern specifier by default.
>
> Signed-off-by: Amitoj Kaur
On Fri, Nov 06, 2015 at 02:57:49PM +0100, Peter Zijlstra wrote:
> On Tue, Oct 27, 2015 at 09:46:53PM -0700, Joonwoo Park wrote:
> > @@ -1272,6 +1272,15 @@ void set_task_cpu(struct task_struct *p, unsigned
> > int new_cpu)
> > WARN_ON_ONCE(p->state != TASK_RUNNING && p->state != TASK_WAKING &&
On Sat, Nov 07, 2015 at 03:29:23AM +0530, Punit Vara wrote:
> This patch is to the linux_wlan.c file that fixes declaration of *wilc
> to remove following error while building it.
>
> make drivers/staging/wilc1000/linux_wlan.o
> drivers/staging/wilc1000/linux_wlan.c:1824:24: error: ‘wilc’
On Fri, Nov 06, 2015 at 10:18:17PM +, Simmons, James A. wrote:
> >All warnings (new ones prefixed by >>):
> >
> > In file included from include/linux/bitops.h:36:0,
> >from
> > drivers/staging/lustre/lustre/libcfs/../../include/linux/libcfs/linux/libcfs.h:44,
> >
On Fri, Oct 30, 2015 at 08:13:11AM -0700, Dmitry Torokhov wrote:
> On Fri, Oct 30, 2015 at 07:40:37AM -0700, Greg Kroah-Hartman wrote:
> > On Fri, Oct 30, 2015 at 04:47:06AM -0700, Dmitry Torokhov wrote:
> > > Many drivers create additional driver-specific device attributes when
> > > binding to
On Fri, Nov 06, 2015 at 07:57:46PM +0530, Ranjith wrote:
> BIT macro is used for defining bit location instead of shifting
> operator - coding style issue
>
> Signed-off-by: Ranjith T
> ---
> drivers/staging/comedi/drivers/ii_pci20kc.c | 70
> +--
> 1 file changed, 35
On 21/09/2015 at 11:33:18 +0200, Boris Brezillon wrote :
> When requested by a user, the PWM is assigned a default period and polarity
> extracted from the DT, the platform data or statically set by the driver.
> Those default values are currently stored in the period and polarity
> fields of the
Add bindings for audio driver in Broadcom Cygnus.
Signed-off-by: Lori Hikichi
Signed-off-by: Simran Rai
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
.../bindings/sound/brcm,cygnus-audio.txt | 54
1 file changed, 54 insertions(+)
create mode 100644
This patch adds Cygnus audio DMA driver. It supports playback and capture
modes and uses ringbuffers for data transfer.
Signed-off-by: Lori Hikichi
Signed-off-by: Simran Rai
Reviewed-by: Ray Jui
Reviewed-by: Arun Parameswaran
Reviewed-by: Scott Branden
---
sound/soc/bcm/Kconfig |9
Hi,
This patchset contains audio support for Broadcom's Cygnus SoC. It
contains DT bindings and core audio driver. The audio driver
supports both capture and playback of Audio PCM samples over I2S/TDM
interface and provides playback support over SPDIF interface.
This patchset is derived from a
This patch adds Cygnus audio DAI driver. It supports I2S, TDM and
SPDIF modes and uses three clocks derived from PLL.
This patchset has been tested on Cygnus wireless audio bcm958305K board.
Signed-off-by: Lori Hikichi
Signed-off-by: Simran Rai
Reviewed-by: Ray Jui
Reviewed-by: Arun
Richard/Thomas:
On Tue, 13 Oct 2015 06:59:26 -0700, Richard Cochran
wrote:
On Mon, Oct 12, 2015 at 11:45:21AM -0700, Christopher S. Hall wrote:
+struct ptp_sys_offset_precise {
+ unsigned int rsv[4];/* Reserved for future use. */
+ struct ptp_clock_time dev;
+ struct
From: James Simmons
The ioctl IOC_LIBCFS_PING_TEST has not been used in
ages. The recent nidstring changes which moved all
the nidstring operations from libcfs to the LNet
layer but this ioctl code was still using an
nidstring operation that was causing an circular
dependency loop between libcfs
Added sys-reboot node to the FSL's LS2080A SoC DT to leverage
the ARM-generic reboot mechanism for this SoC. This mechanism
is enabled through CONFIG_POWER_RESET_SYSCON.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY:
Changes in v6:
- Addressed comment from Javier Martinez Canillas
*
The old microframe scheduler was terribly hard to follow and (it seemed
to me) that it had some bugs in it.
Let's re-write it in a simpler, easier-to-read way. Hopefully this will
work better.
Note: no known problems are fixed by this patch, and in fact I can see
very little impact of the
This patch series addresses the following item from the TODO list
for the MC bus driver to exit staging:
* Interrupt support. For meaningful driver support we need
interrupts, and thus need message interrupt support by the bus
driver.
MC Bus MSI Support Architecture
FSL-MC is a bus type different from PCI and platform, so it needs
its own member in the msi_desc's union.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY
Changes in v3: none
Changes in v2:
- Addressed comment from Jiang Liu
* Added a dedicated structure for FSL-MC in struct msi_desc
THE MSI domain associated with a root DPRC object is
obtained form the device tree. Child DPRCs inherit
the parent DPRC MSI domain.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY
Changes in v3: none
Changes in v2: none
drivers/staging/fsl-mc/bus/dprc-driver.c | 39
The interrupt handler for DPRC IRQs is added. DPRC IRQs are
generated for hot plug events related to DPAA2 objects in a given
DPRC. These events include, creating/destroying DPAA2 objects in
the DPRC, changing the "plugged" state of DPAA2 objects and moving
objects between DPRCs.
Signed-off-by:
All the IRQs for DPAA2 objects in the same DPRC must use
the ICID of that DPRC, as their device Id in the GIC-ITS.
Thus, all these IRQs must share the same ITT table in the GIC.
As a result, a pool of IRQs with the same device Id must be
preallocated per DPRC (fsl-mc bus instance). So, the fsl-mc
Destroy mc_io in error path in dprc_probe() only if the mc_io was
created in this function.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY
Changes in v3: none
Changes in v2: none
- Addressed comment from Dan Carpenter
* Renamed goto error labels to indicate what the goto does
The DPRC built-in portal's mc_io is used to send commands to the MC
to program MSIs for MC objects. This is done by the
fsl_mc_msi_write_msg() callback, which is invoked by the generic MSI
layer with interrupts disabled. As a result, the mc_io used in
fsl_mc_msi_write_msg needs to be an atomic
Created an MSI domain for the fsl-mc bus-- including functions
to create a domain, find a domain, alloc/free domain irqs, and
bus specific overrides for domain and irq_chip ops.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY
Changes in v3: none
- Addressed comments from Marc Zyngier:
*
Initialize/Cleanup ITS-MSI support for the MC bus driver at driver
init/exit time. Associate an MSI domain with each DPAA2 child device.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY
Changes in v3: none
Changes in v2: none
drivers/staging/fsl-mc/bus/mc-bus.c | 12
1 file
Added platform-specific MSI support layer for FSL-MC devices.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY
Changes in v3: none
Changes in v2: none
drivers/staging/fsl-mc/bus/Makefile| 1 +
.../staging/fsl-mc/bus/irq-gic-v3-its-fsl-mc-msi.c | 127 +
Since an FSL-MC bus is a new bus type that is neither PCI nor
PLATFORM, we need a new domain bus token to disambiguate the
IRQ domain for FSL-MC MSIs.
Signed-off-by: J. German Rivera
---
CHANGE HISTORY
Changes in v3: none
Changes in v2: none
include/linux/irqdomain.h | 1 +
1 file changed, 1
Scan the corresponding DPRC container to get total count
of IRQs needed by all its child DPAA2 objects. Then,
preallocate a set of MSI IRQs with the DPRC's ICID
(GIT-ITS device Id) to populate the the DPRC's IRQ pool.
Each child DPAA2 object in the DPRC and the DPRC object itself
will allocate
On 11/06/2015 11:18 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.2.6 release.
There are 110 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 11/06/2015 11:21 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.1.13 release.
There are 86 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 11/06/2015 11:24 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.57 release.
There are 37 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 11/06/2015 11:24 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.93 release.
There are 24 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
When doing ebpf+kprobe on some hot TCP functions (e.g.
tcp_rcv_established), the kprobe_dispatcher shows up in 'perf report'.
In kprobe_dispatcher(), there is a lot of cache bouncing
in 'tk->nhit++'. 'tk->nhit' and 'tk->tp.flags' also share
the same cacheline.
perf report (cycles:pp):
8.30%
When doing ebpf+kprobe on some hot TCP functions (e.g.
tcp_rcv_established), the kprobe_dispatcher shows up in 'perf report'.
In kprobe_dispatcher(), there is a lot of cache bouncing
in 'tk->nhit++'. 'tk->nhit' and 'tk->tp.flags' also share
the same cacheline.
perf report (cycles:pp):
8.30%
In commit 94dfd7edfd5c ("USB: HCD: support giveback of URB in tasklet
context") support was added to give back the URB in tasklet context.
Let's take advantage of this in dwc2.
This speeds up the dwc2 interrupt handler considerably.
Note that this requires the change ("usb: dwc2: host: Add a
All other host controllers who want aligned buffers for DMA do it a
certain way. Let's do that too instead of working behind the USB core's
back. This makes our interrupt handler not take forever and also rips
out a lot of code, simplifying things a bunch.
This also has the side effect of
We'd like to be able to use HCD_BH in order to speed up the dwc2 host
interrupt handler quite a bit. However, according to the kernel doc for
usb_submit_urb() (specifically the part about "Reserved Bandwidth
Transfers"), we need to keep a reservation active as long as a device
driver keeps
The dwc2 interrupt handler is quite slow. On rk3288 with a few things
plugged into the ports and with cpufreq locked at 696MHz (to simulate
real world idle system), I can easily observe dwc2_handle_hcd_intr()
taking > 120 us, sometimes > 150 us. Note that SOF interrupts come
every 125 us with
Previously we needed to set the max_transfer_size to explicitly be 65535
because the old driver would detect that our hardware could support much
bigger transfers and then would try to do them. This wouldn't work
since the DMA alignment code couldn't support it.
Later in commit e8f8c14d9da7
Alan,
On Fri, Nov 6, 2015 at 7:40 AM, Alan Stern wrote:
> On Thu, 5 Nov 2015, Doug Anderson wrote:
>
>> Alan,
>>
>> On Thu, Nov 5, 2015 at 7:19 AM, Alan Stern wrote:
>> > On Wed, 4 Nov 2015, Doug Anderson wrote:
>> >
>> >> In the ChromeOS gerrit
>> >>
On 11/06/2015 12:30 PM, Arnd Bergmann wrote:
On Friday 06 November 2015 11:16:52 Guenter Roeck wrote:
On Wed, Oct 21, 2015 at 02:53:20PM -0700, Guenter Roeck wrote:
On Wed, Oct 21, 2015 at 09:11:53PM +0200, Arnd Bergmann wrote:
On Wednesday 21 October 2015 10:03:05 Guenter Roeck wrote:
On 2015/11/07 1:17, mho...@kernel.org wrote:
> From: Michal Hocko
>
> jbd2_alloc is explicit about its allocation preferences wrt. the
> allocation size. Sub page allocations go to the slab allocator
> and larger are using either the page allocator or vmalloc. This
> is all good but the logic is
Hi Rob,
On Sat, Nov 7, 2015 at 4:03 AM, Rob Herring wrote:
> On Fri, Oct 30, 2015 at 11:55:31AM +0530, Alim Akhtar wrote:
>> From: Thomas Abraham
>>
>> Add dt-binding documentation for s2mps15 PMIC device. The s2mps15 device
>> is similar to s2mps11/14 PMIC device and has 27 LDO and 10 buck
On Fri, Nov 06, 2015 at 03:46:07PM -0800, Elliott, Robert (Persistent Memory)
wrote:
> > -Original Message-
> > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> > ow...@vger.kernel.org] On Behalf Of Jens Axboe
> > Sent: Friday, November 6, 2015 11:20 AM
> ...
> > Subject:
1 - 100 of 1954 matches
Mail list logo
