On Wed, Jun 4, 2014 at 12:25 AM, wrote:
> From: Eric Ernst
>
> For Baytrail, you should never set a GPIO set to direct_irq
> to output mode. When direct_irq_en is set for a GPIO, it is
> tied directly to an APIC internally, and making the pad output
> does not make any sense. Assert a WARN()
On Wed, Jun 4, 2014 at 12:25 AM, eric.er...@linux.intel.com wrote:
From: Eric Ernst eric.er...@linux.intel.com
For Baytrail, you should never set a GPIO set to direct_irq
to output mode. When direct_irq_en is set for a GPIO, it is
tied directly to an APIC internally, and making the pad
On Tue, Jun 03, 2014 at 03:25:16PM -0700, eric.er...@linux.intel.com wrote:
> From: Eric Ernst
>
> For Baytrail, you should never set a GPIO set to direct_irq
> to output mode. When direct_irq_en is set for a GPIO, it is
> tied directly to an APIC internally, and making the pad output
> does
On Tue, Jun 03, 2014 at 03:25:16PM -0700, eric.er...@linux.intel.com wrote:
From: Eric Ernst eric.er...@linux.intel.com
For Baytrail, you should never set a GPIO set to direct_irq
to output mode. When direct_irq_en is set for a GPIO, it is
tied directly to an APIC internally, and making the
From: Eric Ernst
For Baytrail, you should never set a GPIO set to direct_irq
to output mode. When direct_irq_en is set for a GPIO, it is
tied directly to an APIC internally, and making the pad output
does not make any sense. Assert a WARN() in the event this happens.
Signed-off-by: Eric Ernst
From: Eric Ernst eric.er...@linux.intel.com
For Baytrail, you should never set a GPIO set to direct_irq
to output mode. When direct_irq_en is set for a GPIO, it is
tied directly to an APIC internally, and making the pad output
does not make any sense. Assert a WARN() in the event this happens.
6 matches
Mail list logo