From: "Gabriel L. Somlo" <somlo@cmu.edu>
To: Rob Herring <robh@kernel.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Laszlo Ersek" <lersek@redhat.com>,
"Ralf Baechle" <ralf@linux-mips.org>,
"Russell King" <rmk+kernel@arm.linux.org.uk>,
"Eric Anholt" <eric@anholt.net>,
"Hanjun Guo" <hanjun.guo@linaro.org>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Sudeep Holla" <sudeep.holla@arm.com>,
"Andy Gross" <agross@codeaurora.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"matt.fleming@intel.com" <matt.fleming@intel.com>,
mst@redhat.com, jordan.l.justen@intel.com,
kernelnewbies@kernelnewbies.org,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Leif Lindholm" <leif.lindholm@linaro.org>,
"Andy Lutomirski" <luto@amacapital.net>,
"Ard Biesheuvel" <ard.biesheuvel@linaro.org>,
kraxel@redhat.com, stefanha@gmail.com
Subject: Re: [Qemu-devel] [PATCH v4 4/4] devicetree: update documentation for fw_cfg ARM bindings
Date: Tue, 17 Nov 2015 21:17:27 -0500 [thread overview]
Message-ID: <20151118021727.GA14351@GLSMBP.INI.CMU.EDU> (raw)
In-Reply-To: <CAL_JsqKEi9BozyLQ9sKM3VL-hSSRntDyET859N1qTTMT4jkDOw@mail.gmail.com>
On Tue, Nov 17, 2015 at 04:14:42PM -0600, Rob Herring wrote:
> On Mon, Nov 16, 2015 at 2:38 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> >
> > On 15/11/2015 03:07, Rob Herring wrote:
> >> We generally don't want DT docs to depend on other kernel documentation.
> >
> > DT docs do not contain a copy of the data sheets, either. There is no
> > reason to say how to use the device (and even then, only doing so
> > partially) in the DT docs.
>
> The difference is datasheets apply to all OS's, kernel documentation
> does not. In theory at least this could be used for other OS's, right?
>
> Perhaps QEMU is the right place to thoroughly describe this and DT and
> sysfs docs can refer to it.
So, leave only ARM/DT specifc details in
Documentation/devicetree/bindings/arm/fw-cfg.txt,
and rework the fw_cfg sysfs patch (1/4) to only document
sysfs specific details in
Documentation/ABI/testing/sysfs-firmware-qemu_fw_cfg ?
The fw_cfg "datasheet" does exist in QEMU already, so there is
something to point at from either/both of the above.
Thanks,
--Gabriel
next prev parent reply other threads:[~2015-11-18 2:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 3:03 [PATCH v4 0/4] SysFS driver for QEMU fw_cfg device Gabriel L. Somlo
2015-11-14 3:03 ` [PATCH v4 1/4] firmware: introduce sysfs driver for QEMU's " Gabriel L. Somlo
2015-11-14 3:03 ` [PATCH v4 2/4] kobject: export kset_find_obj() for module use Gabriel L. Somlo
2015-11-14 3:03 ` [PATCH v4 3/4] firmware: create directory hierarchy for sysfs fw_cfg entries Gabriel L. Somlo
2015-11-14 3:03 ` [PATCH v4 4/4] devicetree: update documentation for fw_cfg ARM bindings Gabriel L. Somlo
2015-11-15 2:07 ` [Qemu-devel] " Rob Herring
2015-11-16 8:38 ` Paolo Bonzini
2015-11-16 13:51 ` Gabriel L. Somlo
2015-11-17 22:14 ` Rob Herring
2015-11-18 2:17 ` Gabriel L. Somlo [this message]
2015-11-18 13:04 ` François Revol
2015-11-18 20:54 ` Gabriel L. Somlo
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=20151118021727.GA14351@GLSMBP.INI.CMU.EDU \
--to=somlo@cmu.edu \
--cc=agross@codeaurora.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hanjun.guo@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jordan.l.justen@intel.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=kraxel@redhat.com \
--cc=leif.lindholm@linaro.org \
--cc=lersek@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mark.rutland@arm.com \
--cc=matt.fleming@intel.com \
--cc=mst@redhat.com \
--cc=pawel.moll@arm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=ralf@linux-mips.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robh@kernel.org \
--cc=stefanha@gmail.com \
--cc=sudeep.holla@arm.com \
--cc=zajec5@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®