On Mon, May 14, 2018 at 2:44 PM, Michal Simek wrote:
> On 14.5.2018 09:37, Alexander Graf wrote:
>> On 05/14/2018 12:01 AM, Linus Walleij wrote:
>>> On Wed, May 9, 2018 at 11:44 AM, Alexander Graf wrote:
On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
On Mon, May 14, 2018 at 2:44 PM, Michal Simek wrote:
> On 14.5.2018 09:37, Alexander Graf wrote:
>> On 05/14/2018 12:01 AM, Linus Walleij wrote:
>>> On Wed, May 9, 2018 at 11:44 AM, Alexander Graf wrote:
On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
> Can you please name platform that
On 14.5.2018 09:37, Alexander Graf wrote:
>
> On 05/14/2018 12:01 AM, Linus Walleij wrote:
>> On Wed, May 9, 2018 at 11:44 AM, Alexander Graf wrote:
>>> On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
Can you please name platform that has enough support for Alexander to
On 14.5.2018 09:37, Alexander Graf wrote:
>
> On 05/14/2018 12:01 AM, Linus Walleij wrote:
>> On Wed, May 9, 2018 at 11:44 AM, Alexander Graf wrote:
>>> On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
Can you please name platform that has enough support for Alexander to
care about
On 05/14/2018 12:01 AM, Linus Walleij wrote:
On Wed, May 9, 2018 at 11:44 AM, Alexander Graf wrote:
On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
Can you please name platform that has enough support for Alexander to
care about backwards and forwards compatibility but lacks a
On 05/14/2018 12:01 AM, Linus Walleij wrote:
On Wed, May 9, 2018 at 11:44 AM, Alexander Graf wrote:
On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
Can you please name platform that has enough support for Alexander to
care about backwards and forwards compatibility but lacks a pinctrl
driver.
On Wed, May 9, 2018 at 11:44 AM, Alexander Graf wrote:
> On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
>> Can you please name platform that has enough support for Alexander to
>> care about backwards and forwards compatibility but lacks a pinctrl
>> driver.
>
> ZynqMP is one
On Wed, May 9, 2018 at 11:44 AM, Alexander Graf wrote:
> On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
>> Can you please name platform that has enough support for Alexander to
>> care about backwards and forwards compatibility but lacks a pinctrl
>> driver.
>
> ZynqMP is one example that
On 05/08/2018 12:34 AM, Bjorn Andersson wrote:
On Mon 07 May 12:55 PDT 2018, Rob Herring wrote:
On Mon, May 7, 2018 at 1:31 PM, Bjorn Andersson
wrote:
On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
Deferred probe will currently wait forever on dependent
On 05/08/2018 12:34 AM, Bjorn Andersson wrote:
On Mon 07 May 12:55 PDT 2018, Rob Herring wrote:
On Mon, May 7, 2018 at 1:31 PM, Bjorn Andersson
wrote:
On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a
On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a driver will never exist. It's also not always critical for
a driver to exist. Platforms can rely on default
On 05/07/2018 08:31 PM, Bjorn Andersson wrote:
On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a driver will never exist. It's also not always critical for
a driver to exist. Platforms can rely on default
On Mon, May 07, 2018 at 03:34:38PM -0700, Bjorn Andersson wrote:
> And is this really a problem that does not exists in the ACPI world?
Sort of, in that on ACPI systems all devices are expected to live in
glorious isolation and anything they need transparently configured by
the firmware with any
On Mon, May 07, 2018 at 03:34:38PM -0700, Bjorn Andersson wrote:
> And is this really a problem that does not exists in the ACPI world?
Sort of, in that on ACPI systems all devices are expected to live in
glorious isolation and anything they need transparently configured by
the firmware with any
On Mon 07 May 12:55 PDT 2018, Rob Herring wrote:
> On Mon, May 7, 2018 at 1:31 PM, Bjorn Andersson
> wrote:
> > On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
> >
> >> Deferred probe will currently wait forever on dependent devices to probe,
> >> but sometimes a
On Mon 07 May 12:55 PDT 2018, Rob Herring wrote:
> On Mon, May 7, 2018 at 1:31 PM, Bjorn Andersson
> wrote:
> > On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
> >
> >> Deferred probe will currently wait forever on dependent devices to probe,
> >> but sometimes a driver will never exist. It's
On Mon, May 7, 2018 at 1:31 PM, Bjorn Andersson
wrote:
> On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
>
>> Deferred probe will currently wait forever on dependent devices to probe,
>> but sometimes a driver will never exist. It's also not always critical for
>> a
On Mon, May 7, 2018 at 1:31 PM, Bjorn Andersson
wrote:
> On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
>
>> Deferred probe will currently wait forever on dependent devices to probe,
>> but sometimes a driver will never exist. It's also not always critical for
>> a driver to exist. Platforms
On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
> Deferred probe will currently wait forever on dependent devices to probe,
> but sometimes a driver will never exist. It's also not always critical for
> a driver to exist. Platforms can rely on default configuration from the
> bootloader or reset
On Tue 01 May 14:31 PDT 2018, Rob Herring wrote:
> Deferred probe will currently wait forever on dependent devices to probe,
> but sometimes a driver will never exist. It's also not always critical for
> a driver to exist. Platforms can rely on default configuration from the
> bootloader or reset
On Fri, May 4, 2018 at 8:25 PM, Mark Brown wrote:
> On Wed, May 02, 2018 at 07:49:57PM +0100, Robin Murphy wrote:
>
>> I guess there's also the possibility that a single driver may want multiple
>> behaviours, if e.g. if SoC variants A and B have some identical peripherals
>>
On Fri, May 4, 2018 at 8:25 PM, Mark Brown wrote:
> On Wed, May 02, 2018 at 07:49:57PM +0100, Robin Murphy wrote:
>
>> I guess there's also the possibility that a single driver may want multiple
>> behaviours, if e.g. if SoC variants A and B have some identical peripherals
>> but slightly
On Wed, May 02, 2018 at 07:49:57PM +0100, Robin Murphy wrote:
> I guess there's also the possibility that a single driver may want multiple
> behaviours, if e.g. if SoC variants A and B have some identical peripherals
> but slightly different pinctrl/IOMMU/etc. hardware such that A has workable
>
On Wed, May 02, 2018 at 07:49:57PM +0100, Robin Murphy wrote:
> I guess there's also the possibility that a single driver may want multiple
> behaviours, if e.g. if SoC variants A and B have some identical peripherals
> but slightly different pinctrl/IOMMU/etc. hardware such that A has workable
>
On 02/05/18 15:48, Rob Herring wrote:
On Wed, May 2, 2018 at 6:40 AM, Robin Murphy wrote:
On 01/05/18 22:31, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a driver will never exist. It's also not always
On 02/05/18 15:48, Rob Herring wrote:
On Wed, May 2, 2018 at 6:40 AM, Robin Murphy wrote:
On 01/05/18 22:31, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a driver will never exist. It's also not always critical for
a driver to
On Wed, May 2, 2018 at 6:40 AM, Robin Murphy wrote:
> On 01/05/18 22:31, Rob Herring wrote:
>>
>> Deferred probe will currently wait forever on dependent devices to probe,
>> but sometimes a driver will never exist. It's also not always critical for
>> a driver to exist.
On Wed, May 2, 2018 at 6:40 AM, Robin Murphy wrote:
> On 01/05/18 22:31, Rob Herring wrote:
>>
>> Deferred probe will currently wait forever on dependent devices to probe,
>> but sometimes a driver will never exist. It's also not always critical for
>> a driver to exist. Platforms can rely on
On 05/01/2018 11:31 PM, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a driver will never exist. It's also not always critical for
a driver to exist. Platforms can rely on default configuration from the
bootloader or reset defaults for
On 05/01/2018 11:31 PM, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a driver will never exist. It's also not always critical for
a driver to exist. Platforms can rely on default configuration from the
bootloader or reset defaults for
On 01/05/18 22:31, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a driver will never exist. It's also not always critical for
a driver to exist. Platforms can rely on default configuration from the
bootloader or reset defaults for
On 01/05/18 22:31, Rob Herring wrote:
Deferred probe will currently wait forever on dependent devices to probe,
but sometimes a driver will never exist. It's also not always critical for
a driver to exist. Platforms can rely on default configuration from the
bootloader or reset defaults for
On Tue, May 01, 2018 at 04:31:14PM -0500, Rob Herring wrote:
> Deferred probe will currently wait forever on dependent devices to probe,
> but sometimes a driver will never exist. It's also not always critical for
> a driver to exist. Platforms can rely on default configuration from the
>
On Tue, May 01, 2018 at 04:31:14PM -0500, Rob Herring wrote:
> Deferred probe will currently wait forever on dependent devices to probe,
> but sometimes a driver will never exist. It's also not always critical for
> a driver to exist. Platforms can rely on default configuration from the
>
34 matches
Mail list logo