All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: 王文虎 <wenhu.wang@vivo.com>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, kernel@vivo.com, robh@kernel.org,
	Christophe Leroy <christophe.leroy@c-s.fr>,
	Scott Wood <oss@buserror.net>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2,RESEND] misc: new driver sram_uapi for user level SRAM access
Date: Tue, 21 Apr 2020 11:34:27 +0200	[thread overview]
Message-ID: <20200421093427.GC725219@kroah.com> (raw)
In-Reply-To: <AB6A-gBhCLyx5bgBRPuIiqp1.3.1587460187094.Hmail.wenhu.wang@vivo.com>

On Tue, Apr 21, 2020 at 05:09:47PM +0800, 王文虎 wrote:
> Hi, Greg, Arnd,
> 
> Thank you for your comments first, and then really very very very sorry
> for driving Greg to sigh and I hope there would be chance to share Moutai
> (rather than whisky, we drink it much, a kind of Baijiu), after the virus.
> 
> Back to the comments, I'd like to do a bit of documentation or explanation first,
> which should have been done early or else there would not be so much to explain:
> 1. What I have been trying to do is to access the Freescale Cache-SRAM device form
> user level;
> 2. I implemented it using UIO, which was thought of non-proper;

I still think that using uio is the best way to do this, and never said
it was "non-proper".  All we got bogged down in was the DT
representation of stuff from what I remember.  That should be worked
through.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: 王文虎 <wenhu.wang@vivo.com>
Cc: robh@kernel.org, arnd@arndb.de,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org, Scott Wood <oss@buserror.net>,
	kernel@vivo.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2, RESEND] misc: new driver sram_uapi for user level SRAM access
Date: Tue, 21 Apr 2020 11:34:27 +0200	[thread overview]
Message-ID: <20200421093427.GC725219@kroah.com> (raw)
In-Reply-To: <AB6A-gBhCLyx5bgBRPuIiqp1.3.1587460187094.Hmail.wenhu.wang@vivo.com>

On Tue, Apr 21, 2020 at 05:09:47PM +0800, 王文虎 wrote:
> Hi, Greg, Arnd,
> 
> Thank you for your comments first, and then really very very very sorry
> for driving Greg to sigh and I hope there would be chance to share Moutai
> (rather than whisky, we drink it much, a kind of Baijiu), after the virus.
> 
> Back to the comments, I'd like to do a bit of documentation or explanation first,
> which should have been done early or else there would not be so much to explain:
> 1. What I have been trying to do is to access the Freescale Cache-SRAM device form
> user level;
> 2. I implemented it using UIO, which was thought of non-proper;

I still think that using uio is the best way to do this, and never said
it was "non-proper".  All we got bogged down in was the DT
representation of stuff from what I remember.  That should be worked
through.

thanks,

greg k-h

  reply	other threads:[~2020-04-21  9:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  3:05 [PATCH v2,RESEND] misc: new driver sram_uapi for user level SRAM access Wang Wenhu
2020-04-20  3:05 ` [PATCH v2, RESEND] " Wang Wenhu
2020-04-20 14:34 ` [PATCH v2,RESEND] " Arnd Bergmann
2020-04-20 14:34   ` [PATCH v2, RESEND] " Arnd Bergmann
2020-04-20 14:51 ` [PATCH v2,RESEND] " Greg KH
2020-04-20 14:51   ` [PATCH v2, RESEND] " Greg KH
2020-04-21  9:09   ` [PATCH v2,RESEND] " 王文虎
2020-04-21  9:09     ` 王文虎
2020-04-21  9:34     ` Greg KH [this message]
2020-04-21  9:34       ` [PATCH v2, RESEND] " Greg KH
2020-04-21 10:03       ` [PATCH v2,RESEND] " 王文虎
2020-04-21 10:03         ` 王文虎
2020-04-27  4:47       ` Scott Wood
2020-04-27  4:47         ` Scott Wood
2020-04-21  7:23 ` Scott Wood
2020-04-21  7:23   ` Scott Wood
2020-04-23  0:35   ` 王文虎
2020-04-23  0:35     ` 王文虎
2020-04-23  2:26     ` 王文虎
2020-04-23  2:26       ` 王文虎
2020-04-27 14:13 ` Rob Herring
2020-04-27 14:13   ` [PATCH v2, RESEND] " Rob Herring
2020-04-27 22:54   ` [PATCH v2,RESEND] " Scott Wood
2020-04-27 22:54     ` Scott Wood

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=20200421093427.GC725219@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=christophe.leroy@c-s.fr \
    --cc=kernel@vivo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=oss@buserror.net \
    --cc=rdunlap@infradead.org \
    --cc=robh@kernel.org \
    --cc=wenhu.wang@vivo.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.