No functional change. This is in preparation for handling non maxpacket
aligned transfers greater than bounce buffer size. This is basically to
avoid code duplication when using chained TRB transfers to handle
non maxpacket aligned transfers greater than bounce buffer size.
Signed-off-by: Kishon V
DWC3 uses bounce buffer to handle non max packet aligned OUT transfers and
the size of bounce buffer is 512 bytes. However if the host initiates OUT
transfers of size more than 512 bytes (and non max packet aligned), the
driver throws a WARN dump but still programs the TRB to receive more than
512
> -Original Message-
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Thursday, July 23, 2015 8:39 PM
> To: Felipe Balbi
> Cc: Badola Nikhil-B46172; linux-kernel@vger.kernel.org; linux-
> u...@vger.kernel.org; linux-o...@vger.kernel.org;
> gre...@linuxfoundation.org
> Subject: Re: [PATCH
No functional change. Added a new parameter in _dwc3_ep0_start_trans_ to
indicate whether the TRB is a chained TRB or last TRB. This is in
preparation for adding chained TRB support for ep0.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/ep0.c | 15 ---
1 file changed,
Hi Moritz,
On 07/25/2015 02:21 AM, Moritz Fischer wrote:
> Signed-off-by: Moritz Fischer
> ---
> arch/arm/boot/dts/zynq-7000.dtsi| 43 -
This patch is nice in general but every change in binding should be
discussed separately. There is also necessary to wire them up in th
No functional change. Used _roundup_ macro to calculate the transfer
size aligned to maxpacket in dwc3_ep0_complete_data. It also makes it
similar to how transfer size is calculated in __dwc3_ep0_do_control_data.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/ep0.c |4 +---
1 fi
Use chained TRB mechanism to handle non maxpacket aligned transfers
greater than bounce buffer size. With this the first TRB will be programmed
to receive 'ALIGN(ur->length - maxp, maxp)' data and the second TRB
will be programmed to receive the remaining data using bounce buffer.
Signed-off-by: K
Patch series first fixes memory corruption and then adds support to
handle non maxpacket aligned transfers.
Patch series adds support to handle non maxpacket aligned transfers
greater than bounce buffer size (512). It first adds chained TRB
support and then uses it to handle non maxpacket aligned
Add chained TRB support to ep0. Now TRB's can be chained just by
invoking _dwc3_ep0_start_trans_ with 'chain' parameter set to true.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/ep0.c| 16 +---
drivers/usb/dwc3/gadget.c |2 +-
2 files changed, 14 insertions(+)
On Sun, 26 Jul 2015 15:32:54 +0200
Oliver Neukum wrote:
> On Fri, 2015-07-24 at 08:48 +0200, Petr Tesarik wrote:
> > @@ -872,6 +886,12 @@ static int cp210x_startup(struct usb_serial
> > *serial)
> >
> > usb_set_serial_data(serial, spriv);
> >
> > + /* Get the 1-byte part number
On Mon, Jul 20, 2015 at 11:03:25AM +0200, Thomas Petazzoni wrote:
> Maxime,
>
> On Mon, 20 Jul 2015 10:41:32 +0200, Maxime Ripard wrote:
>
> > /**
> > + * enum dmaengine_alignment - defines alignment of the DMA async tx
> > + * buffers
> > + */
> > +enum dmaengine_alignment {
> > + DMAENGINE_A
On Fri, Jul 24, 2015 at 05:28:40PM -0400, Eric B Munson wrote:
> With the refactored mlock code, introduce a new system call for mlock.
> The new call will allow the user to specify what lock states are being
> added. mlock2 is trivial at the moment, but a follow on patch will add
> a new mlock st
auth 37b0e0af subscribe linux-kernel \
lihua@gmail.com
N�r��yb�X��ǧv�^�){.n�+{zX����ܨ}���Ơz�&j:+v���zZ+��+zf���h���~i���z� �w���?�&�)ߢf��^jǫy�m��@A�a���
0��h���i
>
> On Sun, Jul 26, 2015 at 09:54:14AM +0300, Tomas Winkler wrote:
> > FW has gained new capability where a FW client can asynchronously
> > notify the host that an event has occurred in its process.
> > The notification doesn't provide any data and host may need to query
> > further the FW clien
On Fri, Jul 24, 2015 at 05:28:39PM -0400, Eric B Munson wrote:
> Extending the mlock system call is very difficult because it currently
> does not take a flags argument. A later patch in this set will extend
> mlock to support a middle ground between pages that are locked and
> faulted in immediat
This series adds PM support to pci-dra7xx so that PCI clocks can be disabled
during suspend and enabled back during resume without affecting
PCI functionality.
Changes from v2:
*) Used SET_SYSTEM_SLEEP_PM_OPS and SET_NOIRQ_SYSTEM_SLEEP_PM_OPS for
populating PM ops.
Changes from v1:
*) Moved re
Hi Anatol,
Thanks for your suggestion. We are working on different architectures to
support NAU8825 ALSA driver, and I also think it is better we can have a
cooperation for driver development and upstream. We have checked your
code, and we think your implement version should more follow the ALSA
u
Add PM support to pci-dra7xx so that PCI clocks can be disabled
during suspend and enabled back during resume without affecting
PCI functionality.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/host/pci-dra7xx.c | 72 +
1 file changed, 72 insertio
Fix the error handling code in case pm_runtime_get_sync fails. Now
when pm_runtime_get_sync fails pm_runtime_disable is invoked so that
there is no unbalanced pm_runtime_enable calls.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/pci/host/pci-dra7xx.c |4 +++-
1 file changed, 3 insertion
DRA7xx require MSE bit to be cleared to set the master in
standby mode. (In DRA7xx TRM_vE, section 24.9.4.5.2.2.1 PCIe
Controller Master Standby Behavior advises to use the clearing
of the local MSE bit to set the master in standby. Without this
some of the clocks do not idle).
Cleared the MSE bit
Commit-ID: 4365160def95ef2f5da9b5cc5660e5747e5e1956
Gitweb: http://git.kernel.org/tip/4365160def95ef2f5da9b5cc5660e5747e5e1956
Author: Thomas Gleixner
AuthorDate: Mon, 13 Jul 2015 20:31:09 +
Committer: Thomas Gleixner
CommitDate: Sun, 26 Jul 2015 11:47:25 +0200
avr32/at32ap: Consol
Commit-ID: 0aef3997e12a10d4dfb6e01133e2fe478b9aa5eb
Gitweb: http://git.kernel.org/tip/0aef3997e12a10d4dfb6e01133e2fe478b9aa5eb
Author: Florian Fainelli
AuthorDate: Thu, 23 Jul 2015 15:52:21 -0700
Committer: Thomas Gleixner
CommitDate: Mon, 27 Jul 2015 08:09:38 +0200
irqchip/bcm7120-l2:
Commit-ID: fd537766715e9b6bf7ff07abb22f4817201433db
Gitweb: http://git.kernel.org/tip/fd537766715e9b6bf7ff07abb22f4817201433db
Author: Brian Norris
AuthorDate: Wed, 22 Jul 2015 16:21:40 -0700
Committer: Thomas Gleixner
CommitDate: Mon, 27 Jul 2015 08:09:38 +0200
irqchip/bcm7120-l2: Per
Commit-ID: be9b22b6a7e6725162c64155a08b71f0654b675c
Gitweb: http://git.kernel.org/tip/be9b22b6a7e6725162c64155a08b71f0654b675c
Author: Brian Norris
AuthorDate: Wed, 22 Jul 2015 16:21:39 -0700
Committer: Thomas Gleixner
CommitDate: Mon, 27 Jul 2015 08:09:38 +0200
genirq: Add chip_[suspe
Commit-ID: 0d3f2c92e004c67404fabea19728c1962b777bd6
Gitweb: http://git.kernel.org/tip/0d3f2c92e004c67404fabea19728c1962b777bd6
Author: Sudeep Holla
AuthorDate: Wed, 15 Jul 2015 15:38:29 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 27 Jul 2015 08:09:38 +0200
irqchip/gic: Remove red
Commit-ID: c376023b7096e76ac4d5526105cf9be8743bead9
Gitweb: http://git.kernel.org/tip/c376023b7096e76ac4d5526105cf9be8743bead9
Author: Nicolas Pitre
AuthorDate: Fri, 24 Jul 2015 15:24:45 -0400
Committer: Thomas Gleixner
CommitDate: Mon, 27 Jul 2015 08:09:38 +0200
irqchip: Appropriate _
Commit-ID: 1ee4fb3ee1e47f2b3c294ded383a3cd9cc2decd4
Gitweb: http://git.kernel.org/tip/1ee4fb3ee1e47f2b3c294ded383a3cd9cc2decd4
Author: Bjorn Andersson
AuthorDate: Wed, 22 Jul 2015 12:43:04 -0700
Committer: Thomas Gleixner
CommitDate: Mon, 27 Jul 2015 08:09:38 +0200
genirq: Export irq_[
On Sat, Jun 6, 2015 at 7:02 AM, Vaishali Thakkar wrote:
> In big endian cases, macro cpu_to_le16 unfolds to __swab16 which
> provides special case for constants. In little endian cases,
> __constant_cpu_to_le16 and cpu_to_le16 expand directly to the
> same expression. So, replace __constant_cpu_to
Commit-ID: aec89ef72ba6c94420f599dcb684ed66937cdacf
Gitweb: http://git.kernel.org/tip/aec89ef72ba6c94420f599dcb684ed66937cdacf
Author: Sudeep Holla
AuthorDate: Wed, 15 Jul 2015 15:38:28 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 27 Jul 2015 08:09:37 +0200
irqchip/gic: Enable SKI
Commit-ID: 4f31dd63e050b777d3f3139197c4b3860aa89301
Gitweb: http://git.kernel.org/tip/4f31dd63e050b777d3f3139197c4b3860aa89301
Author: Thomas Gleixner
AuthorDate: Mon, 13 Jul 2015 20:31:10 +
Committer: Thomas Gleixner
CommitDate: Sun, 26 Jul 2015 11:47:25 +0200
avr32/at32ap: Use ir
Commit-ID: df6e23ae62d46a524ba3db95a201904a01419bdc
Gitweb: http://git.kernel.org/tip/df6e23ae62d46a524ba3db95a201904a01419bdc
Author: Jiang Liu
AuthorDate: Mon, 13 Jul 2015 20:31:12 +
Committer: Thomas Gleixner
CommitDate: Sun, 26 Jul 2015 11:47:25 +0200
avr32/irq: Use irq_desc_ge
Hi,
On Sun, Jul 26, 2015 at 07:56:55PM -0300, Ezequiel Garcia wrote:
> El jul. 25, 2015 6:40 PM, "Antoine Tenart"
> escribió:
> > +
> > +static const struct of_device_id berlin_pwm_match[] = {
> > + { .compatible = "marvell,berlin-pwm" },
>
> Don't we need a sentinel here?
Oops. I'll fix
Factor out message flushing procedure which is used in run-to-completion
mode. This patch doesn't change the logic.
Signed-off-by: Hidehiro Kawai
---
drivers/char/ipmi/ipmi_si_intf.c | 39 ++
1 file changed, 18 insertions(+), 21 deletions(-)
diff --git a/d
send_panic_events() calls intf->handlers->set_run_to_completion(),
but it has already been done in the caller function panic_event().
Remove it from send_panic_events().
Signed-off-by: Hidehiro Kawai
---
drivers/char/ipmi/ipmi_msghandler.c |2 --
1 file changed, 2 deletions(-)
diff --git a/
Received handlers defined as ipmi_recv_hndl member of struct
ipmi_user_hndl can take a spinlock. This means that if the kernel
panics while holding the lock, a deadlock may happen on the lock
while flushing queued messages in the panic context.
Calling the receive handler doesn't make much meanin
If a BMC is unresponsive for some reason, it ends up completing
the requested message as an error, then kcs_event() is called once
to advance the state machine. However, since the BMC is
unresponsive now, the status of the KCS interface may not be
idle. As the result, the state machine can contin
panic_event() called as a panic notifier tries to flush queued
messages, but it can't handle them if the kernel panic happens
while processing a message. What happens depends on when the
kernel panics.
Here is the summary of message sending process.
smi_send()
smi_add_send_msg()
(1) i
When flushing queued messages in run-to-completion mode,
smi_event_handler() is recursively called.
flush_messages()
smi_event_handler()
handle_transaction_done()
deliver_recv_msg()
ipmi_smi_msg_received()
smi_recv_tasklet()
sender()
flush_messages()
smi_event_h
This patche set fixes multiple bugs in IPMI driver especially for
the panic notifier callback panic_event() and related functions.
This callback is called before kdump if crash_kexec_post_notifiers
boot option is specified, so its robustness is very important.
panic_event() first tries to flush qu
When processing queued messages in the panic context, IPMI driver
tries to do it without any locking to avoid deadlocks. However,
this means we can touch a corrupted list if the kernel panicked
while manipulating the list. Fortunately, current `add-tail and
del-from-head' style implementation won
Hi Kalle,
On Mon, 27 Jul 2015 08:41:49 +0300 Kalle Valo wrote:
>
> Stephen Rothwell writes:
>
> > After merging the wireless-drivers-next tree, today's linux-next build
> > (x86_64 allmodconfig) failed like this:
> >
> > ERROR: "of_default_bus_match_table" [drivers/bcma/bcma.ko] undefined!
> >
Hi all,
Changes since 20150724:
New tree: orangefs
The ext4 tree lost its build failure.
The wireless-drivers-next tree lost its build failure.
The drm tree gained a conflict against Linus' tree.
The input tree lost its build failure.
The battery tree gained a build failure so I used the ver
On 07/27/2015 07:15 AM, Christoph Hellwig wrote:
> On Fri, Jul 17, 2015 at 09:27:04AM +0200, Hannes Reinecke wrote:
>> When running on files the physical blocksize is actually 4k,
>> so we should be announcing it as such. This is enabled with
>> a new LO_FLAGS_BLOCKSIZE flag value to the existing i
Peter Zijlstra [pet...@infradead.org] wrote:
| On Tue, Jul 14, 2015 at 08:01:52PM -0700, Sukadev Bhattiprolu wrote:
| > Move the part of perf_event_read_value() that computes the event
| > counts and event times into a new function, perf_event_compute().
| >
| > This would allow us to call perf_ev
On Fri, Jul 24, 2015 at 07:10:14PM +0800, Daniel Kurtz wrote:
> On Fri, Jul 24, 2015 at 11:02 AM, James Liao
> wrote:
> > Remove the dependency from clk_null, and give all root clocks a
> > typical rate, include clkph_mck_o, usb_syspll_125m and hdmitx_dig_cts.
> >
> > dpi_ck was removed due to no
On Mon, 27 Jul 2015, Michael Schmitz wrote:
> Finn,
>
> my bad - there is indeed a change in the /proc/driver/nvram output:
>
> --- nvram-4.out2015-07-24 12:32:44.0 +1200
> +++ nvram-4p2.out2015-07-27 13:56:06.0 +1200
> @@ -7,7 +7,7 @@
> Keyboard language: English (US)
From: "Peter Zijlstra (Intel)"
In order to free up the perf_event_read_group() name:
s/perf_event_read_\(one\|group\)/perf_read_\1/g
s/perf_read_hw/__perf_read/g
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/events/core.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletion
Move the part of perf_event_read_value() that aggregates the event
counts and event times into a new function, perf_event_aggregate().
This would allow us to call perf_event_aggregate() independently.
Signed-off-by: Sukadev Bhattiprolu
---
Changelog[v4]
[Peter Zijlstra] Add missing lockd
Add a return value to perf_event_read(). The return value will be
needed later in perf_read_group() implements ability to read several
counters in a PERF_PMU_TXN_READ transaction.
Signed-off-by: Sukadev Bhattiprolu
---
kernel/events/core.c | 19 +--
1 file changed, 13 insertion
Hi Stephen,
Stephen Rothwell writes:
> After merging the wireless-drivers-next tree, today's linux-next build
> (x86_64 allmodconfig) failed like this:
>
> ERROR: "of_default_bus_match_table" [drivers/bcma/bcma.ko] undefined!
>
> Caused by commit
>
> cae761b5a6bd ("bcma: populate bus DT subnod
Fixes commit eae79b4f3e82ca63a53478a161b190a0d38fe526 ("rsi: fix memory leak
in rsi_load_ta_instructions()") which stopped the driver from functioning.
Firmware data has been allocated using vmalloc(), resulting in memory
that cannot be used for DMA. Hence the firmware was first copied to a
buffer
Add a 'group' parameter to perf_event_read(). It will be used (set
to true) in a follow-on patch to update event times of the group.
Signed-off-by: Sukadev Bhattiprolu
---
kernel/events/core.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/kernel/events/
perf_event_read() does two things:
- call the PMU to read/update the counter value, and
- compute the total count of the event and its children
Not all callers need both. perf_event_reset() for instance needs the
first piece but doesn't need the second. Similarly, when we impleme
Add a return value to __perf_event_read(). The return value will be
needed later in perf_read_group() implements ability to read several
counters in a PERF_PMU_TXN_READ transaction.
Signed-off-by: Sukadev Bhattiprolu
---
kernel/events/core.c | 22 +++---
1 file changed, 19 inse
The 24x7 counters in Powerpc allow monitoring a large number of counters
simultaneously. They also allow reading several counters in a single
HCALL so we can get a more consistent snapshot of the system.
Use the PMU's transaction interface to monitor and read several event
counters at once. The id
Define a new PERF_PMU_TXN_READ interface to read a group of counters
at once.
pmu->start_txn()// Initialize before first event
for each event in group
pmu->read(event); // Queue each event to be read
pmu->commit_txn() //
Unlike normal hardware PMCs, the 24x7 counters in Power8 are stored in
memory and accessed via a hypervisor call (HCALL). A major aspect of the
HCALL is that it allows retireving _several_ counters at once (unlike
regular PMCs, which are read one at a time). By reading several counters
at once, we
Unroll the calls to perf_event_read_value() in perf_read_group()
so we can later optimize out parts we don't need for group events.
Signed-off-by: Sukadev Bhattiprolu
---
kernel/events/core.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/kernel/events/c
Currently, the PMU interface allows reading only one counter at a time.
But some PMUs like the 24x7 counters in Power, support reading several
counters at once. To leveage this functionality, extend the transaction
interface to support a "transaction type".
The first type, PERF_PMU_TXN_ADD, refers
On Thu, Jun 18, 2015 at 02:13:42PM -0700, Bjorn Andersson wrote:
> Signed-off-by: Courtney Cavin
> Signed-off-by: Bjorn Andersson
> ---
Looks good.
Greg, can you pick this up?
Reviewed-by: Andy Gross
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
>
> This patch adds the support for PPMU (Platform Performance Monitoring Unit)
> version 2.0 for Exynos5433 SoC. Exynos5433 SoC must need PPMUv2 which is
> quite different from PPMUv1.1. The exynos-ppmu.c driver supports both PPMUv1.1
> and PPMUv2.
>
> Cc: MyungJoo Ham
> Cc: Kyungmin Park
>
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in:
arch/x86/mm/mpx.c
between commit:
a89652769470 ("x86/mpx: Do not set ->vm_ops on MPX VMAs")
from Linus' tree and patch:
"mm, mpx: add "vm_flags_t vm_flags" arg to do_mmap_pgoff()"
from the akpm tree.
I fixed it up
>
> This patch updates the documentation to include the information of PPMUv2.
> The PPMUv2 is used for Exynos5433 and Exynos7420 to monitor the performance
> of each IP in Exynos SoC.
>
> Cc: MyungJoo Ham
> Cc: Kyungmin Park
> Signed-off-by: Chanwoo Choi
Acked-by: MyungJoo Ham
> ---
>
On Tue, Jul 21, 2015 at 03:17:06PM +0530, Vinay Simha wrote:
> Joe,
>
> Just want to confirm, shall i delete this code in sm750_help.h, even the
> FIELD_START and FIELD_END is not required.
If they are not used anywhere feel free to send a patch to delete them.
regards
sudip
--
To unsubscribe fro
On Fri, Jul 17, 2015 at 09:27:05AM +0200, Hannes Reinecke wrote:
> Signed-off-by: Hannes Reinecke
Looks good,
Reviewed-by: Christoph Hellwig
(and should be moved first in the series)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord..
Hi Yuyang,
On Mon, Jul 27, 2015 at 04:34:09AM +0800, Yuyang Du wrote:
> On Mon, Jul 27, 2015 at 12:04:20PM +0800, Boqun Feng wrote:
> > > ~~~
> > > > > 1) blocked load is more "difficult" to track, hint, migrate.
> > > ~~~
On Fri, Jul 17, 2015 at 09:27:04AM +0200, Hannes Reinecke wrote:
> When running on files the physical blocksize is actually 4k,
> so we should be announcing it as such. This is enabled with
> a new LO_FLAGS_BLOCKSIZE flag value to the existing ioctl.
The flag is only used in this patch, but not ac
On 07/25/2015 02:21 AM, Moritz Fischer wrote:
> This adds a reset controller driver to control the Xilinx Zynq
> SoC's various resets.
>
> Signed-off-by: Moritz Fischer
> ---
> drivers/reset/Makefile | 1 +
> drivers/reset/reset-zynq.c | 142
> +
On Sun, Jul 26, 2015 at 11:11:44AM -0700, Dan Williams wrote:
> I don't follow. We have __iomem for the cpu mapping of a resource and
> dma_map() for a PCI device. __pmem works the same and is there to
> make sure someone doesn't simply de-reference a pointer to pmem and
> hope that the write is
On Sun, Jul 26, 2015 at 10:49:39AM -0700, Dan Williams wrote:
> On Sun, Jul 26, 2015 at 10:25 AM, Christoph Hellwig wrote:
> > On Fri, Jul 24, 2015 at 10:38:42PM -0400, Dan Williams wrote:
> >> The behavior change to return NULL on an unsupported request is reserved
> >> for a later patch.
> >
> >
On Sun, Jul 26, 2015 at 10:49:39AM -0700, Dan Williams wrote:
> > What's the point of having this MEMREMAP_CACHE alias?
>
> For developers that are used to seeing ioremap_cache()...
Meh. We've got git logs that show clearly what replaced a previous API.
Duplicate names for the same API are highl
Currently, panic() and crash_kexec() can be called at the same time.
For example (x86 case):
CPU 0:
oops_end()
crash_kexec()
mutex_trylock() // acquired
nmi_shootdown_cpus() // stop other cpus
CPU 1:
panic()
crash_kexec()
mutex_trylock() // failed to acquire
sm
If panic on NMI happens just after panic() on the same CPU, panic()
is recursively called. As the result, it stalls after failing to
acquire panic_lock.
To avoid this problem, don't call panic() in NMI context if
we've already entered panic().
V2:
- Use atomic_cmpxchg() instead of current spin_t
This patch introduces new boot option "noextnmi" which disables
external NMI. This option is useful for the dump capture kernel
so that an HA application or administrator wouldn't mistakenly
shoot down the kernel by NMI.
Currently, only x86 supports this option.
Signed-off-by: Hidehiro Kawai
Cc
When an HA cluster software or administrator detects non-response
of a host, they issue an NMI to the host to completely stop current
works and take a crash dump. If the kernel has already panicked
or is capturing a crash dump at that time, further NMI can cause
a crash dump failure.
To solve thi
On 07/25/2015 02:21 AM, Moritz Fischer wrote:
> Signed-off-by: Moritz Fischer
> ---
> Documentation/devicetree/bindings/reset/zynq-reset-pl.txt | 13 +
> 1 file changed, 13 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reset/zynq-reset-pl.txt
>
> diff --git a/
On Mon, Jul 27, 2015 at 07:46:59AM +0800, Fengguang Wu wrote:
> Sorry for the duplicate report! It'll be auto avoided in future.
No problem. And thanks again for the script to reproduce the error. I am
still wondering why it did not came up in my tests before sending the
patch.
regards
sudip
--
To
With "operating-points-v2" bindings, clock-latency is defined per OPP.
Users of this value expect a single value which defines the latency to
switch to any clock rate. Find maximum clock-latency-ns from the OPP
table to service requests from such users.
Reviewed-by: Stephen Boyd
Signed-off-by: Vi
There is no need to complicate _opp_add_dynamic() with allocation of
dev_opp as well. Allocate it from _add_device_opp() instead.
Reviewed-by: Stephen Boyd
Reviewed-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Viresh Kumar
---
drivers/base/power/opp.c | 41 ++---
Later commits would add support for new OPP bindings and this would be
required then. So, lets do it in a separate patch to make it easily
reviewable.
Another change worth noticing is INIT_LIST_HEAD(&opp->node). We weren't
doing it earlier as we never tried to delete a list node before it is
added
With "operating-points-v2" its possible to tell which devices share
OPPs. We already have infrastructure to decode that information.
This patch adds following APIs:
- of_get_cpus_sharing_opps: Returns cpumask of CPUs sharing OPPs (only
valid with v2 bindings).
- of_cpumask_init_opp_table: Initia
This adds support in OPP library to parse and create list of OPPs from
operating-points-v2 bindings. It takes care of most of the properties of
new bindings (except shared-opp, which will be handled separately).
For backward compatibility, we keep supporting earlier bindings. We try
to search for
With "operating-points-v2" bindings, its possible to specify the OPP to
which the device must be switched, before suspending.
This patch adds support for getting that information.
Signed-off-by: Viresh Kumar
---
drivers/base/power/opp.c | 11 +++
1 file changed, 11 insertions(+)
diff -
An opp can be shared by multiple devices, for example its very common
for CPUs to share the OPPs, i.e. when they share clock/voltage rails.
This patch adds support of shared OPPs to the OPP library.
Instead of a single device, dev_opp will not contain a list of devices
that use it. It also senses
Support for parsing operating-points-v2 bindings is in place now, lets
modify cpufreq-dt driver to use them.
For backward compatibility we will continue to support earlier bindings.
Special handling for that is required, to make sure OPPs are initialized
for all the CPUs.
Signed-off-by: Viresh Ku
This will be used from multiple places later. Lets create a separate
routine for that.
Reviewed-by: Stephen Boyd
Reviewed-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Viresh Kumar
---
drivers/base/power/opp.c | 22 +-
1 file changed, 17 insertions(+), 5 deletions(-)
diff -
In order to prepare for the later commits, this relocates few routines
towards the top as they will be used earlier in the code.
Reviewed-by: Stephen Boyd
Reviewed-by: Bartlomiej Zolnierkiewicz
Signed-off-by: Viresh Kumar
---
drivers/base/power/opp.c | 277 -
On Sat, Jul 18, 2015 at 09:38:57AM +0530, Sudip Mukherjee wrote:
> Now since all cleanups are done and the code is ready to be merged lets
> move it out of staging into fbdev location.
Hi Tomi,
A gentle ping
regards
sudip
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Sat, Jul 25, 2015 at 09:49:19AM +0800, Incarnation P. Lee wrote:
> From: "Pan Li"
>
> Add one space after ',' in function call parameters list.
> Signed-off-by: Pan Li
>
> ---
This has already been done by 574150f0d275 ("staging:lustre: fix "space
required after that ', '" error in cl_page.c
From: "David A. Long"
The pt_regs_offset structure is used for the HAVE_REGS_AND_STACK_ACCESS_API
feature and has identical definitions in four different arch ptrace.h
include files. It seems unlikely that definition would ever need to be
changed regardless of architecture so lets move it into
in
From: "David A. Long"
Move duplicate and functionally equivalent code for accessing registers
and stack (CONFIG_HAVE_REGS_AND_STACK_ACCESS_API) from arch subdirs into
common kernel files.
Changes since v1:
Move the REG_OFFSET_NAME and REG_OFFSET_END macros to architecture-
independent in
From: "David A. Long"
Several architectures have identical or functionally equivalent code
implementing parts of the HAVE_REGS_AND_STACK_ACCESS_API feature. Move
that code out of the architecture directories.
Signed-off-by: David A. Long
---
arch/arm/include/asm/ptrace.h | 6 ---
ar
Nicolas Iooss writes:
> Functions map_id_range_down, map_id_down and map_id_up all used the
> construction:
>
> if (...)
> id = ...
> else
> id = ...
> return id;
>
> which can be simplified by directly returning the result of the
> computations in each branch.
>
> Mor
When inserting a new register into a block, the present bit map size is
increased using krealloc. krealloc does not clear the additionally
allocated memory, leaving it filled with random values. Result is that
some registers are considered cached even though this is not the case.
Fix the problem b
On Sun, Jul 26, 2015 at 11:04:13PM +0530, Shraddha Barke wrote:
> This patch compresses two lines into a single line if immediate return
> statement
> is found. Also,remove variable rc as it is no longer needed.
> It is done using tool Coccinelle. And semantic patch used for this is as
> follows:
On Thu, 23 Jul 2015, Kees Cook wrote:
> +
> +/*
> + * Return an allocated string that has been escaped of special characters
> + * and double quotes, making it safe to log in quotes.
> + */
> +static char *kstrdup_quotable(char *src)
> +{
Do you think these should go into a library?
--
James
On Mon, Jul 27, 2015 at 12:04:20PM +0800, Boqun Feng wrote:
> > ~~~
> > > > 1) blocked load is more "difficult" to track, hint, migrate.
> > ~~~
>
> I may not get your point her
On Fri, 2015-07-24 at 17:55 +0100, Will Deacon wrote:
> On Fri, Jul 24, 2015 at 06:43:13AM +0100, Yong Wu wrote:
> > On Tue, 2015-07-21 at 15:59 +0100, Will Deacon wrote:
> > > On Thu, Jul 16, 2015 at 10:04:34AM +0100, Yong Wu wrote:
> > > > +static void mtk_iommu_tlb_flush_all(void *cookie)
> > >
Hi Dietmar,
On Fri, Jul 24, 2015 at 05:41:45PM +0100, Dietmar Eggemann wrote:
> On 15/07/15 01:04, Yuyang Du wrote:
> > For cfs_rq, we have load.weight, runnable_load_avg, and load_avg. We
> > now start to clean up how they are used.
> >
> > First, as group sched_entity already largely uses load_
On Fri, 2015-07-24 at 17:53 +0100, Will Deacon wrote:
> On Fri, Jul 24, 2015 at 06:24:26AM +0100, Yong Wu wrote:
> > On Tue, 2015-07-21 at 18:11 +0100, Will Deacon wrote:
> > > On Thu, Jul 16, 2015 at 10:04:32AM +0100, Yong Wu wrote:
> > > > +/* level 2 pagetable */
> > > > +#define ARM_SHORT_PTE_T
1 - 100 of 270 matches
Mail list logo
