From: Mark Langsdorf <mark.langsdorf@calxeda.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"probinson@gmail.com" <probinson@gmail.com>,
"jonathon@jonmasters.org" <jonathon@jonmasters.org>,
"dmarlin@redhat.com" <dmarlin@redhat.com>,
Rob Herring <rob.herring@calxeda.com>
Subject: Re: [PATCH 2/2] ahci_platform: add custom hard reset for Calxeda ahci ctrlr
Date: Fri, 17 Aug 2012 17:25:31 -0500 [thread overview]
Message-ID: <502EC4DB.6020707@calxeda.com> (raw)
In-Reply-To: <502E7E7E.80101@pobox.com>
On 08/17/2012 12:25 PM, Jeff Garzik wrote:
> On 08/17/2012 10:51 AM, Mark Langsdorf wrote:
>> Calxeda highbank SATA phy has intermittent problems bringing up a link
>> with Gen3 drives. Retrying the phy hard reset can work-around this issue,
>> but each reset also disables spread spectrum support. The reset function
>> also needs to reprogram the phy to enable spread spectrum support.
>>
>> Signed-off-by: Mark Langsdorf <mark.langsdorf@calxeda.com>
>> Signed-off-by: Rob Herring <rob.herring@calxeda.com>
>> ---
>> .../devicetree/bindings/arm/calxeda/combophy.txt | 17 ++
>> .../devicetree/bindings/ata/ahci-platform.txt | 8 +
>> arch/arm/boot/dts/highbank.dts | 17 ++
>> drivers/ata/Makefile | 1 +
>> drivers/ata/ahci.h | 17 ++
>> drivers/ata/ahci_platform.c | 88 ++++++++-
>> drivers/ata/sata_highbank.c | 199 ++++++++++++++++++++
>> 7 files changed, 339 insertions(+), 8 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/arm/calxeda/combophy.txt
>> create mode 100644 drivers/ata/sata_highbank.c
>
> And the biggest issue...
>
> 4) if you need all this code for workarounds, just create your own
> libahci driver at that point. make sata_highbank a real driver.
The frustrating bit is that we're nominally an AHCI compatible
controller except for the reset function and some kind of initialization
for the combophy iomem regions. The ata_port_operations already lets me
override just the reset function, and the ahci_probe() function has a
hook for the iomem initialization.
Is there any way I can inherit most of the existing ahci_platform
functions for suspend, resume, etc.? Because otherwise I'm just going to
duplicate the code and that feels unsatisfactory and seems unlikely to
get accepted anyway.
Would it be permissible to remove the statics from ahci_suspend,
ahci_resume, and ahci_remove so I could use them in my libahci driver?
--Mark Langsdorf
Calxeda, Inc.
next prev parent reply other threads:[~2012-08-17 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 14:51 [PATCH 0/2] ahci: custom reset for Calxeda ahci Mark Langsdorf
2012-08-17 14:51 ` [PATCH 1/2] ahci: un-staticize ahci_dev_classify Mark Langsdorf
2012-08-17 17:27 ` Jeff Garzik
2012-08-17 14:51 ` [PATCH 2/2] ahci_platform: add custom hard reset for Calxeda ahci ctrlr Mark Langsdorf
2012-08-17 15:33 ` Rob Herring
2012-08-17 17:25 ` Jeff Garzik
2012-08-17 22:25 ` Mark Langsdorf [this message]
2012-09-06 21:03 ` [PATCH v2] ata: add platform driver for Calxeda AHCI controller Mark Langsdorf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=502EC4DB.6020707@calxeda.com \
--to=mark.langsdorf@calxeda.com \
--cc=dmarlin@redhat.com \
--cc=jgarzik@pobox.com \
--cc=jonathon@jonmasters.org \
--cc=linux-ide@vger.kernel.org \
--cc=probinson@gmail.com \
--cc=rob.herring@calxeda.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).