From: Jahnavi Meher <jahnavi.meher@redpinesignals.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3.13.1 2/9] rsi: OS dependent functions
Date: Fri, 31 Jan 2014 16:25:29 +0530 [thread overview]
Message-ID: <52EB8121.7040602@redpinesignals.com> (raw)
In-Reply-To: <1391099071.4323.21.camel@jlt4.sipsolutions.net>
Will change to build both SDIO and USB modules
simultaneously, as suggested by Dan.
Regards,
Jahnavi
> On Thu, 2014-01-30 at 21:24 +0530, Jahnavi wrote:
>
>> +rsi_common-y := rsi_core.o rsi_osd_ops.o
>> +ifeq ($(CONFIG_RSI_USB), y)
>> + rsi_common-y += rsi_usb.o
>> + ccflags-y =-DUSE_USB_INTF
>> +else
>> + rsi_common-y += rsi_sdio.o
>> + ccflags-y =-DUSE_SDIO_INTF
>> +endif
> That can't be right - in the Kconfig you declared that it's valid to
> select both SDIO and USB at the same time. You can also use the syntax
> you used below:
>
>> +obj-$(CONFIG_RSI_91x) := rsi_common.o
> for ccflags to clean this up. But you should get rid of the
> -DUSE_XYZ_INTF anyway and use CONFIG_RSI_USB in the code.
>
>> +static int rsi_proc_version_read(struct seq_file *seq, void *data)
> /proc? really? definitely staging material from here on ...
>
>> +/**
>> + * This function is used to put the current execution in a queue
>> + * and reschedules itself for execution on "timeout" or when a
>> + * wakeup is generated.
>> + *
>> + * @param event Pointer to the event structure.
>> + * @param timeout Timeout value in msecs.
>> + * @return status: 0 on success, -1 on failure.
>> + */
>> +int rsi_wait_event(struct rsi_event *event, unsigned int timeout)
>> +{
>> + int status = 0;
>> +
>> + if (!timeout)
>> + status = wait_event_interruptible(event->event_queue,
>> + (atomic_read(&event->event_condition) == 0));
>> + else
>> + status = wait_event_interruptible_timeout(event->event_queue,
>> + (atomic_read(&event->event_condition) == 0),
>> + timeout);
>> + return status;
>> +}
> That's probably better inlined.
>
> Along with the rest of the event and thread functionality - doesn't
> really help readability to obscure things behind layers of "OS
> abstractions"...
>
>> +void rsi_print(int zone, unsigned char *vdata, int len)
>> +{
>> + unsigned short ii;
>> +
>> + if (!(zone & rsi_zone_enabled))
>> + return;
>> +
>> + if (!vdata)
>> + return;
>> +
>> + for (ii = 0; ii < len; ii++) {
>> + if (!(ii % 16))
>> + pr_info("\n");
>> + pr_info("%02x ", (vdata[ii]));
>> + }
>> + pr_info("\n");
>> +}
> Yeah, umm, see above.
>
>> + unsigned int bbp_lmac_clk_reg_val:16;
> 16 bit bitfields? Is there anything wrong with u16 (aka unsigned short)
> on your compiler version?
>
> johannes
>
>
>
prev parent reply other threads:[~2014-01-31 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 15:54 [PATCH 3.13.1 2/9] rsi: OS dependent functions Jahnavi
2014-01-30 16:24 ` Johannes Berg
2014-01-31 10:55 ` Jahnavi Meher [this message]
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=52EB8121.7040602@redpinesignals.com \
--to=jahnavi.meher@redpinesignals.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.