From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 4/6] mmc: fsl_esdhc: Add support to force VSELECT set
Date: Tue, 17 Jun 2014 09:42:42 +0300 [thread overview]
Message-ID: <539FE362.1050704@compulab.co.il> (raw)
In-Reply-To: <CAP9ODKpVjCxBz3F2WJi8syQsKjnMzRA+0UdbVRWPjxdyJkaJWw@mail.gmail.com>
Hi Otavio,
On 06/16/14 14:48, Otavio Salvador wrote:
> On Mon, Jun 16, 2014 at 4:03 AM, Igor Grinberg <grinberg@compulab.co.il> wrote:
>> Hi Otavio,
>>
>> On 06/16/14 05:24, Otavio Salvador wrote:
>>> On Sun, Jun 15, 2014 at 11:03 PM, Marek Vasut <marex@denx.de> wrote:
>>>> On Monday, June 16, 2014 at 03:39:08 AM, Otavio Salvador wrote:
>>>>> On Sun, Jun 15, 2014 at 10:27 PM, Marek Vasut <marex@denx.de> wrote:
>>>>>> On Monday, June 16, 2014 at 03:22:22 AM, Otavio Salvador wrote:
>>>>>>
>>>>>> [...]
>>>>>>
>>>>>>>>> +#ifdef CONFIG_SYS_FSL_ESDHC_FORCE_VSELECT
>>>>>>>>> + esdhc_setbits32(®s->vendorspec, ESDHC_VENDORSPEC_VSELECT);
>>>>>>>>> +#endif
>>>>>>>>
>>>>>>>> Documentation is missing.
>>>>>>>
>>>>>>> There is no FSL ESDHC README file so that's why I didn't include it
>>>>>>> anywhere.
>>>>>>
>>>>>> I'm at loss for words here, really...
>>>>>>
>>>>>> I think you know what needs to be done (hint: write the documentation),
>>>>>> right ?
>>>>>
>>>>> I won't write the full documentation for it. I am sorry.
>>>>
>>>> Undocumented configuration option is not acceptable, period.
>>>
>>> Who accepted the driver in the first version, without Doc?
>>>
>>> I am not in the position to write the full doc.
>>
>> I think there is a misunderstanding here...
>> I think Marek does not want to say that you need to write the full
>> documentation for the driver, but only document the CONFIG_SYS_FSL_ESDHC_FORCE_VSELECT configuration option (what does it
>> do when you define it and why should one define it).
>
> Great but where if it does not exist?
>
> should I make a README.fsl-esdhc and include just it?
Hmmm... May be.
I would make a decision and start something, then send an RFC.
Writing some words should not be hard especially for configuration
options that you introduce yourself, but if you find some stuff
currently hard or time consuming for some reason, a "TODO: ..."
might be an acceptable compromise.
--
Regards,
Igor.
next prev parent reply other threads:[~2014-06-17 6:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 0:46 [U-Boot] [PATCH 1/6] usb: ehci: mx6: Add support for i.MX6SL Otavio Salvador
2014-06-16 0:46 ` [U-Boot] [PATCH 2/6] imx: mx6sl: Extend USDHC SD2 pins to support 8-wire use Otavio Salvador
2014-06-16 0:46 ` [U-Boot] [PATCH 3/6] mmc: fsl_esdhc: Add CMD11 support to switch to 1.8V Otavio Salvador
2014-06-19 15:23 ` Andy Fleming
2014-06-16 0:46 ` [U-Boot] [PATCH 4/6] mmc: fsl_esdhc: Add support to force VSELECT set Otavio Salvador
2014-06-16 0:51 ` Marek Vasut
2014-06-16 1:22 ` Otavio Salvador
2014-06-16 1:27 ` Marek Vasut
2014-06-16 1:39 ` Otavio Salvador
2014-06-16 2:03 ` Marek Vasut
2014-06-16 2:24 ` Otavio Salvador
2014-06-16 7:03 ` Igor Grinberg
2014-06-16 11:48 ` Otavio Salvador
2014-06-17 6:00 ` Marek Vasut
2014-06-17 6:06 ` Michael Trimarchi
2014-06-17 15:49 ` Marek Vasut
2014-06-17 16:00 ` Michael Trimarchi
2014-06-17 6:42 ` Igor Grinberg [this message]
2014-06-17 15:11 ` Stefano Babic
2014-06-17 15:12 ` Otavio Salvador
2014-06-17 15:14 ` Michael Trimarchi
2014-06-17 15:19 ` Stefano Babic
2014-06-16 0:46 ` [U-Boot] [PATCH 5/6] Print ramdisk load address if it is in use Otavio Salvador
2014-06-16 4:38 ` Wolfgang Denk
2014-06-16 11:52 ` Otavio Salvador
2014-06-16 0:46 ` [U-Boot] [PATCH 6/6] warp: Add initial WaRP Board support Otavio Salvador
2014-06-16 0:54 ` Marek Vasut
2014-08-18 17:56 ` Fabio Estevam
2014-08-18 17:57 ` Fabio Estevam
2014-08-18 18:08 ` Otavio Salvador
2014-06-16 0:49 ` [U-Boot] [PATCH 1/6] usb: ehci: mx6: Add support for i.MX6SL Marek Vasut
2014-06-16 1:11 ` Otavio Salvador
2014-06-16 1:28 ` Marek Vasut
2014-06-16 7:05 ` Igor Grinberg
2014-06-16 11:51 ` Otavio Salvador
2014-06-17 14:56 ` Stefano Babic
2014-06-17 14:58 ` Otavio Salvador
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=539FE362.1050704@compulab.co.il \
--to=grinberg@compulab.co.il \
--cc=u-boot@lists.denx.de \
/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