On Tue, Jun 6, 2017 at 1:55 PM, Rajmohan Mani wrote:
> This patch adds support for TPS68470 GPIOs.
> There are 7 GPIOs and a few sensor related GPIOs.
> These GPIOs can be requested and configured as
> appropriate.
>
> Signed-off-by: Rajmohan Mani
Same comments as Andy already sent, plus:
> +s
On Fri, Jun 09, 2017 at 01:05:06PM +0200, Peter Zijlstra wrote:
> The spinlock based atomics should be SC, that is, none of them appear to
> place extra barriers in atomic_cmpxchg() or any of the other SC atomic
> primitives and therefore seem to rely on their spinlock implementation
> being SC (I
Hi Rob,
Thank you for the review.
On 07/06/2017 22:26, Rob Herring wrote:
On Mon, May 29, 2017 at 04:45:38PM +0200, Mylène Josserand wrote:
Add the Cypress TrueTouch Generation 5 touchscreen device tree bindings
documentation. It can use I2C or SPI bus.
This touchscreen can handle some defined
From: Colin Ian King
Make function grub_reclaim static to clean up the following sparse
warning:
"warning: symbol 'grub_reclaim' was not declared. Should it be static?"
Signed-off-by: Colin Ian King
---
kernel/sched/deadline.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Tue, Jun 6, 2017 at 3:03 PM, Baolin Wang wrote:
> This patch adds the binding documentation for Spreadtrum SC9860 pin
> controller device.
>
> Signed-off-by: Baolin Wang
> ---
> Changes since v2:
> - No updates.
Same comments as v3, sorry for my slowness in review :(
Yours,
Linus Walleij
On Fri, Jun 09, 2017 at 11:24:50AM +0200, Peter Zijlstra wrote:
> +Non RmW ops:
> +
> +The non-RmW ops are (typically) regular LOADs and STOREs and are canonically
> +implemented using READ_ONCE(), WRITE_ONCE(), smp_load_acquire() and
> +smp_store_release() respectively.
> +
> +The one detail to th
Currently HDMI 2.0 PHYs do not have a default configuration function.
As these PHYs have the same register layout as the 3D PHYs we can
safely use the default configuration function. If, for some reason,
the PHY is custom this change will not make any impact because
in configuration function we pr
On Tue, Jun 6, 2017 at 3:18 PM, Mika Westerberg
wrote:
> This adds pinctrl/GPIO support for Intel Cannon Lake PCH. The Cannon
> Lake PCH GPIO is based on newer version of the Intel GPIO hardware.
>
> Signed-off-by: Mika Westerberg
> Reviewed-by: Andy Shevchenko
Patch applied.
Yours,
Linus Wal
Hi,
On Friday 09 June 2017 04:07 PM, Ulf Hansson wrote:
> On 9 June 2017 at 10:41, Kishon Vijay Abraham I wrote:
>> commit 94647a30124e2c7 ("ARM: dts: omap3-overo: Enable WiFi/BT combo")
>> while enabling WiFi/BT combo added regulator to trigger the nReset
>> signal of the Bluetooth module in vqm
On Tue, Jun 6, 2017 at 3:18 PM, Mika Westerberg
wrote:
> On some SoCs not all pins in a group use the same mode when a certain
> function is muxed out of them. This makes it possible to specify mode per
> pin as an array instead in addition to single integer.
>
> Signed-off-by: Mika Westerberg
>
On Fri, May 05, 2017 at 11:17:20AM -0700, Ricardo Neri wrote:
> fixup_umip_exception() will be called from do_general_protection. If the
^
|
Please end function names
On Tue, Jun 6, 2017 at 3:18 PM, Mika Westerberg
wrote:
> The Intel GPIO hardware has a concept of pad groups, which means 1 to 32
> pads occupying their own GPI_IS, GPI_IE, PAD_OWN and so on registers. The
> existing hardware has the same amount of pads in each pad group (except the
> last one) s
Hello,
On Fri, 9 Jun 2017 12:09:17 +0200, Gregory CLEMENT wrote:
> In some place in the driver regmap_update_bits was misused. Indeed the
> last argument is not the value of the bit (or group of bits) itself but
> the mask value inside the register.
>
> So when setting the bit N, then the value
On Mon, Jun 5, 2017 at 2:11 PM, Baolin Wang wrote:
> This patch adds the binding documentation for Spreadtrum SC9860 pin
> controller device.
>
> Signed-off-by: Baolin Wang
Good improvements since last iteration!
(...)
> +The Spreadtrum pin controller are organized in 3 blocks (types).
> +
>
On 8 June 2017 at 11:42, Viresh Kumar wrote:
> On 08-06-17, 09:48, Ulf Hansson wrote:
>> It's not a nightmare, just a tricky thing to solve. :-)
>
> I may have just solved it actually :)
That was quick. :-)
>
> So the real locking problem was the case where a subdomain have multiple
> parent
>
On Fri, Jun 09, 2017 at 01:40:59AM +0300, Yury Norov wrote:
> On Thu, Jun 08, 2017 at 03:09:12PM +0100, Catalin Marinas wrote:
> > On Sun, Jun 04, 2017 at 02:59:54PM +0300, Yury Norov wrote:
> > > --- a/arch/arm64/Kconfig
> > > +++ b/arch/arm64/Kconfig
> > > @@ -402,7 +402,7 @@ config ARM64_ERRATUM
On 09/06/17 10:22, Philipp Zabel wrote:
Hi Matthias,
On Fri, 2017-06-09 at 10:14 +0200, Matthias Brugger wrote:
On 01/06/17 08:08, Erin Lo wrote:
From: YT Shen
This patch adds the device nodes for the DISP function blocks for MT2701
Signed-off-by: YT Shen
Signed-off-by: Erin Lo
---
On Thu, 2017-06-08 at 13:45 -0300, Fabio Estevam wrote:
> On Thu, Jun 8, 2017 at 1:26 PM, Leonard Crestez wrote:
>
> >
> > + tempmon: tempmon {
> > + compatible = "fsl,imx6ul-tempmon",
> > "fsl,imx6sx-tempmon";
> > +
On Fri, 9 Jun 2017 12:47:43 +0200
Arnd Bergmann wrote:
> This one was accidentally introduced without any references,
> and it causes a harmless warning:
>
> drivers/mtd/nand/fsl_ifc_nand.c: In function 'fsl_ifc_read_page':
> drivers/mtd/nand/fsl_ifc_nand.c:696:7: error: unused variable 'res'
Hi,
Am Freitag, 9. Juni 2017, 17:02:47 CEST schrieb Sugar Zhang:
> Signed-off-by: Sugar Zhang
I've already applied a previous version (from you and Frank).
See
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm/boot/dts/rk322x.dtsi?id=9d420e9b4140f8938ad6aa0d29e2
On Wed, Jun 07, 2017 at 02:13:53PM -0500, Tom Lendacky wrote:
> Update the CPU features to include identifying and reporting on the
> Secure Memory Encryption (SME) feature. SME is identified by CPUID
> 0x801f, but requires BIOS support to enable it (set bit 23 of
> MSR_K8_SYSCFG). Only show
In hotplug logic, it always indicates non-specific failure to
platform through _OST when handing acpi hot-remove event failed. Then
platform terminates the hot-remove process but it can not identify
the reason.
Base on current hot-remove code, there have two situations that it
returns busy:
- OSP
Resending the patchset after rebasing on linux-phy next branch.
Changes in v8:
=
-Renamed phy shutdown routine
-Used devm_request_irq in stead of threaded irq
-Removed devm_unregister calls in probe routine
Changes in v7:
=
Cleaned up unused variables in phy private data s
This is driver for USB DRD PHY used in Broadcom's Northstar2
SoC. The phy can be configured to be in Device mode or Host
mode based on the type of cable connected to the port. The
driver registers to extcon framework to get appropriate
connect events for Host/Device cables connect/disconnect
state
This patch adds device tree node for USB Dual Role Device PHY for
Broadcom's Northstar2 SoC.
Signed-off-by: Raviteja Garimella
---
arch/arm64/boot/dts/broadcom/ns2.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/boot/dts/broadcom/ns2.dtsi
b/arch/arm64/boot/dt
This patch adds DT bindings documentation for NS2 DRD PHY driver.
Signed-off-by: Raviteja Garimella
Acked-by: Rob Herring
---
.../devicetree/bindings/phy/brcm,ns2-drd-phy.txt | 30 ++
1 file changed, 30 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ph
Hi Kishon,
On Fri, Jun 9, 2017 at 2:36 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Friday 09 June 2017 02:30 PM, Raviteja Garimella wrote:
>> Hi,
>>
>> On Fri, Jun 9, 2017 at 2:25 PM, Kishon Vijay Abraham I wrote:
>>> Hi,
>>>
>>> On Thursday 08 June 2017 04:05 PM, Raviteja Garimella wrote:
>>
This one was accidentally introduced without any references,
and it causes a harmless warning:
drivers/mtd/nand/fsl_ifc_nand.c: In function 'fsl_ifc_read_page':
drivers/mtd/nand/fsl_ifc_nand.c:696:7: error: unused variable 'res'
[-Werror=unused-variable]
Fixes: 79f40cc12fd3 ("mtd: nand: fsl_ifc:
Add a new feature, VIRTIO_BALLOON_F_PAGE_CHUNKS, which enables
the transfer of the ballooned (i.e. inflated/deflated) pages in
chunks to the host.
The implementation of the previous virtio-balloon is not very
efficient, because the ballooned pages are transferred to the
host one by one. Here is th
On Fri 09-06-17 17:51:24, Wei Yang wrote:
> Hi, Michal
>
> I am not that familiar with hotplug and trying to catch up the issue
> and your solution.
>
> One potential issue I found is we don't check the physical boundary
> when add_memory_resource().
>
> For example, on x86-64, only 64T physica
This patch enables for_each_zone()/for_each_populated_zone() to be
invoked by a kernel module.
Signed-off-by: Wei Wang
---
mm/mmzone.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/mm/mmzone.c b/mm/mmzone.c
index a51c0a6..08a2a3a 100644
--- a/mm/mmzone.c
+++ b/mm/mmzone.c
@@ -13,6 +13,7
Add a function to find a page block on the free list specified by the
caller. Pages from the page block may be used immediately after the
function returns. The caller is responsible for detecting or preventing
the use of such pages.
Signed-off-by: Wei Wang
Signed-off-by: Liang Li
---
include/li
Add a new vq, cmdq, to handle requests between the device and driver.
This patch implements two commands send from the device and handled in
the driver.
1) cmd VIRTIO_BALLOON_CMDQ_REPORT_STATS: this command is used to report
the guest memory statistics to the host. The stats_vq mechanism is not
us
This patch series enhances the existing virtio-balloon with the following new
features:
1) fast ballooning: transfer ballooned pages between the guest and host in
chunks, instead of one by one; and
2) cmdq: a new virtqueue to send commands between the device and driver.
Currently, it supports comma
From: Liang Li
This patch saves the deflated pages to a list, instead of the PFN array.
Accordingly, the balloon_pfn_to_page() function is removed.
Signed-off-by: Liang Li
Signed-off-by: Michael S. Tsirkin
Signed-off-by: Wei Wang
---
drivers/virtio/virtio_balloon.c | 22 -
Clean up the comment format.
Signed-off-by: Wei Wang
---
drivers/virtio/virtio_balloon.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
index 4a9f307..ecb64e9 100644
--- a/drivers/virtio/virtio_balloon.c
On 32-bit architectures, we using %lx to print a size_t causes a harmless
warning:
qla2xxx/qla_init.c: In function 'qla24xx_load_risc_flash':
qla2xxx/qla_init.c:6407:7: error: format '%lx' expects argument of type 'long
unsigned int', but argument 5 has type 'unsigned int' [-Werror=format=]
qla2x
Am Freitag, 9. Juni 2017, 17:36:14 CEST schrieb David Wu:
> This adds the necessary data for handling io voltage domains on the rk3228.
>
> Signed-off-by: David Wu
matches the manual, so
Reviewed-by: Heiko Stuebner
Heiko
I ran into a build error on ARM with a platform that has a non-standard
clk implementation:
drivers/clk/clk.o: In function `clk_disable':
clk.c:(.text.clk_disable+0x0): multiple definition of `clk_disable'
arch/arm/mach-omap1/clock.o:clock.c:(.text.clk_disable+0x0): first defined here
drivers/clk/
On Fri, Jun 09, 2017 at 12:31:10PM +0200, Peter Rosin wrote:
> On 2017-06-09 12:22, Arnd Bergmann wrote:
> > COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot
> > compile
> > in that configuration:
>
> Ouch, thanks for catching!
>
> Reviewed-by: Peter Rosin
>
> Greg, I ass
On 9 June 2017 at 10:05, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Thursday 08 June 2017 12:50 PM, Ulf Hansson wrote:
>> On 7 June 2017 at 11:37, Kishon Vijay Abraham I wrote:
>>> There are the set of fixes that were sent initially as part
>>> of [1].
>>>
>>> These are mostly fixes w.r.t populat
On Thu, Jun 08, 2017 at 04:11:21PM +1200, Chris Packham wrote:
> This adds an EDAC driver for the memory controller and L2 cache used on
> a number of Marvell Armada SoCs.
>
> Signed-off-by: Chris Packham
> Cc: linux-arm-ker...@lists.infradead.org
> ---
> drivers/edac/Kconfig | 7 +
> dri
There is a prototype for this function in the header, but the function
itself lacks a 'void' in the argument list, causing a harmless warning
when building with 'make W=1':
drivers/gpu/drm/nouveau/nouveau_drm.c: In function 'nouveau_pmops_runtime':
drivers/gpu/drm/nouveau/nouveau_drm.c:730:1: erro
When CONFIG_QED_SRIOV is disabled, we get a build error:
drivers/net/ethernet/qlogic/qed/qed_int.c: In function 'qed_int_sb_init':
drivers/net/ethernet/qlogic/qed/qed_int.c:1499:4: error: implicit declaration
of function 'qed_vf_set_sb_info'; did you mean 'qed_mcp_get_resc_info'?
[-Werror=implic
On 9 June 2017 at 10:41, Kishon Vijay Abraham I wrote:
> commit 94647a30124e2c7 ("ARM: dts: omap3-overo: Enable WiFi/BT combo")
> while enabling WiFi/BT combo added regulator to trigger the nReset
> signal of the Bluetooth module in vqmmc-supply. However BT should be
> handled by UART. Moreover "v
On Fri, Jun 9, 2017 at 6:37 AM, Binoy Jayan wrote:
> On 8 June 2017 at 20:40, Arnd Bergmann wrote:
>> On Thu, Jun 8, 2017 at 12:04 PM, Binoy Jayan wrote:
>>> The semaphore 'cmd_mutex' is used as a simple mutex, so
>>> it should be written as one. Semaphores are going away in the future.
>>>
>>>
We get a harmless warning when CONFIG_RUNTIME_PM is disabled:
drivers/input/touchscreen/stmfts.c:760:12: error: 'stmfts_runtime_resume'
defined but not used [-Werror=unused-function]
static int stmfts_runtime_resume(struct device *dev)
drivers/input/touchscreen/stmfts.c:748:12: error: 'stmfts_ru
Hi Linus,
Sorry for escalating this right up to you, but this issue
does not seem to be getting any attention and I'm not sure
which subsys maintainer to poke about this.
The problem is that the 4.12-rc# kernels fail to boot on
VirtualBox guests hosted on any machine with a Sky Lake
(and probabl
Removing the default display name left a harmless warning:
fbdev/omap2/omapfb/dss/core.c: In function 'omap_dss_probe':
fbdev/omap2/omapfb/dss/core.c:196:30: error: unused variable 'pdata'
[-Werror=unused-variable]
This removes the now-unused variable as well.
Fixes: 278cba7eaf54 ("drm: omapdrm
On 2017-06-09 12:22, Arnd Bergmann wrote:
> COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot compile
> in that configuration:
Ouch, thanks for catching!
Reviewed-by: Peter Rosin
Greg, I assume you will you be taking this?
Cheers,
peda
The newly added support for the pcc mailbox fails to build
in some configurations:
drivers/i2c/busses/i2c-xgene-slimpro.c: In function 'xgene_slimpro_i2c_probe':
drivers/i2c/busses/i2c-xgene-slimpro.c:516:25: error: implicit declaration of
function 'memremap'; did you mean 'memcmp'?
[-Werror=imp
Felipe Balbi writes:
> Allow for ftrace data to be exported over a USB Gadget
> Controller. With this, we have a potentially very fast pipe for
> transmitting ftrace data to a Host PC for further analysis.
>
> Note that in order to decode the data, one needs access to kernel
> symbols in order to
When CONFIG_MODULES is disabled, we cannot dereference a module pointer:
arch/arm64/kernel/ftrace.c: In function 'ftrace_make_call':
arch/arm64/kernel/ftrace.c:107:36: error: dereferencing pointer to incomplete
type 'struct module'
trampoline = (unsigned long *)mod->arch.ftrace_trampoline;
Al
On 30/05/17 13:03, Geetha sowjanya wrote:
> From: Linu Cherian
>
> Cavium ThunderX2 SMMU implementation doesn't support page 1 register space
> and PAGE0_REGS_ONLY option is enabled as an errata workaround.
> This option when turned on, replaces all page 1 offsets used for
> EVTQ_PROD/CONS, PRIQ_
Thiago Jung Bauermann writes:
> On the OpenPOWER platform, secure boot and trusted boot are being
> implemented using IMA for taking measurements and verifying signatures.
I still want you to implement arch_kexec_kernel_verify_sig() as well :)
cheers
All users of dissolve_free_huge_page() that ignore the result cause a warning
when CONFIG_HUGETLB_PAGE is disabled:
mm/memory-failure.c: In function 'me_huge_page':
include/linux/hugetlb.h:556:36: error: statement with no effect
[-Werror=unused-value]
#define dissolve_free_huge_page(p) 0
We can
On Fri, Jun 9, 2017 at 8:57 AM, Bhumika Goyal wrote:
> Add const to rfkill_ops structures that are only passed as an argument
> to the functions rfkill_alloc or samsung_new_rfkill. These arguments are
> of type const, so such structures can be annotated with const.
>
All three pushed to testing,
When opening the slave end of a PTY, it is not possible for userspace to
safely ensure that /dev/pts/$num is actually a slave (in cases where the
mount namespace in which devpts was mounted is controlled by an
untrusted process). In addition, there are several unresolvable
race conditions if users
COMPILE_TEST makes no sense when I2C is disabled, as the driver cannot compile
in that configuration:
drivers/mux/mux-adg792a.c: In function 'adg792a_write_cmd':
drivers/mux/mux-adg792a.c:34:9: error: implicit declaration of function
'i2c_smbus_write_byte_data'; did you mean 'i2c_set_clientdata'?
Hi Guenter,
Thank you for your comment.
> On 06/06/2017 02:11 AM, Keiji Hayashibara wrote:
> > Add a watchdog driver for Socionext UniPhier series SoC.
> > Note that the timeout value for this device must be a power
> > of 2 because of the specification.
> >
> > Signed-off-by: Keiji Hayashibara
A change to the platform data definitions caused a warning in the board code:
arch/arm/mach-davinci/board-dm646x-evm.c:680:13: error: initialization discards
'const' qualifier from pointer target type [-Werror=discarded-qualifiers]
arch/arm/mach-davinci/board-dm646x-evm.c:690:13: error: initializ
On Fri, Jun 09, 2017 at 12:11:41PM +0200, Heiko Carstens wrote:
> On Fri, Jun 09, 2017 at 11:03:13AM +0200, Greg Kroah-Hartman wrote:
> > We are trying to get rid of DRIVER_ATTR(), and the s390 drivers'
> > attributes can be trivially changed to use DRIVER_ATTR_RO() and
> > DRIVER_ATTR_WO().
> >
>
On 09/06/17 11:11, Oleksij Rempel wrote:
And SOC_IMX6 is already doing "select MFD_SYSCON", so I assume it should
be enough to depend on it.
That should be good enough!!
gcc points out an unusual indentation:
drivers/block/loop.c: In function 'loop_set_status':
drivers/block/loop.c:1149:3: error: this 'if' clause does not guard...
[-Werror=misleading-indentation]
if (figure_loop_size(lo, info->lo_offset, info->lo_sizelimit,
^~
drivers/block/loop.c:1152:4: n
When CONFIG_ARCH_AT91 is enabled, but none of the specific SoC support
is in use, some at91 specific drivers fail to link:
drivers/tty/serial/atmel_serial.o: In function `atmel_serial_suspend':
atmel_serial.c:(.text.atmel_serial_suspend+0x1e): undefined reference to
`at91_suspend_entering_slow_cl
On Thu, 2017-06-08 at 23:50 -0400, Matt Brown wrote:
> >>
> >> * Issues:
> >> * Can be bypassed by interpreted languages such as python. You can run
> >> malicious code by doing: python -c 'evil code'
> >
> > What's the recommendation for people interested in using TPE but
> > having int
When MUSB is a loadable module, we get a link error for a built-in
CPCAP driver:
drivers/phy/built-in.o: In function `cpcap_usb_phy_remove':
phy-cpcap-usb.c:(.text+0xed9): undefined reference to `musb_mailbox'
This adds a Kconfig dependency to prevent this broken configuration,
enforcing that CPC
When the schedutil governor calls cpufreq_driver_resolve_freq() for the
intel_pstate (in passive mode) driver, it simply returns the requested
frequency as there is no ->resolve_freq() callback provided.
The result is that get_next_freq() doesn't get a chance to know the
frequency which will be se
While reducing frequency if there are no frequencies available between
"current" and "next" calculated frequency, then the core will never
select the "next" frequency.
For example, consider the possible range of frequencies as 900 MHz, 1
GHz, 1.1 GHz, and 1.2 GHz. If the current frequency is 1.1 G
The purpose of the "cached_raw_freq" field is to avoid a call to
cpufreq_driver_resolve_freq() when the next selected frequency is same
as the one selected last time and we can use sg_policy->next_freq then.
With the recent changes (reduce frequencies slower), we update the next
frequency at the v
Hi Rafael,
I have identified some regressions with the schedutil governor which
happen due to one of your patches that got merged in 4.12-rc1.
This series fixes all the drivers which provide a ->target_index()
callback but doesn't fix the drivers which provide ->target() callback.
Such platforms
On Fri, Jun 9, 2017 at 11:59 AM, Christian König
wrote:
> From: Christian König
>
> This way we can savely call it on SI as well.
s/savely/safely
FWIW,
Reviewed-by: Andy Shevchenko
> Signed-off-by: Christian König
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 17 -
>
Hi Ralph,
On ven., juin 09 2017, Ralph Sennhauser wrote:
> Hi Thomas,
>
> Commit 2233bf7a92e7 ("gpio: mvebu: switch to regmap for register
> access") in next-20170607 breaks gpio-keys on an armada-385 (Linksys
> WRT3200ACM), noticed due to missing /dev/input/event0 and the below
> dmesg output
On Fri, Jun 09, 2017 at 11:03:13AM +0200, Greg Kroah-Hartman wrote:
> We are trying to get rid of DRIVER_ATTR(), and the s390 drivers'
> attributes can be trivially changed to use DRIVER_ATTR_RO() and
> DRIVER_ATTR_WO().
>
> Cc: Martin Schwidefsky
> Cc: Heiko Carstens
> Cc: Julian Wiedmann
> Cc
On Fri, Jun 09, 2017 at 10:35:15AM +0100, Srinivas Kandagatla wrote:
>
> Few more nit picks!!
>
> On 08/06/17 17:51, Oleksij Rempel wrote:
> > This is a driver for Low Power General Purpose Register (LPGPR)
> > available on i.MX6 SoCs in Secure Non-Volatile Storage (SNVS)
> > of this chip.
> >
>
In some place in the driver regmap_update_bits was misused. Indeed the
last argument is not the value of the bit (or group of bits) itself but
the mask value inside the register.
So when setting the bit N, then the value must be BIT(N) and not 1.
CC: Chris Packham
CC: Ralph Sennhauser
Signed-of
Hi Thomas,
On ven., juin 09 2017, Thomas Petazzoni
wrote:
> Hello,
>
> On Fri, 9 Jun 2017 12:03:18 +0200, Gregory CLEMENT wrote:
>
>> regmap_update_bits(mvchip->regs, GPIO_IO_CONF_OFF,
>> - BIT(pin), 1);
>> + BIT(pin), BIT(pin));
>>
>>
On Thu, Jun 08, 2017 at 02:50:59PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 08, 2017 at 12:24:33PM +0100, Will Deacon wrote:
> > [+ PeterZ]
> >
> > On Thu, Jun 08, 2017 at 01:07:02PM +0200, Vlastimil Babka wrote:
> > > On 06/08/2017 12:40 PM, Kirill A. Shutemov wrote:
> > > > On Thu, Jun 08, 201
On Fri, Jun 09, 2017 at 07:50:43PM +1000, Aleksa Sarai wrote:
> > > When opening the slave end of a PTY, it is not possible for userspace to
> > > safely ensure that /dev/pts/$num is actually a slave (in cases where the
> > > mount namespace in which devpts was mounted is controlled by an
> > > unt
Hello,
On Fri, 9 Jun 2017 12:03:18 +0200, Gregory CLEMENT wrote:
> regmap_update_bits(mvchip->regs, GPIO_IO_CONF_OFF,
> -BIT(pin), 1);
> +BIT(pin), BIT(pin));
>
> return 0;
> }
> @@ -364,7 +364,7 @@ static int mvebu_gpio_direction_ou
In some place in the driver regmap_update_bits was misused. Indeed the
last argument is not the value of the bit (or group of bits) itself but
the mask value inside the register.
So when setting the bit N, then the value must be BIT(N) and not 1.
CC: Chris Packham
CC: Ralph Sennhauser
Signed-of
On Fri, Jun 09, 2017 at 12:35:35PM +0300, Andy Shevchenko wrote:
> On Fri, Jun 9, 2017 at 12:03 PM, Greg Kroah-Hartman
> wrote:
> > We are trying to get rid of DRIVER_ATTR(), and the thinkpad_acpi
> > driver's attributes can be trivially changed to use DRIVER_ATTR_RO() and
> > DRIVER_ATTR_RW().
>
On Thu, Jun 08, 2017 at 09:55:30AM +1200, Chris Packham wrote:
> edac_op_state is a module parameter which affects the behaviour of the
> driver probe which can potentially be invoked as soon as the platform
> driver registration happens. Because of this we need to ensure that we
> sanity check the
On Thu, Jun 08, 2017 at 07:41:37PM +, Ard Biesheuvel wrote:
> This is a follow-up to patches from zhonjiang [0] and myself [1] that aim
> to solve a problem in the kcore code, which gets confused by the presence
> of block mappings in the vmalloc region.
>
> While fixing the crash is quite str
From: Johan Hovold
Make sure to deregister and release the nvmem device and underlying
memory on registration errors.
Note that the private data must be freed using put_device() once the
struct device has been initialised.
Also note that there's a related reference leak in the deregistration
fu
From: Heiner Kallweit
Adding entries to nvmem_cells and deleting entries from it is
protected by nvmem_cells_mutex. Therefore this mutex should
also protect iterating over the list.
Signed-off-by: Heiner Kallweit
Signed-off-by: Srinivas Kandagatla
---
drivers/nvmem/core.c | 8 +++-
1 file
Hi Geetha,
On Tue, May 30, 2017 at 05:33:41PM +0530, Geetha sowjanya wrote:
> From: Geetha Sowjanya
>
> Cavium ThunderX2 SMMU doesn't support MSI and also doesn't have unique irq
> lines for gerror, eventq and cmdq-sync.
>
> This patch addresses the issue by checking if any interrupt sources ar
From: Finley Xiao
This adds the necessary data for handling eFuse on the rk322x.
Signed-off-by: Finley Xiao
Acked-by: Rob Herring
Signed-off-by: Srinivas Kandagatla
---
Documentation/devicetree/bindings/nvmem/rockchip-efuse.txt | 1 +
drivers/nvmem/rockchip-efuse.c
From: Andrey Smirnov
Call put_device() in nvmem_unregister() to make sure nvmem_release
gets called freeing up allocated resources.
Cc: cphe...@gmail.com
Cc: Srinivas Kandagatla
Cc: Maxime Ripard
Signed-off-by: Andrey Smirnov
Signed-off-by: Srinivas Kandagatla
---
drivers/nvmem/core.c | 1 +
Hi Greg,
This patchset contains few fixes to core, Broadcom OTP driver and a patch
for new compatible to support rockchip rk322x-efuse.
Can you please queue these for v4.13.
Thanks,
srini
Andrey Smirnov (1):
nvmem: core: Call put_device() in nvmem_unregister()
Finley Xiao (1):
nvmem: roc
From: Oza Pawandeep
- use data write offset to write otp data instead of read offset
- use OTP program command 0x8 to write otp with ECC rather than just
command 0xA without ECC
Fixes: 9d59c6e8ae27 ("nvmem: Add the Broadcom OTP controller driver")
Signed-off-by: Oza Pawandeep
Signed-off-by: Sco
On Fri, 09 Jun 2017, Greg Kroah-Hartman wrote:
> We are trying to get rid of DRIVER_ATTR(), and the thinkpad_acpi
> driver's attributes can be trivially changed to use DRIVER_ATTR_RO() and
> DRIVER_ATTR_RW().
>
> Cc: Henrique de Moraes Holschuh
> Cc: Darren Hart
> Cc: Andy Shevchenko
> Cc:
> C
On 06/08/2017 03:55 PM, Jerome Brunet wrote:
> Remove the FIXME on clk81 mux and add all the documented parents
>
> Signed-off-by: Jerome Brunet
> ---
> drivers/clk/meson/gxbb.c | 13 -
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/clk/meson/gxbb.c b/dri
Linus,
please pull sound fixes for v4.12-rc5 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.12-rc5
The topmost commit is ba3021b2c79b2fa9114f92790a99deb27a65b728
sound fixes for 4.12-rc5
This
Hello Grygorii, Javier,
2017-06-09 2:00 GMT+02:00 Javier Martinez Canillas :
> Hello Grygorii,
>
> [snip]
>
>>>
>>> For tps65218 couldn't instead of using mfd_add_devices() for all the
>>> sub-devs, had used of_platform_populate() for the ones that have
>>> device nodes and mfd_add_devices() only
On Thu, Jun 08, 2017 at 02:19:40PM +0200, Sebastian Reichel wrote:
> Hi,
>
> On Mon, Jun 05, 2017 at 08:04:45PM +0300, Evgeniy Polyakov wrote:
> > 05.06.2017, 16:52, "Andrew F. Davis" :
> > > Like other subsystems we should be able to define slave devices outside
> > > of the w1 directory. To do t
On 06/08/2017 03:09 PM, Jerome Brunet wrote:
> Add Tsin A pins to bank DV and X.
> We don't have a driver for the tsin yet but since the tsin A pinmux is
> enabled by default at boot time, declaring this pinmux is required to
> properly operate on GPIOX.
>
> Without this change, GPIOX 8, 9, 10 and
From: Helmut Klein
Add the documentation for the device tree binding of Amlogic Meson Serial UART.
Signed-off-by: Helmut Klein
Signed-off-by: Neil Armstrong
---
.../bindings/serial/amlogic,meson-uart.txt | 38 ++
1 file changed, 38 insertions(+)
create mode 100644
Hi, Michal
I am not that familiar with hotplug and trying to catch up the issue
and your solution.
One potential issue I found is we don't check the physical boundary
when add_memory_resource().
For example, on x86-64, only 64T physical memory is supported currently.
Looks it is expanded after
On Mon, Jun 05, 2017 at 02:07:37PM -0500, Alan Tull wrote:
> From: Joshua Clayton
>
> altera-ps-spi loads FPGA firmware over SPI, using the "passive serial"
> interface on Altera Arria 10, Cyclone V or Stratix V FPGAs.
>
> This is one of the simpler ways to set up an FPGA at runtime.
> The signa
601 - 700 of 928 matches
Mail list logo
