U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/7] dm: serial: Add ->getconfig() callback
Date: Wed, 5 Dec 2018 16:01:01 +0200	[thread overview]
Message-ID: <20181205140101.GZ10650@smile.fi.intel.com> (raw)
In-Reply-To: <CAPnjgZ26S_YKAB+EsKdDS=+y0xrUSdDMTbZiu3hMwkmo6NxJ4Q@mail.gmail.com>

On Wed, Dec 05, 2018 at 05:55:37AM -0700, Simon Glass wrote:
> On Tue, 27 Nov 2018 at 09:03, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > On Mon, Nov 26, 2018 at 06:02:28PM -0700, Simon Glass wrote:

> > The rest of similar functions are operate on top of current console device and
> > do not have such parameter, while being DM-based functions.
> >
> > I would gladly rebase my series on top any work which is done regard above request.
> > For now, I don't see such possibility.
> 
> My point is that you are adding a new function which does not use
> driver model properly. The serial_getconfig() function should have a
> device parameter, and it should not support non-DM, since it is a new
> feature.

I understand that, OTOH I can repeat myself that this would be very
inconsistent with preexisting set of the functions. In my opinion that must be
fixed altogether either before or after, but at once.

> I'm going to pick this up, absent any other issues, and see if I can
> do a patch for it afterwards.
> 
> Reviewed-by: Simon Glass <sjg@chromium.org>

Thank you for review, and sorry for being persuader, I have several big tasks
to be accomplished before my vacation starts.

-- 
With Best Regards,
Andy Shevchenko

  reply	other threads:[~2018-12-05 14:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 21:52 [U-Boot] [PATCH v3 0/7] ACPI: Generate SPCR table Andy Shevchenko
2018-11-20 21:52 ` [U-Boot] [PATCH v3 1/7] dm: serial: Add ->getconfig() callback Andy Shevchenko
2018-11-27  1:02   ` Simon Glass
2018-11-27 16:02     ` Andy Shevchenko
2018-12-03 16:18       ` Andy Shevchenko
2018-12-05 12:55       ` Simon Glass
2018-12-05 14:01         ` Andy Shevchenko [this message]
2018-12-05 15:58           ` Simon Glass
2018-12-05 23:11             ` sjg at google.com
2018-11-20 21:52 ` [U-Boot] [PATCH v3 2/7] dm: serial: Introduce ->getinfo() callback Andy Shevchenko
2018-12-05 12:55   ` Simon Glass
2018-12-05 23:11     ` sjg at google.com
2018-11-20 21:52 ` [U-Boot] [PATCH v3 3/7] serial: ns16550: Group reg_* members of ns16550_platdata Andy Shevchenko
2018-12-05 12:55   ` Simon Glass
2018-12-05 23:11     ` sjg at google.com
2018-11-20 21:52 ` [U-Boot] [PATCH v3 4/7] serial: ns16550: Read reg-io-width from device tree Andy Shevchenko
2018-12-05 12:55   ` Simon Glass
2018-12-05 23:11     ` sjg at google.com
2018-11-20 21:52 ` [U-Boot] [PATCH v3 5/7] serial: ns16550: Provide ->getinfo() implementation Andy Shevchenko
2018-12-05 12:55   ` Simon Glass
2018-12-05 23:11     ` sjg at google.com
2018-11-20 21:52 ` [U-Boot] [PATCH v3 6/7] x86: acpi: Add SPCR table description Andy Shevchenko
2018-12-05 23:11   ` sjg at google.com
2018-11-20 21:52 ` [U-Boot] [PATCH v3 7/7] x86: acpi: Generate SPCR table Andy Shevchenko
2018-12-05 12:55   ` Simon Glass
2018-12-05 23:11     ` sjg at google.com

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=20181205140101.GZ10650@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=u-boot@lists.denx.de \
    /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