From: Kalle Valo <kvalo@codeaurora.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: gregkh@linuxfoundation.org, ming.lei@canonical.com,
daniel.wagner@bmw-carit.de, teg@jklm.no, mchehab@osg.samsung.com,
zajec5@gmail.com, linux-kernel@vger.kernel.org,
markivx@codeaurora.org, stephen.boyd@linaro.org,
broonie@kernel.org, zohar@linux.vnet.ibm.com, tiwai@suse.de,
johannes@sipsolutions.net, chunkeey@googlemail.com,
hauke@hauke-m.de, jwboyer@fedoraproject.org,
dmitry.torokhov@gmail.com, dwmw2@infradead.org, jslaby@suse.com,
torvalds@linux-foundation.org, luto@amacapital.net,
fengguang.wu@intel.com, rpurdie@rpsys.net,
j.anaszewski@samsung.com, Abhay_Salunke@dell.com,
Julia.Lawall@lip6.fr, Gilles.Muller@lip6.fr,
nicolas.palix@imag.fr, dhowells@redhat.com,
bjorn.andersson@linaro.org, arend.vanspriel@broadcom.com
Subject: Re: [PATCH v2 3/5] firmware: revamp firmware documentation
Date: Thu, 19 Jan 2017 21:50:43 +0200 [thread overview]
Message-ID: <878tq6omlo.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20161216111038.22064-4-mcgrof@kernel.org> (Luis R. Rodriguez's message of "Fri, 16 Dec 2016 03:10:36 -0800")
"Luis R. Rodriguez" <mcgrof@kernel.org> writes:
> Understanding this code is getting out of control without any
> notes. Give the firmware_class driver a much needed documentation love,
> and while at it convert it to the new sphinx documentation format.
>
> v2: typos and small fixes
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
[...]
> +To upload firmware you will echo 1 onto the loading file to indicate
> +you are loading firmware. You then cat the firmware into the data file,
s/cat/write/?
> +Refer to do_firmware_uevent() for details of the kobject event variables
> +setup. Variables passwdd with a kobject add event:
"passed" or what? I'm not quite understanding the last sentence anyway.
> +* If an asynchronous call is used the firmware cache is only set up for a
> + device if if the second argument (uevent) to request_firmware_nowait() is
> + true. When uevent is true it requests that a kobject uevent be sent to
> + userspace for the firmware request. For details refer to the Fackback
> + mechanism documented below.
Is that "fackback" typo intentional? Pretty funny at least :)
But this was really good, thanks. I learned a lot.
--
Kalle Valo
next prev parent reply other threads:[~2017-01-19 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 11:10 [PATCH v2 0/5] firmware: doc revamp Luis R. Rodriguez
2016-12-16 11:10 ` [PATCH v2 1/5] selftests: firmware: only modprobe if driver is missing Luis R. Rodriguez
2016-12-16 11:10 ` [PATCH v2 2/5] selftests: firmware: send expected errors to /dev/null Luis R. Rodriguez
2016-12-16 11:10 ` [PATCH v2 3/5] firmware: revamp firmware documentation Luis R. Rodriguez
2017-01-19 19:50 ` Kalle Valo [this message]
2016-12-16 11:10 ` [PATCH v2 4/5] firmware: add SmPL report for custom fallback mechanism Luis R. Rodriguez
2017-01-11 8:32 ` Greg KH
2017-01-11 14:02 ` Luis R. Rodriguez
2017-01-11 15:49 ` Greg KH
2017-01-11 17:25 ` Luis R. Rodriguez
2016-12-16 11:10 ` [PATCH v2 5/5] firmware: add DECLARE_FW_CUSTOM_FALLBACK() annotation Luis R. Rodriguez
2016-12-19 10:23 ` Julia Lawall
2017-01-09 20:46 ` Luis R. Rodriguez
2017-01-09 20:54 ` Luis R. Rodriguez
2017-01-09 21:09 ` Julia Lawall
2017-01-10 14:43 ` Luis R. Rodriguez
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=878tq6omlo.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Abhay_Salunke@dell.com \
--cc=Gilles.Muller@lip6.fr \
--cc=Julia.Lawall@lip6.fr \
--cc=arend.vanspriel@broadcom.com \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=chunkeey@googlemail.com \
--cc=daniel.wagner@bmw-carit.de \
--cc=dhowells@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hauke@hauke-m.de \
--cc=j.anaszewski@samsung.com \
--cc=johannes@sipsolutions.net \
--cc=jslaby@suse.com \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=markivx@codeaurora.org \
--cc=mcgrof@kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=ming.lei@canonical.com \
--cc=nicolas.palix@imag.fr \
--cc=rpurdie@rpsys.net \
--cc=stephen.boyd@linaro.org \
--cc=teg@jklm.no \
--cc=tiwai@suse.de \
--cc=torvalds@linux-foundation.org \
--cc=zajec5@gmail.com \
--cc=zohar@linux.vnet.ibm.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