From: Colin Foster <colin.foster@in-advantage.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
Wolfram Sang <wsa@kernel.org>,
Terry Bowman <terry.bowman@amd.com>
Subject: Re: [PATCH v10 net-next 1/7] mfd: ocelot: add helper to get regmap from a resource
Date: Sat, 11 Jun 2022 10:11:48 -0700 [thread overview]
Message-ID: <20220611171148.GA851137@euler> (raw)
In-Reply-To: <CAHp75Vc+V3APvBO8rJ0awu65iPbEoYKn5bn4GhC0DEvC4DiKiw@mail.gmail.com>
Hi Andy,
On Sat, Jun 11, 2022 at 12:37:26PM +0200, Andy Shevchenko wrote:
> On Fri, Jun 10, 2022 at 10:23 PM Colin Foster
> <colin.foster@in-advantage.com> wrote:
> >
> > Several ocelot-related modules are designed for MMIO / regmaps. As such,
> > they often use a combination of devm_platform_get_and_ioremap_resource and
> > devm_regmap_init_mmio.
> >
> > Operating in an MFD might be different, in that it could be memory mapped,
> > or it could be SPI, I2C... In these cases a fallback to use IORESOURCE_REG
> > instead of IORESOURCE_MEM becomes necessary.
> >
> > When this happens, there's redundant logic that needs to be implemented in
> > every driver. In order to avoid this redundancy, utilize a single function
> > that, if the MFD scenario is enabled, will perform this fallback logic.
>
> v10 has the same issues I have pointed out in v9.
>
> Please, take your time and instead of bombing mailing lists with new
> versions try to look how other (most recent) drivers have been done.
Yes - I recognize that my decision to try to throw in a quick fix was
the wrong one. My apologies.
When you mention looking at more recent drivers - are you referencing
the submission process, or something else?
>
> Also pay attention to the API design.
I understand if I'm making a helper function, that helper function
shouldn't change the API if it can be avoided. Hopefully the updates I
suggested are the correct ones.
Thanks again for the feedback.
>
> --
> With Best Regards,
> Andy Shevchenko
next prev parent reply other threads:[~2022-06-11 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 20:23 [PATCH v10 net-next 0/7] add support for VSC7512 control over SPI Colin Foster
2022-06-10 20:23 ` [PATCH v10 net-next 1/7] mfd: ocelot: add helper to get regmap from a resource Colin Foster
2022-06-11 10:37 ` Andy Shevchenko
2022-06-11 17:11 ` Colin Foster [this message]
2022-06-10 20:23 ` [PATCH v10 net-next 2/7] net: mdio: mscc-miim: add ability to be used in a non-mmio configuration Colin Foster
2022-06-10 20:23 ` [PATCH v10 net-next 3/7] pinctrl: ocelot: " Colin Foster
2022-06-10 20:23 ` [PATCH v10 net-next 4/7] pinctrl: microchip-sgpio: " Colin Foster
2022-06-10 20:23 ` [PATCH v10 net-next 5/7] resource: add define macro for register address resources Colin Foster
2022-06-10 20:23 ` [PATCH v10 net-next 6/7] dt-bindings: mfd: ocelot: add bindings for VSC7512 Colin Foster
2022-06-14 20:43 ` Rob Herring
2022-06-14 21:27 ` Colin Foster
2022-06-10 20:23 ` [PATCH v10 net-next 7/7] mfd: ocelot: add support for the vsc7512 chip via spi Colin Foster
2022-06-11 6:23 ` kernel test robot
2022-06-11 18:45 ` kernel test robot
2022-06-10 20:34 ` [PATCH v10 net-next 0/7] add support for VSC7512 control over SPI Jakub Kicinski
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=20220611171148.GA851137@euler \
--to=colin.foster@in-advantage.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=terry.bowman@amd.com \
--cc=vladimir.oltean@nxp.com \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).