From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] ns16550: Add support for AUX regs usage on some ARC SoCs
Date: Fri, 23 Feb 2018 18:08:46 +0000 [thread overview]
Message-ID: <1519409325.4047.6.camel@synopsys.com> (raw)
In-Reply-To: <CAPnjgZ3nKhkZpGj9T0xM2Xdgb7t-pNLo8-ZM4EGKEkSnO=DuwQ@mail.gmail.com>
Hi Simon,
On Thu, 2018-02-22 at 10:29 -0700, Simon Glass wrote:
> Hi Alexey,
>
> On 22 February 2018 at 09:23, Alexey Brodkin
> <Alexey.Brodkin@synopsys.com> wrote:
> > Hi Simon,
> >
> > On Thu, 2018-02-22 at 09:17 -0700, Simon Glass wrote:
> > > Hi,
> > >
> > > On 21 February 2018 at 05:26, Alexey Brodkin
> > > <Alexey.Brodkin@synopsys.com> wrote:
[snip]
> > > > ---
> > > > drivers/serial/ns16550.c | 11 +++++++++--
> > > > 1 file changed, 9 insertions(+), 2 deletions(-)
> > >
> > > I think a separate driver might be better, unless we want to make the
> > > read/write interface go through regmap or similar?
> >
> > But in case of ARC's AUX regs portmap won't help because those AUX regs are
> > couldn't be mapped - that a completely different address space and we may
> > only access them via dedicated instructions (LR vs LD and SR vs ST).
>
> Well...
>
> 1. With a separate driver, you can do whatever you want :-) I know it
> introduces code duplication though...
>
> 2. With regmap you can add your own regmap driver, and again do
> whatever you want. I can help with that if it sounds attractive
That sounds definitely interesting!
Are there any pointers on how that usually done?
-Alexey
next prev parent reply other threads:[~2018-02-23 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 12:26 [U-Boot] [RFC] ns16550: Add support for AUX regs usage on some ARC SoCs Alexey Brodkin
2018-02-22 15:43 ` Tom Rini
2018-02-22 16:07 ` Alexey Brodkin
2018-02-22 16:20 ` Tom Rini
2018-02-22 16:17 ` Simon Glass
2018-02-22 16:23 ` Alexey Brodkin
2018-02-22 17:29 ` Simon Glass
2018-02-23 18:08 ` Alexey Brodkin [this message]
2018-02-23 20:59 ` Simon Glass
2018-03-02 21:51 ` Alexey Brodkin
2018-03-08 20:27 ` Simon Glass
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=1519409325.4047.6.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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