From: Tejun Heo <tj@kernel.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Arnd Bergmann <arnd@arndb.de>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Kevin Hilman <khilman@baylibre.com>, Sekhar Nori <nsekhar@ti.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Russell King <rmk+kernel@armlinux.org.uk>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] pata_pcmcia: add EBSA110's PCMCIA slot support
Date: Thu, 16 Mar 2017 17:26:54 -0400 [thread overview]
Message-ID: <20170316212654.GD1480@htj.duckdns.org> (raw)
In-Reply-To: <3458240.9SL7iGif3L@amdc3058>
Hello,
On Tue, Mar 14, 2017 at 06:50:43PM +0100, Bartlomiej Zolnierkiewicz wrote:
> +static struct ata_port_operations pcmcia_ebsa110_port_ops = {
> + .inherits = &ata_sff_port_ops,
> + .sff_dev_select = pmcmia_ebsa110_dev_select,
^^^^^^
> + .sff_set_devctl = pcmcia_ebsa110_set_devctl,
> + .sff_check_status = pcmcia_ebsa110_check_status,
> + .sff_check_altstatus = pcmcia_ebsa110_check_altstatus,
> + .sff_tf_load = pcmcia_ebsa110_tf_load,
> + .sff_tf_read = pcmcia_ebsa110_tf_read,
> + .sff_exec_command = pcmcia_ebsa110_exec_command,
> + .sff_data_xfer = ata_sff_data_xfer_noirq,
> + .softreset = pata_pcmcia_ebsa110_softreset,
> + .cable_detect = ata_cable_40wire,
> + .set_mode = pcmcia_set_mode,
> +};
Heh, that's a fat driver for a sff device. I suppose this is mostly
copied from the matching ide driver but it'd be nice to explain why it
needs duplicate most standard functions. Is it because PCMCIA
assigned address doesn't fall under the usual read/io boundary on the
arch?
Thanks.
--
tejun
next prev parent reply other threads:[~2017-03-16 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170314175046epcas1p43f98daad14a2bac7f314e7d39e120232@epcas1p4.samsung.com>
2017-03-14 17:50 ` [PATCH] pata_pcmcia: add EBSA110's PCMCIA slot support Bartlomiej Zolnierkiewicz
2017-03-16 21:26 ` Tejun Heo [this message]
2017-03-17 11:59 ` Bartlomiej Zolnierkiewicz
2017-03-17 13:39 ` Tejun Heo
2017-03-17 14:08 ` Bartlomiej Zolnierkiewicz
2017-03-17 14:13 ` Tejun Heo
2017-03-17 15:51 ` Bartlomiej Zolnierkiewicz
2017-03-20 13:00 ` Bartlomiej Zolnierkiewicz
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=20170316212654.GD1480@htj.duckdns.org \
--to=tj@kernel.org \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=dbaryshkov@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=olof@lixom.net \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sergei.shtylyov@cogentembedded.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