public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL 2/3] ARM: tegra: move fuse code out of arch/arm
Date: Mon, 21 Jul 2014 09:06:00 -0600	[thread overview]
Message-ID: <53CD2C58.6060601@wwwdotorg.org> (raw)
In-Reply-To: <CAOesGMh+zLV781wzdR5=_Bpzh+XMwJfWL-5XMDP6DwG_Hg80kw@mail.gmail.com>

On 07/17/2014 11:33 PM, Olof Johansson wrote:
> On Thu, Jul 17, 2014 at 7:45 PM, Stephen Warren <swarren@wwwdotorg•org> wrote:
>> On 07/08/2014 11:47 AM, Olof Johansson wrote:
>>> On Tue, Jul 8, 2014 at 6:43 AM, Peter De Schrijver
>>> <pdeschrijver@nvidia•com> wrote:
>>>> On Mon, Jul 07, 2014 at 02:44:17AM +0200, Olof Johansson wrote:
>>>>> On Mon, Jun 23, 2014 at 03:23:45PM -0600, Stephen Warren wrote:
>>>>>> This branch moves code related to the Tegra fuses out of arch/arm and
>>>>>> into a centralized location which could be shared with ARM64. It also
>>>>>> adds support for reading the fuse data through sysfs.
>>>>>
>>>>> The new/moved misc driver isn't acked by any misc maintainer, so I can't
>>>>> take this branch.
>>>>>
>>>>> I saw no indication from searching the mailing list of that either,
>>>>> so it wasn't just a missed acked-by.
>>>>>
>>>>> I wonder if this code should go under drivers/soc/ instead?
>>>>
>>>> It's modelled after sunxi_sid.c which lives in drivers/misc/eeprom/.
>>>> Originally this driver was also in drivers/misc/eeprom/, but Stephen objected
>>>> and therefore it was moved to drivers/misc/fuse. I think that's the right
>>>> place still.
>>>
>>> I disagree, I think this belongs under drivers/soc. Especially since
>>> you're adding dependencies on this misc driver from other parts of the
>>> kernel / other drivers.
>>>
>>> I also don't like seeing init calls form platform code down into
>>> drivers/misc like you're adding here. Can you please look at doing
>>> that as a regular init call setup?
>>
>> I strongly disagree with using init calls for this kind of thing. There
>> are ordering dependencies between the initialization code that can only
>> be sanely managed by explicitly calling functions in a particular order;
>> there's simply no way to manage this using initcalls. This is exactly
>> why the hooks in the ARM machine descriptors exist...
> 
> Right, but there are non on 64-bit, so you need to solve it for there
> anyway. And once it's solved there, you might as well keep it common
> with 32-bit.

My assertion is that we should just do it directly on 64-bit too.
There's no reason for arm64 to deviate from what arch/arm does already.

  reply	other threads:[~2014-07-21 15:06 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23 21:23 [GIT PULL 1/3] ARM: tegra: rework PCIe regulators Stephen Warren
2014-06-23 21:23 ` [GIT PULL 2/3] ARM: tegra: move fuse code out of arch/arm Stephen Warren
2014-07-07  0:44   ` Olof Johansson
2014-07-08 13:43     ` Peter De Schrijver
2014-07-08 17:47       ` Olof Johansson
2014-07-09 11:16         ` Peter De Schrijver
2014-07-09 12:50           ` Arnd Bergmann
2014-07-11 12:56         ` Thierry Reding
2014-07-18  2:45         ` Stephen Warren
2014-07-18  5:33           ` Olof Johansson
2014-07-21 15:06             ` Stephen Warren [this message]
2014-07-21 15:54               ` Catalin Marinas
2014-07-21 16:14                 ` Pawel Moll
2014-07-21 16:38                 ` Stephen Warren
2014-07-21 16:46                   ` Olof Johansson
2014-07-21 17:00                     ` [PATCH] platform: Make platform_bus device a platform device Pawel Moll
2014-07-21 18:40                       ` Greg Kroah-Hartman
2014-07-22 10:02                         ` [PATCH v2] " Pawel Moll
2014-07-22 17:10                           ` Greg Kroah-Hartman
2014-07-22 17:30                             ` Pawel Moll
2014-07-22 17:37                               ` Greg Kroah-Hartman
2014-07-22 17:55                                 ` [PATCH v3] " Pawel Moll
2014-07-22 18:01                                   ` Pawel Moll
2014-07-22 18:15                                     ` Greg Kroah-Hartman
2014-07-23 17:16                                       ` Pawel Moll
2014-07-23 19:34                                         ` Greg Kroah-Hartman
2014-07-24 17:12                                           ` Pawel Moll
2014-07-22 19:46                                   ` Olof Johansson
2014-07-23 14:26                                     ` Pawel Moll
2014-07-22 22:16                                   ` Greg Kroah-Hartman
2014-07-23 14:27                                     ` Pawel Moll
2014-07-22 10:27                     ` [GIT PULL 2/3] ARM: tegra: move fuse code out of arch/arm Catalin Marinas
2014-07-22 16:27                       ` Stephen Warren
2014-07-22 16:54                         ` Catalin Marinas
2014-07-22 11:26                   ` Catalin Marinas
2014-07-22 16:22                     ` Stephen Warren
2014-07-22 17:04                       ` Catalin Marinas
2014-07-18  2:44       ` Stephen Warren
2014-07-18  5:33         ` Olof Johansson
2014-06-23 21:23 ` [GIT PULL 3/3] ARM: tegra: use us counter as delay timer Stephen Warren
2014-07-07  0:49   ` Olof Johansson
2014-07-07  0:38 ` [GIT PULL 1/3] ARM: tegra: rework PCIe regulators Olof Johansson
2014-07-07  5:52   ` Thierry Reding
2014-07-08  4:45     ` Olof Johansson
2014-07-10 10:15       ` Thierry Reding
2014-07-17 14:20         ` Thierry Reding
2014-07-17 17:52           ` Olof Johansson
2014-07-18  2:47   ` Stephen Warren

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=53CD2C58.6060601@wwwdotorg.org \
    --to=swarren@wwwdotorg$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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