[PATCH v3] EDAC, mpc85xx: Make mpc85xx-pci-edac a platform device

Originally the mpc85xx-pci-edac driver bound directly to the PCI controller node. Commit 905e75c46dba5f30 ("powerpc/fsl-pci: Unify pci/pcie initialization code") turned the PCI controller code into a platform device. Since we can't have two drivers binding to the same device, the edac code was

Re: [PATCH v2 2/2] powerpc: Copy only required pieces of the mm_context_t to the paca

On Thu, 2015-12-10 at 14:46 +1100, Michael Neuling wrote: > Currently we copy the whole mm_context_t to the paca but only access a > few bits of it. This is wasteful of space paca and also takes quite > some time in the hot path of context switching. > > diff --git

[PATCH] powerpc: Call check_if_tm_restore_required() in enable_kernel_*()

Commit a0e72cf12b1a ("powerpc: Create msr_check_and_{set,clear}()") removed a call to check_if_tm_restore_required() in the enable_kernel_*() functions. Add them back in. Fixes: a0e72cf12b1a ("powerpc: Create msr_check_and_{set,clear}()") Reported-by: Rashmica Gupta

[PATCH v2] powerpc: Call restore_sprs() before _switch()

commit 152d523e6307 ("powerpc: Create context switch helpers save_sprs() and restore_sprs()") moved the restore of SPRs after the call to _switch(). There is an issue with this approach - new tasks do not return through _switch(), they are set up by copy_thread() to directly return through

[PATCH v3 2/2] powerpc: Copy only required pieces of the mm_context_t to the paca

Currently we copy the whole mm_context_t to the paca but only access a few bits of it. This is wasteful of space paca and also takes quite some time in the hot path of context switching. This patch pulls in only the required bits from the mm_context_t to the paca and on context switch, copies

[PATCH 0/6] cxlflash: Miscellaneous fixes and updates

This patch set contains miscellaneous fixes and adds support for a future IBM CXL adapter. This series is intended for 4.5 and is bisectable. Manoj Kumar (4): cxlflash: Fix to escalate LINK_RESET also on port 1 cxlflash: Fix to resolve cmd leak after host reset cxlflash: Resolve oops in

[PATCH 1/6] cxlflash: Fix to escalate LINK_RESET also on port 1

From: Manoj Kumar The original fix to escalate a 'login timed out' error to a LINK_RESET was only made for one of the two ports on the card. This fix resolves the same issue for the second port (port 1). Signed-off-by: Manoj N. Kumar ---

[PATCH 4/6] cxlflash: Fix to resolve cmd leak after host reset

From: Manoj Kumar After a few iterations of resetting the card, either during EEH recovery, or a host_reset the following is seen in the logs. cxlflash 0008:00: cxlflash_queuecommand: could not get a free command At every reset of the card, the commands that are

Re: [PATCH 3/6] cxlflash: Updated date of the driver

Hi Uma, It looks like CXLFLASH_DRIVER_DATE is only used once, on init, and it's just printed. Is it necessary? It looks like having it will require sending a patch to update it quite often. Regards, Daniel signature.asc Description: PGP signature

[PATCH] powerpc/powernv: pr_warn_once on unsupported OPAL_MSG type

When running on newer OPAL firmware that supports sending extra OPAL_MSG types, we would print a warning on *every* message received. This could be a problem for kernels that don't support OPAL_MSG_OCC on machines that are running real close to thermal limits and the OCC is throttling the chip.

[PATCH 2/6] cxlflash: Fix to avoid virtual LUN failover failure

From: "Matthew R. Ochs" Applications which use virtual LUN's that are backed by a physical LUN over both adapter ports may experience an I/O failure in the event of a link loss (e.g. cable pull). Virtual LUNs may be accessed through one or both ports of the adapter.

[PATCH 3/6] cxlflash: Updated date of the driver

This change is to update the date when last change was made to the cxlflash driver Signed-off-by: Uma Krishnan --- drivers/scsi/cxlflash/main.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/scsi/cxlflash/main.h

[PATCH 5/6] cxlflash: Resolve oops in wait_port_offline

From: Manoj Kumar If an async error interrupt is generated, and the error requires the FC link to be reset, it cannot be performed in the interrupt context. So a work element is scheduled to complete the link reset in a process context. If either an EEH event or an

[PATCH 6/6] cxlflash: Enable device id for future IBM CXL adapter

From: Manoj Kumar This drop enables a future card with a device id of 0x0600 to be recognized by the cxlflash driver. No card specific programming has been added. These card specific changes will be staged in later. Signed-off-by: Manoj N. Kumar

Re: [PATCH] powerpc/opal: add warning for unimplemented OPAL message type

蒲文 writes: > On Wednesday, December 09, 2015 11:17:12 AM Michael Ellerman wrote: >> On Tue, 2015-12-08 at 15:30 +0800, wen...@powercore.com.cn wrote: >> > I found that there are unimplemented OPAL message types "OPAL_MSG_EPOW" >> > and >> > "OPAL_MSG_DPO" in PowerNV

Re: [PATCH] powerpc/powernv: pr_warn_once on unsupported OPAL_MSG type

On Friday, December 11, 2015 01:21:05 PM Michael Ellerman wrote: > On Fri, 2015-12-11 at 12:08 +1100, Stewart Smith wrote: > > When running on newer OPAL firmware that supports sending extra > > OPAL_MSG types, we would print a warning on *every* message received. > > > > This could be a problem

Re: [PATCH] powerpc/powernv: pr_warn_once on unsupported OPAL_MSG type

On Fri, 2015-12-11 at 12:08 +1100, Stewart Smith wrote: > When running on newer OPAL firmware that supports sending extra > OPAL_MSG types, we would print a warning on *every* message received. > > This could be a problem for kernels that don't support OPAL_MSG_OCC > on machines that are running

Re: [PATCH] powerpc/powernv: pr_warn_once on unsupported OPAL_MSG type

Michael Ellerman writes: > On Fri, 2015-12-11 at 12:08 +1100, Stewart Smith wrote: >> When running on newer OPAL firmware that supports sending extra >> OPAL_MSG types, we would print a warning on *every* message received. >> >> This could be a problem for kernels that don't

[PATCH] arch/powerpc/Kconfig: fix typo in select statement

The 'I' in sanitize was missing: s/ARCH_HAS_UBSAN_SANTIZE_ALL/ARCH_HAS_UBSAN_SANITIZE_ALL/ Fixes: 257e4ee82dbd ("powerpc: enable UBSAN support") Signed-off-by: Valentin Rothberg --- Detected with ./scripts/checkkconfigsymbols.py arch/powerpc/Kconfig | 2 +- 1 file

[PATCH v9 51/60] PCI: Unify skip_ioresource_align()

There are powerpc generic version and x86 local version for skip_ioresource_align(). Move the powerpc version to setup-bus.c, and kill x86 local version. Also kill dummy version in microblaze. Cc: Michal Simek Cc: Paul Mackerras Cc: Michael Ellerman

[PATCH v9 09/60] powerpc/PCI: Add IORESOURCE_MEM_64 for 64-bit resource in OF parsing

For device resource PREF bit setting under bridge 64-bit pref resource, we need to make sure only set PREF for 64bit resource, so set IORESOUCE_MEM_64 for 64bit resource during of device resource flags parsing. Link: https://bugzilla.kernel.org/show_bug.cgi?id=96261 Link:

Re: [PATCH] powerpc/nvram: Fix an incorrect partition merge

Hi, all I do some tests *without* my fix patch. after reboot, I saw logs below. [0.271236] WARNING: nvram partition checksum was 58, should be 24! [0.271239] Terminating nvram partition scan If I do tests *with* my fix patch, logs are: [0.291419] NVRAM

[PATCH v9 58/60] PCI: Introduce resource_disabled()

Current is using !flags, and we are going to use IORESOURCE_DISABLED instead of clearing resource flags. Let's convert all !flags to helper function resource_disabled(). resource_disabled will check !flags and IORESOURCE_DISABLED both. Cc: linux-al...@vger.kernel.org Cc:

Re: [PATCH v3 1/4] printk/nmi: Generic solution for safe printk in NMI

On Wed 2015-12-09 15:50:07, Andrew Morton wrote: > On Wed, 9 Dec 2015 14:21:02 +0100 Petr Mladek wrote: > > > printk() takes some locks and could not be used a safe way in NMI > > context. > > > > The chance of a deadlock is real especially when printing > > stacks from all