From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: zhuyinbo <zhuyinbo@loongson.cn>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Jianmin Lv <lvjianmin@loongson.cn>,
wanghongliang@loongson.cn, Liu Peibao <liupeibao@loongson.cn>,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v11 2/2] spi: loongson: add bus driver for the loongson spi controller
Date: Wed, 24 May 2023 11:19:09 +0100 [thread overview]
Message-ID: <39e99d0b-9a5a-446d-aed7-efee21216ec1@sirena.org.uk> (raw)
In-Reply-To: <CAHp75VdHPFDAd4iHdX5jXCM-tq0ZbFJDjvF9GCR_n7HVtd+obg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
On Wed, May 24, 2023 at 11:42:34AM +0300, Andy Shevchenko wrote:
> On Wed, May 24, 2023 at 10:52 AM zhuyinbo <zhuyinbo@loongson.cn> wrote:
> > >> +#define LOONGSON_SPI_SPCR_REG 0x00
> > >> +#define LOONGSON_SPI_SPSR_REG 0x01
> > >> +#define LOONGSON_SPI_FIFO_REG 0x02
> > >> +#define LOONGSON_SPI_SPER_REG 0x03
> > >> +#define LOONGSON_SPI_PARA_REG 0x04
> > >> +#define LOONGSON_SPI_SFCS_REG 0x05
> > >> +#define LOONGSON_SPI_TIMI_REG 0x06
> > > Where is this used outside of the main driver?
> > These definitions are only used in core.c
> Then the obvious question, why are they located in *.h?
It's absolutely fine to put them in a header file, that's a perfectly
normal way of writing code - it helps keep the driver a bit smaller by
putting big piles of defines in a separate file, that can help make
things a bit more manageable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-05-24 10:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 7:10 [PATCH v11 0/2] spi: loongson: add bus driver for the loongson spi Yinbo Zhu
2023-05-22 7:10 ` [PATCH v11 1/2] dt-bindings: spi: add " Yinbo Zhu
2023-05-24 8:56 ` Conor Dooley
2023-05-24 9:44 ` zhuyinbo
2023-05-24 10:29 ` Conor Dooley
2023-05-25 2:22 ` zhuyinbo
[not found] ` <2196dd29-93ee-00f7-65b4-ede73aa8ba77@linaro.org>
2023-06-01 9:51 ` zhuyinbo
2023-06-01 15:30 ` Krzysztof Kozlowski
2023-06-02 6:46 ` zhuyinbo
[not found] ` <69d355ff-90e1-09d2-d4ff-0d7dedc8addb@linaro.org>
2023-06-01 11:38 ` zhuyinbo
2023-05-22 7:10 ` [PATCH v11 2/2] spi: loongson: add bus driver for the loongson spi controller Yinbo Zhu
2023-05-23 12:54 ` andy.shevchenko
2023-05-24 7:52 ` zhuyinbo
2023-05-24 8:42 ` Andy Shevchenko
2023-05-24 10:19 ` Mark Brown [this message]
2023-05-25 3:34 ` zhuyinbo
2023-05-25 9:16 ` Andy Shevchenko
2023-05-25 9:28 ` zhuyinbo
2023-05-22 10:34 ` [PATCH v11 0/2] spi: loongson: add bus driver for the loongson spi Mark Brown
2023-05-22 11:44 ` zhuyinbo
2023-05-22 11:56 ` Mark Brown
2023-05-22 13:07 ` zhuyinbo
2023-05-22 13:10 ` Mark Brown
2023-05-23 2:08 ` zhuyinbo
2023-05-23 9:57 ` Mark Brown
2023-05-23 11:01 ` zhuyinbo
2023-07-31 19:57 ` Mark Brown
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=39e99d0b-9a5a-446d-aed7-efee21216ec1@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=lvjianmin@loongson.cn \
--cc=robh+dt@kernel.org \
--cc=wanghongliang@loongson.cn \
--cc=zhuyinbo@loongson.cn \
/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).