Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] MIPS: BCM47XX: Move NVRAM driver to the drivers/misc/
Date: Wed, 12 Nov 2014 10:43:39 +0100	[thread overview]
Message-ID: <15071020.3LPpWWN4p1@wuerfel> (raw)
In-Reply-To: <1415735146-31552-1-git-send-email-zajec5@gmail.com>

On Tuesday 11 November 2014 20:45:46 Rafał Miłecki wrote:
> After Broadcom switched from MIPS to ARM for their home routers we need
> to have NVRAM driver in some common place (not arch/mips/).
> We were thinking about putting it in bus directory, however there are
> two possible buses for MIPS: drivers/ssb/ and drivers/bcma/. So this
> won't fit there neither.
> This is why I would like to move this driver to the drivers/misc/
> 
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> 

I think drivers/soc would be more appropriate, as this is a purely
in-kernel interface, and it interacts with other drivers, while
drivers/misc is generally for oddball devices that don't fit in
elsewhere and have their own user interface.

I don't remember if what we had concluded on the previous discussion.
I think I suggested converting the nvram variables into DT properties
on ARM. The API certainly feels obscure, so it would be nice to
keep it out of the modern port if we can come up with a better alternative
to pass the same information.

	Arnd

  parent reply	other threads:[~2014-11-12  9:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 19:45 [PATCH] MIPS: BCM47XX: Move NVRAM driver to the drivers/misc/ Rafał Miłecki
2014-11-12  9:34 ` Zubair Lutfullah Kakakhel
2014-11-12  9:43 ` Arnd Bergmann [this message]
2014-11-12 21:09   ` Hauke Mehrtens
2014-11-12 21:16 ` Hauke Mehrtens
2014-11-23  9:45   ` Rafał Miłecki
2014-11-23 11:22     ` Hauke Mehrtens

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=15071020.3LPpWWN4p1@wuerfel \
    --to=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hauke@hauke-m.de \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=zajec5@gmail.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