Date: Sat, 30 May 2015 20:17:17 +0530 From: Pratik Singhal <ps06756@gmail.com> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: Difference b/w xfer_len and len fields Message-ID: <CAGf2gkM1QNTpw5ROhPS-DXrohDc8v-D9jSfjUGPxLfaoG6v2Kg@mail.gmail.com> In-Reply-To: <1432993550.1200.104.camel@freebsd.org> References: <CAGf2gkMuL0JDnX5PRvWKRSnmAHOFY4jzQEOjM6MQ8u9G4FuLbA@mail.gmail.com> <1432993550.1200.104.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
What do you mean by "driver-internal" variables ? On Sat, May 30, 2015 at 7:15 PM, Ian Lepore <ian@freebsd.org> wrote: > On Sat, 2015-05-30 at 11:26 +0530, Pratik Singhal wrote: > > What is the difference b/w the xfer_len and the len fields in the struct > > mmc_data in file sys/dev/mmc/mmcreg.h ? > > > > AFAIK , len is the length of the data present in mmc_data , what is > > xfer_len ? > > > > The xfer_len field has historically been unused, until recently. When > the dwc mmc driver was added, it uses xfer_len as a driver-internal > variable to track how much of the overal work is done as the IO > proceeds. > > -- Ian > > -- Regards, Pratik Singhal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGf2gkM1QNTpw5ROhPS-DXrohDc8v-D9jSfjUGPxLfaoG6v2Kg>