mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] mfd: intel-lpss: Provide an SSP type to the SPI driver
Date: Wed, 13 Jul 2022 13:57:26 +0300	[thread overview]
Message-ID: <Ys6lFqm4/T/Kb3et@smile.fi.intel.com> (raw)
In-Reply-To: <Ys593spfcFtoILhS@google.com>

On Wed, Jul 13, 2022 at 09:10:06AM +0100, Lee Jones wrote:
> On Sun, 03 Jul 2022, Andy Shevchenko wrote:

> > +static const struct property_entry spt_spi_properties[] = {
> > +	PROPERTY_ENTRY_U32("intel,spi-pxa2xx-type", LPSS_SPT_SSP),
> > +	{ }
> > +};
> > +
> > +static const struct software_node spt_spi_node = {
> > +	.properties = spt_spi_properties,
> > +};
> > +
> >  static const struct intel_lpss_platform_info spt_info = {
> >  	.clk_rate = 120000000,
> > +	.swnode = &spt_spi_node,
> >  };
> 
> IMHO, this is a rubbish interface.
> 
> The amount of 10-line changes required to store a 32-bit value is
> depressing.  Is there not a reduced interface for storing small pieces
> of data that doesn't require arrays of structs?

The part of it that makes it longer because of differentiating the hardware,
but see the difference here:

In this change:
	95 insertions(+), 46 deletions(-)

In the follow up SPI driver cleaning (not yet submitted):
	14 insertions(+), 121 deletions(-)


-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-07-13 10:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 21:19 Andy Shevchenko
2022-07-13  8:10 ` Lee Jones
2022-07-13 10:57   ` Andy Shevchenko [this message]
2022-07-13 13:12     ` Lee Jones
2022-07-13 16:08       ` Andy Shevchenko
2022-08-08 13:59 ` Lee Jones

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=Ys6lFqm4/T/Kb3et@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®