From: maxime.coquelin@st.com (Maxime Coquelin)
To: linux-arm-kernel@lists.infradead.org
Subject: [STLinux Kernel] [PATCH 1/3] media: st-rc: move to using reset_control_get_optional
Date: Wed, 24 Sep 2014 10:37:55 +0200 [thread overview]
Message-ID: <542282E3.8080102@st.com> (raw)
In-Reply-To: <54227CD2.5020705@linaro.org>
Hi Srini, Peter,
On 09/24/2014 10:12 AM, Srinivas Kandagatla wrote:
> Hi Pete,
>
> On 23/09/14 19:02, Peter Griffin wrote:
>> Hi Srini,
>>
>> On Mon, 22 Sep 2014, Srinivas Kandagatla wrote:
>>
>>> This patch fixes a compilation error while building with the
>>> random kernel configuration.
>>>
>>> drivers/media/rc/st_rc.c: In function 'st_rc_probe':
>>> drivers/media/rc/st_rc.c:281:2: error: implicit declaration of
>>> function 'reset_control_get' [-Werror=implicit-function-declaration]
>>> rc_dev->rstc = reset_control_get(dev, NULL);
>>>
>>> drivers/media/rc/st_rc.c:281:15: warning: assignment makes pointer
>>> from integer without a cast [enabled by default]
>>> rc_dev->rstc = reset_control_get(dev, NULL);
>>
>> Is managing the reset line actually optional though? I can't test atm
>> as I don't have
>> access to my board, but quite often if the IP's aren't taken out of
>> reset reads / writes
>> to the perhpiheral will hang the SoC.
>>
> Yes and No.
> AFAIK reset line is optional on SOCs like 7108, 7141.
> I think having the driver function without reset might is a value add in
> case we plan to reuse the mainline driver for these SOCs.
>
> On latest ARM SOCs with SBC the IRB IP is moved to SBC and held in reset.
> Am not sure, if the reset line is optional in next generation SOCs?
I don't know for next SoCs, but I think it makes sense to make it optional.
Regards,
Maxime
>
>> If managing the reset line isn't optional then I think the correct fix
>> is to add
>> depends on RESET_CONTROLLER in the kconfig.
> I agree.
> This would make the COMPILE_TEST less useful though.
>
>
> thanks,
> srini
>>
>> This will then do the right thing for randconfig builds as well.
>>
>> regards,
>>
>> Peter.
>>
>
> _______________________________________________
> Kernel mailing list
> Kernel at stlinux.com
> http://www.stlinux.com/mailman/listinfo/kernel
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Coquelin <maxime.coquelin@st.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Peter Griffin <peter.griffin@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<kernel@stlinux.com>, <linux-arm-kernel@lists.infradead.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: [STLinux Kernel] [PATCH 1/3] media: st-rc: move to using reset_control_get_optional
Date: Wed, 24 Sep 2014 10:37:55 +0200 [thread overview]
Message-ID: <542282E3.8080102@st.com> (raw)
In-Reply-To: <54227CD2.5020705@linaro.org>
Hi Srini, Peter,
On 09/24/2014 10:12 AM, Srinivas Kandagatla wrote:
> Hi Pete,
>
> On 23/09/14 19:02, Peter Griffin wrote:
>> Hi Srini,
>>
>> On Mon, 22 Sep 2014, Srinivas Kandagatla wrote:
>>
>>> This patch fixes a compilation error while building with the
>>> random kernel configuration.
>>>
>>> drivers/media/rc/st_rc.c: In function 'st_rc_probe':
>>> drivers/media/rc/st_rc.c:281:2: error: implicit declaration of
>>> function 'reset_control_get' [-Werror=implicit-function-declaration]
>>> rc_dev->rstc = reset_control_get(dev, NULL);
>>>
>>> drivers/media/rc/st_rc.c:281:15: warning: assignment makes pointer
>>> from integer without a cast [enabled by default]
>>> rc_dev->rstc = reset_control_get(dev, NULL);
>>
>> Is managing the reset line actually optional though? I can't test atm
>> as I don't have
>> access to my board, but quite often if the IP's aren't taken out of
>> reset reads / writes
>> to the perhpiheral will hang the SoC.
>>
> Yes and No.
> AFAIK reset line is optional on SOCs like 7108, 7141.
> I think having the driver function without reset might is a value add in
> case we plan to reuse the mainline driver for these SOCs.
>
> On latest ARM SOCs with SBC the IRB IP is moved to SBC and held in reset.
> Am not sure, if the reset line is optional in next generation SOCs?
I don't know for next SoCs, but I think it makes sense to make it optional.
Regards,
Maxime
>
>> If managing the reset line isn't optional then I think the correct fix
>> is to add
>> depends on RESET_CONTROLLER in the kconfig.
> I agree.
> This would make the COMPILE_TEST less useful though.
>
>
> thanks,
> srini
>>
>> This will then do the right thing for randconfig builds as well.
>>
>> regards,
>>
>> Peter.
>>
>
> _______________________________________________
> Kernel mailing list
> Kernel@stlinux.com
> http://www.stlinux.com/mailman/listinfo/kernel
next prev parent reply other threads:[~2014-09-24 8:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 22:21 [PATCH 0/3] media:st-rc: Misc fixes Srinivas Kandagatla
2014-09-22 22:21 ` Srinivas Kandagatla
2014-09-22 22:22 ` [PATCH 1/3] media: st-rc: move to using reset_control_get_optional Srinivas Kandagatla
2014-09-22 22:22 ` Srinivas Kandagatla
2014-09-23 18:02 ` [STLinux Kernel] " Peter Griffin
2014-09-23 18:02 ` Peter Griffin
2014-09-24 8:12 ` Srinivas Kandagatla
2014-09-24 8:12 ` Srinivas Kandagatla
2014-09-24 8:37 ` Maxime Coquelin [this message]
2014-09-24 8:37 ` Maxime Coquelin
2014-10-24 8:11 ` Peter Griffin
2014-10-24 8:11 ` Peter Griffin
2014-09-22 22:22 ` [PATCH 2/3] media: st-rc: move pm ops setup out of conditional compilation Srinivas Kandagatla
2014-09-22 22:22 ` Srinivas Kandagatla
2014-09-22 22:22 ` [PATCH 3/3] media: st-rc: Remove .owner field for driver Srinivas Kandagatla
2014-09-22 22:22 ` Srinivas Kandagatla
2014-09-23 18:05 ` [STLinux Kernel] " Peter Griffin
2014-09-23 18:05 ` Peter Griffin
2014-09-22 22:39 ` [PATCH 0/3] media:st-rc: Misc fixes Mauro Carvalho Chehab
2014-09-22 22:39 ` Mauro Carvalho Chehab
2014-09-23 7:27 ` Maxime Coquelin
2014-09-23 7:27 ` Maxime Coquelin
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=542282E3.8080102@st.com \
--to=maxime.coquelin@st.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.