From: Suniel Mahesh
Fixed the following checkpatch.pl warning:
Possible unnecessary 'out of memory' message
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for easy review
as suggested by Greg K-H
- Modified subject and description for better re
From: Suniel Mahesh
Fixed the following checkpatch.pl checks:
spaces preferred around that 'operator', spacing provided
Logical continuations should be on the previous line, modified accordingly
Unnecessary parentheses around variables, removed
Please use a blank line after function/struct/union/
From: Suniel Mahesh
Fixed the following checkpatch.pl checks:
Blank lines aren't necessary after an open brace '{'
and before a close brace '}', removed
No space is necessary after a cast, removed
Please don't use multiple blank lines, removed
Signed-off-by: Suniel Mahesh
---
Changes for v3:
-
From: Suniel Mahesh
This patch simplifies code by replacing explicit NULL comparison
with ! or unmark operator
Reported by checkpatch.pl for comparison to NULL could be
written '!foo' or 'foo'
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for ea
From: Suniel Mahesh
Fixed the following checkpatch.pl warnings:
Block comments should align the * on each line
Block comments use * on subsequent lines
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for easy review
as suggested by Greg K-H
- Mo
From: Suniel Mahesh
Split earlier patches into multiple commits for easy review as
suggested by Dan Carpenter.
Modified subject, description and in few patches both for
better readability as suggested by Greg KH.
Fixed the following issues reported by checkpatch.pl:
Block comments should align t
From: Suniel Mahesh
Replaced sizeof(struct foo) into sizeof(*ptr), found by checkpatch.pl
Signed-off-by: Suniel Mahesh
---
Changes for v3:
- Split earlier patches into multiple commits for easy review
as suggested by Greg K-H
- Modified description for better readability
- Rebased on top of
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The altera gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a real-time
> kernel. Because
On Mon, Mar 13, 2017 at 09:47:57AM +, James Hogan wrote:
> >
> > Note that the corruption is different across reboots, both in the size
> > of the corruption and the location. I saw 1900~ and 1400~ byte
> > sequences corrupted on separate occasions, which don't correspond to
> > the system's
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The 104-dio-48e gpio driver currently implements an irq_chip for
> handling interrupts; due to how irq_chip handling is done, it's
> necessary for the irq_chip methods to be invoked from hardirq context,
> even on a a real-time kernel. Be
Hi Heiko
On 03/15/2017 05:03 PM, Heiko Stübner wrote:
Am Mittwoch, 15. März 2017, 16:42:30 CET schrieb Chris Zhong:
For RK3399, the grf clock should be controlled by dw-mipi-dsi driver,
add the description for this clock.
Signed-off-by: Chris Zhong
---
.../devicetree/bindings/display/rockc
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The bcm-kona gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Becau
On Fri, Mar 10, 2017 at 6:28 PM, Ray Jui wrote:
> Is such API use change well accepted by the open source community already?
The raw_*spinlock APIs are in the kernel header files and used at several
sites in the kernel, so yes.
Yours,
Linus Walleij
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The ath79 gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The etraxfs gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Becaus
On Tue, 14 Mar 2017, Bjorn Helgaas wrote:
> On Tue, Mar 14, 2017 at 07:24:14PM -0700, Andi Kleen wrote:
> > > I agree that it should be fairly safe to do ECAM/MMCONFIG without
> > > locking. Can we handle the decision part by adding a "lockless" bit
> > > to struct pci_ops? Old ops don't mention
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The pl061 gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because
On 2017-03-14 19:16, Dan Carpenter wrote:
> Looks good!
Thanks, now pushed out to the for-next branch of
https://gitlab.com/peda-linux/mux.git
Cheers,
peda
From: Chen Liang
The rk3328 soc need more pin function index for pinctrl.
Signed-off-by: Chen Liang
---
include/dt-bindings/pinctrl/rockchip.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/dt-bindings/pinctrl/rockchip.h
b/include/dt-bindings/pinctrl/rockchip.h
index aaec8ba..
From: Chen Liang
The rk3328 saradc is the same as rk3399.
Signed-off-by: Chen Liang
---
Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/iio/adc/rockchip-saradc.txt
b/Documentation/devicetree/bi
From: Chen Liang
The rk3328 i2c is the same as rk3399
Signed-off-by: Chen Liang
---
Documentation/devicetree/bindings/i2c/i2c-rk3x.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
b/Documentation/devicetree/bindings/i2c/i2c-rk3x.txt
in
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The ws16c48 gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Becaus
From: Liang Chen
These patchs depend on pinctrl patchs as below:
https://patchwork.kernel.org/patch/9566427/
https://patchwork.kernel.org/patch/9566425/
https://patchwork.kernel.org/patch/9566431/
Chen Liang (7):
include: dt-bindings: Add pin function index definition for rockchip
pinctrl
From: Chen Liang
Signed-off-by: Chen Liang
---
Documentation/devicetree/bindings/soc/rockchip/grf.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/soc/rockchip/grf.txt
b/Documentation/devicetree/bindings/soc/rockchip/grf.txt
index a0685c2..db4da0b 10064
On Thu, Mar 9, 2017 at 5:21 PM, Julia Cartwright wrote:
> The zx gpio driver currently implements an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because the
On Tue, 7 Mar 2017, Hans de Goede wrote:
> On 07-03-17 10:18, Thomas Gleixner wrote:
> > I'm a bit worried about this being hardcoded for that particular use
> > case. That also means that you cannot use the generic regmap irq handling
> > stuff and need to have your own irq magic there.
>
> Yeah,
Hello!
On 3/15/2017 12:23 AM, Philippe Reynes wrote:
The function gem_begin_auto_negotiation dereference
the pointer ep before testing if it's null. This
patch add a check on ep before dereferencing it.
This issue was added by the patch 92552fdd557:
"net: sun: sungem: use new api ethtool_{get|
On Wed, Mar 15, 2017 at 8:21 AM, Gerd Hoffmann wrote:
> Hi,
>
>> First the flipping of the mmc host driver for the SD card slot will
>> cause issues for users that build it as a module. When I tested this
>> on Fedora the first update I ended up with a system that didn't boot.
>
> Yep, switching
On Tue, Mar 14, 2017 at 01:30:30PM -0700, Laura Abbott wrote:
> On 03/14/2017 01:13 PM, Daniel Vetter wrote:
> > On Tue, Mar 14, 2017 at 01:04:19PM -0700, Laura Abbott wrote:
> >>
> >> dma-buf is designed to share buffers. Sharing means that there needs to
> >> be another subsystem to accept those
On Tue, 14 Mar 2017, Krzysztof Kozlowski wrote:
> The MFD-specific header will go away because it duplicates defines from
> exynos-regs-pmu.h.
>
> Reported-by: kbuild test robot
> Signed-off-by: Krzysztof Kozlowski
> Reviewed-by: Bartlomiej Zolnierkiewicz
> ---
> drivers/mfd/exynos-lpass.c |
Am Mittwoch, 15. März 2017, 17:55:23 CET schrieb Chris Zhong:
> Hi Heiko
>
> On 03/15/2017 05:03 PM, Heiko Stübner wrote:
> > Am Mittwoch, 15. März 2017, 16:42:30 CET schrieb Chris Zhong:
> >> For RK3399, the grf clock should be controlled by dw-mipi-dsi driver,
> >> add the description for this c
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote:
> The bcm pinctrl drivers currently implement an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because
On Tue, 14 Mar 2017, Andy Shevchenko wrote:
> On Tue, 2017-03-14 at 15:02 +, Lee Jones wrote:
> > On Mon, 13 Mar 2017, Andy Shevchenko wrote:
> >
> > > Crystal Cove and Whiskey Cove are two different PMICs which are
> > > installed on Intel Atom SoC based platforms.
> > >
> > > Moreover ther
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote:
> The amd pinctrl drivers currently implement an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Because
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote:
> The sirf atlas7 pinctrl drivers currently implement an irq_chip for
> handling interrupts; due to how irq_chip handling is done, it's
> necessary for the irq_chip methods to be invoked from hardirq context,
> even on a a real-time kernel.
On Thu, Mar 9, 2017 at 5:22 PM, Julia Cartwright wrote:
> The sunxi pinctrl driver currently implement an irq_chip for handling
> interrupts; due to how irq_chip handling is done, it's necessary for the
> irq_chip methods to be invoked from hardirq context, even on a a
> real-time kernel. Becaus
On Wed, Mar 15, 2017 at 03:21:51PM +0530, suni...@techveda.org wrote:
> @@ -1796,7 +1796,7 @@ static short _rtl92e_alloc_rx_ring(struct net_device
> *dev)
>
> for (rx_queue_idx = 0; rx_queue_idx < MAX_RX_QUEUE; rx_queue_idx++) {
> priv->rx_ring[rx_queue_idx] = pci_zalloc_cons
On Wed, Mar 15, 2017 at 5:52 AM, Cong Wang wrote:
> On Fri, Mar 10, 2017 at 12:04 PM, Dmitry Vyukov wrote:
>> On Fri, Mar 10, 2017 at 8:46 PM, Marcelo Ricardo Leitner
>> wrote:
>>> On Fri, Mar 10, 2017 at 4:11 PM, Dmitry Vyukov wrote:
Hello,
I've got the following recursive locki
Also the subject is too vague.
regards,
dan carpenter
On Wed, Mar 8, 2017 at 8:35 PM, Nathan Sullivan wrote:
> The GPIO-based NAND controller on National Instruments 169445 hardware
> exposes a set of simple lines for the control signals.
>
> Signed-off-by: Nathan Sullivan
Oh a newer patch with comments exist. I take out the other patch then
and w
On Wed, Mar 15, 2017 at 03:21:52PM +0530, suni...@techveda.org wrote:
> From: Suniel Mahesh
>
> Fixed the following checkpatch.pl warning:
> Possible unnecessary 'out of memory' message
>
> Signed-off-by: Suniel Mahesh
> ---
> Changes for v3:
>
> - Split earlier patches into multiple commits f
On Friday, March 3, 2017 11:43:00 AM CET Jin Yao wrote:
> v4: Remove the options "--inline-line" and "--inline-name". Just use
> a new option "--inline" to print the inline function information.
> The policy is if the inline function name can be resolved then
> print the name in priorit
Currently we are adding all components from the dts, if one of their
drivers been disabled, we would not be able to bring up others.
Refactor component match logic, follow exynos drm.
Signed-off-by: Jeffy Chen
Reviewed-by: Andrzej Hajda
---
Changes in v3:
Address Andrzej Hajda 's comments.
C
On Tue, 14 Mar 2017, Enric Balletbo i Serra wrote:
> On 14/03/17 14:59, Lee Jones wrote:
> > On Tue, 14 Feb 2017, Enric Balletbo i Serra wrote:
> >
> >> From: Stephen Barber
> >>
> >> If the EC supports RTC host commands, expose an RTC device.
> >>
> >> Signed-off-by: Stephen Barber
> >> Signed-
On Wed, Mar 15, 2017 at 03:21:54PM +0530, suni...@techveda.org wrote:
> @@ -2294,17 +2294,20 @@ static int _rtl92e_ioctl(struct net_device *dev,
> struct ifreq *rq, int cmd)
>
> if (ipw->cmd == IEEE_CMD_SET_ENCRYPTION) {
> if (ipw->u.crypt.set_tx) {
> -
Hi Andrzej,
On 03/14/2017 08:05 PM, Andrzej Hajda wrote:
Hi Jeffy,
On 14.03.2017 11:45, Jeffy Chen wrote:
Currently we are adding all components from the dts, if one of their
drivers been disabled, we would not be able to bring up others.
Refactor component match logic, follow exynos drm.
S
Linus Lüssing wrote:
> When trying to redirect bridged frames to the bridge device itself
> via the ebtables nat-prerouting chain and the dnat target then this
> currently fails:
>
> The ethernet destination of the frame is dnat'ed to the MAC address of
> the bridge itself just fine and the corre
On Tue, 14 Mar 2017, Arnd Bergmann wrote:
> On Tue, Mar 14, 2017 at 12:14 PM, Lee Jones wrote:
> > On Tue, 28 Feb 2017, Arnd Bergmann wrote:
> >
> >> When the db8500 watchdog is enabled without the PRCMU, we get a lot of
> >> warnings about duplicate or missing helper functions:
> >>
> >> In file
On Tue, Mar 7, 2017 at 7:52 PM, Florian Fainelli wrote:
> In case a platform only defaults a "default" set of pins, but not a
> "sleep" set of pins, and this particular platform suspends and resumes
> in a way that the pin states are not preserved by the hardware, when we
> resume, we would call
On Mon, Mar 13, 2017 at 8:06 PM, Andy Shevchenko
wrote:
> On Mon, Mar 13, 2017 at 8:59 PM, Florian Fainelli
> wrote:
>> On 03/07/2017 10:52 AM, Florian Fainelli wrote:
>
>> Linus am I hitting some of your spam folder, or you are really having
>> way too much fun with Gemini ;) ?
>
> A bit offtop
Hi,
Any Update?
Thanks,
Sreekanth
On Mon, Mar 13, 2017 at 12:13 PM, Sreekanth Reddy
wrote:
> Hi,
>
> Our LSI(Broadcom) SAS3.5 HBA device's support virtual SES device.
>
> Whenever we load the mpt3sas driver then we are observing below error message,
>
> "Wrong diagnostic page; asked for 7 got 0
On Tue, 14 Feb 2017, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Add the Altera Arria10 DevKit sysfs attributes to the
> MFD device. Update copyright and email.
>
> Signed-off-by: Thor Thayer
> ---
> drivers/mfd/altera-a10sr.c | 98
> +++
If a console was specified by ACPI SPCR table _and_ command line parameters like
"console=ttyAMA0" _and_ "earlycon" were specified, then log messages
appear twice.
This issue was addressed in the patch [1] but the approach was wrong and
a revert [2] was suggested.
First two patches "printk: fix n
The variable preferred_console is used only inside register_console()
and its semantics is boolean. It is negative when no console has been
made preferred.
Make it static bool and rename to has_preferred.
Renaming was suggested by Peter Hurley
Acked-by: Petr Mladek
Reviewed-by: Steven Rostedt
If a console was specified by ACPI SPCR table _and_ command line
parameters like "console=ttyAMA0" _and_ "earlycon" were specified,
then log messages appear twice.
The root cause is that the code traverses the list of specified
consoles (the `console_cmdline` array) and stops at the first match.
B
The variable selected_console is set in __add_preferred_console()
to point to the last console parameter that was added to the
console_cmdline array.
Rename it to preferred_console so that the name reflects the usage.
Petr Mladek:
"[..] the selected_console/preferred_console
value is used to keep
On Tue, 21 Feb 2017, Javier Martinez Canillas wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
> that the MODALI
On Tue, 21 Feb 2017, Javier Martinez Canillas wrote:
> The driver doesn't have a struct of_device_id table but supported devices
> are registered via Device Trees. This is working on the assumption that a
> I2C device registered via OF will always match a legacy I2C device ID and
> that the MODALI
On Wed, Mar 15, 2017 at 04:18:11AM +0100, Linus Lüssing wrote:
> When trying to redirect bridged frames to the bridge device itself
> via the ebtables nat-prerouting chain and the dnat target then this
> currently fails:
>
> The ethernet destination of the frame is dnat'ed to the MAC address of
>
On Mon, 13 Mar 2017, Andy Shevchenko wrote:
> After commit 028af5941dd8 ("mfd: intel-lpss: Pass SDA hold time to I2C host
> controller driver")
> the driver still has a non-used variable.
>
> Remove it here.
>
> Cc: Mika Westerberg
> Cc: Rafael J. Wysocki
> Signed-off-by: Andy Shevchenko
> -
Currently net/sunrpc/xprtmultipath.c is the only file outside of arch/
headers and asm-generic/ headers to include , apparently
for the use of cmpxchg_relaxed().
However, many architectures do not provide cmpxchg_relaxed() in their
, and it is necessary to include to get
this definition, as noted
On Fri, 10 Mar 2017, Quentin Schulz wrote:
> This adds support for the Allwinner A33 thermal sensor.
>
> Unlike the A10, A13 and A31, the Allwinner A33 only has one channel
> which is dedicated to the thermal sensor. Moreover, its thermal sensor
> does not generate interruptions, thus we only nee
Hi Vivek,
On Fri, 2017-03-10 at 20:10 +0530, Vivek Gautam wrote:
> Hi Philipp,
>
>
> On Wed, Feb 22, 2017 at 10:54 AM, Vivek Gautam
> wrote:
> > Count number of reset phandles available with the device node
> > to know the resets a given device has.
> >
> > Cc: Philipp Zabel
> > Signed-off-by:
On Wed, Mar 15, 2017 at 11:26:08AM +0100, Florian Westphal wrote:
> Linus Lüssing wrote:
> > When trying to redirect bridged frames to the bridge device itself
> > via the ebtables nat-prerouting chain and the dnat target then this
> > currently fails:
> >
> > The ethernet destination of the fram
It also needs any support from VBIOS side ? I mean PCIe large bar support?
Thanks,
Ayyappa.
On Wed, Mar 15, 2017 at 1:07 PM, Christian König
wrote:
> Carizzo is an APU and resizing BARs isn't needed nor supported there. The
> CPU can access the full stolen VRAM directly on that hardware.
>
> As
On 03/15/2017 08:53 AM, Wanpeng Li wrote:
> Ping, :)
> 2017-03-07 13:51 GMT+08:00 Wanpeng Li :
>> From: Wanpeng Li
>>
>> The following warning can be triggered by hot-unplugging the CPU
>> on which an active SCHED_DEADLINE task is running on:
>>
>> [ cut here ]
>> WARNING
On Wed, 2017-02-22 at 10:54 +0530, Vivek Gautam wrote:
> Add support to get a list of resets available for the device.
> These resets must be kept de-asserted until the device is
> in use.
>
> Cc: Felipe Balbi
> Signed-off-by: Vivek Gautam
> ---
>
> Based on torvald's master branch.
>
> drive
Hi,
Thanks for the patch. If the assumption will not be there than this
fix is needed. I tested it on BeagleBoneBlack and it does not effect
anything.
Tested-by: Crt Mori
Acked-by: Crt Mori
Best regards,
Crt
On 15 March 2017 at 05:44, Javier Martinez Canillas
wrote:
> The driver doesn't have
Michal Hocko writes:
> Hi,
> this is a follow up for [1]. In short the current semantic of the memory
> hotplug is awkward and hard/impossible to use from the udev to online
> memory as movable. The main problem is that only the last memblock or
> the adjacent to highest movable memblock can be o
On 13 March 2017 at 16:09, Viresh Kumar wrote:
> On 10-03-17, 12:38, Kevin Hilman wrote:
>> Why limit it to just voltage levels.
>>
>> As I suggested earlier, I think this should use OPPs. Remember that a
>> PM domain is not limited to a hardware power domain, but is just a
>> grouping mechanism
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy I2C device ID and
that the MODALIAS reported will always be of the form i2c:.
But this could c
The driver doesn't have a struct of_device_id table but supported devices
are registered via Device Trees. This is working on the assumption that a
I2C device registered via OF will always match a legacy I2C device ID and
that the MODALIAS reported will always be of the form i2c:.
But this could c
Hi Arnd,
+Mark Brown and Kamal Dasu
Le 14/03/2017 à 22:42, Arnd Bergmann a écrit :
> The newly added broadcom qspi driver in drivers/spi produces a build
> warning when CONFIG_MTD is disabled:
>
> include/linux/mtd/cfi.h:76:2: #warning No CONFIG_MTD_CFI_Ix selected. No NOR
> chip support can wo
If the tps65910 driver has no interrupt, the probe of tps65910-rtc will
fail.
This patch adds a check in the probe of the rtc if an interrupt exist.
The check is similar to the check in the function which creates the
interrupt.
Signed-off-by: Daniel Schultz
---
drivers/rtc/rtc-tps65910.c | 5 ++
From: Suniel Mahesh
Fixed the following checkpatch.pl warning:
Possible unnecessary 'out of memory' message
If it is out of memory, function should return with an
appropriate error code. Since this function is of type void,
a return statement is used.
Signed-off-by: Suniel Mahesh
---
Changes fo
Coverity complains about uart_state checks in polling functions. And it
is indeed correct. We do something like this:
struct uart_state *state = drv->state + line;
if (!state)
return;
Adding 'line' to drv->state would move the potential NULL pointer to
something nea
After commit d705ff3818 (tty: vt, cleanup and document con_scroll), in
the coccinelle output, we can see:
drivers/usb/misc/sisusbvga/sisusb_con.c:852:8-9: WARNING: return of 0/1 in
function 'sisusbcon_scroll_area' with return type bool
Return true instead of 1 in the function returning bool which
Hello Wolfram,
On 03/15/2017 04:58 AM, Wolfram Sang wrote:
>
>> So there isn't an agreement if is better to just rely in the current behavior
>> (and have a superfluous I2C device ID table) or fix the I2C core (and need a
>> OF device ID table).
>
> For at24, the i2c_device_id table is not super
On Tue, Mar 14, 2017 at 09:54:31PM -0300, Mauro Carvalho Chehab wrote:
> Em Tue, 14 Mar 2017 23:32:54 +0100
> Pavel Machek escreveu:
>
> >
> > Well, I believe first question is: what applications would we want to
> > run on complex devices? Will sending control from video to subdevs
> > actually
The X-Powers AXP209 PMIC exposes battery supply various data such as
the battery status (charging, discharging, full, dead), current max
limit, current current, battery capacity (in percentage), voltage max
and min limits, current voltage, and battery capacity (in Ah).
This adds the battery power
On Fri, 10 Mar 2017, Elaine Zhang wrote:
> The RK805 chip is a Power Management IC (PMIC) for multimedia and handheld
> devices. It contains the following components:
>
> - Regulators
> - RTC
> - Clocking
>
> Both RK808 and RK805 chips are using a similar register map,
> so we can re
On Fri, 10 Mar 2017, Elaine Zhang wrote:
> Add device tree bindings documentation for Rockchip's RK805 PMIC.
>
> Signed-off-by: Elaine Zhang
> ---
> Documentation/devicetree/bindings/mfd/rk808.txt | 20 +++-
> 1 file changed, 19 insertions(+), 1 deletion(-)
For my own reference
On Fri, 10 Mar 2017, Elaine Zhang wrote:
> the rk8xx chip id is:
> ((MSB << 8) | LSB) & 0xfff0
>
> Signed-off-by: Elaine Zhang
> ---
> drivers/mfd/rk808.c | 21 +++--
> include/linux/mfd/rk808.h | 1 +
> 2 files changed, 16 insertions(+), 6 deletions(-)
For my own refere
Subject line should be "mfd: rk808: ..."
On Fri, 10 Mar 2017, Elaine Zhang wrote:
> Signed-off-by: Elaine Zhang
> ---
> include/linux/mfd/rk808.h | 115
> ++
> 1 file changed, 115 insertions(+)
Other than that:
For my own reference:
Acked-for-MFD
No, we resize the BAR on the fly during driver load without help from
the BIOS or VBIOS.
Christian.
Am 15.03.2017 um 11:42 schrieb Ayyappa Ch:
It also needs any support from VBIOS side ? I mean PCIe large bar support?
Thanks,
Ayyappa.
On Wed, Mar 15, 2017 at 1:07 PM, Christian König
wrote:
On Tue, Mar 14, 2017 at 02:52:33PM +, Suzuki K Poulose wrote:
> From: Marc Zyngier
>
> We don't hold the mmap_sem while searching for VMAs (via find_vma), in
> kvm_arch_prepare_memory_region, which can end up in expected failures.
>
> Fixes: commit 8eef91239e57 ("arm/arm64: KVM: map MMIO reg
On Wed, Mar 15, 2017 at 09:34:53AM +, Marc Zyngier wrote:
> On 15/03/17 09:17, Christoffer Dall wrote:
> > On Tue, Mar 14, 2017 at 02:52:32PM +, Suzuki K Poulose wrote:
> >> From: Marc Zyngier
> >>
> >> We don't hold the mmap_sem while searching for the VMAs when
> >> we try to unmap each
On Wed, 22 Feb 2017, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> Add Peripheral PHY Reset Controller to the Arria10
> Development Kit System Resource Chip's MFD.
>
> Signed-off-by: Thor Thayer
> ---
> v2 Changes to commit header & body for clarification.
> ---
> drivers/mfd/al
On Wed, Mar 15, 2017 at 11:49 AM, Eva Rachel Retuya wrote:
> On Mon, Mar 13, 2017 at 02:12:54PM +0200, Andy Shevchenko wrote:
>> On Mon, Mar 13, 2017 at 1:11 PM, Eva Rachel Retuya
>> wrote:
> Hello Andy,
> Thanks for the review.
You are welcome!
>> > +static irqreturn_t adxl345_irq(int irq, v
Hello!
On 3/14/2017 5:18 PM, Corentin Labbe wrote:
This patch add the dt node for the syscon register present on the
Allwinner A64.
Only two register are present in this syscon and the only one useful is
the one dedicated to EMAC clock.
Signed-off-by: Corentin Labbe
---
arch/arm64/boot/dts/
On Wed, 22 Feb 2017, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> This patch adds documentation for the Altera A10-SR Reset
> Controller DT bindings.
>
> Signed-off-by: Thor Thayer
> ---
> v2 No change
> ---
> Documentation/devicetree/bindings/mfd/altera-a10sr.txt | 11
On Wed, Mar 15, 2017 at 12:10 PM, Lee Jones wrote:
> On Tue, 14 Mar 2017, Krzysztof Kozlowski wrote:
>
>> The MFD-specific header will go away because it duplicates defines from
>> exynos-regs-pmu.h.
>>
>> Reported-by: kbuild test robot
>> Signed-off-by: Krzysztof Kozlowski
>> Reviewed-by: Bartl
Hi,
On 06/03/17 21:51, Wanpeng Li wrote:
> From: Wanpeng Li
>
> The following warning can be triggered by hot-unplugging the CPU
> on which an active SCHED_DEADLINE task is running on:
>
> [ cut here ]
> WARNING: CPU: 7 PID: 0 at kernel/sched/sched.h:833
> replenish_d
On Wednesday 15 March 2017 03:44 PM, Dan Carpenter wrote:
On Wed, Mar 15, 2017 at 03:21:51PM +0530, suni...@techveda.org wrote:
@@ -1796,7 +1796,7 @@ static short _rtl92e_alloc_rx_ring(struct net_device *dev)
for (rx_queue_idx = 0; rx_queue_idx < MAX_RX_QUEUE; rx_queue_idx++) {
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
This series, for the netfilter subsystem, replaces atomic_t reference
counters with the new refcount_t type and API (see include/linux/refcount.h).
By doing this we prevent intentional or accidental
underflows or overflows that can led to use-after-free vulnerabilities.
Please take the series to y
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
Hi Nick,
Thanks for reviewing the patch.
On Wed, Mar 15, 2017 at 12:05:43AM +1000, Nicholas Piggin wrote:
> On Mon, 13 Mar 2017 11:31:27 +0530
> "Gautham R. Shenoy" wrote:
>
> > From: "Gautham R. Shenoy"
> >
> > Currently during idle-init on power9, if we don't find suitable stop
> > states i
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
101 - 200 of 928 matches
Mail list logo
