public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Loc Ho <lho@apm.com>
Cc: devicetree@vger.kernel.org, Suman Tripathi <stripathi@apm.com>,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	Jon Masters <jcm@redhat.com>,
	Kishon Vijay Abraham I <kishon@ti.com>, Tejun Heo <tj@kernel.org>,
	Olof Johansson <olof@lixom.net>, Tuan Phan <tphan@apm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 3/4] ata: Add APM X-Gene SoC SATA host controller driver
Date: Thu, 21 Nov 2013 14:20:28 +0100	[thread overview]
Message-ID: <201311211420.28509.arnd@arndb.de> (raw)
In-Reply-To: <CAPw-ZTmaz3nnV3ThRgecT_RaYYW0bmfWvL8Kr-S3z1aKyUWc+w@mail.gmail.com>

On Saturday 16 November 2013, Loc Ho wrote:


> >
> > config SATA_XGENE
> >         tristate "APM X-Gene 6.0Gbps SATA host controller support"
> >         depends on ARM64 || COMPILE_TEST
> >         ...
> >
> [Loc Ho]
> Okay. How about this?
> 
>  depends on ARM64 || COMPILE_TEST
>  select SATA_XGENE_PHY && SATA_AHCI_PLATFORM

I think you already found the mistake withis and corrected this in v4.

> > The interface you are looking for is pr_debug() or dev_dbg(), which get
> > built-in only if the DEBUG macro is set.
> >
> > In a lot of cases, it's actually best to remove debug output like this from
> > the driver once you have it working  -- whoever is debugging problems in
> > the driver next might need completely different debugging information or
> > can add them back easily if needed.
> >
> > It's your choice if you want to use pr_debug() or remove that output
> > entirely. If you remove it, best remove the helper functions entirely
> > and use readl/writel directly.
> [Loc Ho]
> I would like to keep this function for now until this driver actual
> being used in production. I will use pr_debug.

Ok.

> >> diff --git a/drivers/ata/sata_xgene.h b/drivers/ata/sata_xgene.h
> >> new file mode 100644
> >> index 0000000..51e73f6
> >> --- /dev/null
> >> +++ b/drivers/ata/sata_xgene.h
> >
> > This file should probably just be folded into the driver, since it contains no
> > interfaces between  modules, just internal definitions.
> [Loc Ho]
> I can get rip this header file now. But in the future I may need to
> add this back as I intended this driver to also support running from
> our co-processor (ARMv7 32-bit). For that, I will need anothe file and
> other function that will need knowledge of the context structure and
> etc.

Hmm, is the code for that coprocessor compiled from the kernel source?
If not, it shouldn't really make a difference as it won't live in a shared
code repository.

	Arnd

  parent reply	other threads:[~2013-11-21 13:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-14 21:39 [PATCH v3 0/4] ata: Add APM X-Gene SoC SATA host controller support Loc Ho
2013-11-14 21:39 ` [PATCH v3 1/4] ata: Export required functions by APM X-Gene SATA driver Loc Ho
2013-11-14 21:39   ` [PATCH v3 2/4] Documentation: Add documentation for APM X-Gene SATA controllor DTS binding Loc Ho
2013-11-14 21:39     ` [PATCH v3 3/4] ata: Add APM X-Gene SoC SATA host controller driver Loc Ho
2013-11-14 21:39       ` [PATCH v4 4/4] arm64: Add APM X-Gene SoC SATA DTS entries Loc Ho
2013-11-15 13:48       ` [PATCH v3 3/4] ata: Add APM X-Gene SoC SATA host controller driver Arnd Bergmann
2013-11-16  6:36         ` Loc Ho
2013-11-19 21:22           ` Loc Ho
2013-11-26 10:11             ` Kishon Vijay Abraham I
2013-11-26 16:41               ` Loc Ho
2013-11-27  5:52                 ` Kishon Vijay Abraham I
2013-11-27  5:58                   ` Loc Ho
2013-11-21 13:20           ` Arnd Bergmann [this message]
2013-11-21 19:01             ` Loc Ho
2013-11-15 13:28     ` [PATCH v3 2/4] Documentation: Add documentation for APM X-Gene SATA controllor DTS binding Arnd Bergmann

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=201311211420.28509.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=jcm@redhat.com \
    --cc=kishon@ti.com \
    --cc=lho@apm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=stripathi@apm.com \
    --cc=tj@kernel.org \
    --cc=tphan@apm.com \
    /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