From: Shawn Lin <shawn.lin@rock-chips.com>
To: Jaehoon Chung <jh80.chung@samsung.com>,
Ziyuan Xu <xzy.xu@rock-chips.com>,
ulf.hansson@linaro.org
Cc: shawn.lin@rock-chips.com, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: dw_mmc: Fix some coding style
Date: Thu, 5 Jan 2017 10:24:30 +0800 [thread overview]
Message-ID: <af98c104-6fc9-b155-5cea-8242344fb8fa@rock-chips.com> (raw)
In-Reply-To: <dca78b88-425e-363a-aaca-9e3c3a43971e@samsung.com>
On 2017/1/5 9:19, Jaehoon Chung wrote:
> Hi,
>
> On 01/04/2017 09:52 PM, Ziyuan Xu wrote:
>> Let's fix the warnings from checkpatch.pl:
>>
>> - line over 80 characters;
>> - block comments should align the * on each Lines;
>> - statements not starting on a tabstop.
>
> If there is no critical problem,
> I think that current codes are keeping better than changing.
> When someone contribute the patches relevant to these, it can be also changed,
> (It's more meaningful.)
>
Indeed.
Moreover, it breaks the git-blame history when we need to review
how the code had been developing..
> Best Regards,
> Jaehoon Chung
>
>>
>> Signed-off-by: Ziyuan Xu <xzy.xu@rock-chips.com>
>> ---
>>
>> drivers/mmc/host/dw_mmc.c | 33 +++++++++++++++++----------------
>> 1 file changed, 17 insertions(+), 16 deletions(-)
>>
>> diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
>> index ed63237..a8efe3f 100644
>> --- a/drivers/mmc/host/dw_mmc.c
>> +++ b/drivers/mmc/host/dw_mmc.c
>> @@ -94,7 +94,8 @@ struct idmac_desc {
>>
>> __le32 des1; /* Buffer sizes */
>> #define IDMAC_SET_BUFFER1_SIZE(d, s) \
>> - ((d)->des1 = ((d)->des1 & cpu_to_le32(0x03ffe000)) | (cpu_to_le32((s) & 0x1fff)))
>> + ((d)->des1 = ((d)->des1 & cpu_to_le32(0x03ffe000)) | \
>> + (cpu_to_le32((s) & 0x1fff)))
>>
>> __le32 des2; /* buffer 1 physical address */
>>
>> @@ -2733,16 +2734,16 @@ static void dw_mci_init_dma(struct dw_mci *host)
>> struct device_node *np = dev->of_node;
>>
>> /*
>> - * Check tansfer mode from HCON[17:16]
>> - * Clear the ambiguous description of dw_mmc databook:
>> - * 2b'00: No DMA Interface -> Actually means using Internal DMA block
>> - * 2b'01: DesignWare DMA Interface -> Synopsys DW-DMA block
>> - * 2b'10: Generic DMA Interface -> non-Synopsys generic DMA block
>> - * 2b'11: Non DW DMA Interface -> pio only
>> - * Compared to DesignWare DMA Interface, Generic DMA Interface has a
>> - * simpler request/acknowledge handshake mechanism and both of them
>> - * are regarded as external dma master for dw_mmc.
>> - */
>> + * Check tansfer mode from HCON[17:16]
>> + * Clear the ambiguous description of dw_mmc databook:
>> + * 2b'00: No DMA Interface -> Actually means using Internal DMA block
>> + * 2b'01: DesignWare DMA Interface -> Synopsys DW-DMA block
>> + * 2b'10: Generic DMA Interface -> non-Synopsys generic DMA block
>> + * 2b'11: Non DW DMA Interface -> pio only
>> + * Compared to DesignWare DMA Interface, Generic DMA Interface has a
>> + * simpler request/acknowledge handshake mechanism and both of them
>> + * are regarded as external dma master for dw_mmc.
>> + */
>> host->use_dma = SDMMC_GET_TRANS_MODE(mci_readl(host, HCON));
>> if (host->use_dma == DMA_INTERFACE_IDMA) {
>> host->use_dma = TRANS_MODE_IDMAC;
>> @@ -2756,9 +2757,9 @@ static void dw_mci_init_dma(struct dw_mci *host)
>> /* Determine which DMA interface to use */
>> if (host->use_dma == TRANS_MODE_IDMAC) {
>> /*
>> - * Check ADDR_CONFIG bit in HCON to find
>> - * IDMAC address bus width
>> - */
>> + * Check ADDR_CONFIG bit in HCON to find
>> + * IDMAC address bus width
>> + */
>> addr_config = SDMMC_GET_ADDR_CONFIG(mci_readl(host, HCON));
>>
>> if (addr_config == 1) {
>> @@ -3337,8 +3338,8 @@ int dw_mci_runtime_resume(struct device *dev)
>> * Restore the initial value at FIFOTH register
>> * And Invalidate the prev_blksz with zero
>> */
>> - mci_writel(host, FIFOTH, host->fifoth_val);
>> - host->prev_blksz = 0;
>> + mci_writel(host, FIFOTH, host->fifoth_val);
>> + host->prev_blksz = 0;
>>
>> /* Put in max timeout */
>> mci_writel(host, TMOUT, 0xFFFFFFFF);
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Best Regards
Shawn Lin
prev parent reply other threads:[~2017-01-05 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170104125752epcas4p2a801fce6fd376d02d7440ad4bfe1716b@epcas4p2.samsung.com>
2017-01-04 12:52 ` Ziyuan Xu
2017-01-04 13:03 ` Andy Shevchenko
2017-01-04 18:32 ` Joe Perches
2017-01-05 7:30 ` Ziyuan
2017-01-05 1:19 ` Jaehoon Chung
2017-01-05 2:24 ` Shawn Lin [this message]
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=af98c104-6fc9-b155-5cea-8242344fb8fa@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=jh80.chung@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=xzy.xu@rock-chips.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®