From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] coresight: Adding coresight support for arm64 architecture
Date: Tue, 3 Feb 2015 20:28:42 +0000 [thread overview]
Message-ID: <20150203202842.GZ8656@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1422990133-26342-1-git-send-email-mathieu.poirier@linaro.org>
On Tue, Feb 03, 2015 at 12:02:13PM -0700, mathieu.poirier at linaro.org wrote:
> diff --git a/drivers/coresight/Kconfig b/drivers/coresight/Kconfig
> new file mode 100644
> index 000000000000..271fad830ae4
> --- /dev/null
> +++ b/drivers/coresight/Kconfig
> @@ -0,0 +1,60 @@
> +#
> +# Coresight configuration
> +#
> +menuconfig CORESIGHT
> + bool "CoreSight Tracing Support"
> + select ARM_AMBA
> + help
> + This framework provides a kernel interface for the CoreSight debug
> + and trace drivers to register themselves with. It's intended to build
> + a topological view of the CoreSight components based on a DT
> + specification and configure the right serie of components when a
> + trace source gets enabled.
> +
You could surround the following options with
if CORESIGHT
...
endif
which will implicitly make anything between depend on CORESIGHT instead of
having to specify it every time.
> diff --git a/drivers/coresight/coresight-etb10.c b/drivers/coresight/coresight-etb10.c
> index c9acd406f0d0..aa47d31fe2a2 100644
> --- a/drivers/coresight/coresight-etb10.c
> +++ b/drivers/coresight/coresight-etb10.c
> @@ -314,7 +314,7 @@ static ssize_t etb_read(struct file *file, char __user *data,
> *ppos += len;
>
> dev_dbg(drvdata->dev, "%s: %d bytes copied, %d bytes left\n",
> - __func__, len, (int) (depth * 4 - *ppos));
> + __func__, (int)len, (int)(depth * 4 - *ppos));
Please use %zu for size_t types.
> return len;
> }
>
> diff --git a/drivers/coresight/coresight-tmc.c b/drivers/coresight/coresight-tmc.c
> index 3ff232f9ddf7..d08460327bd2 100644
> --- a/drivers/coresight/coresight-tmc.c
> +++ b/drivers/coresight/coresight-tmc.c
> @@ -534,7 +534,7 @@ static ssize_t tmc_read(struct file *file, char __user *data, size_t len,
> *ppos += len;
>
> dev_dbg(drvdata->dev, "%s: %d bytes copied, %d bytes left\n",
> - __func__, len, (int) (drvdata->size - *ppos));
> + __func__, (int)len, (int)(drvdata->size - *ppos));
Ditto.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2015-02-03 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 19:02 [PATCH] coresight: Adding coresight support for arm64 architecture mathieu.poirier at linaro.org
2015-02-03 20:28 ` Russell King - ARM Linux [this message]
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=20150203202842.GZ8656@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).