2018-06-14 14:27 GMT+09:00 Masahiro Yamada :
> If a GPIO chip is a part of a hierarchy IRQ domain, there is no
> way to specify the trigger type when gpio(d)_to_irq() allocates an
> interrupt on-the-fly.
>
> Currently, uniphier_gpio_to_irq() sets IRQ_TYPE_NONE, but it causes
> an error in the .allo
On Thu, Jun 14, 2018 at 05:33:46AM +, Nadav Amit wrote:
> at 10:24 PM, Greg Kroah-Hartman wrote:
>
> > On Wed, Jun 13, 2018 at 06:54:11AM -0700, Nadav Amit wrote:
> >> Removing the paragraph about writing to the Free Software Foundation's
> >> mailing address from the sample GPL notice accord
On Thu, Jun 14, 2018 at 05:41:01AM +, Nadav Amit wrote:
> at 10:23 PM, Greg Kroah-Hartman wrote:
>
> > On Wed, Jun 13, 2018 at 06:54:06AM -0700, Nadav Amit wrote:
> >> When balloon batching is not supported by the hypervisor, the guest
> >> frame number (GFN) must fit in 32-bit. However, due
at 10:50 PM, Greg Kroah-Hartman wrote:
> On Thu, Jun 14, 2018 at 05:41:01AM +, Nadav Amit wrote:
>> at 10:23 PM, Greg Kroah-Hartman wrote:
>>
>>> On Wed, Jun 13, 2018 at 06:54:06AM -0700, Nadav Amit wrote:
When balloon batching is not supported by the hypervisor, the guest
frame n
Correct to check the right rx dma cookie status in spit of it
works because only one cookie is running in the current sdma.
But it will not once sdma driver support multi cookies
running based on virt-dma.
Signed-off-by: Robin Gong
---
drivers/tty/serial/imx.c | 2 +-
1 file changed, 1 insertion
The legacy sdma driver has below limitations or drawbacks:
1. Hardcode the max BDs number as "PAGE_SIZE / sizeof(*)", and alloc
one page size for one channel regardless of only few BDs needed
most time. But in few cases, the max PAGE_SIZE maybe not enough.
2. One SDMA channel can't st
No this limitation now after virtual dma used since bd is allocated
dynamically instead of static.
Signed-off-by: Robin Gong
---
drivers/dma/imx-sdma.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index 27b76eb..f56226f 100644
After sdma driver change to virt-dma, all bds will be allocated
dynamically with 'port.lock' acquired instead of statically allocated
before. That means the lock sequence is 'port.lock' -> 'fs_reclaim_acquire'
.But in case uart rx/tx dma callback coming after other kernel code which
have already ac
There are lot of codes overlap between prep_sg and prep_cyclic function.
Add sdma_transfer_init() function to elimated the code overlap.
Signed-off-by: Robin Gong
---
drivers/dma/imx-sdma.c | 83 ++
1 file changed, 37 insertions(+), 46 deletions(-)
Since 'sdmac->vc.lock' and 'sdmac->desc' can be used as 'lock' and
'enabled' in 'struct sdma_channel sdmac', remove them.
Signed-off-by: Robin Gong
---
drivers/dma/imx-sdma.c | 23 ---
1 file changed, 23 deletions(-)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma
From: Sascha Hauer
This is a preparation step to make the adding of virt-dma easier.
We create a struct sdma_desc, move some fields from struct sdma_channel
there and add a pointer from the former to the latter. For now we
allocate the data statically in struct sdma_channel, but with
virt-dma sup
The legacy sdma driver has below limitations or drawbacks:
1. Hardcode the max BDs number as "PAGE_SIZE / sizeof(*)", and alloc
one page size for one channel regardless of only few BDs needed
most time. But in few cases, the max PAGE_SIZE maybe not enough.
2. One SDMA channel can't st
On Wed, Jun 13, 2018 at 04:49:47PM -0700, Cong Wang wrote:
> In ucma_event_handler() we lock the mutex like this:
>
> mutex_lock(&ctx->file->mut);
> ...
> mutex_unlock(&ctx->file->mut);
>
> which seems correct, but we could translate it into this:
>
> f = ctx->file;
> mutex_lock(&f->mut);
> ...
> f
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit 2696ec4566f598ab483a6bebc4ec841b2efb88ec:
>
> Merge tag 'perf-core-for-mingo-4.18-20180606' of
> gi
Commit-ID: 41477acf092251eb0cfe83068f48dbcb2521478a
Gitweb: https://git.kernel.org/tip/41477acf092251eb0cfe83068f48dbcb2521478a
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 7 Jun 2018 14:19:54 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 14:22:53 -0300
per
Commit-ID: 29f9fcdd3f8edccad5809cf939ce921752460fe7
Gitweb: https://git.kernel.org/tip/29f9fcdd3f8edccad5809cf939ce921752460fe7
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 7 Jun 2018 14:33:31 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 14:33:31 -0300
per
On Thu, Jun 14, 2018 at 09:23:54AM +0800, Ming Lei wrote:
> On Wed, Jun 13, 2018 at 07:44:12AM -0700, Christoph Hellwig wrote:
> > Given that we have a single, dubious user of bio_pages_all I'd rather
> > see it as an opencoded bio_for_each_ loop in the caller.
>
> Yeah, that is fine since there i
Commit-ID: e5654455795f2f89328f7b301dacb6926e57e2b8
Gitweb: https://git.kernel.org/tip/e5654455795f2f89328f7b301dacb6926e57e2b8
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 7 Jun 2018 14:27:19 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 14:27:19 -0300
per
Commit-ID: 9660e08ee8cbc94ac835f2c30576c6e51fbece8f
Gitweb: https://git.kernel.org/tip/9660e08ee8cbc94ac835f2c30576c6e51fbece8f
Author: Jiri Olsa
AuthorDate: Thu, 7 Jun 2018 00:15:06 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 15:53:36 -0300
perf stat: Add --i
Commit-ID: c9d366287042489090da0391318df528bdce9941
Gitweb: https://git.kernel.org/tip/c9d366287042489090da0391318df528bdce9941
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 7 Jun 2018 14:42:27 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 14:42:27 -0300
per
On Wed, Jun 13, 2018 at 10:34 PM, Leon Romanovsky wrote:
>
> Hi Cong,
>
> If the compiler optimizes the first line (mutex_lock) as you wrote,
> it will reuse "f" for the second line (mutex_unlock) too.
Nope, check the assembly if you don't trust me, at least
my compiler always fetches ctx->file w
Commit-ID: b37d33edbf41b532ddd156707c037c6f4784e40b
Gitweb: https://git.kernel.org/tip/b37d33edbf41b532ddd156707c037c6f4784e40b
Author: Jiri Olsa
AuthorDate: Thu, 7 Jun 2018 00:15:07 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 15:58:13 -0300
perf stat: Use onl
Commit-ID: f7fa827f5f432a0b1f34e10fc49da93aeef9f817
Gitweb: https://git.kernel.org/tip/f7fa827f5f432a0b1f34e10fc49da93aeef9f817
Author: Jiri Olsa
AuthorDate: Thu, 7 Jun 2018 00:15:05 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 15:50:14 -0300
perf tools: Fix er
Am Donnerstag, 14. Juni 2018, 03:04:40 CEST schrieb kbuild test robot:
> Hi Richard,
>
> I love your patch! Perhaps something to improve:
>
> [auto build test WARNING on mtd/master]
> [also build test WARNING on v4.17 next-20180613]
> [if your patch is applied to the wrong
Commit-ID: c1a1f5d9da800dc715d8c1d8a9692c63c70c2955
Gitweb: https://git.kernel.org/tip/c1a1f5d9da800dc715d8c1d8a9692c63c70c2955
Author: Jiri Olsa
AuthorDate: Thu, 7 Jun 2018 00:15:09 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 16:01:44 -0300
perf stat: Allow t
Commit-ID: f515572734fb323aa0efe9ea2c546cd7fee327f7
Gitweb: https://git.kernel.org/tip/f515572734fb323aa0efe9ea2c546cd7fee327f7
Author: Jiri Olsa
AuthorDate: Thu, 7 Jun 2018 00:15:08 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 15:59:13 -0300
perf stat: Fix met
Commit-ID: a5cfa6217c94a1f1cfad4481fc14f5fc399abde3
Gitweb: https://git.kernel.org/tip/a5cfa6217c94a1f1cfad4481fc14f5fc399abde3
Author: Jiri Olsa
AuthorDate: Thu, 7 Jun 2018 00:15:10 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 7 Jun 2018 16:03:21 -0300
perf stat: Add eve
Commit-ID: 4c8205273626f27b9e5a64bdc194ab483a8cce66
Gitweb: https://git.kernel.org/tip/4c8205273626f27b9e5a64bdc194ab483a8cce66
Author: Jiri Olsa
AuthorDate: Fri, 8 Jun 2018 02:22:11 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 8 Jun 2018 13:35:53 -0300
perf c2c: Keep str
Commit-ID: fad76d4333fe73cf3f73704aa34d4ce523b1c458
Gitweb: https://git.kernel.org/tip/fad76d4333fe73cf3f73704aa34d4ce523b1c458
Author: Seeteena Thoufeek
AuthorDate: Fri, 8 Jun 2018 16:32:28 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 8 Jun 2018 13:41:30 -0300
perf scrip
Hi Punit,
On 2018/6/14 1:39, Punit Agrawal wrote:
> Punit Agrawal writes:
>
>
> [...]
>
>>
>> CONFIG_HAVE_MEMORYLESS node is not enabled on arm64 which means we end
>> up returning the original node in the fallback path.
>>
>> Xie, does the below patch help? I can submit a proper patch if this
Hi David,
On 06/14/2018 03:42 AM, David Collins wrote:
> Hello Rajendra,
>
> On 06/11/2018 09:40 PM, Rajendra Nayak wrote:
>> Add DT bindings to describe the rpmh powerdomains found on Qualcomm
>
> s/powerdomains/power domains/
>
>> Technologies, Inc. SoCs. These power domains communicate a per
On Thu, Jun 14, 2018 at 3:16 AM Masahiro Yamada
wrote:
>
> Could you run sed directly in your tree?
Sure, I did that on the plane. Now on the ground, pushed out.
Somebody should double- and triple-check it.
Linus
On 6/13/2018 4:36 AM, Stephen Boyd wrote:
Update the binding for two more PMICs supported by the same driver.
While we're here, remove the duplicate pmi8994 lines because that
support got merged twice.
Cc: Rajendra Nayak
Cc: Vivek Gautam
Cc:
Signed-off-by: Stephen Boyd
---
.../devicetre
On Wed, Jun 13, 2018 at 10:48:50PM -0300, Rafael Tinoco wrote:
> On 13 June 2018 at 18:08, Rafael David Tinoco
> wrote:
> > On Wed, Jun 13, 2018 at 6:00 PM, Greg Kroah-Hartman
> > wrote:
> >> On Wed, Jun 13, 2018 at 05:47:49PM -0300, Rafael Tinoco wrote:
> >>> Results from Linaro’s test farm.
> >
On Wed, Jun 13, 2018 at 6:24 PM, Niklas Cassel wrote:
> Since commit cab673583d96 ("soc: Unconditionally include qcom Makefile"),
> we unconditionally include the soc/qcom/Makefile.
>
> This opens up the possibility to compile test the code even when
> building for other architectures.
Why do we
On 06/14/2018 03:58 AM, David Collins wrote:
> Hello Rajendra,
>
> On 06/11/2018 09:40 PM, Rajendra Nayak wrote:
>> As we move from no clients/consumers in kernel voting on corners,
>> to *some* voting and some not voting, we might end up in a situation
>> where the clients which remove votes c
On 6/13/2018 6:39 AM, Rob Herring wrote:
On Tue, Jun 12, 2018 at 01:40:34PM +0800, Songjun Wu wrote:
Previous implementation uses platform-dependent API to get the clock.
Those functions are not available for other SoC which uses the same IP.
The CCF (Common Clock Framework) have an abstracti
On Thu, Jun 14, 2018 at 12:05 PM, Vivek Gautam
wrote:
> On Wed, Jun 13, 2018 at 6:24 PM, Niklas Cassel
> wrote:
>> Since commit cab673583d96 ("soc: Unconditionally include qcom Makefile"),
>> we unconditionally include the soc/qcom/Makefile.
>>
>> This opens up the possibility to compile test th
On Thu, Jun 14, 2018 at 07:38:59AM +0200, Oscar Salvador wrote:
> On Thu, Jun 14, 2018 at 05:16:18AM +, Naoya Horiguchi wrote:
...
> >
> > My concern is that there are a few E820 memory types rather than
> > E820_TYPE_RAM and E820_TYPE_RESERVED, and I'm not sure that putting them
> > all into
Hi Amit,
On Tue, Jun 12, 2018 at 4:24 PM, Amit Kucheria wrote:
> SDM845 uses the TSENS v2 IP block
>
> Signed-off-by: Amit Kucheria
> ---
> Documentation/devicetree/bindings/thermal/qcom-tsens.txt | 1 +
> drivers/thermal/qcom/Makefile| 2 +-
> drivers/thermal/qcom
Hi David,
On 06/14/2018 06:02 AM, David Collins wrote:
> Hello Rajendra,
>
> On 06/11/2018 09:40 PM, Rajendra Nayak wrote:
>> The RPMh Power domain driver aggregates the corner votes from various
>> consumers for the ARC resources and communicates it to RPMh.
>>
>> We also add data for all power
On Wed, Jun 13, 2018 at 8:49 PM, Andy Shevchenko
wrote:
> On Mon, Jun 11, 2018 at 10:18 AM, Chris Chiu wrote:
>> Make asus-wmi notify on hotkey kbd brightness changes, listen for
>> brightness events and update the brightness directly in the driver.
>
>> For this purpose, bound check on brightnes
501 - 542 of 542 matches
Mail list logo