Rockchip RGA is a separate 2D raster graphic acceleration unit. It
accelerates 2D graphics operations, such as point/line drawing, image
scaling, rotation, BitBLT, alpha blending and image blur/sharpness
The drvier is mostly based on s5p-g2d v4l2 m2m driver
And supports various operations from the
> -Original Message-
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Wednesday, July 26, 2017 20:05
> To: Mika Westerberg
> Cc: LKML ; Linux PM p...@vger.kernel.org>; Andreas Noever ;
> Jamet, Michael ; Greg Kroah-Hartman
>
> Subject: Re: [RFC][PATCH] thunderbolt: icm: Igno
Hi,
2017-07-31 14:51 GMT+08:00 Jacob Chen :
> Rockchip RGA is a separate 2D raster graphic acceleration unit. It
> accelerates 2D graphics operations, such as point/line drawing, image
> scaling, rotation, BitBLT, alpha blending and image blur/sharpness
>
> The drvier is mostly based on s5p-g2d v4
Hey Marcus,
On 29-07-17 16:17, codekip...@gmail.com wrote:
From: Marcus Cooper
Hi All,
please find attached a series of patches to bring i2s support to the
Allwinner H3 SoC. This has been tested with the following setups:
A20 Olimex EVB connected to a pcm5102
But that's not an H3 is it? :)
Hi,
> From: Julia Lawall
> Sent: Saturday, July 29, 2017 5:42 AM
>
> The hc_driver structure is only passed as the first argument to
> usb_create_hcd, which is declared as const. Thus the hc_driver structure
> itself can be const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia
On Mon, Jul 31, 2017 at 9:50 AM, Arnd Bergmann wrote:
> A sockaddr_in structure on the stack getting passed into rdma_ip2gid
> triggers this warning, since we memcpy into a larger sockaddr_in6
> structure:
>
> In function 'memcpy',
> inlined from 'rdma_ip2gid' at include/rdma/ib_addr.h:175:3,
Ben,
On Mon, 31 Jul 2017, Benjamin Herrenschmidt wrote:
> I noticed a problem with some powerpc systems with threaded IRQs. I
> hadn't looked at threaded irq in the past so there was a bit of
> discovery involved. That lead to a few questions:
>
> - Threaded IRQs rely on IRQF_ONESHOT. Now, is th
On Fri, Jul 28, 2017 at 10:41:57PM +0200, Julia Lawall wrote:
> The hc_driver structure is only passed as the first argument to
> usb_create_hcd, which is declared as const. Thus the hc_driver structure
> itself can be const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
()On Mon, Jul 31, 2017 at 12:41 AM, Jernej Skrabec
wrote:
> ccu_frac_helper_read_rate() prints some info which is not really
> helpful except during debugging.
>
> Replace printk() with pr_debug().
>
> Signed-off-by: Jernej Skrabec
Queued as a fix for 4.13 with the following tag:
Fixes: 89a3dfb
On Mon, Jul 31, 2017 at 07:16:59AM +0900, Minchan Kim wrote:
> rw_page's gain is reducing of dynamic allocation in swap path
> as well as performance gain thorugh avoiding bio allocation.
> And it would be important in memory pressure situation.
There is no need for any dynamic allocation when usi
This patch is to replace the use of BUG_ON macro with WARN_ON
inorder to prevent the crashing of the kernel.
Signed-off-by: Janani Sankara Babu
---
drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/vc04_s
Hi,
2017-07-31 11:07 GMT+08:00 Jacob Chen :
> This patch series add a v4l2 m2m drvier for rockchip RGA direct rendering
> based 2d graphics acceleration module.
>
> Before, my colleague yakir have write a drm RGA drvier and send it to the
> lists.
> http://lists.infradead.org/pipermail/linux-ar
On 28/07/17 19:26, Thomas Gleixner wrote:
On Fri, 28 Jul 2017, Tomi Sarvela wrote:
On 28/07/17 17:50, Thomas Gleixner wrote:
On Fri, 28 Jul 2017, Tomi Sarvela wrote:
On 28/07/17 17:13, Thomas Gleixner wrote:
On Fri, 28 Jul 2017, Tomi Sarvela wrote:
On 28/07/17 16:15, Thomas Gleixner wrote:
On Fri 28-07-17 10:23:21, Jeff Layton wrote:
> From: Jeff Layton
>
> This patch converts most of the in-kernel filesystems that do writeback
> out of the pagecache to report errors using the errseq_t-based
> infrastructure that was recently added. This allows them to report
> errors once for each
On Mon, Jul 31, 2017 at 9:08 AM, Moni Shoua wrote:
> On Mon, Jul 31, 2017 at 9:50 AM, Arnd Bergmann wrote:
>> --- a/include/rdma/ib_addr.h
>> +++ b/include/rdma/ib_addr.h
>> @@ -172,7 +172,8 @@ static inline int rdma_ip2gid(struct sockaddr *addr,
>> union ib_gid *gid)
>>
On Sun, Jul 30, 2017 at 1:36 PM, Icenowy Zheng wrote:
> The I2C pin functions in R_PIO used to be named "s_twi".
>
> As we usually use the name "i2c" instead of "twi" in the mainline
> kernel, change these names to "s_i2c" for consistency.
>
> The "s_twi" functions are not yet referenced by any de
Adds a generic powercap framework to change the system powercap
inband through OPAL-OCC command/response interface.
Signed-off-by: Shilpasri G Bhat
---
.../ABI/testing/sysfs-firmware-opal-powercap | 31 +++
arch/powerpc/include/asm/opal-api.h| 5 +-
arch/powerpc/include/
In P9, OCC (On-Chip-Controller) supports shared memory based
commad-response interface. Within the shared memory there is an OPAL
command buffer and OCC response buffer that can be used to send
inband commands to OCC. The following commands are supported:
1) Set system powercap
2) Set CPU-GPU powe
From: John Crispin
Enable the nand device and setup pinmux on the mt7632m rfb with nand
support.
Signed-off-by: John Crispin
Signed-off-by: Sean Wang
---
arch/arm/boot/dts/mt7623n-rfb-nand.dts | 88 ++
1 file changed, 88 insertions(+)
diff --git a/arch/arm/boo
Adds support for clearing different sensor groups. OCC inband sensor
groups like CSM, Profiler, Job Scheduler can be cleared using this
driver. The min/max of all sensors belonging to these sensor groups
will be cleared.
Signed-off-by: Shilpasri G Bhat
---
.../bindings/powerpc/opal/sensor-groups
This patch adds support to set power-shifting-ratio which hints the
firmware how to distribute/throttle power between different entities
in a system (e.g CPU v/s GPU). This ratio is used by OCC for power
capping algorithm.
Signed-off-by: Shilpasri G Bhat
---
Documentation/ABI/testing/sysfs-firmw
From: Sean Wang
There are 2 versions of the MT7623 SoC, the one is MT7623N and the other
is MT7623A. MT7623N is almost identical to MT7623A but has some
additional multimedia features. The reference boards are available as
NAND or MMC and might have a different ethernet setup. In order to reduce
On 21.7.2017 17:47, Sören Brinkmann wrote:
> On Fri, 2017-07-21 at 11:32:24 +0200, Michal Simek wrote:
>> register_console() is called from
>> uart_add_one_port()->uart_configure_port()
>> that's why register_console() is called twice.
>>
>> This patch remove console_initcall to call register_conso
From: John Crispin
MediaTek produces various PMICs. Which one is used depends on the actual
circuit design. Instead of adding the correct PMIC node to every dts file
we instead add a new intermediate dtsi file which adds the PMIC node. For
those boards with the same PMIC, the intermediate mt6323.
From: Sean Wang
Add support for the Bananapi R2 (BPI-R2) development board from
BIPAI KEJI. Detailed hardware information for BPI-R2 which could be
found on http://www.banana-pi.org/r2.html
The patch added nodes into the SoC-level file mt7623.dtsi such as CPU OPP
table and thermal zone treating
From: John Crispin
All versions of the mt7623n RFB have an USB port so enable the device.
There is a gpio that gets used to power up the port supply. Add support
for this gpio using the fixed-regulator driver.
Signed-off-by: John Crispin
Signed-off-by: Sean Wang
---
arch/arm/boot/dts/mt7623n-
From: John Crispin
This patch does a cleanup of the uart nodes in the dts file of the RFB. It
adds aliases, enables 2 more uarts and explicitly sets the uart mode of the
console.
Signed-off-by: John Crispin
Signed-off-by: Sean Wang
---
arch/arm/boot/dts/mt7623n-rfb.dtsi | 16 +++-
From: Sean Wang
Add clock-frequency property to CPU nodes. Avoids warnings like
[0.001568] /cpus/cpu@0 missing clock-frequency property
[0.001588] /cpus/cpu@1 missing clock-frequency property
[0.001601] /cpus/cpu@2 missing clock-frequency property
[0.001614] /cpus/cpu@3 missing cl
From: Sean Wang
This adds DT binding documentation for Mediatek MT7623a
Signed-off-by: Sean Wang
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/arm/mediatek.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
b/Documentation
Hi Michal,
Sorry for my delay...
On Tue, Jul 25, 2017 at 02:48:37PM +0200, Michal Hocko wrote:
> On Mon 24-07-17 17:29:21, Joey Lee wrote:
> > On Mon, Jul 24, 2017 at 10:57:02AM +0200, Michal Hocko wrote:
> > > On Wed 19-07-17 17:09:10, Joey Lee wrote:
> > > > On Mon, Jul 17, 2017 at 11:05:25AM +
On 07/31/2017 02:55 PM, Michal Hocko wrote:
On Mon 31-07-17 12:13:33, Wei Wang wrote:
Ballooned pages will be marked as MADV_DONTNEED by the hypervisor and
shouldn't be given to the host ksmd to scan.
Could you point me where this MADV_DONTNEED is done, please?
Sure. It's done in the hypervis
From: Sean Wang
Add support for booting secondary CPUs on MT7623a.
Signed-off-by: Sean Wang
---
arch/arm/mach-mediatek/mediatek.c | 2 ++
arch/arm/mach-mediatek/platsmp.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/arch/arm/mach-mediatek/mediatek.c
b/arch/arm/mach-mediatek/mediatek
From: Sean Wang
Change since v4:
- split mt6323 nodes as the independent item which tends to integration with
other MediaTek SoCs
- enhanced commit log
- fixed up building warning shown in make dtsb
- added clock-frequency to CPU nodes to avoid warning in boot time
- added more nodes into the S
on qemu upstream, code in qemu/util/osdep.c
int qemu_madvise(void *addr, size_t len, int advice)
{
if (advice == QEMU_MADV_INVALID) {
errno = EINVAL;
return -1;
}
#if defined(CONFIG_MADVISE)
return madvise(addr, len, advice);
#elif defined(CONFIG_POSIX_MADVISE)
From: Sean Wang
Because there are two versions of MT7623 SoC that is MT7623a and MT7623n
respectively. So update the part of MT7623n bindings to allow that people
tend to differentiate which MT7623 SoC the boards applies.
And "mediatek,mt7623-evb" can be safely changed to
"mediatek,mt7623n-rfb-n
On Mon, Jul 31, 2017 at 09:17:07AM +0200, Christoph Hellwig wrote:
> On Mon, Jul 31, 2017 at 07:16:59AM +0900, Minchan Kim wrote:
> > rw_page's gain is reducing of dynamic allocation in swap path
> > as well as performance gain thorugh avoiding bio allocation.
> > And it would be important in memor
On Mon, Jul 31, 2017 at 04:36:47PM +0900, Minchan Kim wrote:
> Do you suggest define something special flag(e.g., SWP_INMEMORY)
> for in-memory swap to swap_info_struct when swapon time manually
> or from bdi_queue_someting automatically?
> And depending the flag of swap_info_struct, use the onstac
> Sun, Jul 30, 2017 at 11:11 PM, David Lechner wrote:
> fbdev has a place for the physical width and height of a display. I would
> like to have this information available to userspace. This patch works for me,
> but I have a strong suspicion that this is not the "right way".
>
> Any suggestions o
On 04/14/2015 12:14 AM, Arnaldo Carvalho de Melo wrote:
> From: Namhyung Kim
>
> The struct page is opaque for userspace tools, so it'd be better to save
> pfn in order to identify page frames.
>
> The textual output of $debugfs/tracing/trace file remains unchanged and
> only raw (binary) data f
On 28.7.2017 20:39, Alan Cox wrote:
> On Fri, 21 Jul 2017 11:32:23 +0200
> Michal Simek wrote:
>
>> Hi Alan,
>>
>> this is the initial version before next step which is move
>> uart_register_driver to probe function.
>> I was able to get rid of static array with uart_port structures.
>> It was wi
On Mon 31-07-17 15:41:49, Wei Wang wrote:
> On 07/31/2017 02:55 PM, Michal Hocko wrote:
> >On Mon 31-07-17 12:13:33, Wei Wang wrote:
> >>Ballooned pages will be marked as MADV_DONTNEED by the hypervisor and
> >>shouldn't be given to the host ksmd to scan.
> >Could you point me where this MADV_DONTN
On Mon, Jul 31, 2017 at 09:42:06AM +0200, Christoph Hellwig wrote:
> On Mon, Jul 31, 2017 at 04:36:47PM +0900, Minchan Kim wrote:
> > Do you suggest define something special flag(e.g., SWP_INMEMORY)
> > for in-memory swap to swap_info_struct when swapon time manually
> > or from bdi_queue_someting
In P9, OCC (On-Chip-Controller) supports shared memory based
commad-response interface. Within the shared memory there is an OPAL
command buffer and OCC response buffer that can be used to send
inband commands to OCC. The following commands are supported:
1) Set system powercap
2) Set CPU-GPU powe
Adds a generic powercap framework to change the system powercap
inband through OPAL-OCC command/response interface.
Signed-off-by: Shilpasri G Bhat
---
.../ABI/testing/sysfs-firmware-opal-powercap | 31 +++
arch/powerpc/include/asm/opal-api.h| 5 +-
arch/powerpc/include/
This patch adds support to set power-shifting-ratio which hints the
firmware how to distribute/throttle power between different entities
in a system (e.g CPU v/s GPU). This ratio is used by OCC for power
capping algorithm.
Signed-off-by: Shilpasri G Bhat
---
Documentation/ABI/testing/sysfs-firmw
Adds support for clearing different sensor groups. OCC inband sensor
groups like CSM, Profiler, Job Scheduler can be cleared using this
driver. The min/max of all sensors belonging to these sensor groups
will be cleared.
Signed-off-by: Shilpasri G Bhat
---
.../bindings/powerpc/opal/sensor-groups
On Mon, 31 Jul 2017, Tomi Sarvela wrote:
> On 28/07/17 19:26, Thomas Gleixner wrote:
> > Did you change anything else compared to the tests before ?
>
> I did check that the problem persisted in linus-HEAD before testing your
> patch. The testing was done in order (reading from console logs I happ
Hi Thomas !
I noticed a problem with some powerpc systems with threaded IRQs. I
hadn't looked at threaded irq in the past so there was a bit of
discovery involved. That lead to a few questions:
- Threaded IRQs rely on IRQF_ONESHOT. Now, is that a flag/feature that
is generally exposed to drivers
Hi Egil,
On Sunday 30 July 2017 19:58:52 Egil Hjelmeland wrote:
> This series fix the MDIO interface for the lan9303 DSA driver.
> Bugs found after testing on actual HW.
>
> This series is extracted from the first patch of my first large
> series. Significant changes from that version are:
> - us
On Mon 31-07-17 15:41:49, Wei Wang wrote:
> On 07/31/2017 02:55 PM, Michal Hocko wrote:
> >On Mon 31-07-17 12:13:33, Wei Wang wrote:
> >>Ballooned pages will be marked as MADV_DONTNEED by the hypervisor and
> >>shouldn't be given to the host ksmd to scan.
> >Could you point me where this MADV_DONTN
On Sun, Jul 30, 2017 at 02:07:09PM +0530, Arvind Yadav wrote:
> pci_device_id are not supposed to change at runtime. All functions
> working with pci_device_id provided by work with
> const pci_device_id. So mark the non-const structs as const.
Can't this go all in one patch instead of replicatin
On 31/07/17 10:45, Thomas Gleixner wrote:
On Mon, 31 Jul 2017, Tomi Sarvela wrote:
On 28/07/17 19:26, Thomas Gleixner wrote:
Did you change anything else compared to the tests before ?
I did check that the problem persisted in linus-HEAD before testing your
patch. The testing was done in orde
On Sat, 29 Jul 2017, Nicolas Pitre wrote:
> Split out the priority inheritance support to a file of its own
> to make futex.c much smaller, easier to understand and, hopefully,
> to maintain. This also makes it easy to preserve basic futex support
> and compile out the PI support when RT mutexes a
Hi Christoph,
Sorry for the delay, this patch slipped trough the cracks somehow, I
only noticed it in my mailbox today.
On Mon, 15 May 2017 22:30:56 +0200, Christoph Hellwig wrote:
> ... and __initconst if applicable.
>
> Based on similar work for an older kernel in the Grsecurity patch.
On the
On 07/31/2017 06:01 AM, Dima Zavin wrote:
> In codepaths that use the begin/retry interface for reading
> mems_allowed_seq with irqs disabled, there exists a race condition that
> stalls the patch process after only modifying a subset of the
> static_branch call sites.
>
> This problem manifested
This patch fixes the following four warnings found using sparse:
drivers/staging/pi433/pi433_if.c:211:9: warning: mixing different enum types
drivers/staging/pi433/pi433_if.c:211:9: int enum optionOnOff versus
drivers/staging/pi433/pi433_if.c:211:9: int enum packetFormat
drivers/staging/p
On 07/28/2017 06:32 PM, Jerome Brunet wrote:
> mpll0 clock is special compared to the other mplls. It needs another
> bit (ssen) to be set to activate the fractional part the mpll divider
>
> Fixes: 007e6e5c5f01 ("clk: meson: mpll: add rw operation")
> Signed-off-by: Jerome Brunet
> ---
> driver
On Sun, Jul 30, 2017 at 10:37 AM, Arvind Yadav
wrote:
> pci_device_id are not supposed to change at runtime. All functions
> working with pci_device_id provided by work with
> const pci_device_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/scsi/pm800
Hi,
On 07/29/2017 10:04 AM, Chris Moore wrote:
> Hi,
>
> Sorry I forgot to reply to all in my previous post :(
> I hope this corrects things.
>
> Le 28/07/2017 à 11:53, Neil Armstrong a écrit :
>
> [snip]
>
>> +static long aoclk_cec_32k_round_rate(struct clk_hw *hw, unsigned long rate,
>> +
On 07/31/2017 05:07 AM, Jacob Chen wrote:
> At peresent, we don't have a control for Compositing and Blend.
> All drivers are just doing copies while actually many hardwares
> supports more functions.
>
> So Adding V4L2 controls for Compositing and Blend, used for for
> composting streams.
>
> Th
On 07/10/2017 09:56 AM, Neil Armstrong wrote:
> This patchset enables :
> - Support for the AO domain CEC 32k clock
> - AO CEC Controller linked with the HDMI controller all HDMI supported boards
>
> Neil Armstrong (2):
> ARM64: dts: meson-gx: Add PWR and CRT/RTC nodes and adresses
> ARM64:
On Sun, Jul 30, 2017 at 12:29:25PM +0530, Arvind Yadav wrote:
> Fix checkpatch.pl error:
> ERROR: space prohibited before open square bracket '['.
>
> Signed-off-by: Arvind Yadav
Thanks, applied for v4.14.
Am 31.07.2017 um 09:14 schrieb janani-sankarababu:
> This patch is to replace the use of BUG_ON macro with WARN_ON
> inorder to prevent the crashing of the kernel.
Unfortunately it isn't always that simple. checkpatch isn't smart. It's
preferred to handle error cases instead of flooding the kernel
The commit includes changes:
1)Add mt2712 pinctrl driver.
2)Arrange "mtk_pinctrl" before "mtk_pinctrl_devdata"
in "pinctrl-mtk-common.h".
3)Add "spec_dir_set" and "spec_dir_get" in "mtk_pinctrl_devdata".
4)Change "spec_dir_set" and add "spec_dir_get" in "pinctrl-mt2701.c"
and "pinctrl-mtk-commo
This series includes three patches:
1.Add mt2712 compatible node in binding document.
2.Add mt2712 pinctrl device node.
3.Add mt2712 pinctrl driver.
Zhiyong Tao (3):
dt-bindings: pinctrl: mt2712: add binding document
arm64: dts: mt2712: add pintcrl device node.
pinctrl: add mt2712 pinctrl dr
Compliment of the day,
I am Mr.Kere Casmire I Have a Business Proposal of $5.3 million For You.
I am aware of the unsafe nature of the internet,
and was compelled to use this medium due to the nature of this project.
I have access to very vital information that can be used to transfer
this huge a
The commit includes two change:
1)add pintcrl device node for mt2712.
2)add pinfunc file for mt2712.
Signed-off-by: Zhiyong Tao
---
arch/arm64/boot/dts/mediatek/mt2712-pinfunc.h | 1014 +
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 18 +
2 files changed, 1032 insert
The commit adds mt2712 compatible node in binding document.
Signed-off-by: Zhiyong Tao
---
.../devicetree/bindings/pinctrl/pinctrl-mt65xx.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/pinctrl/pinctrl-mt65xx.txt
b/Documentation/devicetree/bindings/p
On Mon, Jul 24, 2017 at 02:07:50PM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> In prep for a new function that will need additional resource information
> during the resource walk, update the resource walk callback to pass the
> resource structure. Since the current callback start and e
On Fri, Jul 28, 2017 at 09:27:22AM +, Saurabh Singh wrote:
> Hi Daniel,
>
> Thanks for your reply.
> Currently I am using connector type 'Unknown' , and functionally it serves my
> need.
> Intention for sending this patch is that userspace tools should recognize SDI
> drivers as SDI only.
>
On Mon, 31 Jul 2017, Tomi Sarvela wrote:
> On 31/07/17 10:45, Thomas Gleixner wrote:
> > On Mon, 31 Jul 2017, Tomi Sarvela wrote:
> > > On 28/07/17 19:26, Thomas Gleixner wrote:
> > > > Did you change anything else compared to the tests before ?
> > >
> > > I did check that the problem persisted i
On Sun, Jul 30, 2017 at 11:28:13AM -0400, Johannes Weiner wrote:
> On Sat, Jul 29, 2017 at 11:10:55AM +0200, Peter Zijlstra wrote:
> > On Thu, Jul 27, 2017 at 11:30:10AM -0400, Johannes Weiner wrote:
> > > +static void domain_cpu_update(struct memdelay_domain *md, int cpu,
> > > +
On 07/31/2017 03:43 PM, Michal Hocko wrote:
On Mon 31-07-17 15:41:49, Wei Wang wrote:
On 07/31/2017 02:55 PM, Michal Hocko wrote:
On Mon 31-07-17 12:13:33, Wei Wang wrote:
Ballooned pages will be marked as MADV_DONTNEED by the hypervisor and
shouldn't be given to the host ksmd to scan.
Could
With SND_SOC_RT5514_SPI=m and SND_SOC_RT5514=y, we get this link error:
sound/soc/codecs/rt5514.o: In function `rt5514_dsp_voice_wake_up_put':
rt5514.c:(.text+0x2068): undefined reference to `rt5514_spi_burst_write'
rt5514.c:(.text+0x20c8): undefined reference to `rt5514_spi_burst_write'
This add
Rafael,
On Fri, 28 Jul 2017, Tomi Sarvela wrote:
> rtcwake-1332 [000] d..164.42: suspend_device_irqs:
> presuspend 8 state 00401200
> rtcwake-1332 [000] d..164.42: __irq_disable: predisable 8
> state 00401200
> rtcwake-1332 [000] d..164.43: __i
On Mon, 2017-07-31 at 09:09 +0200, Thomas Gleixner wrote:
> Ben,
>
> On Mon, 31 Jul 2017, Benjamin Herrenschmidt wrote:
> > I noticed a problem with some powerpc systems with threaded IRQs. I
> > hadn't looked at threaded irq in the past so there was a bit of
> > discovery involved. That lead to a
Hi Matt, Mauro,
On Thu, 17 Mar 2016 15:18:20 +0100, Jean Delvare wrote:
> On Tue, 8 Mar 2016 10:32:37 -0800, Matt Roper wrote:
> > A couple of the EDAC drivers have a nice memdev_dmi_entry structure for
> > decoding DMI memory device entries. Move the structure definition to
> > dmi.h so that it
On Mon 31-07-17 16:23:26, ZhenweiPi wrote:
> On 07/31/2017 03:51 PM, Michal Hocko wrote:
>
> >On Mon 31-07-17 15:41:49, Wei Wang wrote:
> >>>On 07/31/2017 02:55 PM, Michal Hocko wrote:
> >On Mon 31-07-17 12:13:33, Wei Wang wrote:
> > >>Ballooned pages will be marked as MADV_DONTNEED by th
On Mon, Jul 31, 2017 at 09:03:09AM +0300, Avi Kivity wrote:
> I remembered that current->mm does not change when switching to a kernel
> task, but my Kernlish is very rusty, or maybe it has changed.
kernel threads do indeed preserve the mm of the old userspace task, but
we track that in ->active_m
Hi Jacob,
A quick review below:
On 07/31/2017 05:07 AM, Jacob Chen wrote:
> Rockchip RGA is a separate 2D raster graphic acceleration unit. It
> accelerates 2D graphics operations, such as point/line drawing, image
> scaling, rotation, BitBLT, alpha blending and image blur/sharpness
>
> The drvi
ipc_findkey() scanned all objects to look for the wanted key. This is
slow when using a high number of keys, for example on an i5 laptop the
following loop took 17 s, with last semget calls taking ~1 ms each.
for (int i = 0, k=0x424242; i < 31900; ++i)
semget(k++, 1, IPC_CREAT | 0600);
On 31/07/17 11:29, Thomas Gleixner wrote:
On Mon, 31 Jul 2017, Tomi Sarvela wrote:
On 31/07/17 10:45, Thomas Gleixner wrote:
On Mon, 31 Jul 2017, Tomi Sarvela wrote:
On 28/07/17 19:26, Thomas Gleixner wrote:
Did you change anything else compared to the tests before ?
I did check that the pr
On Tue, Jul 18, 2017 at 11:58:54AM -0500, Jintack Lim wrote:
> With HCR_EL2.NV bit set, accesses to EL12 registers in the virtual EL2
> trap to EL2. Handle those traps just like we do for EL1 registers.
>
> One exception is CNTKCTL_EL12. We don't trap on CNTKCTL_EL1 for non-VHE
> virtual EL2 becau
On Mon, 31 Jul 2017, Benjamin Herrenschmidt wrote:
> On Mon, 2017-07-31 at 09:09 +0200, Thomas Gleixner wrote:
> > You asked a lot of questions, but you failed to explain the problem for
> > XICS.
>
> I did but maybe it wasn't clear :-)
>
> "So on some PICs on powerpc, while we do use "fast EOI",
On Mon, Jul 31, 2017 at 12:44:03PM +0530, janani-sankarababu wrote:
> This patch is to replace the use of BUG_ON macro with WARN_ON
> inorder to prevent the crashing of the kernel.
>
> Signed-off-by: Janani Sankara Babu
> ---
> drivers/staging/vc04_services/bcm2835-audio/bcm2835-ctl.c | 2 +-
>
The following commits:
c815fde wlcore: spi: Populate config firmware data
d776fc8 wlcore: sdio: Populate config firmware data
Populated the nvs entry for wilink6 and wilink7 only while it is
still needed for wilink8 as well.
This broke user space backward compatibility when upgrading from older
ke
From: Suravee Suthikulpanit
Current cpu_core_id fixup causes downcored F17h configurations to be
incorrect:
NODE: 0
processor 0 core id : 0
processor 1 core id : 1
processor 2 core id : 2
processor 3 core id : 4
processor 4 core id : 5
processor 5 core id : 0
NODE: 1
pro
On 29 July 2017 at 07:59, Julia Lawall wrote:
>
> The mmc_host_ops structure is only stored in the ops field of an
> mmc_host structure, which is declared as const. Thus the mmc_host_ops
> structure itself can be const.
>
> Done with the help of Coccinelle.
>
> ---
>
> drivers/mmc/host/bcm2835.c
From: Borislav Petkov
Hi guys,
here are two fixes for downcored F17h machines. The respective commit
messages explain the situation adequately, IMO. Both tip:x86/cpu stuff.
Please queue,
thanks.
Suravee Suthikulpanit (2):
x86/amd: Limit cpu_core_id fixup to families older than F17h
x86/amd
From: Suravee Suthikulpanit
For systems with X86_FEATURE_TOPOEXT, current logic uses the APIC ID
to calculate shared_cpu_map. However, APIC IDs are not guaranteed to
be contiguous for cores across different L3s (e.g. family17h system
w/ downcore configuration). This breaks the logic, and results
On Monday 31 July 2017 01:26 PM, Johannes Thumshirn wrote:
On Sun, Jul 30, 2017 at 02:07:09PM +0530, Arvind Yadav wrote:
pci_device_id are not supposed to change at runtime. All functions
working with pci_device_id provided by work with
const pci_device_id. So mark the non-const structs as co
On 07/31/2017 11:37 AM, Peter Zijlstra wrote:
On Mon, Jul 31, 2017 at 09:03:09AM +0300, Avi Kivity wrote:
I remembered that current->mm does not change when switching to a kernel
task, but my Kernlish is very rusty, or maybe it has changed.
kernel threads do indeed preserve the mm of the old us
On Fri, Jul 28, 2017 at 04:55:36PM +0100, Robin Murphy wrote:
> On 28/07/17 15:09, Lorenzo Pieralisi wrote:
> > On Fri, Jul 28, 2017 at 02:08:01PM +0100, Robin Murphy wrote:
> >
> > [...]
> >
> > To ensure that dma_set_mask() and friends actually respect _DMA, would
> > you consider intro
I ran into a build error for the psci_checker:
drivers/firmware/psci_checker.o: In function `psci_checker':
psci_checker.c:(.init.text+0x528): undefined reference to `cpuidle_devices'
As far as I can tell, this is simply a very rare combination of options,
but the problem has existed since the co
Putting a 900 byte array on the stack is a clearly too much in the
kernel, and sometimes results in warnings like:
drivers/staging/pi433/pi433_if.c: In function 'pi433_tx_thread':
drivers/staging/pi433/pi433_if.c:645:1: error: the frame size of 1028 bytes is
larger than 1024 bytes [-Werror=frame-
On 11/07/2017 13:56, Simon Horman wrote:
> On Thu, Nov 24, 2016 at 11:58:43AM +0100, Simon Horman wrote:
>> Hi Magnus,
>>
>> On Mon, Mar 14, 2016 at 11:23:42PM +0900, Magnus Damm wrote:
>>> clocksource: sh_cmt: DT binding rework V4
>>>
>>> [PATCH v4 01/06] devicetree: bindings: Remove sh7372 CMT bi
On Tue, Jul 18, 2017 at 11:58:55AM -0500, Jintack Lim wrote:
nit: The subject is a little hard to understand.
> On VHE systems, EL0 of the host kernel is considered as a part of 'VHE
> host'; The execution of EL0 is affected by system registers set by the
> VHE kernel including the hypervisor. To
Dear Talented,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue Sky Studio a Film
Corporation Located in the United State, is Soliciting for the Right to use
Your Photo/Face and Personality as One of the Semi -Major Role/ Character in
our Upcoming ANIMATED Stereoscope 3D Movie-The Story
The names of the idle states in the output of cpupower monitor
command are truncated to 4 characters. Hence, On POWER9, since
the states are named "stop0, stop1, stop2, stop4, stop11",
this output is ambiguous
root:~# cpupower monitor
|Idle_Stats
PKG |CORE|CPU | snoo | stop | stop
Hi Leon,
> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Leon Romanovsky
> Sent: Sunday, July 30, 2017 10:59 AM
> To: Salil Mehta
> Cc: da...@davemloft.net; Zhuangyuzeng (Yisen); huangdaode; lipeng (Y);
> mehta.salil..
1 - 100 of 980 matches
Mail list logo
