From: Jackie Liu <liu.yun@linux.dev>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Ralf Baechle <ralf@linux-mips.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
Jonathan Cameron <jic23@kernel.org>
Subject: Re: [PATCH] MIPS: rb532: move GPIOD definition into C-files
Date: Wed, 30 Mar 2022 09:46:07 +0800 [thread overview]
Message-ID: <71d1da40-4772-b126-7cbe-0d99024fd284@linux.dev> (raw)
In-Reply-To: <CAHp75VcAL6avNxMSVo9nWbxXOnKmXAiuGMV=uWwAx0BdHnf-+Q@mail.gmail.com>
在 2022/3/29 下午8:54, Andy Shevchenko 写道:
> On Tue, Mar 29, 2022 at 4:46 AM Jackie Liu <liu.yun@linux.dev> wrote:
>>
>> From: Jackie Liu <liuyun01@kylinos.cn>
>>
>> My kernel robot report build error from drivers/iio/adc/da9150-gpadc.c,
>>
>> We define GPIOD in rb.h, in fact he should only be used in gpio.c, but
>
> he --> it
>
>> it affects the driver da9150-gpadc.c which goes against the original
>> intention of the design, just move it to his scope.
>
>> At the same time, GPIONMIEN and IMASK6 are not used anywhere, just delete
>> them.
>
> While not being used it's good to leave (save) them since it might be
> the only means of the HW documentation. I know that Git history will
> keep that, but it is more explicit just to have them in the code.
Sure.
>
> ...
>
>> #define DEV3TC 0x01003C
>> #define BTCS 0x010040
>> #define BTCOMPARE 0x010044
>> -#define GPIOBASE 0x050000
>
> ...
>
>> +#define GPIOBASE 0x050000
>
> I think this one belongs to the header.
I think it would be better to put it in gpio.c, after all it belongs to
the GPIO module and is not used elsewhere. It doesn't feel good if we
put it in the header file.
--
BR, Jackie Liu
next prev parent reply other threads:[~2022-03-30 1:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 1:45 [PATCH] MIPS: rb532: move GPIOD definition into C-files Jackie Liu
2022-03-29 12:54 ` Andy Shevchenko
2022-03-30 1:46 ` Jackie Liu [this message]
2022-03-30 6:42 ` Thomas Bogendoerfer
2022-03-30 9:23 ` Andy Shevchenko
2022-03-30 9:32 ` Thomas Bogendoerfer
2022-03-30 9:41 ` Andy Shevchenko
2022-03-30 9:56 ` Jackie Liu
2022-03-30 10:01 ` Andy Shevchenko
2022-03-30 10:04 ` Jackie Liu
2022-03-30 10:02 ` Thomas Bogendoerfer
2022-03-30 2:01 ` [PATCH v2] " Jackie Liu
2022-03-30 2:07 ` [PATCH v3] " Jackie Liu
2022-03-30 8:52 ` Sergei Shtylyov
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=71d1da40-4772-b126-7cbe-0d99024fd284@linux.dev \
--to=liu.yun@linux.dev \
--cc=andy.shevchenko@gmail.com \
--cc=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mips@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/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.