All of lore.kernel.org
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 3/3] ARM: mvebu: use arm_coherent_dma_ops and re-enable hardware I/O coherency
Date: Fri, 16 Jan 2015 17:15:48 +0100	[thread overview]
Message-ID: <20150116161548.GD17658@lunn.ch> (raw)
In-Reply-To: <1421424689-5971-4-git-send-email-thomas.petazzoni@free-electrons.com>

Hi Thomas

In patch 1/3 you add a comment here saying why you have turned it off.
This hunk turns it back on again. But i don't see the comment being
removed?

Thanks
	Andrew

> @@ -253,7 +206,7 @@ static int coherency_type(void)
>   */
>  int coherency_available(void)
>  {
> -	return false;
> +	return coherency_type() != COHERENCY_FABRIC_TYPE_NONE;
>  }
>  
>  int __init coherency_init(void)
> -- 
> 2.1.0
> 

  reply	other threads:[~2015-01-16 16:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 16:11 [PATCHv2 0/3] ARM: mvebu: I/O coherency related fixes Thomas Petazzoni
2015-01-16 16:11 ` [PATCHv2 1/3] ARM: mvebu: completely disable hardware I/O coherency Thomas Petazzoni
2015-01-16 16:11 ` [PATCHv2 2/3] bus: mvebu-mbus: use automatic I/O synchronization barriers Thomas Petazzoni
2015-04-17 10:45   ` Nicolas Schichan
2015-04-17 11:23     ` Thomas Petazzoni
2015-04-24 14:44       ` [RFC PATCH] bus: mvebu-mbus: do not set WIN_CTRL_SYNCBARRIER on non io-coherent platforms Nicolas Schichan
2015-04-24 14:54         ` Thomas Petazzoni
2015-04-24 15:12       ` [PATCH] " Nicolas Schichan
2015-05-28 19:43     ` [PATCHv2 2/3] bus: mvebu-mbus: use automatic I/O synchronization barriers Aaro Koskinen
2015-05-28 19:57       ` Thomas Petazzoni
2015-01-16 16:11 ` [PATCHv2 3/3] ARM: mvebu: use arm_coherent_dma_ops and re-enable hardware I/O coherency Thomas Petazzoni
2015-01-16 16:15   ` Andrew Lunn [this message]
2015-01-16 16:20     ` Thomas Petazzoni
2015-01-19 22:36 ` [PATCHv2 0/3] ARM: mvebu: I/O coherency related fixes Andrew Lunn
2015-01-20 15:22   ` Thomas Petazzoni

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=20150116161548.GD17658@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.