[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180304223913.ywpg2dohalxj53uf@ninjato>
Date: Sun, 4 Mar 2018 23:39:13 +0100
From: Wolfram Sang <wsa@...-dreams.de>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: linux-mmc@...r.kernel.org,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
Ulf Magnusson <ulfalizer@...il.com>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Simon Horman <horms+renesas@...ge.net.au>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
Ulf Hansson <ulf.hansson@...aro.org>
Subject: Re: [PATCH v3 15/16] mmc: tmio: clear force_pio flag before starting
data transfer
On Thu, Jan 18, 2018 at 01:28:15AM +0900, Masahiro Yamada wrote:
> Currently, force_pio is cleared when the driver exits. Then, it
> resulted in clearing it in multiple places since MMC drivers in
> general have multiple exit points.
>
> tmio_mmc_reset_work - bails out on timeout
> tmio_process_mrq - error out when it cannot send a command
> tmio_mmc_finish_request - successful exit
>
> This is error-prone since we may miss to cover all bail-out points.
>
> To simplify the code, the data structure should be initialized just
> before used since we have a single entrance. force_pio is only used
> for data transfer, so tmio_mmc_start_data() will be a suitable place
> to clear this flag.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>
Reviewed-by: Wolfram Sang <wsa+renesas@...g-engineering.com>
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists