From: John Garry <john.garry@huawei.com>
To: Joe Perches <joe@perches.com>, <xuwei5@huawei.com>
Cc: <linuxarm@huawei.com>, <linux-kernel@vger.kernel.org>,
<olof@lixom.net>, <bhelgaas@google.com>, <arnd@arndb.de>
Subject: Re: [PATCH v3 3/5] bus: hisi_lpc: Clean some types
Date: Tue, 5 Nov 2019 09:50:59 +0000 [thread overview]
Message-ID: <d6c8521c-30c0-7a2c-b658-8734f7b180d3@huawei.com> (raw)
In-Reply-To: <a391e4df7c080c6a4d7eac58708967d02f0449fa.camel@perches.com>
On 04/11/2019 18:39, Joe Perches wrote:
> On Tue, 2019-11-05 at 01:22 +0800, John Garry wrote:
>> Sparse complains of these:
>> drivers/bus/hisi_lpc.c:82:38: warning: incorrect type in argument 1 (different address spaces)
>> drivers/bus/hisi_lpc.c:82:38: expected void const volatile [noderef] <asn:2>*addr
>> drivers/bus/hisi_lpc.c:82:38: got unsigned char *
>> drivers/bus/hisi_lpc.c:131:35: warning: incorrect type in argument 1 (different address spaces)
>> drivers/bus/hisi_lpc.c:131:35: expected unsigned char *mbase
>> drivers/bus/hisi_lpc.c:131:35: got void [noderef] <asn:2>*membase
>> drivers/bus/hisi_lpc.c:186:35: warning: incorrect type in argument 1 (different address spaces)
>> drivers/bus/hisi_lpc.c:186:35: expected unsigned char *mbase
>> drivers/bus/hisi_lpc.c:186:35: got void [noderef] <asn:2>*membase
>> drivers/bus/hisi_lpc.c:228:16: warning: cast to restricted __le32
>> drivers/bus/hisi_lpc.c:251:13: warning: incorrect type in assignment (different base types)
>> drivers/bus/hisi_lpc.c:251:13: expected unsigned int [unsigned] [usertype] val
>> drivers/bus/hisi_lpc.c:251:13: got restricted __le32 [usertype] <noident>
>>
>> Clean them up.
>
> OK, it might also be good to change the _in and _out functions
> to use void * and not unsigned char * for buf
Hi Joe,
In fact, using unsigned char * is the right thing to do, and really the
upper layer prob should not be passing void *. I'll look at this as a
follow up.
Cheers,
John
>
> ---
> drivers/bus/hisi_lpc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/bus/hisi_lpc.c b/drivers/bus/hisi_lpc.c
> index 20c9571..ec2bfb 100644
> --- a/drivers/bus/hisi_lpc.c
> +++ b/drivers/bus/hisi_lpc.c
> @@ -100,7 +100,7 @@ static int wait_lpc_idle(unsigned char *mbase, unsigned int waitcnt)
> */
> static int hisi_lpc_target_in(struct hisi_lpc_dev *lpcdev,
> struct lpc_cycle_para *para, unsigned long addr,
> - unsigned char *buf, unsigned long opcnt)
> + void *buf, unsigned long opcnt)
> {
> unsigned int cmd_word;
> unsigned int waitcnt;
> @@ -153,7 +153,7 @@ static int hisi_lpc_target_in(struct hisi_lpc_dev *lpcdev,
> */
> static int hisi_lpc_target_out(struct hisi_lpc_dev *lpcdev,
> struct lpc_cycle_para *para, unsigned long addr,
> - const unsigned char *buf, unsigned long opcnt)
> + const void *buf, unsigned long opcnt)
> {
> unsigned int waitcnt;
> unsigned long flags;
>
>
> .
>
next prev parent reply other threads:[~2019-11-05 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 17:22 [PATCH v3 0/5] hisi_lpc: Improve build test coverage John Garry
2019-11-04 17:22 ` [PATCH v3 1/5] lib: logic_pio: Enforce LOGIC_PIO_INDIRECT region ops are set at registration John Garry
2019-11-04 17:22 ` [PATCH v3 2/5] logic_pio: Define PIO_INDIRECT_SIZE for !CONFIG_INDIRECT_PIO John Garry
2019-11-04 17:22 ` [PATCH v3 3/5] bus: hisi_lpc: Clean some types John Garry
2019-11-04 18:39 ` Joe Perches
2019-11-05 9:50 ` John Garry [this message]
2019-11-05 15:48 ` Joe Perches
2019-11-04 17:22 ` [PATCH v3 4/5] bus: hisi_lpc: Expand build test coverage John Garry
2019-11-04 17:22 ` [PATCH v3 5/5] logic_pio: Build into a library John Garry
2019-11-09 6:33 ` [PATCH v3 0/5] hisi_lpc: Improve build test coverage Wei Xu
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=d6c8521c-30c0-7a2c-b658-8734f7b180d3@huawei.com \
--to=john.garry@huawei.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=olof@lixom.net \
--cc=xuwei5@huawei.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
all inboxes | Powered by JetHome®