Re: [PATCH] vTPM: Fix Atmel timeout bug.

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Andrew Cooper]

On 30/10/14 13:05, Emil Condrea wrote:
> Some versions of Atmel TPMs provide invalid values for TPM_CAP_PROP_TIS_TIMEOUT query.
> Because timeouts are invalid, every other command after tpm_get_timeouts will fail.
> It is a known issue and it was fixed recently in linux kernel tpm_tis.c on 2014-07-29.
> This patch does not allow timeouts to be less than standard values.
> I tested it on a Dell Latitude E5520 and after making the changes I was able to start vtpmmgr-stubdom.
>
> Signed-off-by: Emil Condrea <emilcondrea@gmail.com>
> ---
>  extras/mini-os/tpm_tis.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
>
> diff --git a/extras/mini-os/tpm_tis.c b/extras/mini-os/tpm_tis.c
> index b067cb7..81d426a 100644
> --- a/extras/mini-os/tpm_tis.c
> +++ b/extras/mini-os/tpm_tis.c
> @@ -33,6 +33,11 @@
>  #ifndef min
>  	#define min( a, b ) ( ((a) < (b)) ? (a) : (b) )
>  #endif
> +#define ADJUST_TIMEOUTS_TO_STANDARD(initial,standard,timeout_no)			\
> +	if((initial) < (standard)){							\
> +		(initial) = (standard);							\
> +		printk("Timeout %c was adjusted to standard value.\n",timeout_no);	\
> +	}
>  
>  #define TPM_HEADER_SIZE 10
>  
> @@ -997,15 +1002,22 @@ int tpm_get_timeouts(struct tpm_chip *chip)
>     }
>     if (timeout)
>        chip->timeout_a = MICROSECS(timeout * scale); /*Convert to msec */
> +   ADJUST_TIMEOUTS_TO_STANDARD(chip->timeout_a,MILLISECS(TIS_SHORT_TIMEOUT),'a');

Surely each of these are just

chip->timeout_a = max(MICROSECS(timeout * scale),
MILLISECS(TIS_SHORT_TIMEOUT))

Also, are you certain that the units here are correct?  The micro vs
milli seconds looks odd.

~Andrew

[PATCH] vTPM: Fix Atmel timeout bug.

[Emil Condrea]

Some versions of Atmel TPMs provide invalid values for TPM_CAP_PROP_TIS_TIMEOUT query.
Because timeouts are invalid, every other command after tpm_get_timeouts will fail.
It is a known issue and it was fixed recently in linux kernel tpm_tis.c on 2014-07-29.
This patch does not allow timeouts to be less than standard values.
I tested it on a Dell Latitude E5520 and after making the changes I was able to start vtpmmgr-stubdom.

Signed-off-by: Emil Condrea <emilcondrea@gmail.com>
---
 extras/mini-os/tpm_tis.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/extras/mini-os/tpm_tis.c b/extras/mini-os/tpm_tis.c
index b067cb7..81d426a 100644
--- a/extras/mini-os/tpm_tis.c
+++ b/extras/mini-os/tpm_tis.c
@@ -33,6 +33,11 @@
 #ifndef min
 	#define min( a, b ) ( ((a) < (b)) ? (a) : (b) )
 #endif
+#define ADJUST_TIMEOUTS_TO_STANDARD(initial,standard,timeout_no)			\
+	if((initial) < (standard)){							\
+		(initial) = (standard);							\
+		printk("Timeout %c was adjusted to standard value.\n",timeout_no);	\
+	}
 
 #define TPM_HEADER_SIZE 10
 
@@ -997,15 +1002,22 @@ int tpm_get_timeouts(struct tpm_chip *chip)
    }
    if (timeout)
       chip->timeout_a = MICROSECS(timeout * scale); /*Convert to msec */
+   ADJUST_TIMEOUTS_TO_STANDARD(chip->timeout_a,MILLISECS(TIS_SHORT_TIMEOUT),'a');
+   
    timeout = be32_to_cpu(timeout_cap->b);
    if (timeout)
       chip->timeout_b = MICROSECS(timeout * scale); /*Convert to msec */
+   ADJUST_TIMEOUTS_TO_STANDARD(chip->timeout_b,MILLISECS(TIS_LONG_TIMEOUT),'b');
+
    timeout = be32_to_cpu(timeout_cap->c);
    if (timeout)
       chip->timeout_c = MICROSECS(timeout * scale); /*Convert to msec */
+   ADJUST_TIMEOUTS_TO_STANDARD(chip->timeout_c,MILLISECS(TIS_SHORT_TIMEOUT),'c');
+
    timeout = be32_to_cpu(timeout_cap->d);
    if (timeout)
       chip->timeout_d = MICROSECS(timeout * scale); /*Convert to msec */
+   ADJUST_TIMEOUTS_TO_STANDARD(chip->timeout_d,MILLISECS(TIS_SHORT_TIMEOUT),'d');
 
 duration:
    tpm_cmd.header.in = tpm_getcap_header;
-- 
1.9.1

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Emil Condrea]

[-- Attachment #1.1: Type: text/plain, Size: 2860 bytes --]

Of course we can use max, but I thought that it might be useful to have a
prink to inform the user that the timeout was adjusted.
In init_tpm_tis the default timeouts are set using:
/* Set default timeouts */ tpm->timeout_a =
MILLISECS(TIS_SHORT_TIMEOUT);//750*1000000UL tpm->timeout_b =
MILLISECS(TIS_LONG_TIMEOUT);//2000*1000000UL tpm->timeout_c =
MILLISECS(TIS_SHORT_TIMEOUT); tpm->timeout_d = MILLISECS(TIS_SHORT_TIMEOUT);

But in kernel fix they are set as 750*1000 instead of 750*1000000UL :
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n381
So if we want to integrate kernel changes I think we should use
MICROSECS(TIS_SHORT_TIMEOUT) which is 750000
Also in kernel the default timeouts are initialized using msecs_to_jiffies
which is different from MILLISECS macro.:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n548
Is there a certain reason for not using msecs_to_jiffies ?


On Thu, Oct 30, 2014 at 2:58 PM, Andrew Cooper <andrew.cooper3@citrix.com>
wrote:

> On 30/10/14 13:05, Emil Condrea wrote:
> > Some versions of Atmel TPMs provide invalid values for
> TPM_CAP_PROP_TIS_TIMEOUT query.
> > Because timeouts are invalid, every other command after tpm_get_timeouts
> will fail.
> > It is a known issue and it was fixed recently in linux kernel tpm_tis.c
> on 2014-07-29.
> > This patch does not allow timeouts to be less than standard values.
> > I tested it on a Dell Latitude E5520 and after making the changes I was
> able to start vtpmmgr-stubdom.
> >
> > Signed-off-by: Emil Condrea <emilcondrea@gmail.com>
> > ---
> >  extras/mini-os/tpm_tis.c | 12 ++++++++++++
> >  1 file changed, 12 insertions(+)
> >
> > diff --git a/extras/mini-os/tpm_tis.c b/extras/mini-os/tpm_tis.c
> > index b067cb7..81d426a 100644
> > --- a/extras/mini-os/tpm_tis.c
> > +++ b/extras/mini-os/tpm_tis.c
> > @@ -33,6 +33,11 @@
> >  #ifndef min
> >       #define min( a, b ) ( ((a) < (b)) ? (a) : (b) )
> >  #endif
> > +#define ADJUST_TIMEOUTS_TO_STANDARD(initial,standard,timeout_no)
>              \
> > +     if((initial) < (standard)){
>              \
> > +             (initial) = (standard);
>              \
> > +             printk("Timeout %c was adjusted to standard
> value.\n",timeout_no);      \
> > +     }
> >
> >  #define TPM_HEADER_SIZE 10
> >
> > @@ -997,15 +1002,22 @@ int tpm_get_timeouts(struct tpm_chip *chip)
> >     }
> >     if (timeout)
> >        chip->timeout_a = MICROSECS(timeout * scale); /*Convert to msec */
> > +
>  ADJUST_TIMEOUTS_TO_STANDARD(chip->timeout_a,MILLISECS(TIS_SHORT_TIMEOUT),'a');
>
> Surely each of these are just
>
> chip->timeout_a = max(MICROSECS(timeout * scale),
> MILLISECS(TIS_SHORT_TIMEOUT))
>
> Also, are you certain that the units here are correct?  The micro vs
> milli seconds looks odd.
>
> ~Andrew
>
>

[-- Attachment #1.2: Type: text/html, Size: 4584 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Ian Campbell]

On Thu, 2014-10-30 at 15:48 +0200, Emil Condrea wrote:
> Of course we can use max, but I thought that it might be useful to
> have a prink to inform the user that the timeout was adjusted.
> In init_tpm_tis the default timeouts are set using:
> /* Set default timeouts */ tpm->timeout_a =
> MILLISECS(TIS_SHORT_TIMEOUT);//750*1000000UL tpm->timeout_b =
> MILLISECS(TIS_LONG_TIMEOUT);//2000*1000000UL tpm->timeout_c =
> MILLISECS(TIS_SHORT_TIMEOUT); tpm->timeout_d =
> MILLISECS(TIS_SHORT_TIMEOUT);
> 
> 
> 
> But in kernel fix they are set as 750*1000 instead of 750*1000000UL :
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n381
> So if we want to integrate kernel changes I think we should use
> MICROSECS(TIS_SHORT_TIMEOUT) which is 750000
> Also in kernel the default timeouts are initialized using
> msecs_to_jiffies which is different from MILLISECS
> macro.: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n548
> Is there a certain reason for not using msecs_to_jiffies ?

jiffies are a Linux specific concept which mini-os doesn't share.

Daniel, do you have any opinion on this patch?

It seems like the Linux fix is made only for the specifically broken
platform. That seems to make sense to me since presumably other systems
report short timeouts which they can indeed cope with. It's only Atmel
which brokenly reports something it cannot handle.

Ian.

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Daniel De Graaf]

On 11/04/2014 05:15 AM, Ian Campbell wrote:
> On Thu, 2014-10-30 at 15:48 +0200, Emil Condrea wrote:
>> Of course we can use max, but I thought that it might be useful to
>> have a prink to inform the user that the timeout was adjusted.
>> In init_tpm_tis the default timeouts are set using:
>> /* Set default timeouts */ tpm->timeout_a =
>> MILLISECS(TIS_SHORT_TIMEOUT);//750*1000000UL tpm->timeout_b =
>> MILLISECS(TIS_LONG_TIMEOUT);//2000*1000000UL tpm->timeout_c =
>> MILLISECS(TIS_SHORT_TIMEOUT); tpm->timeout_d =
>> MILLISECS(TIS_SHORT_TIMEOUT);
>>
>>
>>
>> But in kernel fix they are set as 750*1000 instead of 750*1000000UL :
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n381
>> So if we want to integrate kernel changes I think we should use
>> MICROSECS(TIS_SHORT_TIMEOUT) which is 750000
>> Also in kernel the default timeouts are initialized using
>> msecs_to_jiffies which is different from MILLISECS
>> macro.: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n548
>> Is there a certain reason for not using msecs_to_jiffies ?
>
> jiffies are a Linux specific concept which mini-os doesn't share.
>
> Daniel, do you have any opinion on this patch?
>
> It seems like the Linux fix is made only for the specifically broken
> platform. That seems to make sense to me since presumably other systems
> report short timeouts which they can indeed cope with. It's only Atmel
> which brokenly reports something it cannot handle.
>
> Ian.

I agree that an adjustment is needed when values are too short.  Adjusting
in all cases is not quite as nice as only fixing the broken TPMs, but it
is a lot simpler.  It also doesn't seem harmful to have the timeouts be
too large in the driver: a properly functioning TPM will not time out its
requests in any case, so the user won't notice normally, and the default
short timeout is 0.75 seconds - very few people will complain if they have
to wait that long to get a timeout instead of what their TPM actually uses.

-- 
Daniel De Graaf
National Security Agency

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Emil Condrea]

[-- Attachment #1.1: Type: text/plain, Size: 2374 bytes --]

Daniel,
So, is the patch going to be approved(adjusting all short timeouts) or it
needs to be modified?

On Fri, Nov 7, 2014 at 12:01 AM, Daniel De Graaf <dgdegra@tycho.nsa.gov>
wrote:

> On 11/04/2014 05:15 AM, Ian Campbell wrote:
>
>> On Thu, 2014-10-30 at 15:48 +0200, Emil Condrea wrote:
>>
>>> Of course we can use max, but I thought that it might be useful to
>>> have a prink to inform the user that the timeout was adjusted.
>>> In init_tpm_tis the default timeouts are set using:
>>> /* Set default timeouts */ tpm->timeout_a =
>>> MILLISECS(TIS_SHORT_TIMEOUT);//750*1000000UL tpm->timeout_b =
>>> MILLISECS(TIS_LONG_TIMEOUT);//2000*1000000UL tpm->timeout_c =
>>> MILLISECS(TIS_SHORT_TIMEOUT); tpm->timeout_d =
>>> MILLISECS(TIS_SHORT_TIMEOUT);
>>>
>>>
>>>
>>> But in kernel fix they are set as 750*1000 instead of 750*1000000UL :
>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/
>>> linux.git/tree/drivers/char/tpm/tpm_tis.c#n381
>>> So if we want to integrate kernel changes I think we should use
>>> MICROSECS(TIS_SHORT_TIMEOUT) which is 750000
>>> Also in kernel the default timeouts are initialized using
>>> msecs_to_jiffies which is different from MILLISECS
>>> macro.: https://git.kernel.org/cgit/linux/kernel/git/torvalds/
>>> linux.git/tree/drivers/char/tpm/tpm_tis.c#n548
>>> Is there a certain reason for not using msecs_to_jiffies ?
>>>
>>
>> jiffies are a Linux specific concept which mini-os doesn't share.
>>
>> Daniel, do you have any opinion on this patch?
>>
>> It seems like the Linux fix is made only for the specifically broken
>> platform. That seems to make sense to me since presumably other systems
>> report short timeouts which they can indeed cope with. It's only Atmel
>> which brokenly reports something it cannot handle.
>>
>> Ian.
>>
>
> I agree that an adjustment is needed when values are too short.  Adjusting
> in all cases is not quite as nice as only fixing the broken TPMs, but it
> is a lot simpler.  It also doesn't seem harmful to have the timeouts be
> too large in the driver: a properly functioning TPM will not time out its
> requests in any case, so the user won't notice normally, and the default
> short timeout is 0.75 seconds - very few people will complain if they have
> to wait that long to get a timeout instead of what their TPM actually uses.
>
> --
> Daniel De Graaf
> National Security Agency
>

[-- Attachment #1.2: Type: text/html, Size: 3439 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Ian Campbell]

On Thu, 2014-11-06 at 17:01 -0500, Daniel De Graaf wrote:
> On 11/04/2014 05:15 AM, Ian Campbell wrote:
> > On Thu, 2014-10-30 at 15:48 +0200, Emil Condrea wrote:
> >> Of course we can use max, but I thought that it might be useful to
> >> have a prink to inform the user that the timeout was adjusted.
> >> In init_tpm_tis the default timeouts are set using:
> >> /* Set default timeouts */ tpm->timeout_a =
> >> MILLISECS(TIS_SHORT_TIMEOUT);//750*1000000UL tpm->timeout_b =
> >> MILLISECS(TIS_LONG_TIMEOUT);//2000*1000000UL tpm->timeout_c =
> >> MILLISECS(TIS_SHORT_TIMEOUT); tpm->timeout_d =
> >> MILLISECS(TIS_SHORT_TIMEOUT);
> >>
> >>
> >>
> >> But in kernel fix they are set as 750*1000 instead of 750*1000000UL :
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n381
> >> So if we want to integrate kernel changes I think we should use
> >> MICROSECS(TIS_SHORT_TIMEOUT) which is 750000
> >> Also in kernel the default timeouts are initialized using
> >> msecs_to_jiffies which is different from MILLISECS
> >> macro.: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n548
> >> Is there a certain reason for not using msecs_to_jiffies ?
> >
> > jiffies are a Linux specific concept which mini-os doesn't share.
> >
> > Daniel, do you have any opinion on this patch?
> >
> > It seems like the Linux fix is made only for the specifically broken
> > platform. That seems to make sense to me since presumably other systems
> > report short timeouts which they can indeed cope with. It's only Atmel
> > which brokenly reports something it cannot handle.
> >
> > Ian.
> 
> I agree that an adjustment is needed when values are too short.  Adjusting
> in all cases is not quite as nice as only fixing the broken TPMs, but it
> is a lot simpler.  It also doesn't seem harmful to have the timeouts be
> too large in the driver: a properly functioning TPM will not time out its
> requests in any case, so the user won't notice normally, and the default
> short timeout is 0.75 seconds - very few people will complain if they have
> to wait that long to get a timeout instead of what their TPM actually uses.

Can we take that as an ack?

Also needs the ok from Konrad as release manager. AIUI this is a bugfix
for a particular piece of h/w and as Daniel explains above the downside
is that sometimes someone might need to wait 0.75s for a timeout instead
of something shorter.

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Konrad Rzeszutek Wilk]

On Mon, Nov 10, 2014 at 12:01:59PM +0000, Ian Campbell wrote:
> On Thu, 2014-11-06 at 17:01 -0500, Daniel De Graaf wrote:
> > On 11/04/2014 05:15 AM, Ian Campbell wrote:
> > > On Thu, 2014-10-30 at 15:48 +0200, Emil Condrea wrote:
> > >> Of course we can use max, but I thought that it might be useful to
> > >> have a prink to inform the user that the timeout was adjusted.
> > >> In init_tpm_tis the default timeouts are set using:
> > >> /* Set default timeouts */ tpm->timeout_a =
> > >> MILLISECS(TIS_SHORT_TIMEOUT);//750*1000000UL tpm->timeout_b =
> > >> MILLISECS(TIS_LONG_TIMEOUT);//2000*1000000UL tpm->timeout_c =
> > >> MILLISECS(TIS_SHORT_TIMEOUT); tpm->timeout_d =
> > >> MILLISECS(TIS_SHORT_TIMEOUT);
> > >>
> > >>
> > >>
> > >> But in kernel fix they are set as 750*1000 instead of 750*1000000UL :
> > >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n381
> > >> So if we want to integrate kernel changes I think we should use
> > >> MICROSECS(TIS_SHORT_TIMEOUT) which is 750000
> > >> Also in kernel the default timeouts are initialized using
> > >> msecs_to_jiffies which is different from MILLISECS
> > >> macro.: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n548
> > >> Is there a certain reason for not using msecs_to_jiffies ?
> > >
> > > jiffies are a Linux specific concept which mini-os doesn't share.
> > >
> > > Daniel, do you have any opinion on this patch?
> > >
> > > It seems like the Linux fix is made only for the specifically broken
> > > platform. That seems to make sense to me since presumably other systems
> > > report short timeouts which they can indeed cope with. It's only Atmel
> > > which brokenly reports something it cannot handle.
> > >
> > > Ian.
> > 
> > I agree that an adjustment is needed when values are too short.  Adjusting
> > in all cases is not quite as nice as only fixing the broken TPMs, but it
> > is a lot simpler.  It also doesn't seem harmful to have the timeouts be
> > too large in the driver: a properly functioning TPM will not time out its
> > requests in any case, so the user won't notice normally, and the default
> > short timeout is 0.75 seconds - very few people will complain if they have
> > to wait that long to get a timeout instead of what their TPM actually uses.
> 
> Can we take that as an ack?
> 
> Also needs the ok from Konrad as release manager. AIUI this is a bugfix
> for a particular piece of h/w and as Daniel explains above the downside
> is that sometimes someone might need to wait 0.75s for a timeout instead
> of something shorter.

Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> 

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Daniel De Graaf]

On 11/10/2014 07:01 AM, Ian Campbell wrote:
> On Thu, 2014-11-06 at 17:01 -0500, Daniel De Graaf wrote:
>> On 11/04/2014 05:15 AM, Ian Campbell wrote:
>>> On Thu, 2014-10-30 at 15:48 +0200, Emil Condrea wrote:
>>>> Of course we can use max, but I thought that it might be useful to
>>>> have a prink to inform the user that the timeout was adjusted.
>>>> In init_tpm_tis the default timeouts are set using:
>>>> /* Set default timeouts */ tpm->timeout_a =
>>>> MILLISECS(TIS_SHORT_TIMEOUT);//750*1000000UL tpm->timeout_b =
>>>> MILLISECS(TIS_LONG_TIMEOUT);//2000*1000000UL tpm->timeout_c =
>>>> MILLISECS(TIS_SHORT_TIMEOUT); tpm->timeout_d =
>>>> MILLISECS(TIS_SHORT_TIMEOUT);
>>>>
>>>>
>>>>
>>>> But in kernel fix they are set as 750*1000 instead of 750*1000000UL :
>>>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n381
>>>> So if we want to integrate kernel changes I think we should use
>>>> MICROSECS(TIS_SHORT_TIMEOUT) which is 750000
>>>> Also in kernel the default timeouts are initialized using
>>>> msecs_to_jiffies which is different from MILLISECS
>>>> macro.: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/char/tpm/tpm_tis.c#n548
>>>> Is there a certain reason for not using msecs_to_jiffies ?
>>>
>>> jiffies are a Linux specific concept which mini-os doesn't share.
>>>
>>> Daniel, do you have any opinion on this patch?
>>>
>>> It seems like the Linux fix is made only for the specifically broken
>>> platform. That seems to make sense to me since presumably other systems
>>> report short timeouts which they can indeed cope with. It's only Atmel
>>> which brokenly reports something it cannot handle.
>>>
>>> Ian.
>>
>> I agree that an adjustment is needed when values are too short.  Adjusting
>> in all cases is not quite as nice as only fixing the broken TPMs, but it
>> is a lot simpler.  It also doesn't seem harmful to have the timeouts be
>> too large in the driver: a properly functioning TPM will not time out its
>> requests in any case, so the user won't notice normally, and the default
>> short timeout is 0.75 seconds - very few people will complain if they have
>> to wait that long to get a timeout instead of what their TPM actually uses.
>
> Can we take that as an ack?

Yes.  I was going to check to see if the printks would cause people to see
problems where the timeouts were already reasonable, but since the mini-os
driver is already quite verbose, this should not be a problem.  It might
be nice to output the old/new value of the timeout, but that's mostly for
the curious rather than actually necessary.

> Also needs the ok from Konrad as release manager. AIUI this is a bugfix
> for a particular piece of h/w and as Daniel explains above the downside
> is that sometimes someone might need to wait 0.75s for a timeout instead
> of something shorter.

-- 
Daniel De Graaf
National Security Agency

Re: [PATCH] vTPM: Fix Atmel timeout bug.

[Ian Campbell]

On Mon, 2014-11-10 at 09:35 -0500, Konrad Rzeszutek Wilk wrote:
> Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

Applied with Daniel's ack.