From: Mark Langsdorf <mark.langsdorf@calxeda.com>
To: Tejun Heo <tj@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 2/2 v2] sata highbank: add bit-banged SGPIO driver support
Date: Tue, 04 Jun 2013 10:09:41 -0500 [thread overview]
Message-ID: <51AE0335.902@calxeda.com> (raw)
In-Reply-To: <20130603203727.GB29989@mtj.dyndns.org>
On 06/03/2013 03:37 PM, Tejun Heo wrote:
> Hello, Mark.
>
> In general, please try to reply to reviews addressing each point. It
> gives much better sense of what's going on to the reviewer and also
> helps the reviewee to avoid misunderstandings or missing points.
>
>> +static DEFINE_SPINLOCK(sgpio_lock);
>> +#define SCLOCK 0
>> +#define SLOAD 1
>> +#define SDATA 2
>> +#define SGPIO_PINS 3
>> +#define SGPIO_PORTS 8
>> +
>> +/* can be cast as an ahci_host_priv for compatibility with most functions */
>
> This sounds awfully scary. What's going on here? Are you actually
> overriding ahci_host_priv? If so, please don't ever do things like
> that. Do it properly. Add host_priv->platform_priv or whatever and
> chain the pointer there. If you're worried about the extra deref,
> update ahci core such that it allows specifying extra size and you can
> embed ahci_host_priv in your own priv. ie.
>
> struct ecx_host_priv {
> struct ahci_host_priv ahci_priv; /* must be the first field */
> /* your own stuff */
> };
>
> And tell ahci core sizeof(ecx_host_priv) some way, but really, just
> having a plain pointer should be enough, I think.
I think I want to do the opposite. For 90% of the AHCI EM functions,
I want ecx_host_priv to be an ahci_host_priv so that I can use those
functions without having to keep a local copy of them.
Would something like this:
struct ahci_host_priv {
/* standard AHCI existing stuff */
void *private_data;
};
I shied away from that because a private data structure having a private
data structure doesn't seem right.
>> +static inline int sgpio_bit_shift(struct ecx_host_priv *hpriv, u32 port,
>> + u32 shift)
>> +{
>> + return 1 << (3 * hpriv->port_to_sgpio[port] + shift);
>> +}
>> +
>> +static void ecx_parse_sgpio(struct ecx_host_priv *hpriv, u32 port, u32 state)
>
> Would be kinda nice to have comment explaining what the function does
> as @state == 0 turns off everything while anything else would just
> turn things on.
Okay.
>> +static ssize_t ecx_transmit_led_message(struct ata_port *ap, u32 state,
>> + ssize_t size)
>> +{
> ...
>> + if (!hpriv->em_msg_type & EM_MSG_TYPE_LED)
>> + return size;
>
> Is this really correct? You first negate and convert it to bool and
> then bit-wise and it with a mask? How is supposed to work?
Am I confused about the order of operations? It's meant to be "continue
if hpriv->em_msg_type doesn't have EM_MSG_TYPE_LED set".
>> - ahci_save_initial_config(dev, hpriv, 0, 0);
>> + ahci_save_initial_config(dev, (struct ahci_host_priv *) hpriv, 0, 0);
>
> Ugh....... how is this supposed to work? What if ahci_host_priv grows
> larger than ecx one in the future? :(
For functions like ahci_save_initial_config, I just want to use the
already defined ahci_ functions with my extra data along for the ride.
What's the best way to do that?
--Mark Langsdorf
Calxeda, Inc.
next prev parent reply other threads:[~2013-06-04 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 20:17 [PATCH 1/2] ahci: make ahci_transmit_led_message into a function pointer Mark Langsdorf
2013-05-30 20:17 ` [PATCH 2/2] sata highbank: add bit-banged SGPIO driver support Mark Langsdorf
2013-05-31 1:17 ` Tejun Heo
[not found] ` <1369945051-2582-2-git-send-email-mark.langsdorf-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>
2013-06-03 13:35 ` [PATCH 2/2 v2] " Mark Langsdorf
2013-06-03 20:37 ` Tejun Heo
2013-06-04 15:09 ` Mark Langsdorf [this message]
2013-06-04 20:32 ` Tejun Heo
[not found] ` <20130604203251.GF14916-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2013-06-05 20:19 ` Mark Langsdorf
2013-06-05 22:31 ` [PATCH 2/2] " Mark Langsdorf
2013-06-05 23:15 ` Tejun Heo
[not found] ` <20130605231517.GP10693-9pTldWuhBndy/B6EtB590w@public.gmane.org>
2013-06-06 12:14 ` Mark Langsdorf
2013-06-06 12:52 ` [PATCH 2/2 v4] " Mark Langsdorf
2013-06-06 21:06 ` Tejun Heo
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=51AE0335.902@calxeda.com \
--to=mark.langsdorf@calxeda.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=tj@kernel.org \
/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).