Re: [PATCH 01/34] Documentation/memory-barriers.txt: document __smb_mb()

On Wed, 30 Dec 2015, Michael S. Tsirkin wrote: > Signed-off-by: Michael S. Tsirkin > --- > Documentation/memory-barriers.txt | 33 - > 1 file changed, 28 insertions(+), 5 deletions(-) > > diff --git a/Documentation/memory-barriers.txt > b/Documentation/memory-bar

Re: [PATCH 0/5] xen-netback: Fine-tuning for three function implementations

I think the original code is fine. Wei. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] serial: Remove 68328 driver

On 04/01/16 20:30, One Thousand Gnomes wrote: On Mon, 4 Jan 2016 15:03:50 +1000 Greg Ungerer wrote: If 68328serial.c is removed is there any point keeping the architecture support for 68328 platforms? The 68328serial.c provides pretty much the only type of console that can be used on these de

Re: [PATCH v1 3/3] ARM64 LPC: update binding doc

On Sunday 03 January 2016 20:24:14 Rongrong Zou wrote: > 在 2015/12/31 23:00, Rongrong Zou 写道: > > 2015-12-31 22:40 GMT+08:00 Arnd Bergmann > >: > > > On Thursday 31 December 2015 22:12:19 Rongrong Zou wrote: > > > > 在 2015/12/30 17:06, Arnd Bergmann 写道: > > > > > On Tuesda

Re: net-libertas: Better exception handling in if_spi_host_to_card_worker()

On 4 January 2016 at 11:05, Arend van Spriel wrote: > On 03-01-16 16:18, Rafał Miłecki wrote: >> On 3 January 2016 at 10:36, Arend van Spriel wrote: >>> On 02-01-16 12:21, SF Markus Elfring wrote: > Did you look at the resulting assembly code for different target > architectures? >>

[PATCH v3 0/2] Allow gmap fault to retry

Hello, sorry for the delay since the last version. During Jasons work with postcopy migration support for s390 a problem regarding gmap faults was discovered. The gmap code will call fixup_user_fault which will end up always in handle_mm_fault. Till now we never cared about retries, but as the u

[PATCH 2/2] s390/mm: enable fixup_user_fault retrying

By passing a non-null flag we allow fixup_user_fault to retry, which enables userfaultfd. As during these retries we might drop the mmap_sem we need to check if that happened and redo the complete chain of actions. Signed-off-by: Dominik Dingel --- arch/s390/mm/pgtable.c | 29 ++

[PATCH 1/2] mm: bring in additional flag for fixup_user_fault to signal unlock

With the introduction of userfaultfd, kvm on s390 needs fixup_user_fault to pass in FAULT_FLAG_ALLOW_RETRY and give feedback if during the faulting we ever unlocked mmap_sem. This patch brings in the logic to handle retries as well as it cleans up the current documentation. fixup_user_fault was n

Re: [PATCH 0/6] generic relative extable support

On Sun, Jan 03, 2016 at 05:05:51PM +0100, Ard Biesheuvel wrote: > There are currently four architectures (x86, ia64, alpha and s390) whose > user-access exception tables are relative to the table entry address rather > than absolute. Each of these architectures has its own search_extable() and > so

Re: [PATCH v2] thermal: re-calculate k_po/k_pu when update sustainable power

On 01/01/16 00:03, Leo Yan wrote: Hi Eduardo, Thanks for review. On Thu, Dec 31, 2015 at 09:21:26AM -0800, Eduardo Valentin wrote: On Wed, Dec 30, 2015 at 06:38:40PM +0800, Leo Yan wrote: k_po/k_pu are in essence ratio values compared with sustainable power. So when update sustainable power,

Re: [PATCH v2] memory-hotplug: add automatic onlining policy for the newly added memory

On 22/12/15 16:32, Vitaly Kuznetsov wrote: > @@ -1292,6 +1304,11 @@ int __ref add_memory_resource(int nid, struct resource > *res) > /* create new memmap entry */ > firmware_map_add_hotplug(start, start + size, "System RAM"); > > + /* online pages if requested */ > + if (onli

Re: Thoughts about introducing OPTIMIZATION_CFLAG

On Mon, Jan 4, 2016 at 11:54 AM, Sedat Dilek wrote: > [ Not sure if I have addressed all the correct people and mailing-lists ] > > Hi, > > while still digging into a llvmlinux issue with workqueue I saw that > the wrong optimization compiler-flag was used on x86 architecture and > acpi subsystem.

Re: [PATCH] lightnvm: add full block direct to the gc list

On 01/04/2016 10:54 AM, Wenwei Tao wrote: We allocate gcb to queue full block to the gc list, but gcb allocation may fail, if that happens, the block will not get reclaimed. So add the full block direct to the gc list, omit the queuing step. Signed-off-by: Wenwei Tao --- drivers/lightnvm/rrpc

Re: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option

Hi Andre, Arnd, On Tue, Dec 22, 2015 at 12:27:47PM +, Andre Przywara wrote: > To prepare for supporting the Allwinner A64 SoC, introduce a config > option to allow compiling Allwinner (aka. sunxi) specific drivers > for ARM64. > This patch just defines the ARCH_SUNXI symbol to allow Allwinner

Re: [PATCH 01/34] Documentation/memory-barriers.txt: document __smb_mb()

On Mon, Jan 04, 2016 at 11:08:19AM +, Stefano Stabellini wrote: > On Wed, 30 Dec 2015, Michael S. Tsirkin wrote: > > Signed-off-by: Michael S. Tsirkin > > --- > > Documentation/memory-barriers.txt | 33 - > > 1 file changed, 28 insertions(+), 5 deletions(-) > >

Re: [PATCH 1/2] 390/qeth: Delete an unnecessary variable initialisation in qeth_core_set_online()

On Sun, Jan 03, 2016 at 11:02:00AM +0100, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 3 Jan 2016 10:48:05 +0100 > > Omit explicit initialisation at the beginning for one local variable > that is redefined before its first use. > > Signed-off-by: Markus Elfring > --- > drivers/

Re: [PATCH 2/2] 390/qeth: Refactoring for qeth_core_set_online()

On Sun, Jan 03, 2016 at 11:02:56AM +0100, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 3 Jan 2016 10:50:11 +0100 > > Reduce the scope for the local variable "def_discipline" to one branch > of an if statement. > > Signed-off-by: Markus Elfring > --- > drivers/s390/net/qeth_core

Re: [Xen-devel] [PATCH v2 33/34] xenbus: use virt_xxx barriers

On 31/12/15 19:10, Michael S. Tsirkin wrote: > drivers/xen/xenbus/xenbus_comms.c uses > full memory barriers to communicate with the other side. > > For guests compiled with CONFIG_SMP, smp_wmb and smp_mb > would be sufficient, so mb() and wmb() here are only needed if > a non-SMP guest runs on an

Re: [Xen-devel] [PATCH v2 34/34] xen/io: use virt_xxx barriers

On 31/12/15 19:10, Michael S. Tsirkin wrote: > include/xen/interface/io/ring.h uses > full memory barriers to communicate with the other side. > > For guests compiled with CONFIG_SMP, smp_wmb and smp_mb > would be sufficient, so mb() and wmb() here are only needed if > a non-SMP guest runs on an S

Re: Thoughts about introducing OPTIMIZATION_CFLAG

> As said... I checked only for x86 and acpi only. > > For example '-Os' is hardcoded in... > > arch/x86/Makefile > arch/x86/purgatory/Makefile > > drivers/acpi/Makefile > drivers/acpi/acpica/Makefile > > For acpi part we have currently both used '-O2' and '-Os' ('-Oz' for > llvmlinux) in appro

[PATCH 0/3] checkpatch: handling of memory barriers

As part of memory barrier cleanup, this patchset extends checkpatch to make it easier to stop incorrect memory barrier usage. This applies on top of my series arch: barrier cleanup + barriers for virt and will be included in the next version of the series. Michael S. Tsirkin (3): checkp

[PATCH 2/3] checkpatch: check for __smp outside barrier.h

Introduction of __smp barriers cleans up a bunch of duplicate code, but it gives people an additional handle onto a "new" set of barriers - just because they're prefixed with __* unfortunately doesn't stop anyone from using it (as happened with other arch stuff before.) Add a checkpatch test so it

[PATCH 1/3] checkpatch.pl: add missing memory barriers

SMP-only barriers were missing in checkpatch.pl Refactor code slightly to make adding more variants easier. Signed-off-by: Michael S. Tsirkin --- scripts/checkpatch.pl | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl index

[PATCH 3/3] checkpatch: add virt barriers

Add virt_ barriers to list of barriers to check for presence of a comment. Signed-off-by: Michael S. Tsirkin --- scripts/checkpatch.pl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl index e3f9ad9..5fb6ef7 100755 --- a/scripts/c

Re: [PATCH] ARM: omapfb: Add early framebuffer memory allocator

Hi, On 01/01/16 14:01, Pali Rohár wrote: > Hi Tomi! Can you review this patch? It is waiting here for two years! > > On Thursday 26 December 2013 00:12:39 Ivaylo Dimitrov wrote: >> From: Ivaylo Dimitrov >> >> On memory limited devices, CMA fails easily when asked to allocate >> big chunks of mem

Re: [Xen-devel] [PATCH v2 08/16] xen, mm: Set IORESOURCE_SYSTEM_RAM to System RAM

On 25/12/15 22:09, Toshi Kani wrote: > Set IORESOURCE_SYSTEM_RAM to 'flags' of struct resource entries > with "System RAM". [...] > --- a/drivers/xen/balloon.c > +++ b/drivers/xen/balloon.c > @@ -257,7 +257,7 @@ static struct resource > *additional_memory_resource(phys_addr_t size) >

[PATCH] xen/events: use virt_xxx barriers

drivers/xen/events/events_fifo.c uses rmb() to communicate with the other side. For guests compiled with CONFIG_SMP, smp_rmb would be sufficient, so rmb() here is only needed if a non-SMP guest runs on an SMP host. Switch to the virt_rmb barrier which serves this exact purpose. Pull in asm/barri

Re: Thoughts about introducing OPTIMIZATION_CFLAG

On Mon, Jan 4, 2016 at 12:33 PM, One Thousand Gnomes wrote: >> As said... I checked only for x86 and acpi only. >> >> For example '-Os' is hardcoded in... >> >> arch/x86/Makefile >> arch/x86/purgatory/Makefile >> >> drivers/acpi/Makefile >> drivers/acpi/acpica/Makefile >> >> For acpi part we have

Re: [PATCH] xen/events: use virt_xxx barriers

On 04/01/16 11:46, Michael S. Tsirkin wrote: > drivers/xen/events/events_fifo.c uses rmb() to communicate with the > other side. > > For guests compiled with CONFIG_SMP, smp_rmb would be sufficient, so > rmb() here is only needed if a non-SMP guest runs on an SMP host. > > Switch to the virt_rmb

Re: [PATCH v10 2/3] mtd: nand: jz4780: driver for NAND devices on JZ4780 SoCs

Hi Harvey, On Mon, 4 Jan 2016 10:24:15 + Harvey Hunt wrote: > >> + > >> +static void jz4780_bch_disable(struct jz4780_bch *bch) > >> +{ > >> + writel(readl(bch->base + BCH_BHINT), bch->base + BCH_BHINT); > >> + writel(BCH_BHCR_BCHE, bch->base + BCH_BHCCR); > > > > Not sure what BCH_BHCR_B

Re: [PATCH 1/3] rsi: Delete unnecessary variable initialisations in rsi_send_mgmt_pkt()

On Mon, Jan 04, 2016 at 11:44:15AM +0100, SF Markus Elfring wrote: > > Please stop sending cleanup patches, Markus. Just send fixes. > > How often will source code clean-up fix something? > > > May I resend a consistent patch series for the source file > "drivers/net/wireless/rsi/rsi_91x_pkt.c"

[RFC PATCH v1 1/2] drm/rockchip: vop: add rk3229 vop support

RK3228 registers layout is simalar to RK3288 layout, only the interruput registers is different to RK3288. RK3228 support two overlay plane and one hwc plane, max output resolution is 4K. it support IOMMU, and its IOMMU same as rk3288's. Signed-off-by: Yakir Yang --- drivers/gpu/drm/rockchip/ro

Re: [PATCH v10 2/3] mtd: nand: jz4780: driver for NAND devices on JZ4780 SoCs

Hi Boris, On 04/01/16 11:47, Boris Brezillon wrote: Hi Harvey, On Mon, 4 Jan 2016 10:24:15 + Harvey Hunt wrote: + +static void jz4780_bch_disable(struct jz4780_bch *bch) +{ + writel(readl(bch->base + BCH_BHINT), bch->base + BCH_BHINT); + writel(BCH_BHCR_BCHE, bch->base + BCH

[RFC PATCH v1 2/2] dt-bindings: add document for rk3229-vop

Signed-off-by: Yakir Yang --- Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt b/Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt index

Re: a configfs update for 4.5, and the configfs tree question

On Tue, Dec 29, 2015 at 03:05:30PM -0800, Joel Becker wrote: > > Hoi, > > I'm well aware that I've caught some reviews and missed some others. I > support funneling through hch's tree here. Thanks. I've created a separate repo for configfs: git://git.infradead.org/users/hch/configfs.g

[RFC PATCH v1 0/2] Add RK3229 vop support

Add RK3229 vop support Yakir Yang (2): drm/rockchip: vop: add rk3229 vop support dt-bindings: add document for rk3229-vop .../bindings/display/rockchip/rockchip-vop.txt | 1 + drivers/gpu/drm/rockchip/rockchip_drm_vop.c| 7 +- drivers/gpu/drm/rockchip/rockchip_drm_vop.h

[RFC PATCH v1 1/2] drm/rockchip: vop: add rk3229 vop support

RK3229 registers layout is simalar to RK3288 layout, only the interruput registers is different to RK3288. RK3229 support two overlay plane and one hwc plane, max output resolution is 4K. it support IOMMU, and its IOMMU same as rk3288's. Signed-off-by: Yakir Yang --- drivers/gpu/drm/rockchip/ro

Re: [Xen-devel] patch about "don't reset vcpu_info on a cancelled suspend"

On 29/12/15 05:49, Ouyangzhaowei (Charles) wrote: > Hi David, > > This patch has been applied to for-linus-4.1b, and we wonder if this patch > will be applied to linux kernel, or does > it still needs more test to apply to linux kernel? Sorry, it looks like I forgot to send a pull request for th

[PATCH v5 04/11] arm-cci: Refactor CCI PMU enable/disable methods

This patch refactors the CCI PMU driver code a little bit to make it easier share the code for enabling/disabling the CCI PMU. This will be used by the hooks to work around the special cases where writing to a counter is not always that easy(e.g, CCI-500) No functional changes. Cc: Punit Agrawal

[PATCH v5 08/11] arm-cci: Provide hook for writing to PMU counters

Add a hook for writing to CCI PMU counters. This callback can be used for CCI models which requires some extra work to program the PMU counter values. To accommodate group writes and single counter writes, the call back accepts a bitmask of the counter indices which need to be programmed with the g

[PATCH v5 09/11] arm-cci: CCI-500: Work around PMU counter writes

The CCI PMU driver sets the event counter to the half of the maximum value(2^31) it can count before we start the counters via pmu_event_set_period(). This is done to give us the best chance to handle the overflow interrupt, taking care of extreme interrupt latencies. However, CCI-500 comes with a

[PATCH v5 06/11] arm-cci: Get the status of a counter

Add helper routines to check if the counter is enabled or not. Cc: Punit Agrawal Acked-by: Mark Rutland Signed-off-by: Suzuki K. Poulose --- drivers/bus/arm-cci.c |6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/bus/arm-cci.c b/drivers/bus/arm-cci.c index c768ee4..a3938ef 1

[PATCH v5 10/11] arm-cci500: Rearrange PMU driver for code sharing with CCI-550 PMU

CCI-550 PMU shares most of the CCI-500 PMU attributes including the event format, PMU event codes. The only difference is an additional master interface (MI6 - 0xe). Hence we share the driver code for both, except for a model specific event validate method. This patch renames the common CCI500 symb

[PATCH v5 11/11] arm-cci: CoreLink CCI-550 PMU driver

Add ARM CoreLink CCI-550 cache coherent interconnect PMU driver support. The CCI-550 PMU shares all the attributes of CCI-500 PMU, except for an additional master interface (MI-6 - 0xe). CCI-550 requires the same work around as for CCI-500 to write to the PMU counter. Acked-by: Punit Agrawal Ack

[PATCH v5 05/11] arm-cci PMU: Delay counter writes to pmu_enable

Delay setting the event periods for enabled events to pmu::pmu_enable(). We mark the event.hw->state PERF_HES_ARCH for the events that we know have their counts recorded and have been started. Since we reprogram the counters every time before count, we can set the counters for all the event counter

[PATCH v5 07/11] arm-cci: Add routines to save/restore all counters

Adds helper routines to disable the counter controls for all the counters on the CCI PMU and restore it back, by preserving the original state in caller provided mask. Cc: Punit Agrawal Cc: Mark Rutland Signed-off-by: Suzuki K. Poulose --- drivers/bus/arm-cci.c | 38 +

[PATCH v5 03/11] arm-cci: Group writes to counter

Add a helper to group the writes to PMU counter, this will be used to delay setting the event period to pmu::pmu_enable() Cc: Mark Rutland Cc: Punit Agrawal Signed-off-by: Suzuki K. Poulose --- drivers/bus/arm-cci.c | 15 +++ 1 file changed, 15 insertions(+) diff --git a/drivers

Re: [RFC PATCH v1 1/2] drm/rockchip: vop: add rk3229 vop support

Sorry, there shouldn't have the "3228" prefix, %s/3228/3229 I have send the new patch out, please ignore this one. Thanks, - Yakir On 01/04/2016 07:50 PM, Yakir Yang wrote: RK3228 registers layout is simalar to RK3288 layout, only the interruput registers is different to RK3288. RK3228 su

[PATCH v5 00/11] arm-cci: PMU updates

This series includes: - Work around for writing to CCI-500/550(introduced later) PMU counters (Patches 1-9) - Support for CCI-550 PMU (10-11) with Acked-bys. Since all of these are related I am clubbing it all in one series so that it is easier to carry them around (and merge it possibly).

[PATCH v5 02/11] arm-cci: Refactor pmu_write_counter

Refactor pmu_write_counter to add __pmu_write_counter() which will actually write to the counter once the event is validated. This can be used by hooks specific to CCI PMU model to program the counter, where the event is already validated. Cc: Mark Rutland Cc: Punit Agrawal Signed-off-by: Suzuki

Re: [PATCH] xen/events: use virt_xxx barriers

/20160104-194916 config: x86_64-randconfig-x008-01040711 (attached as .config) reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones prefixed by >>): drivers/xen/events/events_fifo.c: In function 'consume_one_event': >&

[PATCH v5 01/11] arm-cci: Define CCI counter period

Instead of hard coding the period we program on the PMU counters, define a symbol. Cc: Mark Rutland Cc: Punit Agrawal Signed-off-by: Suzuki K. Poulose --- drivers/bus/arm-cci.c | 19 ++- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/drivers/bus/arm-cci.c b/dr

[PATCH] soc: mediatek: PMIC wrap: Clear the vldclr if state machine stay on FSM_VLDCLR state.

Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout, because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It just return error when issue happened, so the state machine will stay on FSM_VLDCLR state when data send back later by PMIC and timeout again in next

[RESEND PATCH v2] soc: mediatek: PMIC wrap: Clear the vldclr if state machine stay on FSM_VLDCLR state.

Sometimes PMIC is too busy to send data in time to cause pmic wrap timeout, because pmic wrap is waiting for FSM_VLDCLR after finishing WACS2_CMD. It just return error when issue happened, so the state machine will stay on FSM_VLDCLR state when data send back later by PMIC and timeout again in next

Re: [PATCH v2 33/34] xenbus: use virt_xxx barriers

On Thu, 31 Dec 2015, Michael S. Tsirkin wrote: > drivers/xen/xenbus/xenbus_comms.c uses > full memory barriers to communicate with the other side. > > For guests compiled with CONFIG_SMP, smp_wmb and smp_mb > would be sufficient, so mb() and wmb() here are only needed if > a non-SMP guest runs on

Re: [PATCH v2 34/34] xen/io: use virt_xxx barriers

On Thu, 31 Dec 2015, Michael S. Tsirkin wrote: > include/xen/interface/io/ring.h uses > full memory barriers to communicate with the other side. > > For guests compiled with CONFIG_SMP, smp_wmb and smp_mb > would be sufficient, so mb() and wmb() here are only needed if > a non-SMP guest runs on an

Re: [PATCH v6 1/4] x86: Clean up extable entry format (and free up a bit)

On Wed, Dec 30, 2015 at 09:59:29AM -0800, Andy Lutomirski wrote: > This adds two bits of fixup class information to a fixup entry, > generalizing the uaccess_err hack currently in place. > > Forward-ported-from-3.9-by: Tony Luck > Signed-off-by: Andy Lutomirski > --- > arch/x86/include/asm/asm.

[PATCH v2] of/unittest: Show broken behaviour in the platform bus

From: Grant Likely Add a single resource to the test bus device to exercise the platform bus code a little more. This isn't strictly a devicetree test, but it is a corner case that the devicetree runs into. Until we've got platform device unittests, it can live here. It doesn't need to be an expl

Re: [RFC PATCH 5/5] arm64: Introduce Allwinner SoC config option

On Monday 04 January 2016 12:26:48 Maxime Ripard wrote: > Hi Andre, Arnd, > > On Tue, Dec 22, 2015 at 12:27:47PM +, Andre Przywara wrote: > > To prepare for supporting the Allwinner A64 SoC, introduce a config > > option to allow compiling Allwinner (aka. sunxi) specific drivers > > for ARM64.

Re: [PATCH] Staging: speakup: Fix getting port information

On Sun, Jan 03, 2016 at 12:25:29AM +0100, Samuel Thibault wrote: > 5e6dc54 broke the port information in the speakup driver: There is a correct format for this. Patch 5e6dc548e453 ('drivers: staging: speakup: serialio: only use platform specific SERIAL_PORT_DFNS.') broke the port information ...

Re: [RFC PATCH 01/10] arm64: introduce KIMAGE_VADDR as the virtual base of the kernel region

On Sunday 03 January 2016 14:50:10 Mark Rutland wrote: > > > - once we have a random number in the bootloader, we should also pass that > > through a DT property. This has been discussed multiple times in the past > > and I think we had reached consensus already but don't know if we had > >

Re: [PATCH] Staging: speakup: Fix getting port information

On Sun, Jan 03, 2016 at 01:56:20AM +0100, Samuel Thibault wrote: > cov...@ccs.covici.com, on Sat 02 Jan 2016 19:10:36 -0500, wrote: > > I had a patch which also worked, but yours may be better -- I enclose it > > here for your information. > > Well, it's not up to serialio.h to include things for

[PATCH 2/2] Bluetooth: hci_bcm: new ACPI IDs

These are used at least by Acer with BCM43241. Signed-off-by: Heikki Krogerus --- drivers/bluetooth/hci_bcm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/bluetooth/hci_bcm.c b/drivers/bluetooth/hci_bcm.c index abf13a7..5f3de18 100644 --- a/drivers/bluetooth/hci_bcm.c +++ b/dri

[PATCH 1/2] Bluetooth: hci_bcm/rfkill-gpio: move all Broadcom ACPI IDs to BCM HCI driver

The IDs should all be for Broadcom BCM43241 module, and hci_bcm is now the proper driver for them. This removes one of two different ways of handling PM with the module. Signed-off-by: Heikki Krogerus Cc: Johannes Berg --- drivers/bluetooth/hci_bcm.c | 4 net/rfkill/rfkill-gpio.c| 4 --

Re: [RFC PATCH v1 1/2] drm/rockchip: vop: add rk3229 vop support

Hi Yakir, Am Montag, 4. Januar 2016, 19:53:58 schrieb Yakir Yang: > RK3229 registers layout is simalar to RK3288 layout, only the > interruput registers is different to RK3288. > > RK3229 support two overlay plane and one hwc plane, max output > resolution is 4K. it support IOMMU, and its IOMMU s

[PATCH 0/2] Bluetooth: hci_bcm: drop BCM43241 support from rfkill_gpio

Now that drivers/bluetooth/hci_bcm.c is able to handle the GPIOs assigned to BCM43241, there is absolutely no reason to continue supporting the module in rfkill_gpio. Heikki Krogerus (2): Bluetooth: hci_bcm/rfkill-gpio: move all Broadcom ACPI IDs to BCM HCI driver Bluetooth: hci_bcm: new

[PATCH 01/10] [media] tvp5150: Restructure version detection

From: Laurent Pinchart Move the version detection code to a separate function and restructure it to prepare for TVP5151 support. Signed-off-by: Laurent Pinchart Signed-off-by: Javier Martinez Canillas --- drivers/media/i2c/tvp5150.c | 79 ++--- 1 file

[PATCH 07/10] [media] tvp5150: Add device tree binding document

Add a Device Tree binding document for the TVP5150 video decoder. Signed-off-by: Javier Martinez Canillas --- .../devicetree/bindings/media/i2c/tvp5150.txt | 35 ++ 1 file changed, 35 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/tvp5150.

[PATCH 09/10] [media] tvp5150: Initialize the chip on probe

After power-up, the tvp5150 decoder is in a unknown state until the RESETB pin is driven LOW which reset all the registers and restarts the chip's internal state machine. The init sequence has some timing constraints and the RESETB signal can only be used if the PDN (Power-down) pin is first relea

[PATCH 05/10] [media] tvp5150: Add s_stream subdev operation support

From: Laurent Pinchart This patch adds the .s_stream subdev operation to the driver. Signed-off-by: Laurent Pinchart Signed-off-by: Javier Martinez Canillas --- drivers/media/i2c/tvp5150.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/media/i2c/tvp5150.c b/dri

[PATCH 03/10] [media] tvp5150: Add pad-level subdev operations

From: Laurent Pinchart This patch enables the tvp5150 decoder driver to be used with the media controller framework by adding pad-level subdev operations and init the media entity pad. Signed-off-by: Laurent Pinchart Signed-off-by: Javier Martinez Canillas --- drivers/media/i2c/tvp5150.c | 6

Re: [PATCH] Staging: speakup: Fix getting port information

On Mon, Jan 04, 2016 at 03:22:49PM +0300, Dan Carpenter wrote: > On Sun, Jan 03, 2016 at 01:56:20AM +0100, Samuel Thibault wrote: > > cov...@ccs.covici.com, on Sat 02 Jan 2016 19:10:36 -0500, wrote: > > > I had a patch which also worked, but yours may be better -- I enclose it > > > here for your i

[PATCH 10/10] [media] tvp5150: Configure data interface via pdata or DT

The video decoder supports either 8-bit 4:2:2 YUV with discrete syncs or 8-bit ITU-R BT.656 with embedded syncs output format but currently BT.656 it's always reported. Allow to configure the format to use via either platform data or a device tree definition. Signed-off-by: Javier Martinez Canilla

Re: [PATCH v2 14/16] x86, nvdimm, kexec: Use walk_iomem_res_desc() for iomem search

On Mon, Jan 04, 2016 at 05:29:37PM +0800, Dave Young wrote: > Replied to Toshi old kernel will export the "GART" region for amd cards. > So for old kernel and new kexec-tools we will have problem. > > I think add the GART desc for compitibility purpose is doable, no? Just read your other mails to

[PATCH v4 0/5] Add Support for Hi6220 PMIC Hi6553 MFD Core

The patch sets add support for Hi6220 PMIC Hi655x MFD core and its regulator driver. Current testing and support board is Hikey which is one of 96boards. It is an arm64 open source board. For more information about this board, please access https://www.96boards.org. This is hardware layout for a

[PATCH 08/10] [media] tvp5150: Add OF match table

From: Eduard Gavin The Documentation/devicetree/bindings/media/i2c/tvp5150.txt DT binding doc lists "ti,tvp5150" as the device compatible string but the driver does not have an OF match table. Add the table to the driver so the I2C core can do an OF style match. Signed-off-by: Eduard Gavin Sign

[PATCH 06/10] [media] tvp5150: Add g_mbus_config subdev operation support

From: Laurent Pinchart This patch adds the .g_mbus_config subdev operation to the driver. Signed-off-by: Laurent Pinchart Signed-off-by: Javier Martinez Canillas --- drivers/media/i2c/tvp5150.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/media/i2c/tvp5150.c b/dri

[PATCH 02/10] [media] tvp5150: Add tvp5151 support

From: Laurent Pinchart Expand the version detection code to identity the tvp5151. Signed-off-by: Laurent Pinchart Signed-off-by: Javier Martinez Canillas --- drivers/media/i2c/tvp5150.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/media/i2c/tvp5150.c b/drivers/media/i2c/tvp5

[PATCH 04/10] [media] tvp5150: Add pixel rate control support

From: Laurent Pinchart This patch adds support for the V4L2_CID_PIXEL_RATE control. Signed-off-by: Laurent Pinchart Signed-off-by: Javier Martinez Canillas --- drivers/media/i2c/tvp5150.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/media/i2c/tvp5150.c b/dr

[PATCH v4 1/5] doc: bindings: Add document for mfd hi665x PMIC

Add document for mfd driver hi655x pmic driver Signed-off-by: Chen Feng Signed-off-by: Fei Wang Signed-off-by: Xinwei Kong --- .../devicetree/bindings/mfd/hisilicon,hi655x.txt| 17 + 1 file changed, 17 insertions(+) create mode 100644 Documentation/devicetree/bindings/

[PATCH 00/10] [media] tvp5150: add MC and DT support

Hello, One of my testing platforms for the MC next gen [0] work has been an OMAP3 board (IGEPv2) with a tvp5151 video decoder attached to the OMAP3ISP block. I've been using some patches from Laurent Pinchart that adds MC support to the tvp5150 driver. The patches were never posted to the list an

Re: [PATCH v2] memory-hotplug: add automatic onlining policy for the newly added memory

On Mon, 04 Jan 2016 11:47:12 +0100 Vitaly Kuznetsov wrote: > Andrew Morton writes: > > > On Tue, 22 Dec 2015 17:32:30 +0100 Vitaly Kuznetsov > > wrote: > > > >> Currently, all newly added memory blocks remain in 'offline' state unless > >> someone onlines them, some linux distributions carr

[PATCH v4 2/5] doc: bindings: Document for hi655x regulator driver

Add Document for hi655x pmic regulator driver Signed-off-by: Chen Feng Signed-off-by: Fei Wang Signed-off-by: Xinwei Kong --- .../regulator/hisilicon,hi655x-regulator.txt | 24 ++ 1 file changed, 24 insertions(+) create mode 100644 Documentation/devicetree/bindings/

[PATCH v4 5/5] hisilicon/dts: Add hi655x pmic dts node

Add the mfd hi655x dts node and regulator support Signed-off-by: Chen Feng Signed-off-by: Fei Wang Signed-off-by: Xinwei Kong --- arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 5 ++ arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 99 ++ 2 files changed, 104 inserti

[PATCH v4 3/5] mfd: hi655x: Add hi665x pmic driver

Add pmic mfd driver to support hisilicon hi665x. Signed-off-by: Chen Feng Signed-off-by: Fei Wang Signed-off-by: Xinwei Kong --- drivers/mfd/Kconfig | 10 +++ drivers/mfd/Makefile| 1 + drivers/mfd/hi655x-pmic.c | 160 i

Re: [PATCH v2 6/7] udf: Remove struct ustr as non-needed intermediate storage

On Thu 24-12-15 10:25:37, Andrew Gabbasov wrote: > Although 'struct ustr' tries to structurize the data by combining > the string and its length, it doesn't actually make much benefit, > since it saves only one parameter, but introduces an extra copying > of the whole buffer, serving as an intermed

Re: [RFC PATCH 01/10] arm64: introduce KIMAGE_VADDR as the virtual base of the kernel region

On Mon, Jan 04, 2016 at 01:21:05PM +0100, Arnd Bergmann wrote: > On Sunday 03 January 2016 14:50:10 Mark Rutland wrote: > > > > > - once we have a random number in the bootloader, we should also pass that > > > through a DT property. This has been discussed multiple times in the > > > past > >

Re: linux-next: manual merge of the integrity tree with the vfs tree

On Mon, 2016-01-04 at 16:23 +1100, Stephen Rothwell wrote: > Hi Mimi, > > On Mon, 04 Jan 2016 00:06:37 -0500 Mimi Zohar > wrote: > > > > On Mon, 2016-01-04 at 03:16 +, Al Viro wrote: > > > > > > FWIW, I'm going to pull the part that introduces memdup_user_nul() into > > > a never-rebased bra

[PATCH v4 4/5] regulator: add regulator driver of hi655x pmic

Add regulator support for hi655x pmic Signed-off-by: Chen Feng Signed-off-by: Fei Wang Signed-off-by: Xinwei Kong --- drivers/regulator/Kconfig| 8 ++ drivers/regulator/Makefile | 1 + drivers/regulator/hi655x-regulator.c | 232 +++ 3 f

Re: rsi: Delete unnecessary variable initialisations in rsi_send_mgmt_pkt()

>> May I resend a consistent patch series for the source file >> "drivers/net/wireless/rsi/rsi_91x_pkt.c" in the near future? > > If you were sending checkpatch.pl fixes that would be easier to deal with Does this feedback mean that you would accept any more suggestions around source code updates

Re: [PATCH 1/2] crypto: af_alg - Add nokey compatibility path

On 01/04/2016 05:35 AM, Herbert Xu wrote: > On Sun, Jan 03, 2016 at 10:42:28AM +0100, Milan Broz wrote: >> >> yes, basically it prepares socket()/bind()/accept() and then it calls setkey >> once. >> (I'll try to fix in next releases to call setkey first though.) > > OK please try these two patch

[PATCH v11 2/3] mtd: nand: jz4780: driver for NAND devices on JZ4780 SoCs

From: Alex Smith Add a driver for NAND devices connected to the NEMC on JZ4780 SoCs, as well as the hardware BCH controller. DMA is not currently implemented. While older 47xx SoCs also have a BCH controller, they are incompatible with the one in the 4780 due to differing register/bit positions,

[PATCH v11 1/3] dt-bindings: binding for jz4780-{nand,bch}

From: Alex Smith Add DT bindings for NAND devices connected to the NEMC on JZ4780 SoCs, as well as the hardware BCH controller, used by the jz4780_{nand,bch} drivers. Signed-off-by: Alex Smith Cc: Zubair Lutfullah Kakakhel Cc: David Woodhouse Cc: Brian Norris Cc: linux-...@lists.infradead.or

[PATCH v11 3/3] MIPS: dts: jz4780/ci20: Add NEMC, BCH and NAND device tree nodes

From: Alex Smith Add device tree nodes for the NEMC and BCH to the JZ4780 device tree, and make use of them in the Ci20 device tree to add a node for the board's NAND. Note that since the pinctrl driver is not yet upstream, this includes neither pin configuration nor busy/write-protect GPIO pins

Re: a configfs update for 4.5, and the configfs tree question

On Mon, Jan 04, 2016 at 12:51:01PM +0100, Christoph Hellwig wrote: > On Tue, Dec 29, 2015 at 03:05:30PM -0800, Joel Becker wrote: > > > > Hoi, > > > > I'm well aware that I've caught some reviews and missed some others. I > > support funneling through hch's tree here. > > Thanks. I've created

Re: [PATCH 2/2] mm/compaction: speed up pageblock_pfn_to_page() when zone is contiguous

On 12/23/2015 07:57 AM, Joonsoo Kim wrote: What are the cases where pageblock_pfn_to_page() is used for a subset of the pageblock and the result would be problematic for compaction? I.e., do we actually care to use pageblocks that are not contiguous at all? The problematic pageblocks are those

Re: [PATCH 09/10] [media] tvp5150: Initialize the chip on probe

-add-MC-and-DT-support/20160104-203224 base: git://linuxtv.org/media_tree.git master config: x86_64-randconfig-x008-01040711 (attached as .config) reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones prefixed by >>): drivers/med

RE: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL PCIe Host Controller

Hi Bjorn, can you comment on this. Marc has also replied for query on irq_dispose_mapping(). > > Subject: RE: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for > > Xilinx NWL PCIe Host Controller > > > > > Subject: Re: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for > > > Xilinx NWL PCIe Hos

Re: [Patch-V2 1/6] INPUT: xpad: Add minimal support for Logitech G920 Wheel

On Mon Jan 4 10:55:24 2016 GMT+0100, Benjamin Tissoires wrote: > On Dec 10 2015 or thereabouts, Dmitry Torokhov wrote: > > On Thu, Dec 10, 2015 at 9:08 AM, Benjamin Tissoires > > wrote: > > > On Dec 09 2015 or thereabouts, Dmitry Torokhov wrote: > > >> On Wed, Dec 9, 2015 at 5:23 PM, Dmitry Toro

Re: [PATCH 00/42] ACPICA: 20151218 Release

On Monday, January 04, 2016 02:27:43 AM Zheng, Lv wrote: > Hi, > > > From: David Lang [mailto:da...@lang.hm] > > Sent: Sunday, January 3, 2016 2:45 PM > > > > what is ACPICA and why should we care about divergence between it and the > > linux > > upstream? Where is it to be found? > [Lv Zheng] >

<    1   2   3   4   5   6   7   8   9   >