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, 2 Mar 2018 21:51:12 +0000 [thread overview]
Message-ID: <1520027469.4430.43.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:
[snip]
> > > 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...
Exactly I hate to introduce another driver which will be 99,9% the same
as an existing one and then we'll need to care of it as well.
> 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
Ok so I took a look at regmap in Linux kernel and indeed that
will solve our problem: we'll have a regmap-mmio.c and regmap-arcaux.c
with appropriate implementation of accessors but I'm not really sure
it worth the trouble. Or your idea was to move all the different #ifdefs from
serial_{in|out}_shift() to the corresponding regmap implementations such that
we have something like below:
regmap-mem32-le.c
regmap-mem32-be.c
regmap-portmapped.c
etc
?
Regards,
Alexey
next prev parent reply other threads:[~2018-03-02 21:51 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
2018-02-23 20:59 ` Simon Glass
2018-03-02 21:51 ` Alexey Brodkin [this message]
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=1520027469.4430.43.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 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.