From: Lukasz Majewski <l.majewski@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] dfu, nand: add medium specific polltimeout function
Date: Thu, 10 Apr 2014 12:08:44 +0200 [thread overview]
Message-ID: <20140410120844.768cd853@amdc2363> (raw)
In-Reply-To: <22E0B499-3CF1-4809-8F4A-AAF720924411@antoniou-consulting.com>
Hi Pantelis,
> Hi Marek,
>
> On Apr 10, 2014, at 10:54 AM, Marek Vasut wrote:
>
> > On Thursday, April 10, 2014 at 07:08:06 AM, Heiko Schocher wrote:
> >> add a possibility to add a medium specific polltimeout
> >> function. So it is possible to define different
> >> poll timeouts.
> >>
> >> Used on nand medium, for setting the DFU_MANIFEST_POLL_TIMEOUT
> >> only on nand ubi partitions, which is currently the only
> >> usecase.
> >>
> >> Signed-off-by: Heiko Schocher <hs@denx.de>
> >> Cc: Lukasz Majewski <l.majewski@samsung.com>
> >> Cc: Kyungmin Park <kyungmin.park@samsung.com>
> >> Cc: Marek Vasut <marex@denx.de>
> >> Cc: Pantelis Antoniou <panto@antoniou-consulting.com>
> >
> > [...]
> >
> >> @@ -174,6 +174,17 @@ static void dnload_request_flush(struct
> >> usb_ep *ep, struct usb_request *req) req->length,
> >> f_dfu->blk_seq_num); }
> >>
> >> +static void dfu_set_poll_timeout_manifest(struct dfu_status
> >> *dstat,
> >> + struct f_dfu *f_dfu)
> >> +{
> >> + struct dfu_entity *dfu =
> >> dfu_get_entity(f_dfu->altsetting); +
> >> + if (dfu->poll_timeout)
> >> + dfu_set_poll_timeout(dstat,
> >> dfu->poll_timeout(dfu));
> >> + else
> >> + dfu_set_poll_timeout(dstat,
> >> DFU_MANIFEST_POLL_TIMEOUT); +}
> >
> > Don't you think it'd be better (yet more intrusive) to have all the
> > DFU users have default implementation of dfu->poll_timeout() ? Then
> > you'd be able to avoid this if and even get rid of this
> > dfu_set_poll_timeout_manifest() function.
> >
>
> Could work, but why not a simple accessor like this:
>
> static inline unsigned int dfu_get_poll_timeout(struct dfu_entity
> *dfu) {
>
> return dfu->poll_timeout ? dfu->poll_timeout(dfu);
> DFU_MANIFEST_POLL_TIMEOUT);
> }
>
> and dfu_set_poll_timeout(dstat, dfu_get_poll_timeout(dfu));
>
> You even get the benefit of have a method to read the timeout value
> if we ever needed sometime in the future.
Seems reasonable for me: +1
Some comment:
Guys, please be consistent with CCing people. I didn't receive this
thread. Also this original reply from Pantelis was not CCed to Heiko.
>
> >
> > [...]
> >
> > Best regards,
> > Marek Vasut
>
> Regards
>
> -- Pantelis
--
Best regards,
Lukasz Majewski
Samsung R&D Institute Poland (SRPOL) | Linux Platform Group
next prev parent reply other threads:[~2014-04-10 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 5:08 [U-Boot] [PATCH 1/2] musb-new, dfu: first send request answer then call completions Heiko Schocher
2014-04-10 5:08 ` [U-Boot] [PATCH 2/2] dfu, nand: add medium specific polltimeout function Heiko Schocher
2014-04-10 7:54 ` Marek Vasut
2014-04-10 8:29 ` Pantelis Antoniou
2014-04-10 10:08 ` Lukasz Majewski [this message]
2014-04-10 10:21 ` Heiko Schocher
2014-04-10 14:31 ` Lukasz Majewski
2014-04-11 4:22 ` Heiko Schocher
2014-04-11 7:20 ` Lukasz Majewski
2014-04-10 11:10 ` Marek Vasut
2014-04-10 7:50 ` [U-Boot] [PATCH 1/2] musb-new, dfu: first send request answer then call completions Marek Vasut
2014-05-08 8:47 ` Lukasz Majewski
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=20140410120844.768cd853@amdc2363 \
--to=l.majewski@samsung.com \
--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