From: Christoph Hellwig <hch@infradead.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Brandt <Chris.Brandt@renesas.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/5] cramfs: direct memory access support
Date: Tue, 3 Oct 2017 07:59:21 -0700 [thread overview]
Message-ID: <20171003145921.GA9954@infradead.org> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1710011659530.5407@knanqh.ubzr>
On Sun, Oct 01, 2017 at 06:27:11PM -0400, Nicolas Pitre wrote:
> If you prefer, the physical address could be specified with a Kconfig
> symbol just like the kernel link address. Personally I think it is best
> to keep it along with the other root mount args. But going all the way
> with a dynamic driver binding interface and a dummy intermediate name is
> like using a sledge hammer to kill an ant: it will work of course, but
> given the context it is prone to errors due to the added manipulations
> mentioned previously ... and a tad overkill.
As soon as a kernel enables CRAMFS_PHYSMEM this mount option is
available, so you don't just need to think of your use case.
The normal way for doings this would be to specify it in the device
tree.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Nicolas Pitre <nicolas.pitre@linaro.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-embedded@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Brandt <Chris.Brandt@renesas.com>,
linux-mtd@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/5] cramfs: direct memory access support
Date: Tue, 3 Oct 2017 07:59:21 -0700 [thread overview]
Message-ID: <20171003145921.GA9954@infradead.org> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1710011659530.5407@knanqh.ubzr>
On Sun, Oct 01, 2017 at 06:27:11PM -0400, Nicolas Pitre wrote:
> If you prefer, the physical address could be specified with a Kconfig
> symbol just like the kernel link address. Personally I think it is best
> to keep it along with the other root mount args. But going all the way
> with a dynamic driver binding interface and a dummy intermediate name is
> like using a sledge hammer to kill an ant: it will work of course, but
> given the context it is prone to errors due to the added manipulations
> mentioned previously ... and a tad overkill.
As soon as a kernel enables CRAMFS_PHYSMEM this mount option is
available, so you don't just need to think of your use case.
The normal way for doings this would be to specify it in the device
tree.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-10-03 14:59 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 23:32 [PATCH v4 0/5] cramfs refresh for embedded usage Nicolas Pitre
2017-09-27 23:32 ` Nicolas Pitre
2017-09-27 23:32 ` [PATCH v4 1/5] cramfs: direct memory access support Nicolas Pitre
2017-09-27 23:32 ` Nicolas Pitre
2017-10-01 8:29 ` Christoph Hellwig
2017-10-01 8:29 ` Christoph Hellwig
2017-10-01 22:27 ` Nicolas Pitre
2017-10-01 22:27 ` Nicolas Pitre
2017-10-03 14:59 ` Christoph Hellwig [this message]
2017-10-03 14:59 ` Christoph Hellwig
2017-10-03 15:06 ` Nicolas Pitre
2017-10-03 15:06 ` Nicolas Pitre
2017-10-03 14:43 ` Rob Herring
2017-10-03 14:43 ` Rob Herring
2017-10-03 14:58 ` Chris Brandt
2017-10-03 14:58 ` Chris Brandt
2017-09-27 23:32 ` [PATCH v4 2/5] cramfs: make cramfs_physmem usable as root fs Nicolas Pitre
2017-09-27 23:32 ` Nicolas Pitre
2017-09-27 23:32 ` [PATCH v4 3/5] cramfs: implement uncompressed and arbitrary data block positioning Nicolas Pitre
2017-09-27 23:32 ` Nicolas Pitre
2017-09-27 23:32 ` [PATCH v4 4/5] cramfs: add mmap support Nicolas Pitre
2017-09-27 23:32 ` Nicolas Pitre
2017-10-01 8:30 ` Christoph Hellwig
2017-10-01 8:30 ` Christoph Hellwig
2017-10-01 22:29 ` Nicolas Pitre
2017-10-01 22:29 ` Nicolas Pitre
2017-10-02 22:45 ` Richard Weinberger
2017-10-02 22:45 ` Richard Weinberger
2017-10-02 23:33 ` Nicolas Pitre
2017-10-02 23:33 ` Nicolas Pitre
2017-10-03 14:57 ` Christoph Hellwig
2017-10-03 14:57 ` Christoph Hellwig
2017-10-03 15:30 ` Nicolas Pitre
2017-10-03 15:30 ` Nicolas Pitre
2017-10-03 15:37 ` Christoph Hellwig
2017-10-03 15:37 ` Christoph Hellwig
2017-10-03 15:40 ` Nicolas Pitre
2017-10-03 15:40 ` Nicolas Pitre
2017-10-04 7:25 ` Christoph Hellwig
2017-10-04 7:25 ` Christoph Hellwig
2017-10-04 20:47 ` Nicolas Pitre
2017-10-04 20:47 ` Nicolas Pitre
2017-10-05 7:15 ` Christoph Hellwig
2017-10-05 7:15 ` Christoph Hellwig
2017-10-05 17:52 ` Nicolas Pitre
2017-10-05 17:52 ` Nicolas Pitre
2017-10-05 20:00 ` Chris Brandt
2017-10-05 20:00 ` Chris Brandt
2017-10-05 21:15 ` Nicolas Pitre
2017-10-05 21:15 ` Nicolas Pitre
2017-10-05 23:49 ` Chris Brandt
2017-10-05 23:49 ` Chris Brandt
2017-09-27 23:32 ` [PATCH v4 5/5] cramfs: rehabilitate it Nicolas Pitre
2017-09-27 23:32 ` Nicolas Pitre
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=20171003145921.GA9954@infradead.org \
--to=hch@infradead.org \
--cc=Chris.Brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nicolas.pitre@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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.