From: <Mario.Limonciello@dell.com>
To: <pali.rohar@gmail.com>, <andy.shevchenko@gmail.com>
Cc: <dvhart@infradead.org>, <linux-kernel@vger.kernel.org>,
<platform-driver-x86@vger.kernel.org>
Subject: RE: [PATCH] platform/x86: dell-laptop: Allocate buffer on heap rather than globally
Date: Wed, 31 Jan 2018 16:46:58 +0000 [thread overview]
Message-ID: <bb29662337484ad8bd2350e6b68133d3@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <20180131090758.v6eyj35gymlfyzhk@pali>
> -----Original Message-----
> From: Pali Rohár [mailto:pali.rohar@gmail.com]
> Sent: Wednesday, January 31, 2018 3:08 AM
> To: Andy Shevchenko <andy.shevchenko@gmail.com>
> Cc: Limonciello, Mario <Mario_Limonciello@Dell.com>; Darren Hart
> <dvhart@infradead.org>; LKML <linux-kernel@vger.kernel.org>; Platform Driver
> <platform-driver-x86@vger.kernel.org>
> Subject: Re: [PATCH] platform/x86: dell-laptop: Allocate buffer on heap rather than
> globally
>
> On Tuesday 30 January 2018 20:14:26 Andy Shevchenko wrote:
> > >> -static void dell_set_arguments(u32 arg0, u32 arg1, u32 arg2, u32 arg3)
> > >> +static void dell_set_arguments(struct calling_interface_buffer *buffer,
> > >> + u32 arg0, u32 arg1, u32 arg2, u32 arg3)
> > >
> > > Hm... this function has too many parameters :-(
> > >
> > > What about following API?
> > >
> > > static struct calling_interface_buffer dell_set_arguments(u32 arg0, u32 arg1,
> u32 arg2, u32 arg3);
> > >
> > > It would return filled structure (not a pointer !)
> >
> > I do not think it's a good idea. Either we allocate request on a heap
> > and return a pointer, or we fill the struct with some data on spot.
> >
> > To naming:
> >
> > for allocation: ..._alloc_request()
> > for filling: _fill_request() / _prepare_request()
> >
> > or alike.
> >
> > _set_arguments() not good enough to me.
>
> Ok. Then we need to stick with 5 arguments... What about name
> dell_fill_request()? E.g.
>
> struct calling_interface_buffer buffer;
> dell_fill_request(&buffer, 0x2, 0, 0, 0);
> ret = dell_send_request(&buffer, CLASS_INFO, SELECT_RFKILL);
>
The other alternative is to just define the input of the structure immediately with
an initializer, no multi argument filler function. Like this:
diff --git a/drivers/platform/x86/dell-laptop.c b/drivers/platform/x86/dell-laptop.c
index ab58373..e7a971b 100644
--- a/drivers/platform/x86/dell-laptop.c
+++ b/drivers/platform/x86/dell-laptop.c
@@ -469,13 +469,15 @@ static int dell_rfkill_set(void *data, bool blocked)
int disable = blocked ? 1 : 0;
unsigned long radio = (unsigned long)data;
int hwswitch_bit = (unsigned long)data - 1;
- struct calling_interface_buffer buffer;
+ struct calling_interface_buffer buffer = {CLASS_INFO,
+ SELECT_RFKILL,
+ {0, 0, 0, 0},
+ {0, 0, 0, 0}};
int hwswitch;
int status;
int ret;
- dell_set_arguments(&buffer, 0, 0, 0, 0);
- ret = dell_send_request(&buffer, CLASS_INFO, SELECT_RFKILL);
+ ret = dell_send_request(&buffer);
if (ret)
return ret;
status = buffer.output[1];
next prev parent reply other threads:[~2018-01-31 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 16:59 Mario Limonciello
2018-01-30 17:17 ` Pali Rohár
2018-01-30 18:14 ` Andy Shevchenko
2018-01-31 9:07 ` Pali Rohár
2018-01-31 16:46 ` Mario.Limonciello [this message]
2018-01-31 16:53 ` Andy Shevchenko
2018-01-31 17:06 ` Pali Rohár
2018-01-31 17:15 ` Andy Shevchenko
2018-01-30 17:20 ` Pali Rohár
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=bb29662337484ad8bd2350e6b68133d3@ausx13mpc120.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=andy.shevchenko@gmail.com \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®