This patch removes all clocks and PHY references from the APM X-Gene
SoC AHCI SATA host controller and PHY DTS nodes. The clock and PHY
are no longer needed as they are handled by the firmware. By removing
only the reference is not enough as any un-used clock entry will get
disabled by the clock fr
This patch removes the NCQ support from the APM X-Gene SoC AHCI
Host Controller driver as it doesn't support it.
Signed-off-by: Loc Ho
Signed-off-by: Suman Tripathi
---
drivers/ata/ahci_xgene.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/ata/ahci_xgene.c b/dr
As per SATA IO specification, when Host sends HOLD, the device takes
about 20DW latency to reply to HOLDA. In some case, device doesn't
response to HOLDA over 20DW and causes FIFO goes into over flow
condition. Due to this condition, device enumerations fails with
those devices. This patch adjust t
APM X-Gene SoC AHCI SATA Host controller driver requires
some correction of Phy Control OOB timing for the
COMINIT/COMWAKE parameters to correctly interoperate with
different kinds of disks.
Signed-off-by: Loc Ho
Signed-off-by: Suman Tripathi
---
drivers/ata/ahci_xgene.c | 6 +++---
1 file chan
This patch set contains a couple of fixes related to APM X-Gene SATA
controller driver.
v2 Change:
1. Drop the Link down retry patch from this patch set.
v4 Change:
1. Drop the patch to fix the csr-mask in dts for PHY clock
node of SATA Host Controller 1.
2. Add the patch to correct
On 07/29/2014 03:13 AM, Luis R. Rodriguez wrote:
On Mon, Jul 28, 2014 at 5:35 PM, Greg KH wrote:
On Mon, Jul 28, 2014 at 05:26:34PM -0700, Luis R. Rodriguez wrote:
On Mon, Jul 28, 2014 at 4:46 PM, Greg KH wrote:
On Mon, Jul 28, 2014 at 12:48:32PM -0700, Luis R. Rodriguez wrote:
On Mon, Jul
On 14-07-28 04:57 PM, Jeremy Linton wrote:
On 7/20/2014 4:54 PM, joystick wrote:
So what happens when the disk tries to write it to the platter and
discovers that there is a media error on that sector? (suppose relocation
does not happen ; maybe sectors exhausted) Does Linux receive the write
er
On Mon, Jul 28, 2014 at 5:35 PM, Greg KH wrote:
> On Mon, Jul 28, 2014 at 05:26:34PM -0700, Luis R. Rodriguez wrote:
>> On Mon, Jul 28, 2014 at 4:46 PM, Greg KH wrote:
>> > On Mon, Jul 28, 2014 at 12:48:32PM -0700, Luis R. Rodriguez wrote:
>> >> On Mon, Jul 28, 2014 at 12:04 PM, Luis R. Rodriguez
On Mon, Jul 28, 2014 at 05:26:34PM -0700, Luis R. Rodriguez wrote:
> On Mon, Jul 28, 2014 at 4:46 PM, Greg KH wrote:
> > On Mon, Jul 28, 2014 at 12:48:32PM -0700, Luis R. Rodriguez wrote:
> >> On Mon, Jul 28, 2014 at 12:04 PM, Luis R. Rodriguez
> >> wrote:
> >> > On Mon, Jul 28, 2014 at 11:55 AM,
On Mon, Jul 28, 2014 at 4:46 PM, Greg KH wrote:
> On Mon, Jul 28, 2014 at 12:48:32PM -0700, Luis R. Rodriguez wrote:
>> On Mon, Jul 28, 2014 at 12:04 PM, Luis R. Rodriguez
>> wrote:
>> > On Mon, Jul 28, 2014 at 11:55 AM, Greg KH
>> > wrote:
>> >> So, what drivers are having problems in their in
The module was removed in c6072609d9bb91ff54aee3ef29304bd5b4fc88aae
Author: James Bottomley
Date: Sun May 27 10:13:46 2012 +0100
[SCSI] Remove scsi_wait_scan module
Signed-off-by: Yannick Brosseau
---
drivers/scsi/Kconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
dif
On 7/20/2014 4:54 PM, joystick wrote:
> So what happens when the disk tries to write it to the platter and
> discovers that there is a media error on that sector? (suppose relocation
> does not happen ; maybe sectors exhausted) Does Linux receive the write
> error upon the next flush it issues?
On Mon, Jul 28, 2014 at 12:48:32PM -0700, Luis R. Rodriguez wrote:
> On Mon, Jul 28, 2014 at 12:04 PM, Luis R. Rodriguez
> wrote:
> > On Mon, Jul 28, 2014 at 11:55 AM, Greg KH
> > wrote:
> >> So, what drivers are having problems in their init sequence, and why
> >> aren't they using async firmwa
> From: joystick
>
> I don't really understand this disk cache thing.
> Suppose a disk with write cache enabled of writeback type: Linux
> receives a write completed notification (a message from the disk) when
> the data has reached the cache of the disk. Correct? At that point it is
> not con
Set the scsi_level correctly for disk arrays such
that things like the rotational field get set
properly by sd.c.
Signed-off-by: Brian King
---
drivers/scsi/ipr.c |1 +
1 file changed, 1 insertion(+)
diff -puN drivers/scsi/ipr.c~ipr_array_scsi_level drivers/scsi/ipr.c
--- linux/drivers/sc
Currently when performing a kexec boot with an ipr adapter,
the adapter gets shutdown completely, flushing all write
cache, as well as performing a full hardware reset of the card
during the shutdown phase of the old kernel. This forces
the new kernel to then wait for the adapter firmware to
reini
Bump driver version.
Signed-off-by: Brian King
---
drivers/scsi/ipr.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN drivers/scsi/ipr.h~ipr_version_2_6_1 drivers/scsi/ipr.h
--- linux/drivers/scsi/ipr.h~ipr_version_2_6_1 2014-07-25 11:27:33.840128017
-0500
+++ linux-b
Export kexec_in_progress for use by device drivers and other modules
to optimize kexec boot.
Signed-off-by: Brian King
---
kernel/kexec.c |2 ++
1 file changed, 2 insertions(+)
diff -puN kernel/kexec.c~kexec_export_in_prog kernel/kexec.c
--- linux/kernel/kexec.c~kexec_export_in_prog 201
Switch device scanning logic in the ipr driver to use
the async scan API. This speeds up boot times, particularly
on large systems.
Signed-off-by: Brian King
---
drivers/scsi/ipr.c | 88 +
drivers/scsi/ipr.h |4 --
2 files changed, 44 i
> -Original Message-
> From: James Bottomley [mailto:jbottom...@parallels.com]
> Sent: Monday, July 28, 2014 1:03 PM
> To: KY Srinivasan
> Cc: linux-ker...@vger.kernel.org; h...@infradead.org; sits...@gmail.com;
> de...@linuxdriverproject.org; a...@canonical.com;
> martin.peter...@oracle.
On Mon, 2014-07-28 at 19:05 +, KY Srinivasan wrote:
>
> > -Original Message-
> > From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
> > Sent: Monday, July 28, 2014 12:03 PM
> > To: KY Srinivasan
> > Cc: Martin K. Petersen; Sitsofe Wheeler; Christoph Hellwig;
> > gre...@linuxf
On Mon, Jul 28, 2014 at 12:04 PM, Luis R. Rodriguez
wrote:
> On Mon, Jul 28, 2014 at 11:55 AM, Greg KH wrote:
>> So, what drivers are having problems in their init sequence, and why
>> aren't they using async firmware loading?
>
> Fixing drivers is one thing, fixing drivers *now* because *now*
>
> -Original Message-
> From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
> Sent: Monday, July 28, 2014 12:03 PM
> To: KY Srinivasan
> Cc: Martin K. Petersen; Sitsofe Wheeler; Christoph Hellwig;
> gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> de...@linuxdriverproje
On Mon, Jul 28, 2014 at 11:55 AM, Greg KH wrote:
> So, what drivers are having problems in their init sequence, and why
> aren't they using async firmware loading?
Fixing drivers is one thing, fixing drivers *now* because *now*
drivers are failing due to a regression is another thing and that's
w
> "KY" == KY Srinivasan writes:
KY,
KY> "At the time thin-provisioning was defined, the discovery
KY> information was first proposed in READ CAPACITY 16 command. And then
KY> moved into the new dedicated VPD page - B2h. You can see the
KY> information reported in this VPD page is richer than
On Mon, Jul 28, 2014 at 11:28:28AM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> Tetsuo bisected and found that commit 786235ee "kthread: make
> kthread_create() killable" modified kthread_create() to bail as
> soon as SIGKILL is received. This is causing some issues with
> some
> -Original Message-
> From: Martin K. Petersen [mailto:martin.peter...@oracle.com]
> Sent: Saturday, July 26, 2014 12:25 PM
> To: KY Srinivasan
> Cc: Martin K. Petersen; Sitsofe Wheeler; Christoph Hellwig;
> gre...@linuxfoundation.org; linux-ker...@vger.kernel.org;
> de...@linuxdriverpro
On Mon, Jul 28, 2014 at 06:30:29PM +, Yuval Mintz wrote:
> > On Mon, Jul 28, 2014 at 06:52:48PM +0200, Luis R. Rodriguez wrote:
> > > On Mon, Jul 28, 2014 at 03:46:32PM +, Yuval Mintz wrote:
> > > > Sorry for not being clear, but I didn't meant 'what guarantees that the
> > > > device
> >
From: "Luis R. Rodriguez"
We need to do this if we want to use the trigger at a later point.
This change has introduces no functional changes.
Cc: Tetsuo Handa
Cc: Joseph Salisbury
Cc: One Thousand Gnomes
Cc: Tim Gardner
Cc: Pierre Fersing
Cc: Andrew Morton
Cc: Oleg Nesterov
Cc: Benjamin
> On Mon, Jul 28, 2014 at 06:52:48PM +0200, Luis R. Rodriguez wrote:
> > On Mon, Jul 28, 2014 at 03:46:32PM +, Yuval Mintz wrote:
> > > Sorry for not being clear, but I didn't meant 'what guarantees that the
> > > device
> > > will be added to the deferred probe', but rather what guarantees th
From: "Luis R. Rodriguez"
Tetsuo bisected and found that commit 786235ee "kthread: make
kthread_create() killable" modified kthread_create() to bail as
soon as SIGKILL is received. This is causing some issues with
some drivers and at times boot. Joseph then found that failures
occur as the system
From: "Luis R. Rodriguez"
Its reported that mptsas can at times take over 30 seconds
to recognize SCSI storage devices [0], this is done on the
driver's probe path. Use the the deferred probe workqueue
to allow long init sequences to complete.
[0] https://bugs.launchpad.net/ubuntu/+source/linux/
From: "Luis R. Rodriguez"
cxgb4 probe can take up to over 1 minute when the firmware is
is written and installed on the device. Use the new delayed probe
preference so that cxgb4 gets probed on the deferred workqueue.
Without this devices that require the update on firmware will fail
on probe.
C
Ack the series.
Acked-by: Chad Dupuis
On Wed, 18 Jun 2014, Joe Lawrence wrote:
Hi Chad, Giri, et al.
Stratus has been testing the upstream qla2xxx driver against surprise
device removal and has found a few minor issues along the way. With
this patchset, results have been good. Although the
On Mon, Jul 28, 2014 at 03:46:32PM +, Yuval Mintz wrote:
> > Subject: Re: [PATCH 1/3] driver core: enable drivers to use deferred probe
> > from
> > init
> >
> > On Mon, Jul 28, 2014 at 03:12:11PM +, Yuval Mintz wrote:
> > > Perhaps this is a silly question, but what guarantees that the
>
On Mon, Jul 28, 2014 at 06:52:48PM +0200, Luis R. Rodriguez wrote:
> On Mon, Jul 28, 2014 at 03:46:32PM +, Yuval Mintz wrote:
> > > Subject: Re: [PATCH 1/3] driver core: enable drivers to use deferred
> > > probe from
> > > init
> > >
> > > On Mon, Jul 28, 2014 at 03:12:11PM +, Yuval Mint
> Subject: Re: [PATCH 1/3] driver core: enable drivers to use deferred probe
> from
> init
>
> On Mon, Jul 28, 2014 at 03:12:11PM +, Yuval Mintz wrote:
> > Perhaps this is a silly question, but what guarantees that the
> > deferred probe list will actually be triggered, e.g., in case the
> >
On Mon, Jul 28, 2014 at 03:12:11PM +, Yuval Mintz wrote:
> > +static int __driver_probe_device(struct device_driver *drv, struct
> > +device *dev) {
> > + if (drv->delay_probe && !dev->init_delayed_probe) {
> > + dev_info(dev, "Driver %s requests probe deferral on init\n",
> > +
> +static int __driver_probe_device(struct device_driver *drv, struct
> +device *dev) {
> + if (drv->delay_probe && !dev->init_delayed_probe) {
> + dev_info(dev, "Driver %s requests probe deferral on init\n",
> + drv->name);
> + dev->init_delayed_pro
On Mon, Jul 28, 2014 at 7:51 AM, Takashi Iwai wrote:
>
> This field isn't used anywhere actually in the patch...?
Yeah sorry that is not needed, I avoided that by adding the simple
bool on the struct device, forgot to nuke that. Will spin v2 unless I
hear otherwise.
Luis
--
To unsubscribe from
At Mon, 28 Jul 2014 07:34:25 -0700,
Luis R. Rodriguez wrote:
>
> From: "Luis R. Rodriguez"
>
> Tetsuo bisected and found that commit 786235ee "kthread: make
> kthread_create() killable" modified kthread_create() to bail as
> soon as SIGKILL is received. This is causing some issues with
> some dr
From: "Luis R. Rodriguez"
cxgb4 probe can take up to over 1 minute when the firmware is
is written and installed on the device. Use the new delayed probe
preference so that cxgb4 gets probed on the deferred workqueue.
Without this devices that require the update on firmware will fail
on probe.
C
From: "Luis R. Rodriguez"
Its reported that mptsas can at times take over 30 seconds
to recognize SCSI storage devices [0], this is done on the
driver's probe path. Use the the deferred probe workqueue
to allow long init sequences to complete.
[0] https://bugs.launchpad.net/ubuntu/+source/linux/
From: "Luis R. Rodriguez"
Tetsuo bisected and found that commit 786235ee "kthread: make
kthread_create() killable" modified kthread_create() to bail as
soon as SIGKILL is received. This is causing some issues with
some drivers and at times boot. Joseph then found that failures
occur as the system
Rickard Strandqvist writes:
> Replacing strncpy with strlcpy to avoid strings that lacks null terminate.
>
> Signed-off-by: Rickard Strandqvist
> ---
> block/bsg.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/bsg.c b/block/bsg.c
> index ff46add..b2688c5 1006
On 25/07/14 12:37, jgr...@suse.com wrote:
> From: Juergen Gross
>
> Add the definition of pvSCSI protocol used between the pvSCSI frontend in a
> XEN domU and the pvSCSI backend in a XEN driver domain (usually Dom0).
>
> This header was originally provided by Fujitsu for XEN based on Linux 2.6.1
the qla4xxx_alloc_fw_dump() calls dma_alloc_coherent() but does not
check its return value.
Signed-off-by: Maurizio Lombardi
---
drivers/scsi/qla4xxx/ql4_init.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/scsi/qla4xxx/ql4_init.c b/drivers/scsi/qla4xxx/ql4_init.c
index 6f12f
Acked-By: Vikas Chaudhary
On 26/07/14 2:11 pm, "Alexander Gordeev" wrote:
>On Wed, Jul 16, 2014 at 08:05:26PM +0200, Alexander Gordeev wrote:
>> As result of deprecation of MSI-X/MSI enablement functions
>> pci_enable_msix() and pci_enable_msi_block() all drivers
>> using these two interface
Acked-by: "Suma Ramars (sramars)"
On 26/07/14 1:45 pm, "Alexander Gordeev" wrote:
>On Wed, Jul 16, 2014 at 08:05:11PM +0200, Alexander Gordeev wrote:
>> As result of deprecation of MSI-X/MSI enablement functions
>> pci_enable_msix() and pci_enable_msi_block() all drivers
>> using these two int
On Sat, 2014-07-26 at 18:21 +0200, Christoph Hellwig wrote:
> Here's a formal one.
>
> James, can I get your signoff for it?
Sure:
Signed-off-by: James Bottomley
> Vladimir, can I get a reviewed-by from you (or anyone else)?
>
> ---
> >From 73b1034ab1418e2dea75ccf642bc85c728b57313 Mon Sep 17
50 matches
Mail list logo
