From: andy.shevchenko@gmail.com
To: zhuyinbo <zhuyinbo@loongson.cn>
Cc: andy.shevchenko@gmail.com, Mark Brown <broonie@kernel.org>,
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 v9 2/2] spi: loongson: add bus driver for the loongson spi controller
Date: Mon, 15 May 2023 12:15:52 +0300 [thread overview]
Message-ID: <ZGH4SPsu40Mt-Z8f@surfacebook> (raw)
In-Reply-To: <16913b76-0256-492a-ec90-d367f2b52cc3@loongson.cn>
Mon, May 15, 2023 at 04:14:00PM +0800, zhuyinbo kirjoitti:
> 在 2023/5/11 下午3:18, zhuyinbo 写道:
> > 在 2023/5/8 下午11:04, andy.shevchenko@gmail.com 写道:
...
> > > > +config SPI_LOONGSON_CORE
> > > > + tristate "Loongson SPI Controller Core Driver Support"
> > >
> > > Does it need to be visible to the user?
>
> I try to set it invisible that by removing the SPI_LOONGSON_CORE Kconfig
> or removing "tristate "Loongson SPI Controller Core Driver Support" that
> will cause spi-core driver doesn't be compiled or compiled fail issue,
> so I will still set it visible to the user.
Making a symbol selectable only can be achieved by removing the description
(near to tristate directive), have you tried that?
...
> > > > + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> > > > + if (res == NULL) {
> > >
> > > Why not using devm_platform_ioremap_resource()?
> > okay, I will use it.
> > >
> > > > + dev_err(dev, "cannot get io resource memory\n");
> > > > + return -ENOENT;
> > >
> > > return dev_err_probe();
>
> It seems that there is no need to print memory log when use
> devm_platform_ioremap_resource because this function had contained
> the this memory log print thus I will return PTR_ERR(reg_base).
>
> reg_base = devm_platform_ioremap_resource(pdev, 0);
> if (IS_ERR(reg_base))
> return PTR_ERR(reg_base);
Good catch! Sure, go with this.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-05-15 9:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 7:10 [PATCH v9 0/2] spi: loongson: add bus driver for the loongson spi Yinbo Zhu
2023-04-26 7:10 ` [PATCH v9 1/2] dt-bindings: spi: add " Yinbo Zhu
2023-04-26 7:10 ` [PATCH v9 2/2] spi: loongson: add bus driver for the loongson spi controller Yinbo Zhu
2023-05-08 13:20 ` Mark Brown
2023-05-09 1:26 ` zhuyinbo
2023-05-08 15:04 ` andy.shevchenko
2023-05-09 4:39 ` Mark Brown
2023-05-10 7:03 ` Andy Shevchenko
2023-05-12 8:12 ` zhuyinbo
2023-05-12 9:40 ` Andy Shevchenko
2023-05-13 6:16 ` zhuyinbo
2023-05-11 7:18 ` zhuyinbo
2023-05-15 8:14 ` zhuyinbo
2023-05-15 9:15 ` andy.shevchenko [this message]
2023-05-15 12:01 ` zhuyinbo
2023-05-15 13:54 ` Andy Shevchenko
2023-05-16 0:50 ` zhuyinbo
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=ZGH4SPsu40Mt-Z8f@surfacebook \
--to=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--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).