All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parker Newman <parker@finest.io>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Parker Newman <pnewman@connecttech.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH v2 00/13] serial: 8250_exar: Clean up the driver
Date: Fri, 6 Sep 2024 10:33:54 -0400	[thread overview]
Message-ID: <20240906103354.0bf5f3b7@SWDEV2.connecttech.local> (raw)
In-Reply-To: <ZtsQrFgH86AkKgPp@smile.fi.intel.com>

On Fri, 6 Sep 2024 17:24:44 +0300
Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:

> On Fri, Sep 06, 2024 at 09:51:41AM -0400, Parker Newman wrote:
> > On Fri, 6 Sep 2024 15:46:51 +0300
> > Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > > On Fri, May 03, 2024 at 02:33:03PM -0400, Parker Newman wrote:
> > > > On Fri,  3 May 2024 20:15:52 +0300
> > > > Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote:
> > > >
> > > > > After a rework for CONNTECH was done, the driver may need a bit of
> > > > > love in order to become less verbose (in terms of indentation and
> > > > > code duplication) and hence easier to read.
> > > > >
> > > > > This clean up series fixes a couple of (not so critical) issues and
> > > > > cleans up the recently added code. No functional change indented by
> > > > > the cleaning up part.
> > > > >
> > > > > Parker, please test this and give your formal Tested-by tag
> > > > > (you may do it by replying to this message if all patches are
> > > > >  successfully tested; more details about tags are available in
> > > > >  the Submitting Patches documentation).
> > > >
> > > > I was able to test the Connect Tech related code and everything is
> > > > work as expected. I can't test the non-CTI related changes but they
> > > > are pretty minor.
> > > >
> > > > Tested-by: Parker Newman <pnewman@connecttech.com>
> > >
> > > Sorry for blast from the past, but I have some instersting information
> > > for you. We now have spi-gpio and 93c46 eeprom drivers available to be
> > > used from others via software nodes, can you consider updating your code
> > > to replace custom bitbanging along with r/w ops by the instantiating the
> > > respective drivers?
> >
> > Hi Andy,
> > The Exar UARTs don't actually use MPIO/GPIO for the EEPROM.
> > They have a dedicated "EEPROM interface" which is accessed by the
> > REGB (0x8E) register. It is a very simple bit-bang interface though,
> > one bit per signal.
> >
> > I guess in theory I could either add  GPIO wrapper to toggle these bits
> > and use the spi-gpio driver but I am not sure if that really improves things?
> > Maybe using the spi-bitbang driver directly is more appropriate?
> > What do you think?
>
> Yes, spi-bitbang seems better in this case.
>

I will try to make some time to implement this... Or if someone else from the
community wants to take this on in the mean time I am certainly happy to test
and help out!
Parker

  reply	other threads:[~2024-09-06 14:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 17:15 [PATCH v2 00/13] serial: 8250_exar: Clean up the driver Andy Shevchenko
2024-05-03 17:15 ` [PATCH v2 01/13] serial: 8250_exar: Don't return positive values as error codes Andy Shevchenko
2024-05-03 17:15 ` [PATCH v2 02/13] serial: 8250_exar: Describe all parameters in kernel doc Andy Shevchenko
2024-05-03 17:15 ` [PATCH v2 03/13] serial: 8250_exar: Kill CTI_PCI_DEVICE() Andy Shevchenko
2024-05-03 17:15 ` [PATCH v2 04/13] serial: 8250_exar: Use PCI_SUBVENDOR_ID_IBM for subvendor ID Andy Shevchenko
2024-05-03 17:15 ` [PATCH v2 05/13] serial: 8250_exar: Trivia typo fixes Andy Shevchenko
2024-05-03 17:15 ` [PATCH v2 06/13] serial: 8250_exar: Extract cti_board_init_osc_freq() helper Andy Shevchenko
2024-05-03 17:15 ` [PATCH v2 07/13] serial: 8250_exar: Kill unneeded ->board_init() Andy Shevchenko
2024-05-03 17:16 ` [PATCH v2 08/13] serial: 8250_exar: Decrease indentation level Andy Shevchenko
2024-05-03 17:16 ` [PATCH v2 09/13] serial: 8250_exar: Return directly from switch-cases Andy Shevchenko
2024-05-03 17:16 ` [PATCH v2 10/13] serial: 8250_exar: Switch to use dev_err_probe() Andy Shevchenko
2024-05-03 17:16 ` [PATCH v2 11/13] serial: 8250_exar: Use BIT() in exar_ee_read() Andy Shevchenko
2024-05-03 17:16 ` [PATCH v2 12/13] serial: 8250_exar: Make type of bit the same in exar_ee_*_bit() Andy Shevchenko
2024-05-03 17:16 ` [PATCH v2 13/13] serial: 8250_exar: Keep the includes sorted Andy Shevchenko
2024-05-03 18:33 ` [PATCH v2 00/13] serial: 8250_exar: Clean up the driver Parker Newman
2024-09-06 12:46   ` Andy Shevchenko
2024-09-06 13:51     ` Parker Newman
2024-09-06 14:24       ` Andy Shevchenko
2024-09-06 14:33         ` Parker Newman [this message]
2024-09-06 14:42           ` Andy Shevchenko
2024-09-06 18:38             ` Parker Newman
2024-09-09 10:06               ` Andy Shevchenko
2024-09-11 17:38                 ` Parker Newman
2024-09-11 20:51                   ` Andy Shevchenko
2024-09-12 12:41                     ` Parker Newman
2024-09-13  9:37                       ` Andy Shevchenko

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=20240906103354.0bf5f3b7@SWDEV2.connecttech.local \
    --to=parker@finest.io \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=pnewman@connecttech.com \
    /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.