From: Marek Vasut <marek.vasut@mailbox.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH 2/2] gpio: rcar: Add R-Car X5H (R8A78000) support
Date: Thu, 9 Jul 2026 00:31:40 +0200 [thread overview]
Message-ID: <9ecabfec-d428-4c64-b398-4e80baaf3752@mailbox.org> (raw)
In-Reply-To: <CAMuHMdXQQWmn612R3y6qSXOZ7YMwZcfrBTrQZ9GzGekhFhtWSw@mail.gmail.com>
On 7/7/26 8:52 AM, Geert Uytterhoeven wrote:
Hello Geert,
>> On 7/6/26 11:19 AM, Bartosz Golaszewski wrote:
>>>> +static inline int gpio_rcar_remap_offset(struct gpio_rcar_priv *p, int *offs)
>>>> +{
>>
>> I am hoping to get some input on this remap function.
>
> I haven't looked at your patch in detail yet, but the remap function
> was the first thing that struck my eyes. This might impact performance
> of bit-banging and of the sloppy logic analyzer.
Regarding the performance impact -- yes, this will impact performance.
Both the remap function and register table look up will, but at least
the remap function is small and (subset of it) ends up inlined, the
indirect look up table is bigger and unlikely to be inlined. That is why
I opted for this over a table look up.
> Have you looked at the code generated by the compiler?
I did, but there is a lot of inlining going on.
> Perhaps it would be better to use a table, like sci_port_params.regs[]
> in the sh-sci driver, and riic_of_data.regs in the riic driver?
Please see above.
[...]
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2026-07-08 22:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-04 15:13 [PATCH 1/2] dt-bindings: gpio: renesas,rcar-gpio: Document R-Car X5H (R8A78000) support Marek Vasut
2026-07-04 15:13 ` [PATCH 2/2] gpio: rcar: Add " Marek Vasut
2026-07-06 9:19 ` Bartosz Golaszewski
2026-07-06 13:06 ` Marek Vasut
2026-07-07 6:52 ` Geert Uytterhoeven
2026-07-08 22:31 ` Marek Vasut [this message]
2026-07-07 13:48 ` Bartosz Golaszewski
2026-07-07 13:53 ` Geert Uytterhoeven
2026-07-05 14:40 ` [PATCH 1/2] dt-bindings: gpio: renesas,rcar-gpio: Document " Conor Dooley
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=9ecabfec-d428-4c64-b398-4e80baaf3752@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh@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