linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Mahoney <jeffm@suse.com>
To: Antti Palosaari <crope@iki.fi>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH] Kconfig: do not select SPI bus on sub-driver auto-select
Date: Fri, 22 Aug 2014 13:04:53 -0400	[thread overview]
Message-ID: <53F77835.7050406@suse.com> (raw)
In-Reply-To: <1408726929-3924-1-git-send-email-crope@iki.fi>

On Fri Aug 22 13:02:09 2014, Antti Palosaari wrote:
> We should not select SPI bus when sub-driver auto-select is
> selected. That option is meant for auto-selecting all possible
> ancillary drivers used for selected board driver. Ancillary
> drivers should define needed dependencies itself.
>
> I2C and I2C_MUX are still selected here for a reason described on
> commit 347f7a3763601d7b466898d1f10080b7083ac4a3
>
> Reverts commit e4462ffc1602d9df21c00a0381dca9080474e27a
>
> Reported-by: Jeff Mahoney <jeffm@suse.com>
> Signed-off-by: Antti Palosaari <crope@iki.fi>
> ---
>  drivers/media/Kconfig | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/drivers/media/Kconfig b/drivers/media/Kconfig
> index f60bad4..3c89fcb 100644
> --- a/drivers/media/Kconfig
> +++ b/drivers/media/Kconfig
> @@ -182,7 +182,6 @@ config MEDIA_SUBDRV_AUTOSELECT
>  	depends on HAS_IOMEM
>  	select I2C
>  	select I2C_MUX
> -	select SPI
>  	default y
>  	help
>  	  By default, a media driver auto-selects all possible ancillary

FWIW, in the patch I used locally, I also did a 'select SPI' in the 
MSI2500 driver since it wouldn't otherwise be obvious that a USB device 
depends on SPI.

-Jeff

--
Jeff Mahoney
SUSE Labs

  reply	other threads:[~2014-08-22 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 17:02 [PATCH] Kconfig: do not select SPI bus on sub-driver auto-select Antti Palosaari
2014-08-22 17:04 ` Jeff Mahoney [this message]
2014-08-22 23:34   ` Randy Dunlap
2014-08-23  0:06     ` Jeff Mahoney

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=53F77835.7050406@suse.com \
    --to=jeffm@suse.com \
    --cc=crope@iki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.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).