On Thu, Oct 06, 2016 at 10:03:56AM +0200, Ulf Hansson wrote:
> On 5 October 2016 at 22:03, Rob Herring wrote:
> > On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
> >> On 23 September 2016 at 22:01, Zach Brown wrote:
> >>> Certain
On Thu, Oct 06, 2016 at 10:03:56AM +0200, Ulf Hansson wrote:
> On 5 October 2016 at 22:03, Rob Herring wrote:
> > On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
> >> On 23 September 2016 at 22:01, Zach Brown wrote:
> >>> Certain board configurations can make highspeed malfunction due to
>
On Thu, Oct 06, 2016 at 09:13:24AM +0300, Adrian Hunter wrote:
> On 06/10/16 04:34, Shawn Lin wrote:
> > On 2016/10/6 5:22, Julia Cartwright wrote:
> >> On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
> >>> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson
> >>>
On Thu, Oct 06, 2016 at 09:13:24AM +0300, Adrian Hunter wrote:
> On 06/10/16 04:34, Shawn Lin wrote:
> > On 2016/10/6 5:22, Julia Cartwright wrote:
> >> On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
> >>> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson
> >>> wrote:
> On 23
On 5 October 2016 at 22:03, Rob Herring wrote:
> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
>> On 23 September 2016 at 22:01, Zach Brown wrote:
>>> Certain board configurations can make highspeed malfunction due to
>>>
On 5 October 2016 at 22:03, Rob Herring wrote:
> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
>> On 23 September 2016 at 22:01, Zach Brown wrote:
>>> Certain board configurations can make highspeed malfunction due to
>>> timing issues. In these cases a way is needed to force the
On 06/10/16 04:34, Shawn Lin wrote:
> On 2016/10/6 5:22, Julia Cartwright wrote:
>> On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
>>> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
On 23 September 2016 at 22:01, Zach Brown wrote:
On 06/10/16 04:34, Shawn Lin wrote:
> On 2016/10/6 5:22, Julia Cartwright wrote:
>> On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
>>> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
On 23 September 2016 at 22:01, Zach Brown wrote:
> Certain board configurations can
On 2016/10/6 5:22, Julia Cartwright wrote:
On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
On 23 September 2016 at 22:01, Zach Brown wrote:
Certain board configurations can make
On 2016/10/6 5:22, Julia Cartwright wrote:
On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
On 23 September 2016 at 22:01, Zach Brown wrote:
Certain board configurations can make highspeed malfunction due to
timing issues. In
On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
> > On 23 September 2016 at 22:01, Zach Brown wrote:
> >> Certain board configurations can make highspeed malfunction due to
> >> timing
On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
> > On 23 September 2016 at 22:01, Zach Brown wrote:
> >> Certain board configurations can make highspeed malfunction due to
> >> timing issues. In these cases a way is needed to
On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
> On 23 September 2016 at 22:01, Zach Brown wrote:
>> Certain board configurations can make highspeed malfunction due to
>> timing issues. In these cases a way is needed to force the controller
>> and
On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
> On 23 September 2016 at 22:01, Zach Brown wrote:
>> Certain board configurations can make highspeed malfunction due to
>> timing issues. In these cases a way is needed to force the controller
>> and card into standard speed even if they
On 23 September 2016 at 22:01, Zach Brown wrote:
> Certain board configurations can make highspeed malfunction due to
> timing issues. In these cases a way is needed to force the controller
> and card into standard speed even if they otherwise appear to be capable
> of
On 23 September 2016 at 22:01, Zach Brown wrote:
> Certain board configurations can make highspeed malfunction due to
> timing issues. In these cases a way is needed to force the controller
> and card into standard speed even if they otherwise appear to be capable
> of highspeed.
>
> The
On Fri, Sep 23, 2016 at 03:01:08PM -0500, Zach Brown wrote:
> Certain board configurations can make highspeed malfunction due to
> timing issues. In these cases a way is needed to force the controller
> and card into standard speed even if they otherwise appear to be capable
> of highspeed.
>
>
On Fri, Sep 23, 2016 at 03:01:08PM -0500, Zach Brown wrote:
> Certain board configurations can make highspeed malfunction due to
> timing issues. In these cases a way is needed to force the controller
> and card into standard speed even if they otherwise appear to be capable
> of highspeed.
>
>
Certain board configurations can make highspeed malfunction due to
timing issues. In these cases a way is needed to force the controller
and card into standard speed even if they otherwise appear to be capable
of highspeed.
The sd-broken-highspeed property will let the sdhci driver know that
Certain board configurations can make highspeed malfunction due to
timing issues. In these cases a way is needed to force the controller
and card into standard speed even if they otherwise appear to be capable
of highspeed.
The sd-broken-highspeed property will let the sdhci driver know that
20 matches
Mail list logo