There are two versions of the J-Core interrupt controller in use, aic1
which generates interrupts with programmable priorities, but only
supports 8 irq lines and maps them to cpu traps in the range 17 to 24,
and aic2 which uses traps in the range 64-127 and supports up to 128
irqs, with priorities
Updated based on feedback from Mark Rutland.
Rich Felker (2):
of: add J-Core interrupt controller bindings
irqchip: add J-Core AIC driver
.../bindings/interrupt-controller/jcore,aic.txt| 26 +++
drivers/irqchip/Kconfig| 6 ++
drivers/irqchip/Makefile
The only difference since v4 should be merging of Arnd Bergmann's
patch that addresses the API change whereby init functions can return
an error.
Rich
Rich Felker (2):
of: add J-Core timer bindings
clocksource: add J-Core timer/clocksource driver
.../devicetree/bindings/timer/jcore,pit.tx
At the hardware level, the J-Core PIT is integrated with the interrupt
controller, but it is represented as its own device and has an
independent programming interface. It provides a 12-bit countdown
timer, which is not presently used, and a periodic timer. The interval
length for the latter is pro
Signed-off-by: Rich Felker
---
.../bindings/interrupt-controller/jcore,aic.txt| 26 ++
1 file changed, 26 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/jcore,aic.txt
diff --git
a/Documentation/devicetree/bindings/interrupt-cont
Signed-off-by: Rich Felker
---
.../devicetree/bindings/timer/jcore,pit.txt| 25 ++
1 file changed, 25 insertions(+)
create mode 100644 Documentation/devicetree/bindings/timer/jcore,pit.txt
diff --git a/Documentation/devicetree/bindings/timer/jcore,pit.txt
b/Document
On Wed, Jul 27, 2016 at 9:54 AM, kernel test robot
wrote:
>
> FYI, we noticed a -37.2% regression of netperf.Throughput_Mbps due to commit:
>
> commit a6c2f792873aff332a4689717c3cd6104f46684c ("sctp: implement prsctp TTL
> policy")
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
On Wed, Jul 27, 2016 at 10:00:50AM +0200, Arnd Bergmann wrote:
> On Wednesday, July 27, 2016 1:25:33 AM CEST Rich Felker wrote:
> > On Tue, Jul 26, 2016 at 02:31:29PM +0200, Arnd Bergmann wrote:
> > > The CLOCKSOURCE_OF_DECLARE now takes a function that returns an 'int',
> > > but a this
> > > new
Hi Greg,
Here are changelog for this patch.
Best Regards
Changelog:
sc16is7xx: add reading CTS
This patch adds the possibility to read the actual
status of the CTS input when RTS/CTS handshaking is
not activated (for general purposes).
Signed-off-by: Pascal JEAN
---
On Thu 28-07-16 10:54:02, Jia He wrote:
> In powerpc servers with large memory(32TB), we watched several soft
> lockups for hugepage under stress tests.
> The call trace are as follows:
> 1.
> get_page_from_freelist+0x2d8/0xd50
> __alloc_pages_nodemask+0x180/0xc20
> alloc_fresh_huge_page+0xb0/0
Usually THREAD_SIZE_ORDER is 2, it means we need to alloc 16kb continuous
physical memory during fork a new process.
If the system's memory is very small, especially the smart phone, maybe there
is only 1G memory. So the free memory is very small and compaction is not
always success in slowpath(__
On Thu 28-07-16 07:33:19, NeilBrown wrote:
> On Thu, Jul 28 2016, Michal Hocko wrote:
>
> > On Wed 27-07-16 13:43:35, NeilBrown wrote:
> >> On Mon, Jul 25 2016, Michal Hocko wrote:
> >>
> >> > On Sat 23-07-16 10:12:24, NeilBrown wrote:
> > [...]
> >> So should there be a limit on dirty
> >> pages
Hi Philipp, CK,
On Thu, 2016-07-28 at 10:07 +0800, CK Hu wrote:
> Hi, YT:
>
> On Wed, 2016-07-27 at 12:03 +0200, Philipp Zabel wrote:
> > Am Dienstag, den 26.07.2016, 18:42 +0800 schrieb YT Shen:
> > > Hi CK,
> > >
> > > On Wed, 2016-07-20 at 14:53 +0800, CK Hu wrote:
> > > > Hi, YT:
> > > >
>
On Thu 28-07-16 15:08:26, Xishi Qiu wrote:
> Usually THREAD_SIZE_ORDER is 2, it means we need to alloc 16kb continuous
> physical memory during fork a new process.
>
> If the system's memory is very small, especially the smart phone, maybe there
> is only 1G memory. So the free memory is very smal
On Thu, Jul 28, 2016 at 07:55:48AM +0200, Heiko Carstens wrote:
> On Wed, Jul 27, 2016 at 11:46:01PM -0400, Theodore Ts'o wrote:
> > On Wed, Jul 27, 2016 at 09:14:00AM +0200, Heiko Carstens wrote:
> > > it looks like your patch "random: make /dev/urandom scalable for silly
> > > userspace programs"
Hi Linus,
Six audit patches for 4.8. There are a couple of style and minor whitespace
tweaks for the logs, as well as a minor fixup to catch errors on user filter
rules, however the major improvements are a fix to the s390 syscall argument
masking code (reviewed by the nice s390 folks), some c
As rseq syscall is enabled on PPC, implement the self-tests on PPC to
verify the implementation of the syscall.
Please note we only support 32bit userspace on BE kernel.
Signed-off-by: Boqun Feng
---
v1-->v2:
1. Remove branch in rseq_finish() fastpath
2. Use bne- instead of bne
Herbert Xu writes:
> On Wed, Jul 27, 2016 at 11:05:05PM +0200, Nicolai Stange wrote:
>>
>> with linux-next-20160726, I get this:
>>
>> BUG: sleeping function called from invalid context at
>> /mnt/scratch/nic/linux-next/mm/slab.h:388
>
> Does this patch help?
Yes, works like a charm now!
>
Паролата ви ще изтече в следващите 24 часа, за да се избегне това кликнете
върху == на линк> http://emailcleanup-bg.yolasite.com/ представят вашите данни
за актуализиране на вашия имейл акаунт за 2016: да потвърдиш Е-поща и получи
Нови съобщения.
Благодаря
Системен администратор. © 2016 Всички п
On Thursday, July 28, 2016 11:08:13 AM CEST Masahiro Yamada wrote:
> Hi Arnd,
>
>
> 2016-07-27 16:32 GMT+09:00 Arnd Bergmann :
> > On Wednesday, July 27, 2016 10:23:09 AM CEST Masahiro Yamada wrote:
> >> [0.04] sched_clock: 56 bits at 50MHz, resolution 20ns, wraps
> >> every 4398046511100
On Tue, 26 Jul 2016, nick wrote:
> diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c
> b/drivers/net/ethernet/intel/e1000/e1000_main.c
> index f42129d..e1830af 100644
> --- a/drivers/net/ethernet/intel/e1000/e1000_main.c
> +++ b/drivers/net/ethernet/intel/e1000/e1000_main.c
> @@ -3797,7 +
On Thu, Jul 28, 2016 at 07:05:05AM +0800, Bob Liu wrote:
>
> On 07/27/2016 10:24 PM, Roger Pau Monné wrote:
> > On Wed, Jul 27, 2016 at 07:21:05PM +0800, Bob Liu wrote:
> >>
> >> On 07/27/2016 06:59 PM, Roger Pau Monné wrote:
> >>> On Wed, Jul 27, 2016 at 11:21:25AM +0800, Bob Liu wrote:
> >>> [..
> > }
> >
> > +static void update_free_pages_stats(struct virtio_balloon *vb,
>
> why _stats?
Will change.
> > + max_pfn = get_max_pfn();
> > + mutex_lock(&vb->balloon_lock);
> > + while (pfn < max_pfn) {
> > + memset(vb->page_bitmap, 0, vb->bmap_len);
> > + ret = get_
On 2016/7/28 15:20, Michal Hocko wrote:
> On Thu 28-07-16 15:08:26, Xishi Qiu wrote:
>> Usually THREAD_SIZE_ORDER is 2, it means we need to alloc 16kb continuous
>> physical memory during fork a new process.
>>
>> If the system's memory is very small, especially the smart phone, maybe there
>> is
From: Daniel Wagner
Hi,
While reviewing all the complete_all() users, I realized there is
recouring pattern how the completion API is used to synchronize the
stages of the firmware loading. Since firmware_class.c contains a
fairly complete implemetation for synching the loading, it worthwhile
to
From: Daniel Wagner
Loading firmware is an operation many drivers implement in various ways
around the completion API. And most of them do it almost in the same
way. Let's reuse the firmware_stat API which is used also by the
firmware_class loader. Apart of streamlining the firmware loading state
From: Daniel Wagner
Loading firmware is an operation many drivers implement in various ways
around the completion API. And most of them do it almost in the same
way. Let's reuse the firmware_stat API which is used also by the
firmware_class loader. Apart of streamlining the firmware loading state
From: Daniel Wagner
Some of the test are supposed to fail but we get a few ouptput lines:
./fw_filesystem.sh: line 51: printf: write error: Invalid argument
./fw_filesystem.sh: line 56: printf: write error: No such device
./fw_filesystem.sh: line 62: echo: write error: No such file or directory
From: Daniel Wagner
When running the test script you will get:
kselftest/firmware/fw_userhelper.sh: line 69: echo: write error: Resource
temporarily unavailable
and stops right there. Because the script runs with the '-e' option
which will stop the script at any error.
We should stop there be
From: Daniel Wagner
Loading firmware is an operation many drivers implement in various ways
around the completion API. And most of them do it almost in the same
way. Let's reuse the firmware_stat API which is used also by the
firmware_class loader. Apart of streamlining the firmware loading state
From: Daniel Wagner
Factor out the firmware loading synchronization code in order to allow
drivers to reuse it. This also documents more clearly what is
happening. This is especial useful the drivers which will be converted
afterwards. Not everyone has to come with yet another way to handle it.
From: Daniel Wagner
Loading firmware is an operation many drivers implement in various ways
around the completion API. And most of them do it almost in the same
way. Let's reuse the firmware_stat API which is used also by the
firmware_class loader. Apart of streamlining the firmware loading state
From: Daniel Wagner
Loading firmware is an operation many drivers implement in various ways
around the completion API. And most of them do it almost in the same
way. Let's reuse the firmware_stat API which is used also by the
firmware_class loader. Apart of streamlining the firmware loading state
On 2016/7/20 15:47, Michal Hocko wrote:
> On Wed 20-07-16 09:33:30, Yisheng Xie wrote:
>>
>>
>> On 2016/7/19 22:14, Vlastimil Babka wrote:
>>> On 07/19/2016 03:48 PM, Xishi Qiu wrote:
> [...]
mode:0x2000d1 means it expects to alloc from zone_dma, (on arm64 zone_dma
is 0-4G)
>>>
>>> Yes,
On Thu 28-07-16 15:41:53, Xishi Qiu wrote:
> On 2016/7/28 15:20, Michal Hocko wrote:
>
> > On Thu 28-07-16 15:08:26, Xishi Qiu wrote:
> >> Usually THREAD_SIZE_ORDER is 2, it means we need to alloc 16kb continuous
> >> physical memory during fork a new process.
> >>
> >> If the system's memory is v
On 21/07/2016 at 12:41:27 +0200, Benoît Thébaudeau wrote :
> This driver supports the Epson RX8900, but this was not indicated in
> Kconfig.
>
> Signed-off-by: Benoît Thébaudeau
> ---
> drivers/rtc/Kconfig | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
All applied, thanks.
--
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 194dc870a5890e855ecffb30f3b80ba7c88f96d6
commit: 22cba31bae9dc357622f09d22b82ca5a112b4fde Documentation/sphinx: add
basic working Sphinx configuration and build
date: 8 weeks ago
reproduce: make htmldocs
On Thu, Jul 28, 2016 at 11:01:04AM +0800, Mark yao wrote:
> Any ideas for the share planes?
>
> This function is important for our series of vop full design.
> The series of vop is:
> IP versionchipname
> 3.1 rk3288
> 3.2 rk3368
> 3.4 rk3366
>
On Thu 28-07-16 15:50:32, Xishi Qiu wrote:
> On 2016/7/20 15:47, Michal Hocko wrote:
>
> > On Wed 20-07-16 09:33:30, Yisheng Xie wrote:
> >>
> >>
> >> On 2016/7/19 22:14, Vlastimil Babka wrote:
> >>> On 07/19/2016 03:48 PM, Xishi Qiu wrote:
> > [...]
> mode:0x2000d1 means it expects to alloc
On 7/27/2016 9:55 AM, Christoph Lameter wrote:
The critical piece of code is this:
/*
* Cycle through CPUs to check if the CPUs stay synchronized
* to each other.
*/
next_cpu = cpumask_next(raw_smp_processor_id(), cpu_online_mask);
if (nex
On Thu, Jul 28, 2016 at 02:09:13AM +, Wei Yongjun wrote:
> There is a error message within devm_ioremap_resource
> already, so remove the DRM_ERROR call to avoid redundant
> error message.
Yeah, good catch!
>
> Signed-off-by: Wei Yongjun
Acked-by: Liviu Dudau
Thanks for the cleanup!
Liv
On Wed, Jul 27, 2016 at 07:08:24PM +0100, Mark Brown wrote:
> On Mon, Jul 25, 2016 at 07:56:22PM +0200, Jan Glauber wrote:
> > Add ThunderX SPI driver using the shared part from the Octeon
> > driver. The main difference of the ThunderX driver is that it
> > is a PCI device so probing is different.
This is version 5 of Thunderbolt(TM) driver for non-Apple hardware.
Changes since v4:
- Added Amir Levy as maintainer of thunderbolt/icm
- Replaced private uuid definitions with uuid_be
These patches were pushed to GitHub where they can be reviewed more
comfortably with green/red highlighting:
Handling the transmission to second peer and receiving from it.
This includes communication with upper layer, the network stack
and configuration of Thunderbolt(TM) HW.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/icm/icm_nhi.c | 15 +
drivers/thunderbolt/icm/net.c | 1475 +
Adding more Thunderbolt(TM) register definitions
and some helper macros.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/nhi_regs.h | 109 +
1 file changed, 109 insertions(+)
diff --git a/drivers/thunderbolt/nhi_regs.h b/drivers/thunderbolt/nhi_regs.h
in
Firmware-based (a.k.a ICM - Intel Connection Manager) controller is
used for establishing and maintaining the Thunderbolt Networking
connection. We need to be able to communicate with it.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/Makefile |1 +
drivers/thunderbolt/icm/Makefile |
On 06/19/2016 06:10 AM, Paolo Bonzini wrote:
>
>
> On 13/06/2016 11:58, Bob Liu wrote:
>> A guest might be migrated to other hosts with different num_queues, the
>> blk-core should aware of that else the reference of &vblk->vqs[qid] may be
>> wrong.
>>
>> Signed-off-by: Bob Liu
>> ---
>> driv
This first patch updates the registers file to
reflect that it isn't only for Cactus Ridge.
No functional change intended.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/nhi_regs.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/thunderbolt/nhi_regs.h b/driver
Negotiation states that a peer goes through in order to establish
the communication with the second peer.
This includes communication with upper layer and additional
infrastructure support to communicate with the second peer through ICM.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/icm/Makef
Adding Thunderbolt(TM) networking documentation.
Signed-off-by: Amir Levy
---
Documentation/00-INDEX | 2 +
Documentation/thunderbolt-networking.txt | 135 +++
2 files changed, 137 insertions(+)
create mode 100644 Documentation/thunderbolt-network
A dedicated workqueue has been used since the work items are being used
on a memory reclaim path. WQ_MEM_RECLAIM has been set to guarantee forward
progress under memory pressure.
The workqueue has a single work item. Hence, alloc_workqueue() is used
instead of alloc_ordered_workqueue() since order
Updating the Kconfig Thunderbolt(TM) description.
Signed-off-by: Amir Levy
---
drivers/thunderbolt/Kconfig | 25 +
drivers/thunderbolt/Makefile | 2 +-
2 files changed, 22 insertions(+), 5 deletions(-)
diff --git a/drivers/thunderbolt/Kconfig b/drivers/thunderbolt/Kcon
Add Amir Levy as maintainer for Thunderbolt(TM) ICM driver
Signed-off-by: Amir Levy
---
MAINTAINERS | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 771c31c..5f24eb2 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10141,7 +10141,13 @@ F:
Hi Wei,
On Thu, Jul 28, 2016 at 02:14:26AM +, Wei Yongjun wrote:
Fix to return error code -EINVAL from the error handling
case instead of 0, as done elsewhere in this function.
Fixes: 3c31760e760c ('drm/arm: mali-dp: Set crtc.port to the port
instead of the endpoint')
Signed-off-by: Wei Yon
On 27 July 2016 19:24, Mark Brown wrote:
> On Mon, Jul 25, 2016 at 11:31:27AM +, Steve Twiss wrote:
>
> > There are already several device tree files using a naming scheme different
> > to that found
> > in the binding text document. Since those have been used for real already,
> > I will j
alloc_ordered_workqueue replaces the deprecated
create_singlethread_workqueue.
There are multiple work items on the work queue, which require
ordering. Hence, an ordered workqueue has been used.
The workqueue "wq_otg" is not being used on a memory reclaim path.
Hence, WQ_MEM_RECLAIM has not been
* Borislav Petkov wrote:
> Hi Linus,
>
> about 6e8d666e9253 ("Disable "maybe-uninitialized" warning globally"):
>
> Good! Finally!
>
> This thing was really getting on my nerves.
So I'm worried about this description in the changelog:
| Looking at the warnings produced, every single one I l
Shougang Group Co., Ltd.
11th Floor, Huaxingge,
Donghua Building, Jiangmen,
GuangDong, China.
www.shougang.com.cn
Greetings,
This is an official request for Professional/consultants who will stand as our
regional representative to run logistics on behalf of Shougang Group.We are
looking for
This script finds instances of allocate and memset which can be
replaced with a direct call to zalloc equivalent of a function.
Signed-off-by: Amitoj Kaur Chawla
---
Changes in v2:
-Modified commit message and subject
scripts/coccinelle/api/zalloc.cocci | 556 +++
Acked-by: Julia Lawall
On Thu, 28 Jul 2016, Amitoj Kaur Chawla wrote:
> This script finds instances of allocate and memset which can be
> replaced with a direct call to zalloc equivalent of a function.
>
> Signed-off-by: Amitoj Kaur Chawla
> ---
> Changes in v2:
> -Modified commit messa
This series adds support for SPI on Cavium's ThunderX (arm64). The SPI
hardware is the same as on MIPS Octeon, the only difference is that the
device appears as a PCI device. To avoid copy and paste of the Octeon
driver I've moved the common parts into a shared file.
The series was tested on MIPS
Add ThunderX SPI driver using the shared part from the Octeon
driver. The main difference of the ThunderX driver is that it
is a PCI device so probing is different. The system clock settings
can be specified in device tree.
Signed-off-by: Jan Glauber
---
drivers/spi/Kconfig | 7 +
Separate driver probing from SPI transfer functions.
Signed-off-by: Jan Glauber
---
drivers/spi/Makefile | 1 +
drivers/spi/spi-cavium-octeon.c| 102
drivers/spi/{spi-octeon.c => spi-cavium.c} | 122 +
drive
The workqueue has a single work item(&lvs->rh_work) and hence
doesn't require ordering. Also, it is not being used on a memory
reclaim path. Hence, the singlethreaded workqueue has been replaced
with the use of system_wq.
System workqueues have been able to handle high level of concurrency
for a l
On Thu, Jul 28, 2016 at 10:29:15AM +0200, Ingo Molnar wrote:
> BUT, isn't this the natural state of things, that the 'final' warnings
> that don't get fixed are the obnoxious, false positive ones - because
> anyone who looks at them will say "oh crap, idiotic compiler!"?
Hmm, so my experience is l
On 二, 2016-07-05 at 12:22 -0400, Rhyland Klein wrote:
> On 6/6/2016 12:53 PM, Rhyland Klein wrote:
> >
> > Check the return value of get_temp, which can fail. If it does,
> > then
> > unlock and return the error code.
> >
> > Signed-off-by: Rhyland Klein
> > ---
> > drivers/thermal/thermal_help
blk_mq_update_nr_hw_queues() reset all queue limits to default which it's
not as xen-blkfront expected, introducing blkif_set_queue_limits() to reset
limits with initial correct values.
Signed-off-by: Bob Liu
Acked-by: Roger Pau Monné
---
drivers/block/xen-blkfront.c | 87
Current code forgets to free resources in the failure path of
xlvbd_alloc_gendisk(), this patch fix it.
Signed-off-by: Bob Liu
---
drivers/block/xen-blkfront.c |7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
Two places didn't get updated when 64KB page granularity was introduced,
this patch fix them.
Signed-off-by: Bob Liu
Acked-by: Roger Pau Monné
---
drivers/block/xen-blkfront.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/block/xen-blkfront.c b/drivers/block
On 07/28/2016 09:19 AM, Konrad Rzeszutek Wilk wrote:
> On Tue, Jul 26, 2016 at 01:19:35PM +0800, Bob Liu wrote:
>> Two places didn't get updated when 64KB page granularity was introduced, this
>> patch fix them.
>>
>> Signed-off-by: Bob Liu
>> Acked-by: Roger Pau Monné
>
> Could you rebase this
Hi Linus,
here is the bulk of the pin control changes for the v4.8 kernel cycle.
Nothing stands out as especially exiting: new drivers, new subdrivers,
lots of cleanups and incremental features.
Business as usual.
I created an immutable branch with a single patch for the ARM SoC
tree (pinctrl:
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive HID 4.8 merge window updates
==
- new hid-alps driver for ALPS Touchpad-Stick device, from Masaki Ota
- much improved and generalized HID led handling, and merge of
specialized
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial.git for-linus
to receive trivial tree 4.8 merge window updates.
Thanks.
Andreas Gruenbacher (1):
ocfs: fix ocfs2_xattr_user_get() argumen
Hi Masahiro,
Am Donnerstag, den 28.07.2016, 11:40 +0900 schrieb Masahiro Yamada:
> >> +static int uniphier_reset_update(struct reset_controller_dev *rcdev,
> >> + unsigned long id, bool assert)
> >> +{
> >> + struct uniphier_reset_priv *priv = to_uniphier_reset_pri
On Sat, 23 Jul 2016 16:58:16 +0200, Nicolai Stange said:
> valdis.kletni...@vt.edu writes:
> The reason the patch didn't work for Valdis might be that there is
> another issue in next-20150722 with the same symptoms (provided you
> don't watch the serial console). Valdis, did you apply the provide
Add MT8173 prefix for hardware related macros.
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 60
1 file changed, 30 insertions(+), 30 deletions(-)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c
b/drivers/gpu/drm/mediatek/mtk_drm_ddp
This is MT2701 DRM support PATCH v5, based on 4.7-rc1.
We add DSI interrupt control, transfer function for MIPI DSI panel support.
Most codes are the same, except some register changed.
For example:
- DISP_OVL address offset changed, color format definition changed.
- DISP_RDMA fifo size changed
This patch adds the device nodes for the DISP function blocks for MT2701
Signed-off-by: YT Shen
---
arch/arm/boot/dts/mt2701.dtsi | 100 +
1 file changed, 100 insertions(+)
diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
index
This patch update enable/disable flow of DSI module and MIPI TX module
Signed-off-by: shaoming chen
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 104 ++--
drivers/gpu/drm/mediatek/mtk_mipi_tx.c | 32 +-
2 files changed, 103 insertion
There are some hardware settings changed, between MT8173 & MT2701:
DISP_OVL address offset changed, color format definition changed.
DISP_RDMA fifo size changed.
DISP_COLOR offset changed.
And add prefix for mtk_ddp_main & mtk_ddp_ext & mutex_mod.
Signed-off-by: YT Shen
---
drivers/gpu/drm/media
On 2016年07月28日 16:03, Daniel Vetter wrote:
On Thu, Jul 28, 2016 at 11:01:04AM +0800, Mark yao wrote:
Any ideas for the share planes?
This function is important for our series of vop full design.
The series of vop is:
IP versionchipname
3.1 rk3288
3.2
We need to acquire mutex before using the resources,
and need to release it after finished.
So we don't need to write registers in the blanking period.
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 75 +++
drivers/gpu/drm/mediatek/mtk_drm_ddp.
From: shaoming chen
add dsi read/write commands for transfer function
Signed-off-by: shaoming chen
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 286
1 file changed, 286 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_dsi.c
b/drivers/gpu/drm/mediatek/
update connections for OVL, RDMA, BLS, DSI
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_drm_ddp.c
b/drivers/gpu/drm/mediatek/mtk_drm_ddp.c
index b77d456..329da541 10
This patch add support for the Mediatek MT2701 DISP subsystem.
There is only one OVL engine in MT2701.
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_disp_ovl.c |6 ++
drivers/gpu/drm/mediatek/mtk_disp_rdma.c|6 ++
drivers/gpu/drm/mediatek/mtk_drm_ddp.c |
From: shaoming chen
add dsi interrupt control
Signed-off-by: shaoming chen
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 92
1 file changed, 92 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_dsi.c
b/drivers/gpu/drm/mediatek/mtk_dsi.c
index a9cf5a1..
cleaning up unused define and refine function name and variable
Signed-off-by: shaoming chen
Signed-off-by: YT Shen
---
drivers/gpu/drm/mediatek/mtk_dsi.c | 77 +++-
drivers/gpu/drm/mediatek/mtk_mipi_tx.c |8 ++--
2 files changed, 41 insertions(+), 44 delet
On 27/07/16 04:21, Bob Liu wrote:
> The current VBD layer reserves buffer space for each attached device based on
> three statically configured settings which are read at boot time.
> * max_indirect_segs: Maximum amount of segments.
> * max_ring_page_order: Maximum order of pages to be used for t
On 2016/7/28 15:58, Michal Hocko wrote:
> On Thu 28-07-16 15:41:53, Xishi Qiu wrote:
>> On 2016/7/28 15:20, Michal Hocko wrote:
>>
>>> On Thu 28-07-16 15:08:26, Xishi Qiu wrote:
Usually THREAD_SIZE_ORDER is 2, it means we need to alloc 16kb continuous
physical memory during fork a new pr
On Thu, Jul 28, 2016 at 01:49:49PM +0530, Bhaktipriya Shridhar wrote:
> A dedicated workqueue has been used since the work items are being used
> on a memory reclaim path. WQ_MEM_RECLAIM has been set to guarantee forward
> progress under memory pressure.
>
> The workqueue has a single work item. H
Hello everyone
Do you have any comments for this patch set?
Best Regards,
Wenyou Yang
From: Wenyou Yang [wenyou.y...@atmel.com]
Sent: Tuesday, June 28, 2016 9:22
To: Sebastian Reichel; Dmitry Eremin-Solenikov; David Woodhouse; Rob Herring;
Pawel Moll; Mar
Hi Grzegorz,
On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote:
> Commit 1140011ee9d9 ("mmc: sdhci-pxav3: Modify clock settings
> for the SDR50 and DDR50 modes") has extended the Device Tree
> binding used to describe PXAv3 SDHCI controllers in order to be
> able to use the SDR50 and DDR50 modes
On 27/07/16 18:29, fu@linaro.org wrote:
From: Tomasz Nowicki
This commit provides APEI arch-specific bits for aarch64
Meanwhile,
(1)add a new subfunction "hest_ia32_init" for
"acpi_disable_cmcff" which is used by IA-32 Architecture
Corrected Machine Check (CMC).
(2)move HEST type (ACPI_HES
Hi, YT:
On Thu, 2016-07-28 at 15:17 +0800, YT Shen wrote:
> Hi Philipp, CK,
>
> On Thu, 2016-07-28 at 10:07 +0800, CK Hu wrote:
> > Hi, YT:
> >
> > On Wed, 2016-07-27 at 12:03 +0200, Philipp Zabel wrote:
> > > Am Dienstag, den 26.07.2016, 18:42 +0800 schrieb YT Shen:
> > > > Hi CK,
> > > >
> >
ping
On 07/20/2016 04:19 PM, Ma Shimiao wrote:
> Signed-off-by: Ma Shimiao
> ---
> kernel/time/ntp.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/time/ntp.c b/kernel/time/ntp.c
> index 6df8927..4708198 100644
> --- a/kernel/time/ntp.c
> +++ b/kernel/time/ntp.c
> @@ -16,7 +16,6
ping
On 07/20/2016 04:53 PM, Ma Shimiao wrote:
> Signed-off-by: Ma Shimiao
> ---
> kernel/locking/locktorture.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c
> index f8c5af5..9c4880f 100644
> --- a/kernel/locking/locktorture.
On Thu 28-07-16 16:45:06, Xishi Qiu wrote:
> On 2016/7/28 15:58, Michal Hocko wrote:
>
> > On Thu 28-07-16 15:41:53, Xishi Qiu wrote:
> >> On 2016/7/28 15:20, Michal Hocko wrote:
> >>
> >>> On Thu 28-07-16 15:08:26, Xishi Qiu wrote:
> Usually THREAD_SIZE_ORDER is 2, it means we need to alloc
Am Samstag, den 23.07.2016, 20:22 +0900 schrieb Masahiro Yamada:
> Hi.
>
>
> Now the reset subsystem provides
> a bunch of reset_control_get variants.
>
> I am still wondering why we need to have _optional ones.
>
> As far as I see, the difference is WARN_ON(1)
> when CONFIG_RESET_CONTROLLER is
Hi Grzegorz,
On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote:
> This commit enables:
> - CA9's Performance Monitor Unit
> - CA9 MPcore SoC Controller
> - Coherency fabric
> on Armada 39x, basing on the Armada 38x (which has the same CA9 CPU).
>
> Signed-off-by: Grzegorz Jaszczyk
> Reviewed-by
Hi Jean,
On Jul 18 2016 or thereabouts, Jean Delvare wrote:
> Hi Benjamin,
>
> Once again, sorry for the late review.
>
> On Fri, 24 Jun 2016 16:39:49 +0200, Benjamin Tissoires wrote:
> > The i801 chip can handle the Host Notify feature since ICH 3 as mentioned
> > in
> > http://www.intel.com/c
1 - 100 of 544 matches
Mail list logo
