All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: "Hoan Tran" <hoan@os.amperecomputing.com>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Bartosz Golaszewski" <brgl@bgdev.pl>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Michael Büsch" <mb@bues.ch>
Subject: Re: [PATCH v2] gpio: dwapb: Fold dwapb_context into dwapb_gpio_port
Date: Mon, 24 Nov 2025 09:57:55 +0200	[thread overview]
Message-ID: <aSQQA1pCyFN2rppy@smile.fi.intel.com> (raw)
In-Reply-To: <aSQPwEJhsUxuDAmH@smile.fi.intel.com>

On Mon, Nov 24, 2025 at 09:56:53AM +0200, Andy Shevchenko wrote:
> On Mon, Nov 24, 2025 at 08:32:06AM +0800, Jisheng Zhang wrote:
> > Fold dwapb_context into struct dwapb_gpio_port to further simplify
> > the code. Sure this brings a tiny 36 bytes data overhead for
> > !PM_SLEEP. After grepping the arm/arm64/riscv dts dir, the max dwapb
> > GPIO port number is 6(the berlin2q soc family), so this means we will
> > waste 216 bytes memory in total which is trivial compared to the
> > system memory.
> > 
> > From another side, as Michael mentioned:
> > "The driver currently allocates the struct with kzalloc and stores a
> > pointer to it in case of PM=y.
> > So this probably has an overhead in the same order of magnitude
> > (pointer + malloc overhead/alignment/fragmentation) in case of PM=y
> > now."
> > 
> > So let's Fold dwapb_context into struct dwapb_gpio_port.
> 
> Fold --> fold
> 
> Given more thinking on this, I believe the approach with kmalloc() is
> preferable, but what should be done is

> - making context a global variable

I mean global _per device_, so moving it to the DWAPB device level structure.

> - considering allocation for all ports at once
> 
> If this is done, the embedded approach will look less efficient.
> So, please try that one instead.

-- 
With Best Regards,
Andy Shevchenko



      reply	other threads:[~2025-11-24  7:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24  0:32 [PATCH v2] gpio: dwapb: Fold dwapb_context into dwapb_gpio_port Jisheng Zhang
2025-11-24  7:56 ` Andy Shevchenko
2025-11-24  7:57   ` Andy Shevchenko [this message]

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=aSQQA1pCyFN2rppy@smile.fi.intel.com \
    --to=andriy.shevchenko@intel.com \
    --cc=brgl@bgdev.pl \
    --cc=hoan@os.amperecomputing.com \
    --cc=jszhang@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bues.ch \
    /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.