openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Oskar Senft <osk@google.com>
To: Lei YU <mine260309@gmail.com>
Cc: "Andrew Jeffery" <andrew@aj.id.au>,
	"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
	張漢彬 <henbinchang@gmail.com>
Subject: Re: UART Route setting
Date: Wed, 1 Aug 2018 23:20:11 -0400	[thread overview]
Message-ID: <CABoTLcQn6s6TCV=Zf==-Mm_VSAuN8nD3caT7Z5UPoW46LthxqQ@mail.gmail.com> (raw)
In-Reply-To: <CAARXrtm1NMpzHOuKB45nWimT6m18EY7sWYWu9FoGJaDW+ZyD7A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

Interesting suggestion, that looks promising, thank you?

What's the state of that driver? I.e. where do we expect it to land?

Thanks
Oskar.

On Wed, Aug 1, 2018, 10:12 PM Lei YU <mine260309@gmail.com> wrote:

> On Thu, Aug 2, 2018 at 9:55 AM Oskar Senft <osk@google.com> wrote:
> >
> > Hi Andrew
> >
> > Thanks for the suggestion. I see that the register would map quite
> nicely to pinmux. However, the ability to change the configuration from
> user space is critical. How could that be done via pinmux?
>
> I believe Andrew Jeffery's [bmc-misc-ctr][1] driver is perfect for this
> requirement:
> 1. You can define related registers in dts and expose as sysfs attributes
> 2. User space is able to read/write the sysfs attributes to do what you
> need
>    to configure.
>
> [1]: https://patchwork.ozlabs.org/cover/942322/
>

[-- Attachment #2: Type: text/html, Size: 1416 bytes --]

  reply	other threads:[~2018-08-02  3:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01  7:11 UART Route setting Henbin Chang
     [not found] ` <CAO=notxVZowBBB4DSVYZv5MdC+H1CZ01r+DCPbZeYAJdqjAcug@mail.gmail.com>
2018-08-01 16:16   ` Oskar Senft
2018-08-02  0:30     ` Henbin Chang
2018-08-02  1:02       ` Oskar Senft
2018-08-02  1:18         ` Andrew Jeffery
2018-08-02  1:55           ` Oskar Senft
2018-08-02  2:11             ` Lei YU
2018-08-02  3:20               ` Oskar Senft [this message]
2018-08-02  3:33                 ` Andrew Jeffery
2018-08-02 15:00                   ` Avi Fishman
2018-08-02 18:11                     ` Oskar Senft
2018-08-03 14:59                   ` Patrick Venture
2018-08-03 22:03                     ` Andrew Jeffery
2018-08-06 16:47                       ` Patrick Venture
2018-08-06 21:45                         ` Kun Yi

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='CABoTLcQn6s6TCV=Zf==-Mm_VSAuN8nD3caT7Z5UPoW46LthxqQ@mail.gmail.com' \
    --to=osk@google.com \
    --cc=andrew@aj.id.au \
    --cc=henbinchang@gmail.com \
    --cc=mine260309@gmail.com \
    --cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).